Quick answers
- Is CVE-2026-34022 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34022 being exploited in the wild.
- How severe is CVE-2026-34022?
- Informational severity, with a CVSS score of 7.1, published 15 June 2026.
- Which products and versions are affected?
- Wertheim Controller 65000 AssemblyVersion 6.11.8130.22319; Wertheim SafeController Family 65000 AssemblyVersion 6.11.8130.22319.
- Is there a fix for CVE-2026-34022?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-34022 attacked?
- It is attacked from the adjacent network, in a network appliance.
- Am I affected by CVE-2026-34022?
- Check whether you run Wertheim Controller 65000 or Wertheim SafeController Family 65000 at an affected version. 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
The Wertheim SafeController Family 65000 (specifically AssemblyVersion 6.11.8130.22319) suffers from the use of hard-coded cryptographic keys and a weak, custom encryption algorithm (CWE-321). An attacker positioned as an adversary-in-the-middle on the local network or adjacent communication link can intercept and decrypt data traffic. Research indicates that the encryption routine can be broken without prior knowledge of the key, and the key itself can be recovered by analyzing a sufficient volume of intercepted messages. The vendor has stated that this cannot be fixed due to hardware limitations; users are advised to assess business risks and consider migrating to supported hardware.
Affected products
- Wertheim SafeController Family 65000 AssemblyVersion 6.11.8130.22319
- Wertheim Controller 65000 AssemblyVersion 6.11.8130.22319
Timeline
- 2023-04-03: other: Vulnerability discovered by SEC Consult
- 2023-06-20: disclosed: Initial meeting with vendor
- 2024-03-29: other: Recheck confirmed vulnerability remains unfixed
- 2026-06-15: advisory: Public disclosure by SEC Consult