CVE-2026-52490

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-24. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 4 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

An issue in libtiff 85f2ac8e0b01cb7db2bbecf4a3b891bdbef67938 allows an attacker to execute arbitrary code via the process_command_opts() function in tools/tiffcrop.c

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

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 computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 24, 2026

Last Modified

October 12, 2026

Advisory Details (2)

Auto-updated Oct 13, 2026
Patch available.
Web page

tiffcrop: -S cols×rows check can be bypassed via unsigned 32-bit overflow (#846) · Issues · libtiff / libtiff · GitLab

https://gitlab.com/libtiff/libtiff/-/work_items/846
Web page

CVE-2026-52490.txt · GitHub

https://gist.github.com/okyfh/122c2d72e991a78c8af80a3af3be8671

Vendor Advisories for CVE-2026-52490(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatlibtiff-0:4.0.9-39.el8_102026-09-21redhat
redhatlibtiff-main-4.7.2-2.hum12026-08-11redhat

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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
tiff4.5.0-6 ... 4.7.2-1 (23 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
tiff4.7.0-3 ... 4.7.2-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
tiff4.7.0-3 ... 4.7.1-3 (6 versions)
  • every version up to 4.7.2-1: fixed in 4.7.2-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 30× in last 7d / 293× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 536 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 436 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 01:16 UTCEG score recompute
  2. 2026-10-14 01:16 UTCVendor advisory
  3. 2026-10-14 01:16 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-12 21:25 UTCEG score recompute
  6. 2026-10-12 21:25 UTCVendor advisory
  7. 2026-10-12 21:25 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-12 15:58 UTCEG score recompute
  10. 2026-10-12 07:07 UTCVendor advisory
  11. 2026-10-12 07:07 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-11 19:41 UTCEG score recompute
  13. 2026-10-11 16:56 UTCEG score recompute
  14. 2026-10-11 14:20 UTCEG score recompute
  15. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-10-10 13:18 UTCEG score recompute
  18. 2026-10-10 13:18 UTCVendor advisory
  19. 2026-10-10 13:18 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-10-09 05:03 UTCEG score recompute
  22. 2026-10-09 05:03 UTCVendor advisory
  23. 2026-10-09 05:03 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-10-08 08:30 UTCVendor advisory
Show 75 more
  1. 2026-10-08 08:29 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-08 04:21 UTCEG score recompute
  3. 2026-10-08 04:21 UTCVendor advisory
  4. 2026-10-08 04:21 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-07 09:57 UTCVendor advisory
  7. 2026-10-07 09:57 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-07 05:32 UTCVendor advisory
  9. 2026-10-07 05:32 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-07 01:24 UTCVendor advisory
  11. 2026-10-07 01:24 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-06 21:16 UTCVendor advisory
  13. 2026-10-06 21:16 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-06 16:42 UTCEG score recompute
  15. 2026-10-06 16:42 UTCVendor advisory
  16. 2026-10-06 16:42 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  18. 2026-10-06 12:06 UTCVendor advisory
  19. 2026-10-06 12:06 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-06 07:47 UTCVendor advisory
  21. 2026-10-06 07:47 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-06 02:57 UTCVendor advisory
  23. 2026-10-06 02:57 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-05 18:00 UTCEG score recompute
  25. 2026-10-05 18:00 UTCVendor advisory
  26. 2026-10-05 18:00 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  28. 2026-10-05 13:52 UTCVendor advisory
  29. 2026-10-05 13:52 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-05 09:44 UTCVendor advisory
  31. 2026-10-05 09:44 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-05 05:37 UTCVendor advisory
  33. 2026-10-05 05:37 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-05 01:29 UTCEG score recompute
  35. 2026-10-05 01:29 UTCVendor advisory
  36. 2026-10-05 01:29 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  38. 2026-10-04 20:44 UTCVendor advisory
  39. 2026-10-04 20:44 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-04 15:36 UTCVendor advisory
  41. 2026-10-04 15:36 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-04 11:09 UTCVendor advisory
  43. 2026-10-04 11:09 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-04 06:29 UTCVendor advisory
  45. 2026-10-04 06:29 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-04 02:21 UTCVendor advisory
  47. 2026-10-04 02:21 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-03 20:47 UTCVendor advisory
  49. 2026-10-03 20:47 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-03 16:34 UTCEG score recompute
  51. 2026-10-03 16:34 UTCVendor advisory
  52. 2026-10-03 16:34 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  54. 2026-10-03 05:04 UTCVendor advisory
  55. 2026-10-03 05:04 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-03 00:37 UTCVendor advisory
  57. 2026-10-03 00:37 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-02 19:22 UTCEG score recompute
  59. 2026-10-02 19:22 UTCVendor advisory
  60. 2026-10-02 19:22 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  62. 2026-10-02 15:12 UTCVendor advisory
  63. 2026-10-02 15:12 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-10-02 11:03 UTCVendor advisory
  65. 2026-10-02 11:03 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-10-02 06:43 UTCVendor advisory
  67. 2026-10-02 06:43 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-10-02 01:19 UTCVendor advisory
  69. 2026-10-02 01:19 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-10-01 21:10 UTCEG score recompute
  71. 2026-10-01 21:10 UTCVendor advisory
  72. 2026-10-01 21:10 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  74. 2026-10-01 13:54 UTCVendor advisory
  75. 2026-10-01 13:54 UTCGHSA enrichmentGHSA-6qm2-q5vx-rh4c · GitHub severity CRITICAL · GitHub CVSS 9.8

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-52490?
CVE-2026-52490 is a critical-severity vulnerability; its CVE record was published on August 24, 2026. An issue in libtiff 85f2ac8e0b01cb7db2bbecf4a3b891bdbef67938 allows an attacker to execute arbitrary code via the processcommandopts() function in tools/tiffcrop.c
When was the CVE record for CVE-2026-52490 published?
The CVE record for CVE-2026-52490 was published on August 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-52490 actively exploited?
CVE-2026-52490 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52490?
CVE-2026-52490 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-52490?
A fix for CVE-2026-52490 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52490 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52490

Explore →

Is Your Infrastructure Affected by CVE-2026-52490?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs