Skip to main content
Menu
CVEs

CVE

Microsoft jxrlib denial of service in JPEG XR orientation tag parsing

CVE-2026-129860

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

6.8MediumCNA
Exploited
No known exploitation
Fix
Fixed in 1.3.7
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.3.7.

Published
Last modified
Reference
Last checked
7/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Microsoft jxrlib and the mircomir jxrlib fork contain a reachable assertion in ParsePFDEntry() that lets a local attacker abort applications with a crafted JPEG XR file containing an invalid orientation tag, and the attack requires user interaction. The crash affects default assertion-enabled builds, while other builds may instead store an unchecked orientation value.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

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.

cve.now Index

7Pcve.now Index 7 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.8/10CVSS 6.8
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 1.3.7.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129860 (Microsoft jxrlib through 1.1 Reachable Assertion via ParsePFDEntry Orientation Tag), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129860 (entry last updated 2026-11-16):
Affected:
- Microsoft jxrlib: through 1.1
- mircomir jxrlib: fixed in 1.3.7
Fixed versions: 1.3.7.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129860 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129860 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/mircomir/jxrlib/commit/7d2d462f6ca2d8395dde8b33883a9751299d6144
- https://issues.oss-fuzz.com/issues/511393476
- https://seclists.org/oss-sec/2026/q4/368
- https://github.com/mircomir/jxrlib/blob/1.3.7/README.md#changelog
- https://github.com/4creators/jxrlib/blob/v2019.10.9/jxrgluelib/JXRGlueJxr.c#L1570-L1574
- https://www.vulncheck.com/advisories/microsoft-jxrlib-through-1.1-reachable-assertion-via-parsepfdentry-orientation-tag
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129860
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129860"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Microsoft jxrlib

    through 1.1

  • mircomir jxrlib

    fixed in 1.3.7

Evidence 8

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Write-ups · 2

Establishes: Technical detail and context.

  1. Report
  2. Link

Other links · 4

  1. Patch
  2. Repository
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129860

Is CVE-2026-129860 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-129860?

jxrlib: through 1.1. jxrlib: before 1.3.7.Source: cve.now feed data

How do I fix CVE-2026-129860?

Upgrade to a fixed version: 1.3.7.Source: cve.now feed data