dbcve.org
Cxtpc FirmwareOperating system · Lexmark

CVE-2023-26070

CRITICAL · 9.8 CVSS v3.1 Developing Published 2023-04-10
No fix yet
No fix has been published. The vendor has not shipped a fixed release or patch. You remain exposed.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-07-31.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cxtpc FirmwareOperating system
Affected:< cxtpc.081.232
Cstpc FirmwareOperating system
Affected:< cstpc.081.232
Mxtct FirmwareOperating system
Affected:< mxtct.081.232
Mxtpm FirmwareOperating system
Affected:< mxtpm.081.232
Cxtmm FirmwareOperating system
Affected:< cxtmm.081.232
Mslsg FirmwareOperating system
Affected:< mslsg.081.232
Mxlsg FirmwareOperating system
Affected:< mxlsg.081.232
Mslbd FirmwareOperating system
Affected:< mslbd.081.232

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Recommended fix High confidence

Firmware version 081.232 for each affected model (cxtpc.081.232, cstpc.081.232, mxtct.081.232, mxtpm.081.232, cxtmm.081.232, mslsg.081.232, mxlsg.081.232, mslbd.081.232)

  1. Identify the specific Lexmark device model (Cxtpc, Cstpc, Mxtct, Mxtpm, Cxtmm, Mslsg, Mxlsg, or Mslbd) from the affected product list
  2. Navigate to the official Lexmark support site at support.lexmark.com
  3. Search for your device model and locate the firmware download section
  4. Download the firmware version 081.232 (or later) for your specific device model
  5. Review the firmware release notes for any specific upgrade instructions or prerequisites
  6. Connect to the device administration interface (web-based or embedded web server)
  7. Locate the Firmware Update or Device Maintenance section in the management interface
  8. Upload and apply the downloaded firmware file (.flf or .hd firmware file)
Caveat Review firmware release notes for potential configuration or feature changes; some legacy settings may need adjustment after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

No vendor fix exists Cxtpc Firmware has not published a patch for this.

There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.

Add your voice

Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.

Can’t wait

We develop and verify an original fix where the vendor hasn’t, from $2,300. Deployed to your staging first — never straight to production.

Scope it with us

See what else the community needs solved on the solutions-needed board.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26070 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-26070 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data