Quick answers
- Is CVE-2026-34027 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34027 being exploited in the wild.
- How severe is CVE-2026-34027?
- Informational severity, with a CVSS score of 5.3, published 15 June 2026.
- Which products and versions are affected?
- Wertheim SafeController AssemblyVersion 6.15.8328.28014.
- Is there a fix for CVE-2026-34027?
- 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-34027 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-34027?
- Check whether you run Wertheim SafeController 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 vulnerability exists in the '/safe/contract/uploadcustomdocuments' endpoint of the Wertheim SafeController Software (AssemblyVersion 6.15.8328.28014). The application performs file type validation by checking the user-controlled HTTP Content-Type header for allowed strings (e.g., pdf, jpeg, tiff, png) rather than validating the actual file content or extension. An authenticated attacker with low-level privileges can spoof this header to upload arbitrary files. When chained with other vulnerabilities identified in the same advisory (such as path traversal or unauthenticated access to web data), this can lead to Remote Code Execution (RCE) and full system compromise, especially as the service is known to run with NT AUTHORITY/SYSTEM privileges.
Affected products
- Wertheim SafeController Software for VAULT ROOMS (Safe Service 6.0) AssemblyVersion 6.15.8328.28014
Timeline
- 2023-04-03: other: Vulnerability discovered by SEC Consult
- 2026-06-15: disclosed: Public disclosure of CVE-2026-34027