CVE-2026-34029

CVE-2026-34029 is a medium-severity vulnerability with a CVSS 4.0 base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-321.

Key facts

Description

The Wertheim SafeController Software, AssemblyVersion 6.15.8328.28014, contains a hard-coded cryptographic key in the SafeSystem.Infrastructure.Security.dll component. An attacker with access to the application files can reverse engineer the DLL and recover the hard-coded cryptographic key. This key can be used to decrypt the licence.whs file, which contains sensitive information about the licensing party and a second key that can be used to decrypt other configuration files.

Frequently asked questions

What is CVE-2026-34029?
The Wertheim SafeController Software, AssemblyVersion 6.15.8328.28014, contains a hard-coded cryptographic key in the SafeSystem.Infrastructure.Security.dll component. An attacker with access to the application files can reverse engineer the DLL and recover the hard-coded cryptographic key. This key can be used to decrypt the licence.whs file, which contains sensitive information about the licensing party and a second key that can be used to decrypt other configuration files.
How severe is CVE-2026-34029?
CVE-2026-34029 has a CVSS 4.0 base score of 6.8, rated medium severity.
Is CVE-2026-34029 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-34029?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-34029 have an EU (EUVD) identifier?
Yes. CVE-2026-34029 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-36712.
When was CVE-2026-34029 published?
CVE-2026-34029 was published on 2026-06-15 and last updated on 2026-06-17.

References

Other CWE-321 vulnerabilities

Browse all CWE-321 vulnerabilities →