cve.bz

CVE-2023-26067 lexmark: Improper Input Validation

8.1 highEPSS 38%

High (8.1) in lexmark. EPSS 38% estimated probability of exploitation activity in the next 30 days.

On this page
Certain Lexmark devices through 2023-02-19 mishandle Input Validation (issue 1 of 4).

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
38% (unchanged from 38% a week ago; 38% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-02-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-26067 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-26067?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-26067?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-26067 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
lexmark:cxtpc_firmwarebefore cxtpc.081.232
lexmark:cstpc_firmwarebefore cstpc.081.232
lexmark:mxtct_firmwarebefore mxtct.081.232
lexmark:mxtpm_firmwarebefore mxtpm.081.232
lexmark:cxtmm_firmwarebefore cxtmm.081.232
lexmark:mslsg_firmwarebefore mslsg.081.232
lexmark:mxlsg_firmwarebefore mxlsg.081.232
lexmark:mslbd_firmwarebefore mslbd.081.232
lexmark:mxlbd_firmwarebefore mxlbd.081.232
lexmark:msngm_firmwarebefore msngm.081.232
lexmark:mxngm_firmwarebefore mxngm.081.232
lexmark:mxtgm_firmwarebefore mxtgm.081.232
lexmark:msngw_firmwarebefore msngw.081.232
lexmark:mstgw_firmwarebefore mstgw.081.232
lexmark:mxtgw_firmwarebefore mxtgw.081.232
lexmark:cslbn_firmwarebefore cslbn.081.232
lexmark:cslbl_firmwarebefore cslbl.081.232
lexmark:cxlbn_firmwarebefore cxlbn.081.232
lexmark:cxlbl_firmwarebefore cxlbl.081.232
lexmark:csnzj_firmwarebefore csnzj.081.232
lexmark:cxtzj_firmwarebefore cxtzj.081.232
lexmark:cxnzj_firmwarebefore cxnzj.081.232
lexmark:cxtpp_firmwarebefore cxtpp.081.233
lexmark:cxtpp_firmwarebefore cstpp.081.233
lexmark:cstat_firmwarebefore cstat.081.233
lexmark:cxtat_firmwarebefore cxtat.081.233
lexmark:cstmh_firmwarebefore cstmh.081.233
lexmark:cstmh_firmwarebefore cstmx.081.233

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON