CVE-2026-74870: Insertion of Sensitive Information into Log File in jahlives openssl_encrypt
openssl_encrypt (pip) versions <= 1.4.7 contain an information exposure vulnerability where the 'hsm fido2-test' and 'hsm onlykey-test' diagnostic commands unconditionally print the full derived hardware pepper as hex to stdout/stderr (crypt_cli.py, handle_hsm_command). The printed value can persist in terminal scrollback, session recordings, or CI logs. Impact is limited because the pepper is derived from a random per-invocation test salt and is salt-bound, so the leaked value cannot be used to decrypt real files. A related plugin issue logged raw prf_data outside the secret-redaction path. Fixed in 1.4.8 (and 1.5.0) by removing the hex dumps and routing plugin debug output through the redaction layer.
AI Analysis
Technical Summary
The vulnerability in openssl_encrypt (pip) versions <= 1.4.7 involves the 'hsm fido2-test' and 'hsm onlykey-test' diagnostic commands unconditionally printing the full derived hardware pepper as hex to stdout/stderr in crypt_cli.py's handle_hsm_command. This sensitive information exposure can result in the pepper value persisting in terminal scrollback, session recordings, or CI logs. However, the leaked pepper is derived from a random per-invocation test salt and is salt-bound, so it cannot be used to decrypt actual files. Additionally, a related plugin issue logged raw prf_data outside the secret-redaction path. The vulnerability was addressed in versions 1.4.8 and 1.5.0 by removing the hex dumps and ensuring plugin debug output passes through the redaction layer.
Potential Impact
Sensitive derived hardware pepper values are exposed in logs and terminal output, which could lead to information leakage. However, the impact is limited because the leaked pepper is based on a random test salt and cannot be used to decrypt real encrypted data. There is no indication of privilege escalation or direct compromise from this vulnerability.
Mitigation Recommendations
A fix is available in openssl_encrypt versions 1.4.8 and 1.5.0 that removes the hex dumps of sensitive data and routes debug output through a redaction layer. Users should upgrade to at least version 1.4.8 to remediate this vulnerability. No other mitigation steps are indicated.
CVE-2026-74870: Insertion of Sensitive Information into Log File in jahlives openssl_encrypt
Description
openssl_encrypt (pip) versions <= 1.4.7 contain an information exposure vulnerability where the 'hsm fido2-test' and 'hsm onlykey-test' diagnostic commands unconditionally print the full derived hardware pepper as hex to stdout/stderr (crypt_cli.py, handle_hsm_command). The printed value can persist in terminal scrollback, session recordings, or CI logs. Impact is limited because the pepper is derived from a random per-invocation test salt and is salt-bound, so the leaked value cannot be used to decrypt real files. A related plugin issue logged raw prf_data outside the secret-redaction path. Fixed in 1.4.8 (and 1.5.0) by removing the hex dumps and routing plugin debug output through the redaction layer.
CVSS v4.0
Score 8.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in openssl_encrypt (pip) versions <= 1.4.7 involves the 'hsm fido2-test' and 'hsm onlykey-test' diagnostic commands unconditionally printing the full derived hardware pepper as hex to stdout/stderr in crypt_cli.py's handle_hsm_command. This sensitive information exposure can result in the pepper value persisting in terminal scrollback, session recordings, or CI logs. However, the leaked pepper is derived from a random per-invocation test salt and is salt-bound, so it cannot be used to decrypt actual files. Additionally, a related plugin issue logged raw prf_data outside the secret-redaction path. The vulnerability was addressed in versions 1.4.8 and 1.5.0 by removing the hex dumps and ensuring plugin debug output passes through the redaction layer.
Potential Impact
Sensitive derived hardware pepper values are exposed in logs and terminal output, which could lead to information leakage. However, the impact is limited because the leaked pepper is based on a random test salt and cannot be used to decrypt real encrypted data. There is no indication of privilege escalation or direct compromise from this vulnerability.
Mitigation Recommendations
A fix is available in openssl_encrypt versions 1.4.8 and 1.5.0 that removes the hex dumps of sensitive data and routes debug output through a redaction layer. Users should upgrade to at least version 1.4.8 to remediate this vulnerability. No other mitigation steps are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-17T10:31:04.593Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a82f001bf8831d539c482dd
Added to database: 08/17/2026, 11:26:57 UTC
Last enriched: 08/17/2026, 11:56:23 UTC
Last updated: 08/17/2026, 17:19:14 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.