Advisory

GHSA-hvc7-763r-4f3h

Also known as: CVE-2026-74877, PYSEC-2026-3743

Summary

openssl-encrypt has no owner verification on key revocation — any client can revoke any key

Details

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

  • Add an ownership check: verify client_id == key.owner_client_id before allowing revocation
  • Return 403 Forbidden if the requesting client does not own the key

Fix

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-04-01 21:11 UTC
Modified
2026-09-01 09:25 UTC

Affected packages and fixes

openssl-encrypt

PyPI · All systems

Affected

  • introduced 0, fixed 1.4.0 (ecosystem)

Fixed versions

1.4.0

Fix

  • Fixed version 1.4.0
    pip install --upgrade openssl-encrypt==1.4.0

Fix 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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences