openssl-encrypt
Affected
- introduced
0, fixed1.4.0(ecosystem)
Fixed versions
1.4.0
Fix
- Fixed version
1.4.0pip install --upgrade openssl-encrypt==1.4.0
Advisory
Also known as: CVE-2026-74877, PYSEC-2026-3743
openssl-encrypt has no owner verification on key revocation — any client can revoke any key
Summary
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.
Impact
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.
Recommended Fix
client_id == key.owner_client_id before allowing revocationFix
Fixed 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.
Medium Basis: The source's own band: MODERATE
0, fixed 1.4.0 (ecosystem)1.4.0
1.4.0pip install --upgrade openssl-encrypt==1.4.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0