/

CVE-2026-81691

Severity:

HIGH RISK

(7.5)

Cleartext Transmission (CWE-319) in openssl_encrypt

CVE-2026-81691

Analyzed

Vulnerability type

Category:

Cleartext Transmission of Sensitive Information

CWE:

CWE-319

Impact:

Credential Theft and Account Takeover

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

openssl_encrypt versions before 1.4.9 may accept unencrypted HTTP server URLs and hosts that are not configured in the client. An attacker positioned on the network path could intercept login or registration credentials, client identifiers, and JWTs, potentially taking over keyserver accounts.

Affected context

The vulnerability occurs in deployments using affected openssl_encrypt versions where the login or register_with_email functions communicate with a server selected through an HTTP URL or an unconfigured host. The risk depends on whether an attacker can observe or manipulate traffic between the client and the keyserver.

Exploit preconditions

  • Attack surface: Network communication from the client to the keyserver
  • Required access: Position on the network path, such as a compromised network, proxy, or access point
  • Trigger point: Login or email-registration requests sent to an accepted server URL
  • Why exploitation is possible: URL and host validation may permit cleartext HTTP communication, allowing sensitive request and response data to be observed or altered

Why this happens

The underlying issue is insufficient validation of server endpoints before transmitting sensitive authentication data. Accepting HTTP URLs or hosts that are outside the configured trust set can expose credentials and tokens over an unencrypted channel. This maps to CWE-319, where sensitive information is transmitted without adequate protection in transit.

Potential impact

  • An attacker may capture client identifiers and passwords.
  • An attacker could obtain JWTs or other authentication tokens.
  • Captured credentials may enable keyserver account takeover.
  • An attacker could alter requests or responses while traffic is in transit.
  • Compromised accounts may be used to access or modify protected data.

General mitigation guidance

Mitigation generally focuses on enforcing secure endpoint selection and

protecting authentication data in transit.

Common defensive patterns include:

  • Permit only HTTPS endpoints for authentication and registration traffic.
  • Validate server URLs against an explicit, trusted host configuration.
  • Reject unconfigured hosts by default rather than accepting arbitrary endpoints.
  • Centralize endpoint validation so all authentication flows use the same policy.
  • Avoid transmitting credentials or tokens until transport security and host

identity have been established.

  • Apply least privilege and short token lifetimes to limit the consequences of

credential exposure.

How teams detect issues like this

Organizations can detect related risks through:

  • Static analysis rules that identify HTTP URLs in authentication or token flows.
  • Code review checks for missing URL-scheme and allowlist validation.
  • Tests that verify unencrypted URLs and unconfigured hosts are rejected.
  • Network monitoring for cleartext authentication requests and unexpected

keyserver destinations.

  • Policy enforcement that blocks non-TLS outbound connections from sensitive

application components.

Automated code review and dependency-analysis tools may help identify insecure

endpoint handling and affected library usage.

Sources

SourceLink
github.comgithub.com/jahlives/openssl_encrypt/security/advisories/GHSA-xr64-hcxg-4ghr
vulncheck.comvulncheck.com/advisories/openssl-encrypt-before-1.4.9-credential-leakage-via-unvalidated-server-urls

Frequently asked

questions

It can be exploitable by an attacker who can observe or interfere with the

network path used by the client. It does not necessarily require direct access

to the keyserver.

The attacker generally needs a position on the relevant network path, such as

control of a local network, proxy, wireless access point, or other traffic

interception point.

Require HTTPS, validate the server against an explicit trusted-host policy,

and reject HTTP URLs or unconfigured hosts before sending credentials or

tokens.

Treat endpoint configuration as security-sensitive, test rejection of

insecure destinations, monitor for cleartext authentication traffic, and

apply secure transport policies consistently across all authentication flows.

Find out what's already
exploitable in your codebase.