CVE-2025-1178VulnerabilityPublished 2 Feb 2025Updated 3 Jun 2026

Microsoft · GNU Binutils ld libbfd.c bfd_putl64 memory corruption

Affects MicrosoftSource GCVE Database

Not known to be exploited.

Data as of 25 Oct 2026, 21:13 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

microsoft-security-response-ce

What to do

Affected software

Product	Affected	Fixed in
Microsoft Security Response Center Microsoft	Affected =2.0 =3.0	Fixed in–

Description

CVE-2025-1178 is a memory corruption vulnerability in the GNU Binutils ld component, specifically in the libbfd.c function bfd_putl64. The vulnerability is associated with Microsoft products referencing this component. No CVSS score is provided, and no public exploit or patch information is currently available.

Impact

Memory corruption vulnerabilities like this can potentially lead to application crashes or arbitrary code execution if exploited. However, no known exploits are reported in the wild for this vulnerability, and the impact specifics are not detailed in the provided data.

Summary

This vulnerability involves a memory corruption issue in the bfd_putl64 function within libbfd.c of GNU Binutils ld. The affected product is Microsoft-related software that includes or uses this component. The vulnerability is identified by CWE-119, which relates to improper restriction of operations within the bounds of a memory buffer.

CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Overflow Buffers (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Filter Failure through Buffer Overflow (opens in a new tab)
MIME Conversion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Oct 2026, 21:13 UTC

WeaknessesCWE-119

Technical details

References

Community reviews

Related threats