cve.bz

CVE-2026-91780 gnu binutils: Improper Resource Shutdown or Release

1.9 lowEPSS 0.2%

Low (1.9) in gnu binutils. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A weakness has been identified in GNU Binutils 2.47. This impacts the function elf_link_add_object_symbols of the file bfd/elflink.c. Executing a manipulation can lead to null pointer dereference. The attack needs to be launched locally. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through a bug report but has not responded yet.

Severity

CVSS 4.0

1.9 low
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

CVSS 3.1

3.3 low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-09-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-404 Improper Resource Shutdown or Release
CWE-476 NULL Pointer Dereference
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-91780 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-91780?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-91780?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-91780 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
gnu:binutils2.47

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14binutilsno fix listedDEBIAN-CVE-2026-91780
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 5 morebinutilsno fix listedUBUNTU-CVE-2026-91780
Red Hathummingbird:1binutils, binutils-gold, binutils-devel and 1 more0:2.46.1-1.2.hum1RHSA-2026:67961
Azure Linux3binutilsno fix listedAZL-103373

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat has rated this flaw as having a Moderate severity impact because triggering the crash requires processing a specially crafted ELF binary, which only terminates the specific binary utility without affecting the wider host system or persistent state. Binutils command-line tools are short-lived user-space utilities typically invoked during compilation and build operations rather than persistent listening services. As a result, the blast radius is confined to the crash of the active linking or inspection process, presenting no risk to system integrity or confidentiality.

ProductPackageStateAdvisory
Red Hat Hardened Imagesbinutils-main-2.46.1-1.2.hum1Fixed 2026-09-16RHSA-2026:67961

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-91780.

Attack patterns (CAPEC)

  • CAPEC-125 Flooding Likelihood: High · Severity: Medium
  • CAPEC-130 Excessive Allocation Likelihood: Medium · Severity: Medium
  • CAPEC-131 Resource Leak Exposure Likelihood: Medium · Severity: Medium
  • CAPEC-494 TCP Fragmentation
  • CAPEC-495 UDP Fragmentation
  • CAPEC-496 ICMP Fragmentation
  • CAPEC-666 BlueSmacking Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON