# CVE-2025-70955: Denial of service in n/a

> Attackers can crash TON validator nodes by deploying smart contracts with deeply nested jumps, causing a network-wide denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2026
- **Updated:** 18 Feb 2026
- **Also known as:** GHSA-964f-vc2f-ch6j

## What is CVE-2025-70955?

CVE-2025-70955 is a high-severity denial of service vulnerability in n/a, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2025-70955?


## How do I fix CVE-2025-70955?

No fix has been published for CVE-2025-70955 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-70955 being exploited?

There is no known exploitation of CVE-2025-70955 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-70955 and fix it if it is affected.

What it is: CVE-2025-70955 is a high-severity denial of service vulnerability in n/a, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-70955 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-70955/ (Markdown: https://insights.sbomify.com/CVE-2025-70955/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-70955
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-70955
- OSV: https://osv.dev/vulnerability/CVE-2025-70955

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-70955/
Summaries are generated and may contain mistakes; the official description above is the record.