A flaw was found in the GNU Binutils (Binary Utilities) linker. This vulnerability, a heap-buffer-overflow read (CWE-125), occurs when the linker processes a specially crafted 32-bit XCOFF (Extended Common Object File Format) object file. An attacker could exploit this by providing a malicious file, leading to an out-of-bounds read of memory. This can result in information disclosure, potentially revealing sensitive heap data, and a Denial of Service (DoS) due to the linker crashing.
CVE-2026-15003
Score 5.6 from GitHub Security Advisory published 2026-07-27. a secondary CVSS source baseline 5.6; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.6
- EG Score
- 5.6(medium)
- EG Risk
- 25(Track)EG Risk 25/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 computedSeverity56% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
July 27, 2026
Last Modified
August 21, 2026
Advisory Details (3)
Auto-updated Jul 27, 202634053 – Heap-buffer-overflow READ in xcoff_link_add_symbols() via unvalidated n_numaux index (CWE-125)
https://sourceware.org/bugzilla/show_bug.cgi?id=340532497805 – (CVE-2026-15003) CVE-2026-15003 binutils: GNU Binutils: Heap-buffer-overflow in linker leads to information disclosure and denial of service
https://bugzilla.redhat.com/show_bug.cgi?id=2497805Vendor Advisories for CVE-2026-15003(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | binutils-main-2.46.1-1.1.hum1 | 2026-07-28 | redhat |
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| binutils | 2.35.2-2 ... 2.47-2 (213 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| binutils | 2.40-2 ... 2.47-2 (118 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| binutils | 2.44-3 ... 2.47-2 (44 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| binutils | 2.44-3 ... 2.46.90.20260712-1 (42 versions) | 2.47-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 21× in last 7d / 115× 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 132 total refreshes for this CVE.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 23:54 UTCEG score recompute
- 2026-08-29 23:54 UTCVendor advisory
- 2026-08-29 23:54 UTCGHSA enrichment
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 09:44 UTCEG score recompute
- 2026-08-27 09:44 UTCVendor advisory
- 2026-08-27 09:44 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 06:50 UTCEG score recompute
- 2026-08-26 06:50 UTCVendor advisory
- 2026-08-26 06:50 UTCGHSA enrichment
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 07:35 UTCEG score recompute
- 2026-08-25 07:35 UTCVendor advisory
- 2026-08-25 07:35 UTCGHSA enrichment
- 2026-08-24 09:03 UTCVendor advisory
- 2026-08-24 09:03 UTCGHSA enrichment
- 2026-08-23 10:32 UTCVendor advisory
- 2026-08-23 10:32 UTCGHSA enrichment
- 2026-08-22 12:01 UTCEG score recompute
- 2026-08-22 12:01 UTCVendor advisory
- 2026-08-22 12:01 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-21 13:21 UTCEG score recompute
- 2026-08-21 13:21 UTCVendor advisory
- 2026-08-21 13:21 UTCGHSA enrichment
- 2026-08-21 12:30 UTCEG score recompute
- 2026-08-21 12:30 UTCVendor advisory
- 2026-08-21 12:30 UTCGHSA enrichment
- 2026-08-21 04:54 UTCEG score recompute
- 2026-08-21 04:54 UTCVendor advisory
- 2026-08-21 04:54 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 06:23 UTCVendor advisory
- 2026-08-20 06:23 UTCGHSA enrichment
- 2026-08-19 07:52 UTCEG score recompute
- 2026-08-19 07:52 UTCVendor advisory
- 2026-08-19 07:51 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 09:16 UTCEG score recompute
- 2026-08-18 09:16 UTCVendor advisory
- 2026-08-18 09:16 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 10:45 UTCEG score recompute
- 2026-08-17 10:45 UTCVendor advisory
- 2026-08-17 10:45 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:15 UTCEG score recompute
- 2026-08-16 12:15 UTCVendor advisory
- 2026-08-16 12:15 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 13:45 UTCEG score recompute
- 2026-08-15 13:45 UTCVendor advisory
- 2026-08-15 13:45 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 15:14 UTCEG score recompute
- 2026-08-14 15:14 UTCVendor advisory
- 2026-08-14 15:14 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 16:43 UTCVendor advisory
- 2026-08-13 16:43 UTCGHSA enrichment
- 2026-08-12 18:09 UTCEG score recompute
- 2026-08-12 18:09 UTCVendor advisory
- 2026-08-12 18:09 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 19:38 UTCEG score recompute
- 2026-08-11 19:38 UTCVendor advisory
- 2026-08-11 19:38 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 21:08 UTCVendor advisory
- 2026-08-10 21:08 UTCGHSA enrichment
- 2026-08-09 22:37 UTCEG score recompute
- 2026-08-09 22:37 UTCVendor advisory
- 2026-08-09 22:37 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 00:07 UTCEG score recompute
- 2026-08-09 00:07 UTCVendor advisory
- 2026-08-09 00:07 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 01:36 UTCEG score recompute
- 2026-08-08 01:36 UTCVendor advisory
- 2026-08-08 01:36 UTCGHSA enrichment
- 2026-08-07 03:05 UTCEG score recompute
- 2026-08-07 03:05 UTCVendor advisory
- 2026-08-07 03:05 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 04:34 UTCEG score recompute
- 2026-08-06 04:34 UTCVendor advisory
- 2026-08-06 04:34 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 06:04 UTCEG score recompute
- 2026-08-05 06:04 UTCVendor advisory
- 2026-08-05 06:04 UTCGHSA enrichment
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-04 07:30 UTCEG score recompute
- 2026-08-04 07:30 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-15003?
When was CVE-2026-15003 disclosed?
Is CVE-2026-15003 actively exploited?
What is the CVSS score of CVE-2026-15003?
How do I remediate CVE-2026-15003?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15003
Is Your Infrastructure Affected by CVE-2026-15003?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.