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 — 4 sources updated 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%CVSS: 7.3Exploit: None knownExposed: 0

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.3(medium)
EG Risk
33(Track)
EG Risk 33/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
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

June 29, 2026

Last Modified

August 14, 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(10)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcompat-libtiff3-0:3.9.4-13.el8_6.32026-08-13redhat
redhatcompat-libtiff3-0:3.9.4-13.el8_4.32026-08-13redhat
redhatcompat-libtiff3-0:3.9.4-13.el8_8.32026-08-13redhat
redhatlibtiff-0:4.4.0-13.el9_6.62026-08-05redhat
redhatlibtiff-0:4.6.0-6.el10_0.42026-08-03redhat
redhatlibtiff-0:4.0.9-38.el8_102026-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 rangeFixed inDependents
tiff4.2.0-1 ... 4.7.2-1 (51 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
tiff4.5.0-6 ... 4.7.2-1 (23 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
tiff4.7.0-3, 4.7.0-3+deb13u1, 4.7.0-3+deb13u24.7.0-3+deb13u3
Debian:14(1)
PackageVulnerable rangeFixed inDependents
tiff4.7.0-3 ... 4.7.1-3 (6 versions)4.7.2-1

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 54× in last 7d / 194× 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 287 total refreshes for this CVE.

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

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 in the National Vulnerability Database on June 29, 2026, with the most recent update on August 14, 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% probability of exploitation in the next 30 days, which ranks it in the top 82.3% of all scored CVEs.
What is the CVSS score of CVE-2026-12912?
CVE-2026-12912 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-12912?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12912, 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-12912

Explore →

Is Your Infrastructure Affected by CVE-2026-12912?

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