Skip to main content
CVE-2025-66861VulnerabilityPublished Updated

CVE-2025-66861: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 2.5 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
2.5Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Dec 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-25.

What to do

AI-suggested

1. Restrict access to systems and user accounts that have BinUtils 2.26 installed, limiting usage to trusted personnel only. 2. Implement strict file handling policies to prevent untrusted or suspicious PE files from being processed by BinUtils tools. 3. Monitor system logs and process behavior for signs of crashes or hangs related to BinUtils usage, enabling rapid detection of exploitation attempts. 4. Use sandboxing or containerization to isolate BinUtils processes, minimizing the impact of potential crashes on broader systems. 5. Educate users about the risks of opening or processing untrusted PE files, reducing the likelihood of user interaction exploitation. 6. Track vendor advisories and apply patches or updates promptly once they become available to remediate the vulnerability definitively. 7. Consider upgrading to newer versions of BinUtils if they are confirmed not vulnerable or contain fixes for this issue. 8. Employ application whitelisting to control execution of BinUtils binaries and related tools.

Description

An issue was discovered in function d_unqualified_name in file cp-demangle.c in BinUtils 2.26 allowing attackers to cause a denial of service via crafted PE file.

References

Community reviews

Loading reviews…