Authenticity-output forgery via unescaped key identifiers
Published Aug 27, 2026 · Updated Aug 27, 2026
Terminal injection in jahlives OpenSSL Encrypt before 1.4.9 allows attackers to forge authenticity output through a crafted encrypted file. detect_encryption_type parses header JSON and prints asymmetric.recipients[].key_id values to stderr without neutralizing terminal control sequences. Exploitation requires the hostile file to be decrypted in an interpreting terminal; the bounded result is deceptive output, not code execution.
Summary
What happened
Terminal injection in jahlives OpenSSL Encrypt before 1.4.9 allows attackers to forge authenticity output through a crafted encrypted file. detect_encryption_type parses header JSON and prints asymmetric.recipients[].key_id values to stderr without neutralizing terminal control sequences. Exploitation requires the hostile file to be decrypted in an interpreting terminal; the bounded result is deceptive output, not code execution.
The record
- CVE
- CVE-2026-81695
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- jahlives
- Product
- OpenSSL Encrypt
- Classifications
- CWE-117, T1036
- Attack vector
- local
- 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?
Published CVSS scores
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.
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