CVE-2026-12912

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-29. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in libtiff. A remote attacker could exploit this vulnerability by providing a specially crafted PixarLog-compressed TIFF image. This issue occurs when decoding Pixarlog codec images with the PIXARLOGDATAFMT_8BITABGR output format and a specific stride value, leading to a heap-based buffer overflow. This could potentially result in arbitrary code execution or a denial of service (DoS).

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/100CISA SSVC

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
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 29, 2026

Last Modified

October 2, 2026

Advisory Details (4)

Auto-updated Jun 29, 2026
Patch available. Sources: redhat.
generic

Heap buffer-overflow in `PixarLogDecode` with `PIXARLOGDATAFMT_8BITABGR` format (#824) · Issues · libtiff / libtiff · GitLab

https://gitlab.com/libtiff/libtiff/-/work_items/824
generic

pixarlog: fix heap-buffer-overflow in 8BITABGR decode with stride 3 (#824) (!873) · Merge requests · libtiff / libtiff · GitLab

https://gitlab.com/libtiff/libtiff/-/merge_requests/873
redhat

2492871 – (CVE-2026-12912) CVE-2026-12912 libtiff: libtiff: Heap-based buffer overflow via crafted PixarLog-compressed TIFF image

https://bugzilla.redhat.com/show_bug.cgi?id=2492871
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-12912

Patch Availability(27)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhai/base-image-rocm-rhel9:17907035062026-10-01redhat
redhatrhai/base-image-tpu-rhel9:17907034972026-10-01redhat
redhatrhai/base-image-cpu-rhel9:17907035902026-10-01redhat
redhatrhai/base-image-cuda-rhel9:17907035862026-10-01redhat
redhatrhai/base-image-rocm-rhel9:17907034942026-10-01redhat
redhatrhai/base-image-spyre-rhel9:17907035682026-10-01redhat
redhatrhai/base-image-spyre-rhel9:17902768892026-09-30redhat
redhatrhai/base-image-tpu-rhel9:17902768842026-09-30redhat
redhatrhai/base-image-rocm-rhel9:17902768862026-09-30redhat
redhatrhai/base-image-cuda-rhel9:17902769742026-09-30redhat
redhatrhai/base-image-cpu-rhel9:17902770452026-09-30redhat
redhatlibtiff-0:4.0.9-18.el8_4.32026-09-21redhat
redhatcompat-libtiff3-0:3.9.4-12.el7_9.32026-08-31redhat
redhatlibtiff-0:4.0.9-29.el8_8.32026-08-24redhat
redhatlibtiff-0:4.4.0-12.el9_4.62026-08-24redhat
redhatlibtiff-0:4.0.9-21.el8_6.32026-08-24redhat
redhatlibtiff-0:4.4.0-8.el9_2.62026-08-24redhat
redhatcompat-libtiff3-0:3.9.4-13.el8_4.32026-08-13redhat
redhatcompat-libtiff3-0:3.9.4-13.el8_8.32026-08-13redhat
redhatcompat-libtiff3-0:3.9.4-13.el8_6.32026-08-13redhat
redhatlibtiff-0:4.4.0-13.el9_6.62026-08-05redhat
redhatlibtiff-0:4.0.9-38.el8_102026-08-03redhat
redhatlibtiff-0:4.6.0-6.el10_0.42026-08-03redhat
redhatcompat-libtiff3-0:3.9.4-16.el8_102026-08-03redhat
redhatlibtiff-0:4.4.0-18.el9_8.12026-07-21redhat
redhatlibtiff-0:4.6.0-8.el10_2.42026-07-20redhat
redhatlibtiff-main-4.7.1-2.4.hum12026-07-02redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
tiff4.2.0-1 ... 4.7.2-1 (51 versions)
  • every version on: no fix on record
—
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.0-3+deb13u1, 4.7.0-3+deb13u2
  • every version up to 4.7.0-3+deb13u3: fixed in 4.7.0-3+deb13u3
—
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.

Additional Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 24× in last 7d / 60× 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 412 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-12912?
CVE-2026-12912 is a high vulnerability published on June 29, 2026. A flaw was found in libtiff. A remote attacker could exploit this vulnerability by providing a specially crafted PixarLog-compressed TIFF image. This issue occurs when decoding Pixarlog codec images with the PIXARLOGDATAFMT_8BITABGR output format and a specific stride value, leading to a heap-based…
When was CVE-2026-12912 disclosed?
CVE-2026-12912 was first published on June 29, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12912 actively exploited?
CVE-2026-12912 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12912?
CVE-2026-12912 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12912?
A fix for CVE-2026-12912 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-12912 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-12912

Explore →

Is Your Infrastructure Affected by CVE-2026-12912?

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