openssl_encrypt versions before 1.4.0 contain a hardcoded default secret key in the standalone telemetry server configuration that is used for API key hashing. Attackers who know this default value can predict or forge API key hashes to compromise telemetry API authentication.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-p926-6hjp-w9jw Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.7 · jahlivesNVD modified 2026-10-23 23:10
Affected (CPE criteria) 1
cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:python:*:*
References 2
- https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-p926-6hjp-w9jw Mitigation, Vendor Advisory
- https://www.vulncheck.com/advisories/openssl-encrypt-before-hardcoded-secret-key Third Party Advisory