CVE Intelligence
Skip to main content
MEDIUM

CVE-2025-65080

CVE-2025-65080 — Type confusion vulnerability in Postscript interpreter

A type confusion 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.

Published Updated Sources: cvelistV5, Lexmark

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

lexmark

2 products listed

CVSS base

6.9

MEDIUM

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

lexmark

Products (2)

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 cxtzjcstat cxtat mslbd mxlbd cslbl cxlbl cslbn cxlbn cstmh cxtmh cstpp cxtpp mslsg mxlsg

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
6.9CVSS 4.0MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-843

References

1 on the record

Elsewhere on this site

  • lexmarkevery CVE for this vendor
  • CWE-843other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.