# CVE-2026-80469: CVE-2026-80469

> Attackers can execute arbitrary code by uploading malicious device driver packages that bypass verification, requiring user interaction.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-qpmw-pvq9-j6gq

## What is CVE-2026-80469?

CVE-2026-80469 is a high-severity code injection vulnerability in SICK AG Sentio Creator Extension 'Device Manager', published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An attacker may achieve arbitrary code execution on a target system by uploading a malicious device driver package, bypassing driver verification mechanisms, and triggering the execution of
attacker-controlled code. User interaction is required.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

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

## Is CVE-2026-80469 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80469 is a high-severity code injection vulnerability in SICK AG Sentio Creator Extension 'Device Manager', published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-80469 in the wild and no public exploit code.

Affected product: SICK AG Sentio Creator Extension 'Device Manager'. 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-80469/ (Markdown: https://insights.sbomify.com/CVE-2026-80469/index.md)
```

## Sources

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

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