Skip to main content
EPSS 0.3%top 84%

CVE-2026-81715: Insertion of Sensitive Information into Log File in jahlives openssl_encrypt

0
High
VulnerabilityCVE-2026-81715cvecve-2026-81715
Published: 08/27/2026 (08/27/2026, 14:51:10 UTC)
Source: CVE Database V5
Vendor/Project: jahlives
Product: openssl_encrypt

Description

openssl_encrypt (pip package openssl-encrypt) versions <= 1.4.8 do not redact the keyserver bearer token passed as the positional argument to 'keyserver set-token' in the --debug argv dump, because sanitize_argv_for_debug fails to sanitize it. As a result the token is printed in cleartext to stderr under --debug (even without --unsafe-show-secrets), persisting the credential in logs and terminal history. Fixed in 1.4.9.

CVSS v4.0

Score 8.7high

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
None
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Affected software

jahlives

openssl_encrypt

Affected versions
>=0 <1.4.9

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/02/2026, 15:56:52 UTC

Technical Analysis

In the openssl_encrypt package (pip package openssl-encrypt) versions less than 1.4.9, the function sanitize_argv_for_debug fails to sanitize the keyserver bearer token passed as a positional argument to the 'keyserver set-token' command. As a result, when the package is run with the --debug argument, the bearer token is printed in cleartext to stderr, even without the --unsafe-show-secrets flag. This leads to sensitive credential leakage in logs and terminal history. The vulnerability is identified as CVE-2026-81715 and has a CVSS 4.0 score of 8.7 (high severity). The issue is fixed in version 1.4.9.

Potential Impact

Sensitive bearer tokens used for keyserver authentication can be exposed in cleartext in debug output, logs, and terminal history. This exposure could allow unauthorized parties to obtain credentials if they have access to these logs or histories. There is no indication of privilege requirements or user interaction needed, increasing the risk of exposure during debugging. No known exploits in the wild have been reported.

Mitigation Recommendations

Upgrade the openssl_encrypt package to version 1.4.9 or later, where the issue is fixed. Avoid using the --debug flag in production environments or where sensitive tokens are involved until the upgrade is applied. No other mitigations are indicated by the vendor advisory.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-08-27T11:13:14.063Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6a906bbaacd9273b4983a296

Added to database: 08/27/2026, 16:54:18 UTC

Last enriched: 10/02/2026, 15:56:52 UTC

Last updated: 10/11/2026, 06:48:19 UTC

Views: 75

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses