External risk intelligence

Armeria-xds TLS Peer Verification Bypass Allows Man-in-the-Middle Attacks

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-11751

The vulnerability affects xDS upstream TLS peer verification within a library. xDS is typically used for internal service-to-service communication or sidecar-to-control-plane traffic in service mesh deployments, which are usually isolated within internal network segments rather than exposed directly to the public internet.

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been found in the Armeria-xDS library that could allow attackers to bypass security checks for connections between services. This could potentially enable man-in-the-middle attacks on these internal communications.

  • Security checks for internal connections can be bypassed.
  • Confirm if this internal communication library is in use.
  • Understand exposure and relevance to your services.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by intercepting traffic to services that rely on Armeria's xDS functionality. By triggering a specific condition, the attacker could bypass TLS verification, enabling them to perform man-in-the-middle attacks on connections managed by xDS. This could lead to the exposure of sensitive data or the manipulation of communication between services.

  • Attacker needs network access.
  • Trigger by establishing xDS-managed connections.
  • Risk of man-in-the-middle attacks.

Live Threat

Current exploitation, exposure, and threat context

When upstream TLS peer verification is not properly performed, man-in-the-middle attacks could intercept traffic between xDS-managed services. This could lead to the exposure of communication content when the vulnerability is present and exploited.

  • xDS-managed upstream connections.
  • TLS peer verification can be bypassed.
  • Interception of service communication.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in armeria-xds impacts secure communication channels, particularly affecting teams managing service meshes or critical internal API gateways. The immediate priority is to inventory where Armeria is deployed, identify critical or exposed instances, and confirm ownership for remediation planning.

  • Own by platform and application teams.
  • Verify upstream TLS peer verification is enabled.
  • Plan remediation based on business criticality.

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 the armeria-xds library used for?

Armeria-xds is a component of the Armeria library that integrates support for xDS protocols. These protocols are commonly used to dynamically configure service meshes and control plane communications. Developers use it to manage how services discover and talk to each other in complex, distributed software environments.

What does CVE-2026-11751 mean for TLS verification?

This vulnerability involves a failure in how the library confirms the identity of a server during a connection attempt. Because TLS peer verification is silently disabled, the software fails to validate that it is talking to the intended, legitimate server. This weakness allows an attacker to intercept or modify traffic between services without being detected.

How can an attacker trigger this vulnerability?

An attacker needs the ability to position themselves between two services communicating over an xDS-managed connection. They trigger the flaw by intercepting the traffic flow. Importantly, simply having the library in the codebase is not enough; the vulnerability only manifests when the application initiates a connection where this faulty verification logic is active.

Is my service at risk if it is not internet-facing?

According to Halo Surface Signal, this vulnerability affects internal service-to-service or sidecar-to-control-plane communication, which is typically isolated. While the risk is generally lower for services hidden from the public internet, you should still evaluate if your internal network architecture sufficiently protects these sensitive communication paths from unauthorized access.

What should I do if I use armeria-xds?

First, verify which services in your environment rely on this library by auditing your dependencies. Once identified, prioritize updating to version 1.41.0 or later to resolve the verification defect. Engage your platform or application teams to confirm these updates are deployed to critical service mesh or API gateway infrastructure.

References