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

> An attacker can cause a denial of service in the TON Lite Server by injecting a malicious Continuation object that consumes excessive CPU resources with low gas costs.

- **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-rvhp-mghq-8mvw

## What is CVE-2025-70957?

CVE-2025-70957 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 Denial of Service (DoS) vulnerability was discovered in the TON Lite Server before v2024.09. The vulnerability arises from the handling of external arguments passed to locally executed "get methods." An attacker can inject a constructed Continuation object (an internal TVM type) that is normally restricted within the VM. When the TVM executes this malicious continuation, it consumes excessive CPU resources while accruing disproportionately low virtual gas costs. This "free" computation allows an attacker to monopolize the Lite Server's processing power, significantly reducing its throughput and causing a denial of service for legitimate users acting through the gateway.

Weakness: CWE-674 (Uncontrolled Recursion)

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


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

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

## Is CVE-2025-70957 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70957 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-70957 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-70957/ (Markdown: https://insights.sbomify.com/CVE-2025-70957/index.md)
```

## Sources

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

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