CVE-2026-55379

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% 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, secondary
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.

Pillow is a Python imaging library. Prior to 12.3.0, PIL/BdfFontFile.py bdf_char() read the BBX width and height field from a BDF font file and passed attacker-controlled dimensions to Image.new() without calling Image._decompression_bomb_check(), bypassing Pillow's documented decompression bomb protection and allowing excessive memory allocation. This issue is fixed in version 12.3.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

BdfFontFile`: `Image.new()` called without `_decompression_bomb_check()` — bomb protection bypass via font loading · Advisory · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/security/advisories/GHSA-45hq-cxwh-f6vc
github_commit Patch Available

commit 0a263e6264aa (python-pillow/Pillow)

Patch available: python-pillow/Pillow 12.3.0 (contains commit 0a263e6264aa)

https://github.com/python-pillow/Pillow/commit/0a263e6264aa5399988d9acd3bbfbca2ca3ec77d
generic

Pillow/docs/releasenotes/12.3.0.rst at main · python-pillow/Pillow · GitHub

https://github.com/python-pillow/Pillow/blob/main/docs/releasenotes/12.3.0.rst

Vendor Advisories for CVE-2026-55379(20)

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

Patch Availability(21)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhelai3/disk-image-cuda-rhel9:17882903142026-09-01redhat
redhatrhelai3/bootc-gcp-cuda-rhel9:17882739772026-09-01redhat
redhatrhaiis/vllm-rocm-rhel9:17878848732026-08-31redhat
redhatrhaiis/vllm-cuda-rhel9:17878605802026-08-31redhat
redhatrhaiis/model-opt-cuda-rhel9:17877721572026-08-31redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatrhaiis/model-opt-cuda-rhel9:17876011592026-08-25redhat
redhatquay/quay-rhel8:17863950652026-08-11redhat
redhatquay/quay-rhel8:17861706352026-08-10redhat
redhatpython-pillow-0:5.1.1-15.el8_4.22026-08-10redhat
redhatquay/quay-rhel8:17859500042026-08-05redhat
redhatpython3.12-pillow-0:12.3.0-1.el9ap2026-08-04redhat
redhatpython-pillow-0:12.3.0-1.el9pc2026-08-04redhat
redhatpython3.12-pillow-0:12.3.0-1.el9pc2026-08-04redhat
redhatansible-automation-platform-25/hub-rhel8:17853762742026-08-04redhat
redhatansible-automation-platform-26/lightspeed-chatbot-rhel9:17856461882026-08-04redhat
redhatansible-automation-platform-27/lightspeed-chatbot-rhel9:17854267342026-08-04redhat
redhatpython-pillow-0:5.1.1-20.el8_82026-07-31redhat
redhatpython-pillow-0:5.1.1-20.el8_62026-07-31redhat
redhatquay/quay-rhel8:17852615062026-07-30redhat
redhatpython-pillow-0:5.1.1-22.el8_102026-07-14redhat

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
pillow10.0.0-1 ... 9.5.0-1 (38 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pillow10.0.0-1 ... 9.5.0-1 (23 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pillow11.1.0-5 ... 12.3.0-1 (13 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pillow11.1.0-5 ... 12.2.0-1 (8 versions)12.3.0-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
pillow1.0 ... 9.5.0 (106 versions)12.3.0—

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

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 14× 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 191 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-55379?
CVE-2026-55379 is a high vulnerability published on July 6, 2026. Pillow is a Python imaging library. Prior to 12.3.0, PIL/BdfFontFile.py bdfchar() read the BBX width and height field from a BDF font file and passed attacker-controlled dimensions to Image.new() without calling Image.decompressionbombcheck(), bypassing Pillow's documented decompression bomb…
When was CVE-2026-55379 disclosed?
CVE-2026-55379 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55379 actively exploited?
CVE-2026-55379 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 63.9% of all scored CVEs.
What is the CVSS score of CVE-2026-55379?
CVE-2026-55379 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-55379?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55379, 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-55379

Explore →

Is Your Infrastructure Affected by CVE-2026-55379?

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

Start Free Scan →Browse All CVEs