CVE-2026-81715
Last modified
CVE-2026-81715 is a low-severity vulnerability rated 3.3/10 on the CVSS scale. 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. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
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/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
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| jahlives | openssl_encrypt | < 1.4.9 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-81715?
How severe is CVE-2026-81715?
How do I fix CVE-2026-81715?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-81703openssl_encrypt versions before 1.4.9 fail to validate encry…5.5
- CVE-2026-81704openssl_encrypt versions before 1.4.9 contain a weak key der…7.5
- CVE-2026-81705openssl-encrypt before 1.4.9 fails to redact the file passwo…7.5
- CVE-2026-81706openssl_encrypt before 1.4.9 fails to prevent namespace coll…6.8
- CVE-2026-81707openssl_encrypt before 1.4.9 fails to sanitize the email fie…9.8
- CVE-2026-81714openssl_encrypt (pip: openssl-encrypt) versions <= 1.4.8 use…7
- CVE-2026-81716openssl_encrypt (pip: openssl-encrypt) versions before 1.4.9…5.2
- CVE-2026-81717openssl_encrypt (pip package openssl-encrypt) before 1.4.9 c…3.5
- CVE-2026-81718openssl_encrypt versions before 1.4.9 use under-parameterize…7.5
- CVE-2026-81719openssl_encrypt before 1.4.9 executes untrusted third-party …7.8
- CVE-2026-8172The Simple Basic Contact Form WordPress plugin through 20250…7.1
- CVE-2026-81720openssl_encrypt before 1.4.9 fails to validate the memory_co…6.2
Are you affected by CVE-2026-81715?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST