# CVE-2026-35467: Private Key stored as extractable in browser IndexeDB

> Attackers can extract encryption credentials from browser storage due to improper protection of private keys in the client library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-3435-g6fx-jc4p

## What is CVE-2026-35467?

CVE-2026-35467 is a high-severity vulnerability in CERT/CC cveClient/encrypt-storage.js, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-35467?

It affects 1 product.


Products: Cmu Cveclient.

## How do I fix CVE-2026-35467?

No fix has been published for CVE-2026-35467 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-35467 being exploited?

There is no known exploitation of CVE-2026-35467 in the wild and no public exploit code.

## Other vulnerabilities in CERT/CC cveClient/encrypt-storage.js

- [CVE-2026-35466](https://insights.sbomify.com/CVE-2026-35466/): Stored XSS via unsanitized input from remote service (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35467 and fix it if it is affected.

What it is: CVE-2026-35467 is a high-severity vulnerability in CERT/CC cveClient/encrypt-storage.js, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-35467 in the wild and no public exploit code.

Affected product: CERT/CC cveClient/encrypt-storage.js. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35467/ (Markdown: https://insights.sbomify.com/CVE-2026-35467/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35467
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35467
- OSV: https://osv.dev/vulnerability/CVE-2026-35467

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35467/
Summaries are generated and may contain mistakes; the official description above is the record.