Skip to main content
VulnerabilityPublished

CVE-2025-5898: GNU PSPP · Out-of-bounds Write

Affects GNU PSPPSource CVE Database V5

0

Public exploit available · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 15:59 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 5% 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 9 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Immediate mitigation involves restricting local access to systems running the affected PSPP version to trusted users only, minimizing the risk of exploitation by unauthorized personnel.
  2. Monitor official GNU PSPP repositories and security advisories closely for patches or updates addressing CVE-2025-5898 and apply them promptly once available.
  3. Implement strict user privilege management and sandboxing for PSPP processes to limit the potential impact of any exploit attempts.
  4. Conduct regular integrity checks and backups of statistical data processed by PSPP to detect and recover from any data corruption incidents.
  5. Consider isolating PSPP usage to dedicated virtual machines or containers with limited access to sensitive system resources, reducing the attack surface.
  6. Educate users about the risks of running untrusted inputs through PSPP and enforce input validation policies where possible. These steps go beyond generic advice by focusing on access control, monitoring, and containment strategies tailored to the local attack vector and the specific software environment.

Description

A vulnerability classified as critical has been found in GNU PSPP 82fb509fb2fedd33e7ac0c46ca99e108bb3bdffb. Affected is the function parse_variables_option of the file utilities/pspp-convert.c. The manipulation leads to out-of-bounds write. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…