CVE-2026-46599

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

May 29, 2026

Last Modified

July 22, 2026

Advisory Details (4)

Auto-updated Jun 5, 2026
No patch confirmed yet.
generic

GO-2026-5032 - Go Packages

https://pkg.go.dev/vuln/GO-2026-5032
generic
https://groups.google.com/g/golang-announce/c/uhYX90BlBvI
generic

x/image/tiff: excessive resource consumption in PackBits decompression · Issue #79577 · golang/go · GitHub

https://go.dev/issue/79577
generic
https://go.dev/cl/759960

Vendor Advisories for CVE-2026-46599(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 / EcosystemFixed in / PatchReleasedSource
redhatcryostat/cryostat-storage-rhel9:4.2.0-192026-07-29redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
golang-golang-x-image0.0~git20200119.58c2397-1 ... 0.9.0-1 (22 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-golang-x-image0.11.0-1 ... 0.9.0-1 (17 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-golang-x-image0.18.0-1 ... 0.45.0-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-golang-x-image0.18.0-1 ... 0.45.0-1 (7 versions)——
Go(1)
PackageVulnerable rangeFixed inDependents
golang.org/x/image—0.41.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 35× 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.

Showing the most recent 100 of 180 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46599?
CVE-2026-46599 is a high vulnerability published on May 29, 2026. The TIFF decoder does not place a limit on the size of PackBits-compressed data. A maliciously-crafted image can exploit this to cause a small image (both in terms of pixel width/height and encoded size) to make the decoder decode large amounts of compressed data.
When was CVE-2026-46599 disclosed?
CVE-2026-46599 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46599 actively exploited?
CVE-2026-46599 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.3% of all scored CVEs.
What is the CVSS score of CVE-2026-46599?
CVE-2026-46599 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-46599?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46599, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-46599?

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

Start Free Scan →Browse All CVEs