Is CVE-2026-35467 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-35467 being exploited in the wild.

How severe is CVE-2026-35467?

High severity, with a CVSS score of 7.5, published 2 April 2026.

Which products and versions are affected?

CERT/CC cveClient versions up to (excluding) 1.0.24.

Is there a fix for CVE-2026-35467?

A patch was published on 2026-04-01: Pull request merged into main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-35467 attacked?

It is attacked with local access, in a network appliance.

Am I affected by CVE-2026-35467?

Check whether you run Cmu Cveclient. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-35467: CERT/CC cveClient insufficient protection of credentials in browser storage

CVE-2026-35467 · Severity: high · CVSS 7.5 · Published 2026-04-02

A vulnerability in the cveClient tool, used by security organizations to manage vulnerability records, could allow sensitive API keys to be exposed. The software failed to properly protect encryption keys and stored API keys in a way that could be accessed through a browser's developer console or by malicious scripts. If exploited, an attacker could gain unauthorized access to the CVE management system, potentially allowing them to modify or view sensitive vulnerability data.

Vendors: Cmu.

Quick answers

Is CVE-2026-35467 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-35467 being exploited in the wild.
How severe is CVE-2026-35467?: High severity, with a CVSS score of 7.5, published 2 April 2026.
Which products and versions are affected?: CERT/CC cveClient versions up to (excluding) 1.0.24.
Is there a fix for CVE-2026-35467?: A patch was published on 2026-04-01: Pull request merged into main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-35467 attacked?: It is attacked with local access, in a network appliance.
Am I affected by CVE-2026-35467?: Check whether you run Cmu Cveclient. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability in CERT/CC cveClient (prior to version 1.0.24) stems from insufficient protection of credentials stored in the browser. The application stored API keys in plaintext within localStorage or sessionStorage before encryption processes were completed. Additionally, RSA private keys were stored as extractable JWK objects in IndexedDB rather than non-extractable CryptoKey objects. An attacker with local access or the ability to execute JavaScript in the context of the browser (e.g., via a separate XSS or console access) could extract these credentials. The fix involves marking keys as non-extractable and ensuring plaintext keys are not persisted before encryption is finalized.

Affected products

CERT/CC cveClient versions up to (excluding) 1.0.24

Timeline

2026-03-31: other: Fix proposed via pull request
2026-04-01: patched: Pull request merged into main branch
2026-04-02: disclosed: CVE published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.