Skip to main content
VulnerabilityPublished

CVE-2024-58407: Microsoft jxrlib · Out-of-bounds Read

Affects Microsoft jxrlibSource CVE Database V5

0
Compare

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

Data as of 16 Nov 2026, 15:05 UTC

CVSS 4.0 base score
6.9Medium
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.06.9
CNA (VulnCheck)CVSS 3.16.1
Patch
Available – fixed in 1.3.1
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/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 jxrlib is available that addresses this vulnerability. Users and administrators should upgrade to version 1.3.1 or later to remediate this issue. No additional mitigation steps are indicated.

Description

CVE-2024-58407 is a global buffer over-read vulnerability in Microsoft jxrlib versions through 1.1 and the mircomir jxrlib fork before 1.3.1. The flaw exists in the DecodeSignificantRun() function due to an unchecked run length, allowing crafted JPEG XR files with out-of-range iMaxRun values to cause out-of-bounds reads. This can lead to memory disclosure or crashes during image decoding.

References

Community reviews

Loading reviews…