CVE-2022-34300: In tinyexr 1.0.1, there is a heap-based buffer over-read in tinyexr::DecodePixelData.

This month

HIGH 8.8DOWNGRADE

CVE-2022-34300 is a high-severity flaw (CVSS 8.8) affecting tinyexr. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In tinyexr 1.0.1, there is a heap-based buffer over-read in tinyexr::DecodePixelData.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-125
Published	2022-06-23
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: tinyexr project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-06-23 17:15 UTCPublished CVE record published
2026-06-17 04:50 UTCUpdated Record last modified

tinyexr project tinyexr DOWNGRADE

Affected: 1.0.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.1

1. Check installed version

apt-cache policy tinyexr || rpm -q tinyexr || tinyexr --version

2. No fixed release: DOWNGRADE to a release before 1.0.1 (Debian / Ubuntu)

apt-cache madison tinyexr sudo apt install tinyexr=<VERSION_BEFORE_1.0.1> sudo apt-mark hold tinyexr

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list tinyexr sudo dnf downgrade tinyexr-<VERSION_BEFORE_1.0.1> sudo dnf versionlock add tinyexr

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-34300?

tinyexr: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-34300 being exploited?

CVE-2022-34300 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-34300 affect?

CVE-2022-34300 affects tinyexr. Severity is high (CVSS 8.8). In tinyexr 1.0.1, there is a heap-based buffer over-read in tinyexr::DecodePixelData.

How urgent is CVE-2022-34300?

Priority 54/100. High severity; Public exploit reference

Related CVEs

CVE-2022-38529 HIGH 7.8 DOWNGRADE tinyexr commit 0647fb3 was discovered to contain a heap-buffer overflow via the component rleUncompress.
CVE-2020-19490 MEDIUM 5.5 DOWNGRADE tinyexr 0.9.5 has a integer overflow over-write in tinyexr::DecodePixelData in tinyexr.h, related to OpenEXR c
CVE-2020-18430 HIGH 7.5 DOWNGRADE tinyexr 0.9.5 was discovered to contain an array index error in the tinyexr::DecodeEXRImage component, which c
CVE-2020-18428 HIGH 7.5 DOWNGRADE tinyexr commit 0.9.5 was discovered to contain an array index error in the tinyexr::SaveEXR component, which c

References

← Back to latest CVEs