CVE-2026-18220

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.8EG
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.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An out-of-bounds write vulnerability was found in the BFD library's DLX ELF backend (bfd/elf32-dlx.c) in GNU binutils. The dlx_rtype_to_howto() function maps ELF relocation types to internal howto structures but fails to perform adequate bounds checking on attacker-controlled relocation type values (via ELF32_R_TYPE(r_info)) before indexing into the dlx_elf_howto_table[] array. The DLX relocation type number space is non-contiguous (basic types 0-6, extended types at 0x10000+), but the default case in the switch statement allows arbitrary index values to reach the array access.

A specially crafted ELF/DLX object file can trigger this out-of-bounds write when processed by any BFD-consuming tool (objdump, readelf, strip, ld, nm, objcopy). The vulnerability has been demonstrated to achieve arbitrary code execution via a File Stream Oriented Programming (FSOP) attack against glibc FILE structures (stderr), redirecting control flow to system().

Attack scenarios include CI/CD pipelines performing automated binary analysis, developer workstations running objdump/readelf on untrusted binaries, automated security scanning or malware analysis tools invoking binutils, and package build systems processing third-party code.

Note: This vulnerability is only exploitable when binutils is built with the DLX backend enabled (typically via --enable-targets=all).

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
51(Track)
EG Risk 51/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
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (2)

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

2507670 – (CVE-2026-18220) CVE-2026-18220 binutils: binutils: Out-of-bounds write in BFD DLX ELF backend relocation processing

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

cve-details

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

Vendor Advisories for CVE-2026-18220(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
binutils2.35.2-2 ... 2.47-2 (213 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
binutils2.40-2 ... 2.47-2 (118 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
binutils2.44-3 ... 2.47-2 (44 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
binutils2.44-3 ... 2.47-2 (44 versions)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 112× 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 125 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC4D4J/objdump-Out-Of-Bounds-write
    First seen Jun 22, 2026

    Proof of Concept (PoC) demonstrating the CVE-2026-18220, an out-of-bounds (OOB) write vulnerability in the DLX ELF backend of GNU binutils (specifically triggered via `objdump -g`)

    Open source ↗

Frequently asked(5)

What is CVE-2026-18220?
CVE-2026-18220 is a high vulnerability published on July 29, 2026. An out-of-bounds write vulnerability was found in the BFD library's DLX ELF backend (bfd/elf32-dlx.c) in GNU binutils. The dlxrtypetohowto() function maps ELF relocation types to internal howto structures but fails to perform adequate bounds checking on attacker-controlled relocation type values…
When was CVE-2026-18220 disclosed?
CVE-2026-18220 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18220 actively exploited?
CVE-2026-18220 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 78.2% of all scored CVEs.
What is the CVSS score of CVE-2026-18220?
CVE-2026-18220 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-18220?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18220, 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-18220

Explore →

Is Your Infrastructure Affected by CVE-2026-18220?

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