Key substitution via identity name shadowing
Published Aug 27, 2026 · Updated Aug 27, 2026
Identity namespace collision in OpenSSL Encrypt before 1.4.9 allows attackers to substitute contact keys for encrypted files. IdentityStore accepted a contact name already owned by a local identity and kept the colliding contact hidden until that identity was deleted. An attacker able to supply or create the contact entry can then make later recipient resolution select the attacker's keys, silently redirecting encrypted files.
Summary
What happened
Identity namespace collision in OpenSSL Encrypt before 1.4.9 allows attackers to substitute contact keys for encrypted files. IdentityStore accepted a contact name already owned by a local identity and kept the colliding contact hidden until that identity was deleted. An attacker able to supply or create the contact entry can then make later recipient resolution select the attacker's keys, silently redirecting encrypted files.
The record
- CVE
- CVE-2026-81706
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- jahlives
- Product
- OpenSSL Encrypt
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
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?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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
No sourced classifications are available.
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