dbcve.org
Cxtpc FirmwareOperating system · Lexmark

CVE-2023-26066

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 have Improper Validation of an Array Index.

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 · moderate confidence

Improper validation of an array index in certain Lexmark devices allows an attacker to access memory outside the bounds of an allocated array, potentially leading to buffer overflow conditions and remote code execution. This is a classic CWE-129 vulnerability where the application fails to properly validate array indices before accessing array elements.

MitigationApply available firmware updates from Lexmark immediately; if no patch exists, isolate affected devices on a restricted network segment and monitor for exploitation attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Lexmark device model
    Access the printer web interface (embedded web server) or print a configuration/settings page to determine the exact model number. Common paths: http://<printer-ip>/ or menu button > Reports > Menu Settings Page.
    Affected if The model is one of: Cxtpc, Cstpc, Mxtct, Mxtpm, Cxtmm, Mslsg, Mxlsg, or Mslbd.
  2. Locate the firmware version
    In the printer web interface, navigate to General > Firmware or Settings > Device Information. Alternatively, print a configuration page: Menu > Reports > Menu Settings Page and look for 'Firmware Date Code' or 'Firmware Version'.
    Affected if A firmware version is found that is numerically lower than 081.232 for your specific model prefix.
  3. Compare firmware version to fixed versions
    Match your firmware version against the fixed versions: cxtpc.081.232, cstpc.081.232, mxtct.081.232, mxtpm.081.232, cxtmm.081.232, mslsg.081.232, mxlsg.081.232, mslbd.081.232. The version format is typically MODEL.XXX.XXX (e.g., cxtpc.081.231).
    Affected if Your installed firmware version has a build number less than 232 for your model prefix, or the firmware cannot be determined (unable to query).

You are affected if you own a Lexmark Cxtpc, Cstpc, Mxtct, Mxtpm, Cxtmm, Mslsg, Mxlsg, or Mslbd device running firmware version lower than 081.232 for your specific model.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available firmware updates from Lexmark immediately; if no patch exists, isolate affected devices on a restricted network segment and monitor for exploitation attempts.

Recommended fix Moderate confidence

Firmware version .232 or later for each affected product (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. Navigate to the official Lexmark support website (support.lexmark.com)
  2. Locate the support page for your specific Lexmark device model (Cxtpc, Cstpc, Mxtct, Mxtpm, Cxtmm, Mslsg, Mxlsg, or Mslbd)
  3. Access the Firmware section or Downloads/Drivers area for your device
  4. Download the firmware version .232 or later for your specific model (e.g., cxtpc.081.232, cstpc.081.232, mxtct.081.232, etc.)
  5. Back up any critical device configurations before proceeding with the update
  6. Access the device's web interface or management console
  7. Locate the Firmware Update or Device Maintenance section
  8. Upload and apply the downloaded firmware file
Caveat Standard firmware upgrade risks apply - ensure configuration backup before updating; some legacy features may be deprecated in newer firmware releases

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

Fix this in Cxtpc Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26066 — 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-26066 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