CVE-2026-11526

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GD versions before 2.86 for Perl allow OS command injection and file overwrite via a 2-arg open() of filename arguments in _make_filehandle.

GD::Image::_make_filehandle opens a filename argument with Perl's 2-arg open(), so a filename that begins or ends with a pipe ("| cmd", "cmd |") or begins with a redirect ("> path", ">> path") is run as a command or redirect rather than opened as a file. _make_filehandle is the single open path behind every filename-accepting constructor (new, newFromPng, newFromJpeg, and the rest); the in-memory *Data variants do not open a path and are unaffected.

Any caller that forwards untrusted input to one of these constructors as a pathname can run an arbitrary command or truncate a file under the process UID.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
1.4%
EPSS %ILE
70th
KEV
Not listed

Published

June 14, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Oct 10, 2026
Patch available.
genericMentions a patch (unverified)

[SECURITY] [DLA 4638-1] libgd-perl security update

https://lists.debian.org/debian-lts-announce/2026/06/msg00027.html
generic

oss-security - CVE-2026-11526: GD versions before 2.86 for Perl allow OS command injection and file overwrite via a 2-arg open() of filename arguments in _make_filehandle

http://www.openwall.com/lists/oss-security/2026/06/14/4

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibgd-perl (2.84-2ubuntu0.1) @ resolute2026-09-14ubuntu
redhatperl-GD-0:2.49-3.el7_9.12026-08-03redhat

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

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
perl-gd—
  • every version up to 2.86-r0: fixed in 2.86-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
perl-gd—
  • every version up to 2.86-r0: fixed in 2.86-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
perl-gd—
  • every version up to 2.86-r0: fixed in 2.86-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
perl-gd—
  • every version up to 2.86-r0: fixed in 2.86-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libgd-perl2.73-1
  • every version up to 2.73-1+deb11u1: fixed in 2.73-1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libgd-perl2.76-4
  • every version up to 2.76-4+deb12u1: fixed in 2.76-4+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libgd-perl2.78-1
  • every version up to 2.78-1+deb13u1: fixed in 2.78-1+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libgd-perl2.78-1, 2.83-1, 2.84-1, 2.84-2
  • every version up to 2.84-3: fixed in 2.84-3
—

Weakness Classification(2)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 26× 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 613 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-11526?
CVE-2026-11526 is a critical vulnerability published on June 14, 2026. GD versions before 2.86 for Perl allow OS command injection and file overwrite via a 2-arg open() of filename arguments in makefilehandle. GD::Image::makefilehandle opens a filename argument with Perl's 2-arg open(), so a filename that begins or ends with a pipe ("| cmd", "cmd |") or begins with a…
When was CVE-2026-11526 disclosed?
CVE-2026-11526 was first published on June 14, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11526 actively exploited?
CVE-2026-11526 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (70th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11526?
CVE-2026-11526 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-11526?
A fix for CVE-2026-11526 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-11526 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-11526

Explore →

Is Your Infrastructure Affected by CVE-2026-11526?

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