Security Resilience

CVE-2026-81705

Info Disclosure in Jahlives Openssl Encrypt ≤ 1.4.9

Public PoCInfo Disclosure
Published
27 August 2026
Modified
01 September 2026
Patch / advisory
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0044 38th percentile
Risk Priority 44 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-81705 is a high-severity Insertion of Sensitive Information into Log File (CWE-532) vulnerability in Jahlives Openssl Encrypt. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Local Accounts (T1078.003); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

openssl-encrypt before 1.4.9 fails to redact the file password in its --debug argv dump when the password is supplied via bundled short-option spellings (e.g. -apHunter2) or abbreviated long-option spellings (e.g. --passw). The sanitizer only recognized exact option names, --option=value forms,…

more

and tokens starting with -p, so these spellings bypass the redaction chokepoint and the cleartext password is written to stderr. Anyone with access to that output (terminal scrollback, merged 2>&1 output, CI job logs, or the GUI's persistent debug log) can recover the password.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1078.003 Local Accounts Stealth
Adversaries may obtain and abuse credentials of a local account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
T1552.003 Shell History Credential Access
Adversaries may search the command history on compromised systems for insecurely stored credentials.
T1552.007 Container API Credential Access
Adversaries may gather credentials via APIs within a containers environment.
T1589.001 Credentials Reconnaissance
Adversaries may gather credentials that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-81715Same product: Jahlives Openssl Encrypt
CVE-2026-74870Same product: Jahlives Openssl Encrypt
CVE-2026-74873Same product: Jahlives Openssl Encrypt
CVE-2026-74887Same product: Jahlives Openssl Encrypt
CVE-2026-81699Same product: Jahlives Openssl Encrypt
CVE-2026-74893Same product: Jahlives Openssl Encrypt
CVE-2026-74874Same product: Jahlives Openssl Encrypt
CVE-2026-81694Same product: Jahlives Openssl Encrypt
CVE-2026-81719Same product: Jahlives Openssl Encrypt
CVE-2026-81716Same product: Jahlives Openssl Encrypt

Affected Assets

jahlives
openssl encrypt
≤ 1.4.9

Mitigating Controls

Likely Mitigating Controls

Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-532

Procedures mandate excluding sensitive data from logs to prevent unauthorized exposure via audit records.

addresses: CWE-532

Identifies insertion of sensitive data into logs, allowing detection of unauthorized disclosure.

addresses: CWE-532

Cross-organizational coordination enables agreement on what data to include in audit logs, directly reducing insertion of sensitive information.

addresses: CWE-532

Identifying logging as a data action allows prevention of sensitive information being inserted into log files.

addresses: CWE-532

The process of identifying and eradicating spilled information applies directly to sensitive data inserted into log files.

addresses: CWE-532

Specific processing rules for sensitive PII categories commonly include restrictions on logging, making insertion of such data into log files less likely.

addresses: CWE-532

PIAs detect planned or existing logging of PII and require removal or protection, preventing insertion of sensitive information into logs.

addresses: CWE-532

Limits insertion of sensitive operational details into logs by treating such data as key information requiring protection.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly prohibit writing sensitive data to logs; eliminating the weakness satisfies only one narrow slice of the control.

PR.PS-04 partial match
blocks

Log generation configuration can and should exclude sensitive data, but the control statement focuses on availability rather than content filtering.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

A.8.29's SOURCE reach (SAST, code review) catches the bulk of CWE-532 instances where sensitive data is passed directly to logging calls, and RUNTIME reach (penetration testing) can surface sensitive data in accessible logs; the remainder is bounded and nameable — cases where sensitivity is context-dependent and not flagged by configured rules, and indirect logging patterns (e.g., logging entire objects whose toString() exposes sensitive fields) that SAST rules miss.

prevents

A.8.28 mandates secure coding practices that include guidance on what not to log (sensitive data is exactly the kind of 'common and historical coding practice' the clause names), but the mechanism is human practice — developers must know what counts as sensitive, redact it, and apply that consistently across error paths and third-party libraries. This is the same practice-not-mechanism reading that graded A.8.28 -> CWE-79 and A.8.28 -> CWE-502 at `partial`, and the clause carries a declared ceiling of `partial` on this verb for code-level defects.

References