CVE-2026-34022
Received Received - Intake
Weak Cryptographic Algorithm in Wertheim SafeController Family 65000

Publication date: 2026-06-15

Last updated on: 2026-06-15

Assigner: SEC Consult Vulnerability Lab

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-15
Last Modified
2026-06-15
Generated
2026-06-15
AI Q&A
2026-06-15
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wertheim safecontroller_family 6.11.8130.22319
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-321 The product uses a hard-coded, unchangeable cryptographic key.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-34022 affects the Wertheim SafeController Family 65000, specifically version AssemblyVersion 6.11.8130.22319. The vulnerability arises because the system uses weak, custom cryptographic algorithms with hard-coded cryptographic keys to protect communication.

An attacker positioned as a man-in-the-middle can intercept and decrypt the data traffic between the SafeController and connected devices. It is possible to break the encryption and decrypt messages without knowing the encryption key, or to discover the key by intercepting enough messages.

No fix is available due to missing hardware support. Workarounds include physically isolating devices, hardening connected systems, enforcing strong authentication, and restricting access to authorized personnel.

Impact Analysis

This vulnerability allows an attacker in an adversary-in-the-middle position to intercept and decrypt sensitive communication between the SafeController and connected devices.

As a result, confidential data could be exposed, potentially compromising the security of the safe deposit locker system.

Since no patch is available, the risk remains until mitigated by physical isolation, system hardening, strong authentication, and restricted access.

Detection Guidance

The vulnerability involves weak custom cryptographic algorithms with hard-coded keys used by the Wertheim SafeController Family 65000, allowing an attacker in a man-in-the-middle position to decrypt communication traffic.

Detection would involve monitoring network traffic between the SafeController devices and connected systems for unencrypted or weakly encrypted data streams that can be intercepted and decrypted.

Since the encryption can be broken without knowledge of the key, commands that capture and analyze network traffic such as using Wireshark or tcpdump to capture packets on the relevant network segment could be used.

  • Use tcpdump to capture traffic: tcpdump -i <interface> host <SafeController IP>
  • Use Wireshark to analyze captured packets for weak or custom encryption patterns.
  • Look for repeated patterns or static keys in the encrypted payloads indicating hard-coded keys.
Mitigation Strategies

No fix or patch is available for this vulnerability due to missing hardware support.

Immediate mitigation steps include physically isolating the affected devices from untrusted networks to prevent interception.

Harden connected systems by enforcing strong authentication and restricting access to authorized personnel only.

Limit network exposure of the SafeController devices and monitor for any suspicious activity.

Compliance Impact

The vulnerability in the Wertheim SafeController Family 65000 involves weak custom cryptographic algorithms with hard-coded keys, allowing an attacker in a man-in-the-middle position to decrypt data traffic. This insufficient transport layer encryption compromises the confidentiality and integrity of the data transmitted.

Such weaknesses can negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require strong protection of sensitive data in transit to prevent unauthorized access and data breaches.

Since the vendor has confirmed no fix is possible due to missing hardware support, organizations using this system must rely on physical isolation, system hardening, strong authentication, and strict access controls as mitigations to reduce compliance risks.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-34022. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart