CVE-2026-74892 openssl_encrypt before 1.4.0 Hardcoded Secret Key
Attackers can forge API key hashes using a hardcoded secret key to bypass telemetry API authentication in the openssl_encrypt library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-74892?
CVE-2026-74892 is a high-severity vulnerability in Jahlives Openssl Encrypt, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-798
Which versions are affected by CVE-2026-74892?
1 open source package ship an affected version, including openssl-encrypt. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
openssl-encrypt PyPI | All versions | 1.4.0 |
Products include Jahlives Openssl Encrypt.
How do I fix CVE-2026-74892?
Upgrade openssl-encrypt to 1.4.0 or later.
Is CVE-2026-74892 being exploited?
There is no known exploitation of CVE-2026-74892 in the wild and no public exploit code.
Other vulnerabilities in Jahlives Openssl Encrypt
- CVE-2026-81680 openssl_encrypt before 1.4.9 Authentication Bypass via Recovery Slot Removal
- CVE-2026-81681 openssl_encrypt before 1.4.9 False Encryption via Cleartext Storage
- CVE-2026-81685 openssl_encrypt before 1.4.9 Text Injection via Recovery Slot Metadata
- CVE-2026-81694 openssl-encrypt before 1.4.9 Output Injection via Unsanitized Filenames in verify-usb Command
- CVE-2026-81695 openssl_encrypt before 1.4.9 Terminal Injection via key_id
Sources
Also known as GHSA-p926-6hjp-w9jw, GHSA-qg6r-j76g-wv2q, PYSEC-2026-3746.