Advisory record · GHSA-9468-v6mj-fppw

Centrifugo: Client-forgeable headers emulation lets any client spoof headers forwarded to proxy backends

CVSS 9.1 CriticalCriticalEPSS 0.0061 · 49th percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 2 Sept 2026, 23:41 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/centrifugal/centrifugoGo<6.9.06.9.0
Identifiers
GHSA-9468-v6mj-fppw · CVE-2026-71485 · GO-2026-6490
Weakness (CWE)
CWE-290
Published
2 Sept 2026
Updated
28 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The Centrifugo package (Go module github.com/centrifugal/centrifugo) before 6.9.0 lets a connecting client supply header values through its own connect message, and those values are forwarded to proxy backends under names the operator has allowlisted as trusted. An unauthenticated attacker who can connect directly to Centrifugo can therefore impersonate identities the backend trusts, for every proxy call type. Upgrade to 6.9.0 or later. Operators who rely on forwarded headers for access control should not treat them as trustworthy until the fix is applied.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.1 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0061, the 49th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:12 UTC First seen by agentprime
  2. 31 Oct 2026, 14:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.