+44 1865 950 828 Secure Your Business
Actively exploited

CVE-2024-9537 ScienceLogic SL1 Unspecified Vulnerability

ScienceLogic SL1 (formerly EM7) is affected by an unspecified vulnerability involving an unspecified third-party component.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch nowCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 21 Oct 2024.
  • Rated Critical severity (CVSS 9.8, scored by Vendor).
  • It has been in the catalogue for 746 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

ScienceLogic SL1 (formerly EM7) is affected by an unspecified vulnerability involving an unspecified third-party component packaged with SL1. The vulnerability is addressed in SL1 versions 12.1.3+, 12.2.3+, and 12.3+. Remediations have been made available for all SL1 versions back to version lines 10.1.x, 10.2.x, 11.1.x, 11.2.x, and 11.3.x.

Affected Versions

ProductVersions
ScienceLogic SL1before 12.1.3
before 12.2.3
before 12.3
before 10.1.x
before 10.2.x
before 11.1.x

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for ScienceLogic SL1. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Vendor Advisories

Regulation

The Compliance Clock

Cyber EssentialsRated critical, so if it affects devices in your Cyber Essentials scope, the update must be installed within 14 days of the vendor releasing it.NIS2If exploitation causes a significant incident, essential and important entities owe their CSIRT an early warning within 24 hours and a notification within 72 hours.DORAFinancial entities must classify ICT incidents and send an initial notification for a major incident within strict deadlines, with exploited flaws a common cause.US federal (BOD 22-01)Federal civilian agencies had until 11 Nov 2024 to remediate. A sensible benchmark for everyone else.

General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.

Stay Ahead

More Exploited ScienceLogic Flaws

Get alerts for ScienceLogicWe email you when a new ScienceLogic vulnerability is confirmed as exploited. Add more vendors on Threat Watch.

By signing up you agree to receive Threat Watch alerts. Unsubscribe at any time. See our Privacy Policy.

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2024-9537 and every other exploited flaw on the list.

Check My Exposure
Evidence

Sources

  1. CISA Known Exploited Vulnerabilities catalogue
  2. NVD: CVE-2024-9537
  3. CVE record: CVE-2024-9537
  4. FIRST EPSS
  5. support.sciencelogic.com/s/article/15527
  6. rackspace.service-now.com/system_status?id=detailed_status&service=4dafca5a87f41610568b206f8bbb35a6
  7. twitter.com/ynezzor/status/1839931641172467907
  8. theregister.com/2024/09/30/rackspace_zero_day_attack/
  9. arcticwolf.com/resources/blog/rackspace-breach-linked-to-zero-day-vulnerability-sciencelogic-sl1s-th
  10. bleepingcomputer.com/news/security/rackspace-monitoring-data-stolen-in-sciencelogic-zero-day-attack/
  11. support.sciencelogic.com/s/article/15465
  12. community.sciencelogic.com/blog/latest-kb-articles-and-known-issues-blog-board/week-of-september-30-