# CVE-2025-27593: RCE due to Device Driver

> Attackers can execute arbitrary code on SICK DL100 sensors by distributing malicious device drivers due to missing download verification.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **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:** 14 Mar 2025
- **Updated:** 14 Mar 2025
- **Also known as:** GHSA-jqv5-4r34-g3x7

## What is CVE-2025-27593?

CVE-2025-27593 is a critical code injection vulnerability in SICK DL100-2xxxxxxx, published on 14 Mar 2025. 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

The product can be used to distribute malicious code using SDD Device Drivers due to missing download verification checks, leading to code execution on target systems.

Weakness: CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2025-27593?


## How do I fix CVE-2025-27593?

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

## Is CVE-2025-27593 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27593 and fix it if it is affected.

What it is: CVE-2025-27593 is a critical code injection vulnerability in SICK DL100-2xxxxxxx, published on 14 Mar 2025. 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-2025-27593 in the wild and no public exploit code.

Affected product: SICK DL100-2xxxxxxx. 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-2025-27593/ (Markdown: https://insights.sbomify.com/CVE-2025-27593/index.md)
```

## Sources

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

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