# CVE-2025-1127: Combination Path Traversal and Concurrent Execution vulnerability exists within the embedded web server

> Attackers can exploit path traversal and race conditions in the embedded web server to execute arbitrary code or modify filesystem data.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2025
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-2qmv-6vxr-xhwg

## What is CVE-2025-1127?

CVE-2025-1127 is a critical path traversal vulnerability in Lexmark CX, XC, CS, MS, MX, XM, et. al., published on 13 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The vulnerability can be leveraged by an attacker to execute arbitrary code as an unprivileged user and/or modify the contents of any data on the filesystem.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2025-1127 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1127 is a critical path traversal vulnerability in Lexmark CX, XC, CS, MS, MX, XM, et. al., published on 13 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1127 in the wild and no public exploit code.

Affected product: Lexmark CX, XC, CS, MS, MX, XM, et. al.. 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-1127/ (Markdown: https://insights.sbomify.com/CVE-2025-1127/index.md)
```

## Sources

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

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