Skip to main content
VulnerabilityPublished Updated

CVE-2026-2330: SICK Lector85x · Exposed Files or Directories

Affects SICK Lector85xSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.4 Critical.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
SICK AGSICK Lector85xAffected
  • <2.8.0
Fixed in–
SICK AGSICK Lector83xAffected
  • <2.8.0
Fixed in–

AI-suggested

Until an official patch is released by SICK AG, organizations should implement strict network segmentation to isolate Lector85x devices from untrusted networks and restrict access to the CROWN REST interface using firewalls or access control lists. Monitoring network traffic for unusual access attempts to the REST interface can help detect exploitation attempts. Device reboots should be controlled and monitored to prevent activation of malicious parameter files. Where possible, disable or restrict access to internal testing directories and audit device configurations regularly. Employ intrusion detection systems tailored for industrial control systems to identify anomalous behavior. Engage with SICK AG for updates on patches or firmware upgrades and plan for immediate deployment once available. Additionally, consider implementing multi-factor authentication or VPN access for management interfaces if supported, to add an additional layer of protection.

Description

An attacker may access restricted filesystem areas on the device via the CROWN REST interface due to incomplete whitelist enforcement. Certain directories intended for internal testing were not covered by the whitelist and are accessible without authentication. An unauthenticated attacker could place a manipulated parameter file that becomes active after a reboot, allowing modification of critical device settings, including network configuration and application parameters.

References

Community reviews

Loading reviews…