Credential and session-token disclosure via plaintext registry storage
Published Jul 24, 2025 · Updated Jul 24, 2025
Sensitive-data exposure in Capillary.io CapillaryScope allows local users to extract proxy credentials and JWT session tokens from Windows. The Windows client writes proxy credentials and its JWT session token in plaintext to separate registry keys instead of protecting them. The affected range is before 2.5.0, and exploitation requires an authenticated local account with registry-read access on Windows.
Summary
What happened
Sensitive-data exposure in Capillary.io CapillaryScope allows local users to extract proxy credentials and JWT session tokens from Windows. The Windows client writes proxy credentials and its JWT session token in plaintext to separate registry keys instead of protecting them. The affected range is before 2.5.0, and exploitation requires an authenticated local account with registry-read access on Windows.
The record
- CVE
- CVE-2025-40680
- Published
- Jul 24, 2025
- Updated
- Jul 24, 2025
- Vendor
- Capillary.io
- Product
- CapillaryScope
- Classifications
- CWE-311, T1552.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 24, 2025CVE publishedPublication date reported by the CVE source.
- Jul 24, 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=0 <2.5.0
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.
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