External risk intelligence

OpenSSL Encrypt Token Leakage Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-74880

The vulnerability affects keyserver and telemetry server routes which are common, network-accessible endpoints. These types of services are frequently deployed as public-facing API or backend infrastructure, making them reachable over the internet in many standard configurations.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability involves how certain encryption functions handle refresh tokens. If these functions are used in specific server routes, sensitive tokens could be exposed through common web logs and browser data, potentially allowing unauthorized access to systems. The primary concern is to determine if our systems utilize these functions in the described manner.

  • Sensitive tokens can be leaked through web logs.
  • It could grant unauthorized system access.
  • Confirm relevance to our environment and potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker can access sensitive refresh tokens by observing network traffic or server logs. This exposure occurs when the `openssl_encrypt` function, used in keyserver and telemetry routes, improperly accepts refresh tokens directly within URL query parameters. By obtaining these tokens, an attacker can then use them to gain unauthorized access to the system.

  • Tokens exposed in URLs.
  • Network traffic or logs can be intercepted.
  • Leads to unauthorized system access.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow attackers to steal refresh tokens from server logs, proxy logs, browser history, or HTTP Referer headers. If these tokens are successfully exfiltrated, an attacker could use them to gain unauthorized access to systems.

  • Refresh tokens could be exposed.
  • Tokens may leak from logs and headers.
  • Unauthorized system access could occur.

Operational Fix

Recommended remediation, mitigation, and detection steps

The `openssl_encrypt` vulnerability impacts the security of keyserver and telemetry server routes, suggesting that platform or infrastructure teams responsible for these services are the primary owners. The first critical step is to inventory all instances of the affected technology, assess their network exposure, and determine business criticality to prioritize remediation efforts.

  • Platform or infrastructure teams should own.
  • Verify all affected service instances.
  • Plan vendor coordination and patching.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is openssl_encrypt?

openssl_encrypt is a software component often used to handle cryptographic operations within applications. In this specific context, it is integrated into keyserver and telemetry server routes to manage secure data, such as refresh tokens, which are essential for maintaining authenticated user sessions.

What is the vulnerability in CVE-2026-74880?

This vulnerability is classified as CWE-598, which involves the use of HTTP GET requests for sensitive information. Specifically, the affected software incorrectly accepts refresh tokens as URL query parameters. Because URLs are often stored in logs, this design flaw allows sensitive credentials to be written to plaintext files or headers.

How do attackers trigger this token leakage?

The vulnerability is triggered when the application processes a request where a refresh token is included directly in the URL query string. It is important to note that simply visiting a site does not trigger the bug; the system must be actively using the vulnerable route to handle these tokens via URL parameters. Securely sending tokens in the request body instead of the URL would avoid this exposure.

Is my system at risk from CVE-2026-74880?

If you are running the affected software, your risk depends on network connectivity. According to Halo Surface Signal, this vulnerability is particularly significant for keyserver and telemetry routes. If these routes are exposed to the internet, they are highly accessible to external actors; internal-only services with restricted access face a lower immediate risk of external exploitation.

What should I do to address this issue?

Start by identifying all instances of the affected software within your infrastructure, focusing on services that handle keyserver or telemetry functions. Verify if your configuration currently passes tokens via URL parameters. Once identified, prioritize these systems for an update to version 1.4.0 or later to resolve the improper handling of these sensitive credentials.

References