Skip to main content
CVE-2025-65079VulnerabilityPublished Updated

CVE-2025-65079: Lexmark MXTCT, MSNGM, MSTGM, MXNGM, MXTGM, CSNGV, CSTGV, CXTGV, MSNGW, MSTGW, MXTGW, CSTLS, CXTLS, MXTLS, CSTMM, CXTMM, CSTPC, CXTPC, MXTPM, MSNSN, MSTSN, MXTSN, CSNZJ, CSTZJ, CXNZJ, CXTZJ · Heap-based Buffer Overflow

Affects Lexmark MXTCT, MSNGM, MSTGM, MXNGM, MXTGM, CSNGV, CSTGV, CXTGV, MSNGW, MSTGW, MXTGW, CSTLS, CXTLS, MXTLS, CSTMM, CXTMM, CSTPC, CXTPC, MXTPM, MSNSN, MSTSN, MXTSN, CSNZJ, CSTZJ, CXNZJ, CXTZJSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium : upgrade to 250.210 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 250.210, 230.506
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade MXTCT, MSNGM, MSTGM, MXNGM, MXTGM, CSNGV, CSTGV, CXTGV, MSNGW, MSTGW, MXTGW, CSTLS, CXTLS, MXTLS, CSTMM, CXTMM, CSTPC, CXTPC, MXTPM, MSNSN, MSTSN, MXTSN, CSNZJ, CSTZJ, CXNZJ, CXTZJ to 250.210; CSTAT, CXTAT, MSLBD, MXLBD, CSLBL, CXLBL, CSLBN, CXLBN, CSTMH, CXTMH, CSTPP, CXTPP, MSLSG, MXLSG to 230.506.

Affected software

ProductAffectedFixed in
LexmarkMXTCT, MSNGM, MSTGM, MXNGM, MXTGM, CSNGV, CSTGV, CXTGV, MSNGW, MSTGW, MXTGW, CSTLS, CXTLS, MXTLS, CSTMM, CXTMM, CSTPC, CXTPC, MXTPM, MSNSN, MSTSN, MXTSN, CSNZJ, CSTZJ, CXNZJ, CXTZJAffected
  • <250.210
Fixed in
  • 250.210
LexmarkCSTAT, CXTAT, MSLBD, MXLBD, CSLBL, CXLBL, CSLBN, CXLBN, CSTMH, CXTMH, CSTPP, CXTPP, MSLSG, MXLSGAffected
  • <230.506
Fixed in
  • 230.506

AI-suggested

1. Immediately restrict network access to affected Lexmark printers by implementing strict firewall rules and network segmentation to limit exposure to untrusted networks. 2. Disable or restrict Postscript printing capabilities if not required, reducing the attack surface. 3. Monitor printer network traffic for anomalous or unexpected Postscript data that could indicate exploitation attempts. 4. 5. Implement strong access controls on printer management interfaces, including authentication and encryption. 6. Conduct regular security assessments and penetration tests focusing on printer infrastructure. 7. Educate IT and security staff about this vulnerability to ensure rapid detection and response. 8. Maintain comprehensive logging and alerting on printer activity to facilitate incident investigation. 9. Consider isolating printers on dedicated VLANs with limited connectivity to critical systems. 10. Prepare incident response plans specifically addressing printer compromise scenarios.

Description

A heap-based buffer overflow vulnerability has been identified in the Postscript interpreter in various Lexmark devices. This vulnerability can be leveraged by an attacker to execute arbitrary code as an unprivileged user.

References

Community reviews

Loading reviews…