Skip to main content
CVE-2025-11413VulnerabilityPublished Updated

CVE-2025-11413: GNU Binutils · Out-of-Bounds Read

Affects GNU BinutilsSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium · fixed in 2.46 : update GNU Binutils when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.46
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GNUBinutilsAffected
  • =2.45
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:gnu:binutils:*:*:*:*:*:*:*:*

AI-suggested

Upgrade GNU Binutils to version 2.46 or later to apply the official patch (commit 72efdf166aa0ed72ecc69fc2349af6591a7a19c0) that fixes this out-of-bounds read vulnerability. This is the recommended and effective remediation.

Description

A vulnerability was found in GNU Binutils 2.45. Affected is the function elf_link_add_object_symbols of the file bfd/elflink.c of the component Linker. The manipulation results in out-of-bounds read. The attack needs to be approached locally. The exploit has been made public and could be used. Upgrading to version 2.46 is able to address this issue. The patch is identified as 72efdf166aa0ed72ecc69fc2349af6591a7a19c0. Upgrading the affected component is advised.

References

Community reviews

Loading reviews…