Email flooding via unrestricted verification resends
Published Sep 17, 2025 · Updated Sep 17, 2025
Uncontrolled resource consumption in CISA Thorium 1.0.0 through 1.1.0 allows remote attackers to flood pending users with verification emails. The verification-email resend path sends a new message for every request without checking when the account's previous verification message was sent. No authentication is required, but email verification must be enabled, the target username must be known, and that account must still be unverified; only verification messages can be sent.
Summary
What happened
Uncontrolled resource consumption in CISA Thorium 1.0.0 through 1.1.0 allows remote attackers to flood pending users with verification emails. The verification-email resend path sends a new message for every request without checking when the account's previous verification message was sent. No authentication is required, but email verification must be enabled, the target username must be known, and that account must still be unverified; only verification messages can be sent.
The record
- CVE
- CVE-2025-35432
- Published
- Sep 17, 2025
- Updated
- Sep 17, 2025
- Vendor
- Cybersecurity and Infrastructure Security Agency (CISA)
- Product
- Thorium
- Classifications
- CWE-400, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2025CVE publishedPublication date reported by the CVE source.
- Sep 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <1.1.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo