Arbitrary key revocation via missing owner check
Published Aug 17, 2026 · Updated Aug 18, 2026
Authorization bypass in jahlives OpenSSL Encrypt before 1.4.0 allows remote authenticated users to revoke other clients' keys. The revoke_key method accepts a client_id and honors a valid ML-DSA revocation signature without checking that the requester matches key.owner_client_id. Exploitation requires network access to an authenticated keyserver session and a signing key accepted for revocation, resulting in unauthorized key invalidation rather than code execution.
Summary
What happened
Authorization bypass in jahlives OpenSSL Encrypt before 1.4.0 allows remote authenticated users to revoke other clients' keys. The revoke_key method accepts a client_id and honors a valid ML-DSA revocation signature without checking that the requester matches key.owner_client_id. Exploitation requires network access to an authenticated keyserver session and a signing key accepted for revocation, resulting in unauthorized key invalidation rather than code execution.
The record
- CVE
- CVE-2026-74877
- Published
- Aug 17, 2026
- Updated
- Aug 18, 2026
- Vendor
- jahlives
- Product
- OpenSSL Encrypt
- Classifications
- CWE-639
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.4.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo