Unauthenticated file access via exposed HTTP directory
Published Mar 6, 2026 · Updated Mar 6, 2026
Improper access control in SICK Lector83x and Lector85x firmware 2.6.0 through 2.7.0 allows remote attackers to read and write device files. AppEngine Fileaccess over HTTP exposes a critical filesystem directory without authentication, including device parameters and the custom application directory. Any network client that reaches the HTTP interface can alter settings and customer-defined passwords or place Lua code that executes inside the AppEngine sandbox.
Summary
What happened
Improper access control in SICK Lector83x and Lector85x firmware 2.6.0 through 2.7.0 allows remote attackers to read and write device files. AppEngine Fileaccess over HTTP exposes a critical filesystem directory without authentication, including device parameters and the custom application directory. Any network client that reaches the HTTP interface can alter settings and customer-defined passwords or place Lua code that executes inside the AppEngine sandbox.
The record
- CVE
- CVE-2026-2331
- Published
- Mar 6, 2026
- Updated
- Mar 6, 2026
- Vendor
- SICK AG
- Product
- Lector85x
- Classifications
- CWE-552, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 6, 2026CVE publishedPublication date reported by the CVE source.
- Mar 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.0 <=2.7.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo