Skip to main content
CVE-2025-8736VulnerabilityPublished

CVE-2025-8736: GNU cflow · Buffer Overflow

Affects GNU cflowSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium.

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.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GNU cflowAffected
  • =1.0
  • =1.1
  • =1.2
  • =1.3
  • =1.4
  • =1.5
  • =1.6
  • =1.7
  • =1.8
Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should first identify all instances of GNU cflow in their environments, including development, testing, and production systems. Given the lack of an official patch at the time of disclosure, organizations should consider the following specific actions: 1) Restrict local access to systems running GNU cflow to trusted users only and enforce strict access controls and monitoring to detect unauthorized local activity. 2) Employ application whitelisting and endpoint protection solutions to prevent exploitation attempts and detect anomalous behavior related to buffer overflow exploitation. 3) Where feasible, replace GNU cflow with alternative static analysis tools that do not have this vulnerability, especially in critical environments. 4) Monitor vendor communications and security advisories for patches or updates and apply them promptly once available. 5) Implement robust logging and alerting on systems running GNU cflow to detect potential exploitation attempts early. 6) Conduct user training to reduce the risk of local compromise that could lead to exploitation of this vulnerability. These targeted mitigations go beyond generic advice by focusing on access control, monitoring, and tool replacement strategies specific to the nature of this vulnerability.

Description

A vulnerability, which was classified as critical, has been found in GNU cflow up to 1.8. Affected by this issue is the function yylex of the file c.c of the component Lexer. The manipulation leads to buffer overflow. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…