CISA Thorium does not validate TLS connections to Elasticsearch
Key facts
- Attack vector
- Adjacent network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Attack requirements
- None
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-295.
Summary
CISA Thorium does not validate TLS certificates when connecting to Elasticsearch. An unauthenticated attacker with access to a Thorium cluster could impersonate the Elasticsearch service. Fixed in 1.1.2.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA Thorium (CISA) Fixed in 1.1.2
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
CISA Thorium 1.1.2
2 records Highest priority Priority MEDIUM 2 MEDIUM
Other records, highest priority first
- TI-2025-24585 CISA Thorium insecure downloaded file path validationPriority MEDIUM 57
Timeline
- 2026-10-02 Threatist record created from CVE-2025-35434
- 2026-10-03 Alias added: GHSA-r8gr-36v8-m732
More CISA Thorium vulnerabilities
- TI-2025-24590 CISA Thorium download stream divide by zero CVSS 4.0MEDIUM 5.3
- TI-2025-24585 CISA Thorium insecure downloaded file path validation CVSS 4.0MEDIUM 5.3
- TI-2025-24591 CISA Thorium account verification email error handling CVSS 4.0MEDIUM 6.9
- TI-2025-24587 CISA Thorium does not rate limit account verification email messages CVSS 4.0MEDIUM 6.9
- TI-2025-24586 CISA Thorium LDAP injection CVSS 4.0MEDIUM 5.3
- TI-2025-24588 Insufficient session expiration in CISA Thorium CVSS 4.0LOW 2.3
Sources
- CVE-2025-35434 · CVE Program
- CVE-2025-35434 · NVD
- FIRST EPSS
- GHSA-r8gr-36v8-m732 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences