Skip to main content
VulnerabilityPublished Updated

CVE-2025-8746: GNU libopts · Memory Corruption

Affects GNU liboptsSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium · end of life, no fix coming : replace or isolate GNU libopts; no fix will be released.

Data as of 26 Oct 2026, 09:16 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 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
None coming – the product is end of life
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 9 Aug 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 26 Oct 2026.

What to do

No fix will be released: GNU libopts is end of life. Replace it, or isolate it from untrusted networks until you can.

Affected software

ProductAffectedFixed in
GNU liboptsAffected
  • =27.0
  • =27.1
  • =27.2
  • =27.3
  • =27.4
  • =27.5
  • =27.6
Fixed in–

AI-suggested

Since no official patches are available due to the affected versions being unsupported, European organizations should take the following specific measures: 1) Conduct thorough software inventory and dependency analysis to identify any usage of GNU libopts versions 27.0 through 27.6 within their systems. 2) Where possible, replace or upgrade software components that depend on vulnerable libopts versions with updated or alternative libraries that are actively maintained. 3) If replacement is not feasible, consider recompiling affected software with patched or hardened versions of libopts, potentially applying community or third-party patches if available. 4) Restrict local access to systems running vulnerable software by enforcing strict access controls, limiting user privileges, and monitoring for suspicious local activity. 5) Employ runtime protections such as memory corruption mitigations (e.g., ASLR, DEP, stack canaries) to reduce exploitation likelihood. 6) Monitor security advisories and community resources for any emerging exploit code or patches related to this vulnerability. 7) Implement robust endpoint detection and response (EDR) solutions to detect anomalous behavior indicative of exploitation attempts. 8) Educate system administrators and users about the risks of local exploitation and the importance of maintaining updated software stacks.

Description

A vulnerability, which was classified as problematic, was found in GNU libopts up to 27.6. Affected is the function __strstr_sse2. The manipulation leads to memory corruption. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. This issue was initially reported to the tcpreplay project, but the code maintainer explains, that this "bug appears to be in libopts which is an external library." This vulnerability only affects products that are no longer supported by the maintainer.

References

Community reviews

Loading reviews…