Skip to main content
CVE-2025-29365VulnerabilityPublished

CVE-2025-29365: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 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

AI-suggested

Since no official patches are currently available, European organizations should implement the following specific mitigations: 1) Restrict usage of spimsimulator to trusted users and environments only, preventing untrusted or external code from being run within the simulator. 2) Employ input validation and sanitization at the application or wrapper level to limit the length and content of strings passed to the READ_STRING_SYSCALL function, if feasible. 3) Monitor for updates from the spimsimulator maintainers and apply patches immediately once released. 4) Consider using alternative MIPS simulation tools that have been verified as secure or have received recent security updates. 5) Educate users about the risks of running untrusted code in the simulator and enforce strict access controls. 6) Implement network segmentation and endpoint protection to limit the impact of any potential exploitation. 7) Conduct code reviews and static analysis if the simulator source code is available, to identify and remediate buffer overflow risks proactively.

Description

spimsimulator spim v9.1.24 and before is vulnerable to Buffer Overflow in READ_STRING_SYSCALL.

References

Community reviews

Loading reviews…