# CVE-2025-9269: Server-Side Request Forgery (SSRF) vulnerability found in embedded web server

> Attackers can force Lexmark printers to send arbitrary HTTP requests, enabling internal network access and potential data disclosure.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 29 Sep 2025
- **Also known as:** GHSA-57w5-cgmj-2fr4

## What is CVE-2025-9269?

CVE-2025-9269 is a medium-severity server-side request forgery vulnerability in Lexmark CX, XC, CS, MS, MX, XM, et. al., published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Server-Side Request Forgery (SSRF) vulnerability has been identified in the embedded web server in various Lexmark devices. This vulnerability can be leveraged by an attacker to force the device to send an arbitrary HTTP request to a third-party server. Successful exploitation of this vulnerability can lead to internal network access / potential data disclosure from a device.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2025-9269 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9269 is a medium-severity server-side request forgery vulnerability in Lexmark CX, XC, CS, MS, MX, XM, et. al., published on 9 Sep 2025. 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-2025-9269 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-9269/ (Markdown: https://insights.sbomify.com/CVE-2025-9269/index.md)
```

## Sources

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

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