Malicious plugin execution via revoked GPG keys
Published Aug 27, 2026 · Updated Aug 27, 2026
Improper signature verification in OpenSSL Encrypt before 1.4.9 allows attackers to execute malicious plugins via revoked or expired keys. gpg_runner.verify_detached accepts VALIDSIG output without rejecting REVKEYSIG, EXPKEYSIG, EXPSIG, failed status lines, or a nonzero GPG exit code. An attacker must control a compromised-then-revoked signing key or an expired project key; accepted plugin code runs in the host process.
Summary
What happened
Improper signature verification in OpenSSL Encrypt before 1.4.9 allows attackers to execute malicious plugins via revoked or expired keys. gpg_runner.verify_detached accepts VALIDSIG output without rejecting REVKEYSIG, EXPKEYSIG, EXPSIG, failed status lines, or a nonzero GPG exit code. An attacker must control a compromised-then-revoked signing key or an expired project key; accepted plugin code runs in the host process.
The record
- CVE
- CVE-2026-81700
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- jahlives
- Product
- OpenSSL Encrypt
- Classifications
- CWE-347
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 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.9
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