cve.bz

CVE-2025-1127 lexmark cx, xc, cs, ms, mx, xm, et. al.: Path traversal

9.1 criticalEPSS 0.5%Fix available

Critical (9.1) in lexmark cx, xc, cs, ms, mx, xm, et. al.. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
The vulnerability can be leveraged by an attacker to execute arbitrary code as an unprivileged user and/or modify the contents of any data on the filesystem.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th 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: total, assessed 2025-02-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Lexmark CX, XC, CS, MS, MX, XM, et. al.: fixed in CXTLS.240.206 and later
  • Lexmark CX, XC, CS, MS, MX, XM, et. al.: fixed in MXTLS.240.206 and later
  • Lexmark CX, XC, CS, MS, MX, XM, et. al.: fixed in CSTLS.240.206 and later
  • Lexmark CX, XC, CS, MS, MX, XM, et. al.: fixed in MSNSN.240.206 and later
  • Lexmark CX, XC, CS, MS, MX, XM, et. al.: fixed in MSTSN.240.206 and later
  • Lexmark CX, XC, CS, MS, MX, XM, et. al.: fixed in MXTSN.240.206 and later
  • Lexmark CX, XC, CS, MS, MX, XM, et. al.: fixed in CSNGV.240.206 and later
  • Lexmark CX, XC, CS, MS, MX, XM, et. al.: fixed in CSTGV.240.206 and later

Ask an AI about this CVE

Show the promptExplain CVE-2025-1127 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-1127?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-1127?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-2025-1127 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 CNA's record in the CVE List.

ProductAffected
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CXTLS.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MXTLS.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CSTLS.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MSNSN.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MSTSN.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MXTSN.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CSNGV.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CSTGV.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CXTGV.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CXTPC.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CSTPC.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MXTCT.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MXTPM.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CXTMM.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CSTMM.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MSNGM.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MSTGM.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MXNGM.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MXTGM.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MSNGW.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MSTGW.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MXTGW.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CSTZJ.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CSNZJ.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CXTZJ.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CXNZJ.240.205
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MSLSG.240.407
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MXLSG.240.407
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MSLBD.240.407
Lexmark CX, XC, CS, MS, MX, XM, et. al.through MXLBD.240.407
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CSLBN.240.407
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CSLBL.240.407
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CXLBN.240.407
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CXLBL.240.407
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CXTPP.240.407
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CSTPP.240.407
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CSTAT.240.407
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CXTAT.240.407
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CSTMH.240.407
Lexmark CX, XC, CS, MS, MX, XM, et. al.through CXTMH.240.407

Fixed in

ProductFixed in
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTLS.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MXTLS.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTLS.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MSNSN.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MSTSN.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MXTSN.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSNGV.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTGV.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTGV.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTPC.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTPC.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MXTCT.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MXTPM.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTMM.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTMM.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MSNGM.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MSTGM.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MXNGM.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MXTGM.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MSNGW.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MSTGW.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MXTGW.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTZJ.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSNZJ.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTZJ.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXNZJ.240.206 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MSLSG.240.408 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MXLSG.240.408 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MSLBD.240.408 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.MXLBD.240.408 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSLBN.240.408 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSLBL.240.408 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXLBN.240.408 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXLBL.240.408 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTPP.240.408 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTPP.240.408 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTAT.240.408 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTAT.240.408 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CSTMH.240.408 and later
Lexmark CX, XC, CS, MS, MX, XM, et. al.CXTMH.240.408 and later

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON