CVE-2026-74877
highpriority · track · 0OT risk · elevatedEPSS 0.005 · 39 %ileEUUSEPSS · scored 2026-10-26
openssl_encrypt versions before 1.4.0 contain a missing ownership verification vulnerability in the revoke_key method that allows authenticated clients to revoke any other client's key. Attackers can revoke arbitrary keys by providing a valid ML-DSA signature, bypassing the intended ownership restriction.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.3–8.8
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- GHSA-hvc7-763r-4f3hopenssl-encrypt has no owner verification on key revocation — any client can revoke any key2026-04-01ghsa · osvUS
### 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.
- PYSEC-2026-37432026-08-17vendor · osvUS
openssl_encrypt versions before 1.4.0 contain a missing ownership verification vulnerability in the revoke_key method that allows authenticated clients to revoke any other client's key. Attackers can revoke arbitrary keys by providing a valid ML-DSA signature, bypassing the intended ownership restriction.
also known as (4)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (4)
External citations — patches, advisories, analysis.
- https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-hvc7-763r-4f3henisa_euvd
- https://www.vulncheck.com/advisories/openssl-encrypt-before-missing-ownership-verification-via-revoke-keyenisa_euvd
- https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-hvc7-763r-4f3hMitigationVendor Advisorynvd
- https://www.vulncheck.com/advisories/openssl-encrypt-before-missing-ownership-verification-via-revoke-keyThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan