Skip to main content
VulnerabilityPublished Updated

CVE-2025-70955: TON Virtual Machine · Uncontrolled Recursion

Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 16:39 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% 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:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Feb 2026

  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

AI-suggested

To mitigate CVE-2025-70955, organizations should: 1) Upgrade the TON Virtual Machine to version 2024.10 or later once patches are released that address the stack overflow issue. 2) Implement runtime limits on the depth of continuation jumps and stack usage within smart contract execution environments to prevent excessive recursion or nested calls. 3) Monitor validator node logs and system metrics for signs of stack exhaustion or abnormal crashes indicative of exploitation attempts. 4) Employ network-level protections such as rate limiting and anomaly detection to identify and block suspicious smart contract deployment or invocation patterns. 5) Engage with the TON developer community to stay informed about patches, advisories, and best practices. 6) Consider deploying redundant validator nodes and failover mechanisms to maintain blockchain availability during potential attacks. 7) Conduct thorough code reviews and testing of smart contracts to detect and prevent malicious nested jump logic before deployment. These measures go beyond generic advice by focusing on specific runtime controls and operational monitoring tailored to the nature of this vulnerability.

Description

A Stack Overflow vulnerability was discovered in the TON Virtual Machine (TVM) before v2024.10. The vulnerability stems from the improper handling of vmstate and continuation jump instructions, which allow for continuous dynamic tail calls. An attacker can exploit this by crafting a smart contract with deeply nested jump logic. Even within permissible gas limits, this nested execution exhausts the host process's stack space, causing the validator node to crash. This results in a Denial of Service (DoS) for the TON blockchain network.

References

Community reviews

Loading reviews…