Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-71485 – Authentication Bypass via Header Spoofing – Centrifugo <= 6.8.4

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-71485 is a critical authentication bypass vulnerability (CWE-290: Authentication Bypass by Spoofing) affecting Centrifugo, the open-source real-time messaging server, in versions prior to 6.9.0. The flaw allows a remote, unauthenticated client to forge trusted headers that Centrifugo forwards to backend proxy services, which can result in full identity or authorization spoofing. The issue carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: Centrifugo’s http_headers and grpc_metadata proxy options are meant to forward header/metadata values that originate from trusted transport-level HTTP requests, but the implementation instead copies values from the client-controlled protocol.ConnectRequest.headers map (received directly from the client) into an internal "emulated headers" context used by every proxy call.
  • Affected code paths include the header/metadata construction logic used for HTTP and gRPC proxy backends, as well as the unidirectional gRPC connection handler.
  • Trigger condition: a backend must be configured to trust forwarded headers (e.g., x-trusted-user) for authentication or authorization decisions when using Centrifugo’s connect, refresh, subscribe, publish, or RPC proxy calls.
  • Attack vector: network, no authentication or user interaction required — an attacker simply connects to Centrifugo and supplies arbitrary header values in the client connect command.
  • Impact: high confidentiality and integrity impact (attacker can impersonate trusted users/headers and gain unauthorized access to backend resources); no availability impact.

Affected software

  • Centrifugo (Centrifugal), all versions prior to 6.9.0

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Centrifugo to version 6.9.0 or later, which addresses the header-forwarding logic.
  • If immediate patching is not possible: Do not rely on Centrifugo-forwarded http_headers or grpc_metadata values (e.g., x-trusted-user) for authentication or authorization decisions on backend proxy services, since these values can originate from client-supplied data rather than genuine trusted transport headers. Review proxy backend configurations for any sensitive access-control logic keyed on forwarded headers and disable or restrict such trust until patched.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Centrifugo

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge