# CVE-2026-2331: CVE-2026-2331

> Unauthenticated attackers can read and modify sensitive files and execute arbitrary Lua code via exposed HTTP file access on SICK scanners.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-cvvv-49vh-384q

## What is CVE-2026-2331?

CVE-2026-2331 is a critical missing authorization vulnerability in SICK Lector83x, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An attacker may perform unauthenticated read and write operations on sensitive filesystem areas via the AppEngine Fileaccess over HTTP due to improper access restrictions. A critical filesystem directory was unintentionally exposed through the HTTP-based file access feature, allowing access without authentication. This includes device parameter files, enabling an attacker to read and modify application settings, including customer-defined passwords. Additionally, exposure of the custom application directory may allow execution of arbitrary Lua code within the sandboxed AppEngine environment.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2026-2331?


## How do I fix CVE-2026-2331?

No fix has been published for CVE-2026-2331 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2331 being exploited?

There is no known exploitation of CVE-2026-2331 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2331 and fix it if it is affected.

What it is: CVE-2026-2331 is a critical missing authorization vulnerability in SICK Lector83x, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2331 in the wild and no public exploit code.

Affected product: SICK Lector83x. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2331/ (Markdown: https://insights.sbomify.com/CVE-2026-2331/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2331
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2331
- OSV: https://osv.dev/vulnerability/CVE-2026-2331

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2331/
Summaries are generated and may contain mistakes; the official description above is the record.