CVE-2026-74870: openssl_encrypt before 1.4.8 Hardware Pepper Information Disclosure

Published Aug 17, 2026
·
Updated

opensslencrypt (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 (cryptcli.py, handlehsmcommand). 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 prfdata 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.

Affected Software

1 affected component
pypi/openssl_encrypt<1.4.8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.4.8
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.5.0
  3. Configuration

    In openssl_encrypt versions <= 1.4.7, remove the unconditional printing of the full derived hardware pepper hex in the 'hsm fido2-test' and 'hsm onlykey-test' diagnostic commands (crypt_cli.py, handle_hsm_command) by routing any plugin debug output through the secret-redaction layer (fixed in 1.4.8 and 1.5.0).

    openssl_encrypt (pip) diagnostic commands: 'hsm fido2-test' and 'hsm onlykey-test' (crypt_cli.py, handle_hsm_command) debug output / hex dumps routing through secret-redaction layer = remove hex dumps and route plugin debug output through redaction layer

Event History

Aug 17, 2026
CVE Published
via MITRE·11:04 AM
Data Sourced
via MITRE·11:04 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:16 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-74870?

The severity of CVE-2026-74870 is classified as low with a score of 3.3.

2

What software is affected by CVE-2026-74870?

CVE-2026-74870 affects openssl_encrypt versions before 1.4.8.

3

How do I fix CVE-2026-74870?

To fix CVE-2026-74870, upgrade openssl_encrypt to version 1.4.8 or later.

4

What type of vulnerability is CVE-2026-74870?

CVE-2026-74870 is an information exposure vulnerability.

5

What can be the impact of CVE-2026-74870?

The impact of CVE-2026-74870 can include unauthorized disclosure of the derived hardware pepper value.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203