cve.bz

CVE-2026-129860 Microsoft jxrlib through 1.1 Reachable Assertion via ParsePFDEntry Orientation Tag

6.8 medium

Medium (6.8).

Microsoft jxrlib through 1.1 and the mircomir jxrlib fork before 1.3.7 contain a reachable assertion vulnerability in ParsePFDEntry() that allows attackers to abort applications via an invalid orientation tag. Attackers can supply a crafted JPEG XR file with an out-of-range WMP_tagTransformation value to crash applications using default assertion-enabled builds, or store an unchecked orientation value otherwise.

Severity

CVSS 4.0

6.8 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CWE
CWE-617 Reachable Assertion
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-129860 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-129860?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-129860?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-2026-129860 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
Microsoft jxrlibthrough 1.1
mircomir jxrlibbefore 1.3.7

References

Check your stackJSON