An integer overflow in the libtiff rgb2ycbcr utility's cvtRaster() function when computing strip buffer sizes can result in an undersized heap allocation and subsequent heap-based buffer overflow during YCbCr conversion of a crafted TIFF image
CVE-2026-52492
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
August 24, 2026
Last Modified
August 27, 2026
Advisory Details (2)
Auto-updated Aug 27, 2026Add -Wconversion to extra-warnings (94affc5c) · Commits · libtiff / libtiff · GitLab
https://gitlab.com/libtiff/libtiff/-/commit/94affc5cf54111312f9891eb77accb93eebc28d7Vendor Advisories for CVE-2026-52492(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | libtiff-main-4.7.2-2.hum1 | 2026-08-11 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 23× in last 7d / 23× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:32 UTCEG score recompute
- 2026-08-30 01:32 UTCVendor advisory
- 2026-08-30 01:32 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 13:04 UTCVendor advisory
- 2026-08-29 13:04 UTCGHSA enrichment
- 2026-08-29 00:29 UTCEG score recompute
- 2026-08-29 00:29 UTCVendor advisory
- 2026-08-29 00:29 UTCGHSA enrichment
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 09:00 UTCEG score recompute
- 2026-08-28 09:00 UTCVendor advisory
- 2026-08-28 09:00 UTCGHSA enrichment
- 2026-08-27 20:28 UTCGHSA enrichment
- 2026-08-27 20:17 UTCEG score recompute▲ 7.80
- 2026-08-27 20:17 UTCGHSA enrichment
- 2026-08-27 20:13 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 21:25 UTCNVD update
- 2026-08-24 20:36 UTCEG score recompute
- 2026-08-24 20:36 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-190
Frequently asked(5)
What is CVE-2026-52492?
When was CVE-2026-52492 disclosed?
Is CVE-2026-52492 actively exploited?
What is the CVSS score of CVE-2026-52492?
How do I remediate CVE-2026-52492?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-52492
Is Your Infrastructure Affected by CVE-2026-52492?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.