# CVE-2026-34022: Weak custom cryptography and hard-coded keys in Wertheim SafeController 65000 allow traffic decryption

> Weak custom cryptography and hard-coded keys in Wertheim SafeController 65000 allow attackers to decrypt traffic and recover keys.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-qxc2-68gx-hgrv

## What is CVE-2026-34022?

CVE-2026-34022 is a high-severity vulnerability in Wertheim SafeController Family 65000 Hardware for VAULT ROOMS (Safe Deposit Locker System - Microcontroller), published on 15 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Wertheim SafeController Family 65000, Controller 65000 - AssemblyVersion 6.11.8130.22319, uses weak custom cryptographic algorithms with hard-coded cryptographic keys to protect communication. An attacker in an adversary-in-the-middle position can decrypt the data traffic. During reassessment, it was possible to break the encryption/decryption routine and decrypt messages without knowledge of the encryption key. It was also possible to gain knowledge about the encryption key by intercepting enough messages.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2026-34022 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34022 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34022 is a high-severity vulnerability in Wertheim SafeController Family 65000 Hardware for VAULT ROOMS (Safe Deposit Locker System - Microcontroller), published on 15 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34022 exists.

Affected product: Wertheim SafeController Family 65000 Hardware for VAULT ROOMS (Safe Deposit Locker System - Microcontroller). 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-34022/ (Markdown: https://insights.sbomify.com/CVE-2026-34022/index.md)
```

## Sources

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

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