Persistent access via unsaved token rotation
Published Sep 17, 2025 · Updated Sep 17, 2025
Insufficient session expiration in CISA Thorium before 1.1.1 allows remote authenticated users to retain account access after a reset. The password-update path generates a replacement token but fails to save it, leaving the previously issued token valid. A previously authenticated token and an LDAP-enabled cluster are required; the token continues to authorize API access after the account password changes.
Summary
What happened
Insufficient session expiration in CISA Thorium before 1.1.1 allows remote authenticated users to retain account access after a reset. The password-update path generates a replacement token but fails to save it, leaving the previously issued token valid. A previously authenticated token and an LDAP-enabled cluster are required; the token continues to authorize API access after the account password changes.
The record
- CVE
- CVE-2025-35433
- Published
- Sep 17, 2025
- Updated
- Sep 17, 2025
- Vendor
- Cybersecurity and Infrastructure Security Agency (CISA)
- Product
- Thorium
- Classifications
- CWE-613, T1550.001
- Attack vector
- network
- Privileges
- authenticated
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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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