Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
MediumPublic exploit

Division by Zero DoS in CISA Thorium

IdentifiersCVE-2025-35435CWE-369· Divide By Zero

CVE-2025-35435 is a division-by-zero vulnerability in CISA Thorium. According to the provided description, Thorium accepts a stream split size value of zero and subsequently divides by that value, causing a crash condition. The issue is remotely reachable by an authenticated attacker and results in service termination. The vulnerability was fixed in commit 89101a6.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote, authenticated attacker can trigger a denial-of-service condition by supplying a stream split size of zero, causing the Thorium service to crash when it performs a division by that value. Based on the provided information, the impact is limited to service disruption and loss of availability; no evidence was provided for code execution, privilege escalation, or data exposure.

Mitigation

If you can’t patch tonight, do this now.

As a temporary mitigation, prevent untrusted or lower-trust authenticated users from supplying a stream split size of zero. Add server-side input validation to enforce a non-zero, valid minimum value for the stream split size parameter before processing. Where possible, restrict access to the affected functionality to only trusted authenticated users and monitor for malformed requests that set the split size to zero, as these may indicate exploitation attempts.

Remediation

Patch, then assume compromise.

Update CISA Thorium to a version that includes the fix introduced in commit 89101a6. If source-based deployment is used, apply or backport that commit. The underlying remediation is to reject or safely handle a stream split size of zero before performing arithmetic operations that use it as a divisor.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
CISAThoriumapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.