CVE-2026-74877Medium▾ Sunlitopenssl-encrypt has no owner verification on key revocation — any client can revoke any key
▾ Sunlit zone — Low / medium · no exploitation signal
impact 27.5 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Aug 18.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.3%
The revoke_key method in openssl_encrypt_server/modules/keyserver/service.py at lines 195-270 accepts a client_id parameter but never verifies that the requesting client is the same as key.owner_client_id.
Any authenticated client can revoke any other client's key, as long as they provide a valid revocation signature. While the signature requirement mitigates this somewhat (you need the private key to sign), the lack of ownership check is a defense-in-depth gap.
client_id == key.owner_client_id before allowing revocationFixed in commit 05e45f3 on branch releases/1.4.x — added documentation that ML-DSA signature verification IS the cryptographic ownership check; added info-level logging on successful verification.
openssl-encrypt < 1.4.0Upgrade to a patched release:
openssl-encrypt 1.4.0Connected by shared product, vendor, weakness, or advisory.
CVE-2026-74874Mediumopenssl-encrypt has non-cryptographic PRNG used for steganography pixel selection
CVE-2026-74872Mediumopenssl-encrypt: Dynamic .so loading for Whirlpool uses broad glob pattern without integrity verification
CVE-2026-74878Criticalopenssl-encrypt: TOTP rate limiter is in-memory only — not shared across workers, lost on restart
CVE-2026-74873Mediumopenssl-encrypt has visible password in process list via --password CLI argument
CVE-2026-74876Mediumopenssl-encrypt's unverified key bundle from_dict() + to_identity() path allows encryption to attacker keys
CVE-2026-74880Mediumopenssl-encrypt accepts refresh tokens as URL query parameters causing token leakage