CVE-2026-35467 Details
Description
The stored API keys in temporary browser client is not marked as protected allowing for JavScript console or other errors to allow for extraction of the encryption credentials.
A vulnerability exists in the CVE Client's handling of API keys, which are stored in temporary browser client storage. The keys are not adequately protected, allowing for their extraction through the JavaScript console or other error outputs. This issue arises because the API keys are required for every transaction with the cve-services API, and there is currently no middleware to manage sessions or provide CSRF protection.
Users can update to the latest version of the CVE Client, which includes enhancements for API key storage and encryption key management. Instructions for installation are available in the project's INSTALL.md file.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Apr 3, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/CERTCC/cveClient/ | [email protected] | Product |
| https://github.com/CERTCC/cveClient/pull/39 | [email protected] | Issue TrackingPatch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-522 | Insufficiently Protected Credentials | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| cmu cveclient | < 1.0.24 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 24, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 3, 2026 | Initial Analysis | [email protected] |
| Apr 3, 2026 | CVE Modified | CISA-ADP |
| Apr 2, 2026 | New CVE Received | [email protected] |