Description
openssl_encrypt before 1.4.0 contains an authentication bypass vulnerability in the verify_api_token function that accepts any non-empty Bearer token string without validation. Attackers can upload arbitrary public keys, enumerate all keys, and revoke keys belonging to any user by providing any Bearer token in the Authorization header.
Published: 2026-08-17
Score: 9.3 Critical
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability in openssl_encrypt before version 1.4.0 resides in the verify_api_token function, which mistakenly accepts any non‑empty "Bearer" token without performing validation. This flaw permits an attacker to upload arbitrary public keys, enumerate all existing keys, and revoke keys belonging to any user by simply providing a token in the Authorization header. The result is an authentication bypass that enables unauthorized manipulation of key material and potentially broader access by a malicious actor.

Affected Systems

The affected product is jahlives:openssl_encrypt, version 1.4.0 and earlier.

Risk and Exploitability

The CVSS score of 9.3 reflects a high severity. EPSS is not available, and the vulnerability is not listed in the CISA KEV catalog. The attack vector is inferred to be a simple HTTP request containing a Bearer token; authentication bypass is trivial once the token is provided. The weakness is classified as CWE‑287 (Improper Authentication).

Generated by OpenCVE AI on August 17, 2026 at 13:31 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update jahlives:openssl_encrypt to version 1.4.0 or newer, which includes proper Bearer token validation.
  • If an upgrade cannot be performed immediately, block the API token endpoints that accept public key uploads and enumeration until the vulnerability is patched, or enforce that only pre‑approved tokens are accepted.
  • Verify that all API calls validate the Bearer token against a securely stored list of legitimate tokens before allowing key operations; reject any token that does not match an entry.

Generated by OpenCVE AI on August 17, 2026 at 13:31 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 17 Aug 2026 11:15:00 +0000

Type Values Removed Values Added
Description openssl_encrypt before 1.4.0 contains an authentication bypass vulnerability in the verify_api_token function that accepts any non-empty Bearer token string without validation. Attackers can upload arbitrary public keys, enumerate all keys, and revoke keys belonging to any user by providing any Bearer token in the Authorization header.
Title openssl_encrypt before 1.4.0 Authentication Bypass via Bearer Token
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-17T11:04:56.540Z

Reserved: 2026-08-17T10:42:40.455Z

Link: CVE-2026-74894

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-17T11:16:44.523

Modified: 2026-08-17T11:16:44.523

Link: CVE-2026-74894

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-17T13:45:04Z

Weaknesses