CVE-2026-74870

Hardware-pepper disclosure via diagnostic hex dumps

Published Aug 17, 2026 · Updated Aug 17, 2026

Information exposure in jahlives openssl_encrypt before 1.4.8 allows local users to disclose derived hardware-pepper test output via HSM diagnostics. In openssl_encrypt/modules/crypt_cli.py, handle_hsm_command unconditionally hex-dumps the full derived hardware pepper for the hsm fido2-test and hsm onlykey-test paths, and related code also logged raw prf_data outside the secret-redaction path. Reachability requires the ability to run those diagnostic commands or capture their stdout, stderr, or debug logs, and the consequence is bounded to disclosure of salt-bound test material rather than decryption of real files.

CVSS severity8.7
High
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information exposure in jahlives openssl_encrypt before 1.4.8 allows local users to disclose derived hardware-pepper test output via HSM diagnostics. In openssl_encrypt/modules/crypt_cli.py, handle_hsm_command unconditionally hex-dumps the full derived hardware pepper for the hsm fido2-test and hsm onlykey-test paths, and related code also logged raw prf_data outside the secret-redaction path. Reachability requires the ability to run those diagnostic commands or capture their stdout, stderr, or debug logs, and the consequence is bounded to disclosure of salt-bound test material rather than decryption of real files.

The record

CVE
CVE-2026-74870
Published
Aug 17, 2026
Updated
Aug 17, 2026
Vendor
jahlives
Product
OpenSSL Encrypt
Classifications
CWE-532
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 17, 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.

  1. Affected versionversion=0 <1.4.8

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

jahlives · OpenSSL Encryptversion=0 <1.4.8

Published CVSS scores

3.3NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
8.7GitHub Advisory DatabaseCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-532Insertion of Sensitive Information into Log File

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