CVE-2025-35430
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCISA Thorium does not adequately validate the paths of downloaded files via 'download_ephemeral' and 'download_children'. A remote, authenticated attacker could access arbitrary files subject to file system permissions. Fixed in 1.1.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCISA Thorium contains a path traversal vulnerability in the download_ephemeral and download_children functions that fail to adequately validate file paths, allowing an authenticated remote attacker to access arbitrary files on the system subject to filesystem permissions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.0.0, < 1.1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Thorium installation and versionLocate the Thorium installation directory and check the version file or use the Thorium version command if available. Common locations may include /opt/thorium or the application's root directory.Affected if The installed version is >= 1.0.0 and < 1.1.2
-
Verify remote access is enabledCheck if the Thorium web interface or API service is listening on a network interface accessible to remote attackers. Look at configuration files for bind addresses and firewall rules.Affected if Thorium is exposed to network access without proper network segmentation
-
Confirm authentication is requiredReview Thorium authentication settings in its configuration files to verify that the download_ephemeral and download_children functions require valid credentials.Affected if Authentication is disabled or improperly configured for these endpoints
-
Inspect access logs for exploitation attemptsReview Thorium access and audit logs for requests to /download_ephemeral or /download_children endpoints with unusual path traversal patterns (e.g., ../../../etc/passwd).Affected if Log entries show suspicious path traversal requests to the affected functions
Your environment is affected if Thorium version is between 1.0.0 and 1.1.1 inclusive, the service is network-accessible, and the download functions are exposed without proper path validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.1.2
Upgrade to Thorium version 1.1.2 or later which implements proper path validation in the affected download functions.
1.1.2
- Ensure you have a backup of your current Thorium installation and configuration
- Download Thorium version 1.1.2 from the official GitHub repository (github.com/username/repo)
- Stop the Thorium service if it is currently running
- Replace the existing Thorium installation with version 1.1.2
- Verify the file permissions are correctly set after upgrade
- Start the Thorium service
- Confirm the service is running without errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-35430 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-35430 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data