Skip to main content
CVE-2025-8735VulnerabilityPublished Updated

CVE-2025-8735: GNU cflow · NULL Pointer Dereference

Affects GNU cflowSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium.

Data as of 25 Oct 2026, 19:02 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 4% 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:N/VI:N/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-25.

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 CVE-2025-8735, European organizations should first inventory all systems running GNU cflow versions 1.0 through 1.8 and assess their exposure. Since no official patches are currently linked, organizations should monitor GNU project repositories and security advisories for updates addressing this vulnerability. In the interim, restricting local access to trusted personnel only will reduce the risk of exploitation. Implementing strict access controls and user permissions on development and build servers can prevent unprivileged users from triggering the vulnerability. Where feasible, replacing GNU cflow with alternative static analysis tools not affected by this issue can be considered. Additionally, integrating runtime monitoring to detect abnormal process crashes or unusual behavior in build environments can provide early warning of exploitation attempts. For organizations with in-house development capabilities, reviewing and patching the vulnerable yylex function in the c.c source code may be an option. Finally, educating developers and system administrators about the vulnerability and safe handling of local access rights will strengthen overall security posture.

Description

A vulnerability classified as problematic was found in GNU cflow up to 1.8. Affected by this vulnerability is the function yylex of the file c.c of the component Lexer. The manipulation leads to null pointer dereference. An attack has to be approached locally. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…