# CVE-2023-26069: Other in n/a

> Lexmark devices mishandle input validation, potentially allowing attackers to exploit unspecified weaknesses in device processing.

- **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:** 10 Apr 2023
- **Updated:** 11 Feb 2025
- **Also known as:** GHSA-gcx9-562f-5mwm

## What is CVE-2023-26069?

CVE-2023-26069 is a critical vulnerability in n/a, published on 10 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain Lexmark devices through 2023-02-19 mishandle Input Validation (issue 3 of 4).

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2023-26069?

It affects 26 products.


Products: Lexmark Cslbl Firmware, Lexmark Cslbn Firmware, Lexmark Csnzj Firmware, Lexmark Cstat Firmware, Lexmark Cstmh Firmware, Lexmark Cstpc Firmware, Lexmark Cxlbl Firmware, Lexmark Cxlbn Firmware, Lexmark Cxnzj Firmware, Lexmark Cxtat Firmware, Lexmark Cxtmm Firmware, Lexmark Cxtpc Firmware, Lexmark Cxtpp Firmware, Lexmark Cxtzj Firmware, Lexmark Mslbd Firmware, Lexmark Mslsg Firmware, Lexmark Msngm Firmware, Lexmark Msngw Firmware, Lexmark Mstgw Firmware, Lexmark Mxlbd Firmware and 6 more.

## How do I fix CVE-2023-26069?

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

## Is CVE-2023-26069 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-26063](https://insights.sbomify.com/CVE-2023-26063/): Other in n/a (critical 9.8)
- [CVE-2023-26064](https://insights.sbomify.com/CVE-2023-26064/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-26065](https://insights.sbomify.com/CVE-2023-26065/): Integer overflow in n/a (critical 9.8)
- [CVE-2023-26066](https://insights.sbomify.com/CVE-2023-26066/): Integer overflow in n/a (critical 9.8)
- [CVE-2023-26068](https://insights.sbomify.com/CVE-2023-26068/): Other in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26069 and fix it if it is affected.

What it is: CVE-2023-26069 is a critical vulnerability in n/a, published on 10 Apr 2023. 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-2023-26069 in the wild and no public exploit code.

Affected product: n/a. 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-2023-26069/ (Markdown: https://insights.sbomify.com/CVE-2023-26069/index.md)
```

## Sources

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

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