Skip to main content
VulnerabilityPublished

CVE-2026-129857: Microsoft jxrlib · Integer Overflow or Wraparound

Affects Microsoft jxrlibSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.5 High : upgrade to 1.3.1 soon.

Data as of 16 Nov 2026, 15:03 UTC

CVSS 4.0 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.5
CNA (VulnCheck)CVSS 3.17.8
Patch
Available – fixed in 1.3.1
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 15 Nov 2026.

What to do

Upgrade Microsoft jxrlib to 1.3.1.

Affected software

ProductAffectedFixed in
MicrosoftjxrlibAffected
  • <=1.1
Fixed in–
mircomirjxrlibAffected
  • <1.3.1
Fixed in
  • 1.3.1
GitHubjxrlibpkg:github/jxrlibOther threatsAffected
  • <1.3.1
Fixed in
  • 1.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fixed version 1.3.1 of the mircomir jxrlib fork is available that addresses this vulnerability. Users and developers should upgrade to version 1.3.1 or later to remediate this issue. No additional vendor advisory or patch links are provided, but the presence of fixedVersions confirms that an official fix exists.

Description

CVE-2026-129857 is a heap buffer overflow vulnerability in Microsoft jxrlib through version 1.1 and the mircomir jxrlib fork before version 1.3.1. The flaw occurs in the ReadBinaryData() function due to an integer overflow of the metadata count, allowing an attacker to supply a specially crafted JPEG XR file that causes an undersized buffer allocation and subsequent heap corruption during decoding.

References

Community reviews

Loading reviews…