vciy

CVE-2026-39886

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

OpenEXR has HTJ2K Signed Integer Overflow in ht_undo_impl()

CVE-2026-398864 of 4 sources documented this
15

rank 15 = 0 + 13 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00302  ·  without this subject the record ranks 15

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.3, from the CNA  ·  without this subject the record ranks 2

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 15

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 13

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 15

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$3,620over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$3,620 = $4.99M incident cost x 0.24048551839932833 exposure x 0.00302 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00302EPSSNOT IN KEVas of 2026-09-20
Severity5.3 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2026-04-21, 55 days at 0.00, as of 2026-06-15. arc-rules@v1

Foresight · where to check next

CVE-2013-2729CVE-2016-1010CVE-2015-8651CVE-2012-5054Qualcomm, Inc.kernel39886

This record is one instance of CWE-190, integer overflow or wraparound. The index holds 3586 prior instances of this class, 21 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running AcademySoftwareFoundation openexr? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactPartial availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-190 Integer Overflow or Wraparoundreceipt
Published consequencesCWE-190: Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (Memory), DoS: Instability; Integrity: Modify Memory; Confidentiality, Availability, Access Control: Execute…[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchopenexr 3.4.10receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA5.3 MEDIUMreceipt
Exploit probability0.00302 · top 77% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byGitHub_Mreceipt
Recorded changes6 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productAcademySoftwareFoundation openexrreceipt
Published rangesopenexr >= 3.4.0 < 3.4.10receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. Versions 3.4.0 through 3.4.9 have a signed integer overflow vulnerability in OpenEXR's HTJ2K (High-Throughput JPEG 2000) decompression path. The `ht_undo_impl()` function in `src/lib/OpenEXRCore/internal_ht.cpp` accumulates a bytes-per-line value (`bpl`) using a 32-bit signed integer with no overflow guard. A crafted EXR file with 16,385 FLOAT channels at the HTJ2K maximum width of 32,767 causes `bpl` to overflow `INT_MAX`, producing undefined behavior confirmed by UBSan. receipt

Read the rest of the CNA's description

On an allocator-permissive host where the required ~64 GB allocation succeeds, the wrapped negative `bpl` value would subsequently be used as a per-scanline pointer advance, which would produce a heap out-of-bounds write. On a memory-constrained host, the allocation fails before `ht_undo_impl()` is entered. This is the second distinct integer overflow in `ht_undo_impl()`. CVE-2026-34545 addressed a different overflow in the same function — the `int16_t p` pixel-loop counter at line ~302 that overflows when iterating over channels whose `width` exceeds 32,767. The CVE-2026-34545 fix did not touch the `int bpl` accumulator at line 211, which is the subject of this advisory. The `bpl` accumulator was also not addressed by any of the 8 advisories in the 2026-04-05 v3.4.9 release batch. This finding is structurally identical to CVE-2026-34588 (PIZ `wcount*nx` overflow in `internal_piz.c`) and should be remediated with the same pattern. The CVE-2026-34588 fix did not touch `internal_ht.cpp`. Version 3.4.10 contains a remediation that addresses the vulnerability in `internal_ht.cpp`.

NVD's analysis a second authority

weakness
CWE-190
affected versions
openexr >= 3.4.0 < 3.4.10
also scored by
[email protected] 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

check it yourself github.com github.com receipt

Movement the material steps

21 Apr 20260.00039
15 Jun 20260.00302 · scoring model v2026.06.15
Show all 6 observations
21 Apr 20260.00039
23 Apr 20260.00041
27 Apr 20260.00054
23 May 20260.00059
2 Jun 20260.0008
15 Jun 20260.00302

6 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00302Published2026-04-21Index as of2026-06-15

The record had been public for 1 month when this index was last written.

Published 2026-04-21 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-190, integer overflow or wraparound. The index holds 3586 prior instances of this class, 21 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2013-2729matches 5 of 8KEV listed · 2013receipt
CVE-2016-1010matches 4 of 8KEV listed · 2016receipt
CVE-2015-8651matches 4 of 8KEV listed · 2015receipt
CVE-2012-5054matches 4 of 8KEV listed · 2012receipt
CVE-2023-33107 · Qualcomm, Inc. Snapdragonmatches 4 of 9KEV listed · 2023receipt
CVE-2022-0185 · kernelmatches 4 of 9KEV listed · 2022receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

3586 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2026-39886.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.