Skip to main content

openssl-encrypt CVE-2026-81684

| EUVDEUVD-2026-67040 MEDIUM
Invocation of Process Using Visible Sensitive Information (CWE-214)
2026-08-27 VulnCheck GHSA-82vg-rggx-556v
6.9
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local shell on target host
  2. Delivery
    Monitor /proc for openssl-encrypt child subprocess
  3. Exploit
    Read /proc/<pid>/cmdline during subprocess lifetime
  4. Execution
    Extract plaintext --stego-password value
  5. Impact
    Access or decrypt steganographically hidden data

Vulnerability Assessment

Weakness
CWE
Exploitation Conditions

Exploitation requires an existing local user account on the Linux host where openssl-encrypt is installed. The vulnerable condition is triggered exclusively when a user operates the openssl-encrypt desktop GUI and initiates an encrypt or decrypt operation that involves the steganography feature - the --stego-password argument is only passed when this feature is actively used. The exploit window is limited to the subprocess lifetime of that operation, typically seconds, requiring the attacker to monitor /proc continuously. The main encryption password is passed via environment variable and is not exposed. The vulnerability does not apply to CLI-only usage that bypasses the GUI, to Windows deployments where /proc is unavailable, or to any operation that does not invoke the steganography password feature. Exploitation is bounded to shared-access Linux hosts where at least one other local account exists alongside the victim.

Impact

The CVSS 4.0 score of 6.9 with vector AV:L/AC:L/AT:N/PR:N/UI:N reflects a locally exploitable confidentiality-only vulnerability. The local attack vector (AV:L) is the primary risk constraint: an attacker must already possess an active session on the affected host. Once local access exists, no special privileges, configurations, or victim interaction are required to read /proc entries - AC:L and PR:N are accurate. The practical difficulty is the narrow exploit window: the steganography password is only exposed for the duration of the child subprocess (typically seconds), requiring the attacker to poll /proc continuously or use filesystem event monitoring (e.g., inotifywait) to catch the entry before it disappears. This timing dependency makes opportunistic exploitation harder than raw CVSS metrics suggest, though a determined local attacker with a persistent script would find this reliably exploitable. The vulnerability is not in CISA KEV and no public proof-of-concept has been identified, consistent with its local-only, narrow-window character. The impact is the full disclosure of the steganography password, which may completely undermine the confidentiality model of the steganographic operation - the purpose of steganography is concealment, so password disclosure defeats that purpose entirely regardless of CVSS score. Multi-user systems where openssl-encrypt is deployed are the realistic risk scenario.

Exploit ScenarioDerived

A local attacker with a shell session on a multi-user Linux host runs a polling loop against /proc watching for an openssl-encrypt child process, then reads /proc/<pid>/cmdline during that subprocess's lifetime to extract the --stego-password value in plaintext. The entire attack is achievable with standard Linux utilities (e.g., grep -r stego-password /proc/*/cmdline on a polling loop) and requires no elevated privileges. No public proof-of-concept code has been identified, but the technique requires no specialized knowledge.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 27, 2026

Local information disclosure in the openssl-encrypt pip package (versions ≤ 1.4.8) exposes steganography passwords to all unprivileged users on the same Linux host. When the desktop GUI initiates an encrypt or decrypt operation involving the steganography feature, it spawns a CLI child process with the password supplied as the --stego-password command-line argument rather than via an environment variable, making it readable from /proc/<pid>/cmdline for the entire subprocess lifetime by any local user. The main encryption password is handled correctly via environment variable and is unaffected. A vendor-released patch is available in version 1.4.9; no public exploit has been identified at time of analysis.

RemediationAI

Upgrade openssl-encrypt to version 1.4.9 or later, which resolves the issue by routing the steganography password through an environment variable consistent with the existing handling of the main password. The vendor advisory at https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-rx2c-m92f-qv6p confirms the fix. If immediate upgrade is not possible, the most effective compensating control is to ensure that only the user who runs the openssl-encrypt GUI has a local account on the host, eliminating any other user who could read /proc - though this may be impractical in shared or multi-user environments. As a second compensating control, avoid using the steganography feature until patched, since the main encryption password path is unaffected and the vulnerability is triggered only by steganographic encrypt/decrypt operations. Running the application inside a single-tenant container or VM with no other local accounts also eliminates the exposure with no trade-offs for functionality.

Affected VersionsENISA

openssl_encrypt 0 <1.4.9

Affected Packages

pypi openssl-encrypt fix: 1.4.9

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in pypi

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-214 (Sensitive Information in Process Environment) describes the root cause: process command-line arguments on Linux are stored in /proc/<pid>/cmdline, a world-readable pseudo-file accessible to all local users without any elevated privileges. The openssl-encrypt pip package (CPE: cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:*:*:*) provides a desktop GUI wrapper around OpenSSL-based encryption and steganographic hiding of data. The design inconsistency is that the developer correctly passes the main password via environment variable - which is not exposed in /proc by default - but passes the steganography password (--stego-password) as a positional CLI argument to the child process. This inconsistency suggests the secure-handling pattern was applied to one credential path and forgotten for the other. The attack window is transient, bounded by the subprocess lifetime of the encryption or decryption operation.

Know when OpenSSL gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 6.9 MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 5.5 MEDIUM

Local vector, low complexity; no attacker privileges needed to read /proc, but victim must actively run the GUI and invoke the steganography feature for the subprocess to exist.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
4.0 AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Aug 27, 2026 - 18:02 EUVD
CVE Published
Aug 27, 2026 - 14:50 cve.org
MEDIUM 6.9

DescriptionCVE.org

In openssl_encrypt (pip package openssl-encrypt) versions <= 1.4.8, the desktop GUI passes the steganography password to the CLI child process on the command line via the --stego-password argument (on both encrypt and decrypt paths) instead of via an environment variable as done for the main password. Any local user can read the steganography password from /proc/<pid>/cmdline for the lifetime of the subprocess. Fixed in 1.4.9.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Rare
niche pip package for GUI steganographic encryption, limited user base
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2014-0160 HIGH POC
7.5 Apr 07

The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe

CVE-2021-3711 CRITICAL POC
9.8 Aug 24

In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Rated cri

CVE-2014-0195 MEDIUM POC
6.8 Jun 05

The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0

CVE-2014-0224 HIGH POC
7.4 Jun 05

OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph

CVE-2016-0800 MEDIUM POC
5.9 Mar 01

The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to se

CVE-2015-0204 MEDIUM POC
4.3 Jan 09

The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k

CVE-2022-2068 HIGH
7.3 Jun 21

In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehas

CVE-2015-4000 LOW POC
3.7 May 21

The TLS protocol 1.2 and earlier, when a DHE_EXPORT ciphersuite is enabled on a server but not on a client, does not pro

CVE-2014-3566 LOW POC
3.4 Oct 15

The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which mak

CVE-2016-2107 MEDIUM POC
5.9 May 05

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a

CVE-2015-1793 MEDIUM POC
6.5 Jul 09

The X509_verify_cert function in crypto/x509/x509_vfy.c in OpenSSL 1.0.1n, 1.0.1o, 1.0.2b, and 1.0.2c does not properly

CVE-2022-3602 HIGH
7.5 Nov 01

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Rated hig

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy