Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Centrifugo's InsecureSkipTokenSignatureVerify flag silently disables JWT verification with no warning

GHSA-q926-c743-49qj

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/centrifugal/centrifugo/v5

    Affected
    <= 5.4.9
    Fixed in
    no fixed version recorded

  • Go github.com/centrifugal/centrifugo/v4

    Affected
    <= 4.1.5
    Fixed in
    no fixed version recorded

  • Go github.com/centrifugal/centrifugo/v3

    Affected
    <= 3.2.3
    Fixed in
    no fixed version recorded

  • Go github.com/centrifugal/centrifugo/v6

    Affected
    <= 6.6.2
    Fixed in
    6.7.0

  • Go github.com/centrifugal/centrifugo

    Affected
    <= 2.4.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary Centrifugo supports a configuration flag insecureskiptokensignatureverify that completely disables JWT signature verification. When enabled, Centrifugo accepts any JWT token regardless of signature validity — including tokens signed with wrong keys, random signatures, or no signature at all. Critically, no warning is logged at startup or runtime when this flag is active, making it invisible to operators and security auditors. Note: This vulnerability requires the operator to have explicitly set insecureskiptokensignatureverify=true. The core issue is the absence of any warning when this flag is active, making accidental production exposure undetectable. Details The flag is defined in internal/configtypes/types.go: It is passed directly to token verification in internal/client/handler.go: In tokenverifierjwt.go, when skipVerify=true the entire signature block is bypassed: The flag is configurable via multiple vectors making accidental exposure likely: - Config file:…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-q926-c743-49qj

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-q926-c743-49qj

Advisory: Centrifugo's InsecureSkipTokenSignatureVerify flag silently disables JWT verification with no warning
IDs: GHSA-q926-c743-49qj
Record: https://patchnext.com/advisories/ghsa-q926-c743-49qj (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/centrifugal/centrifugo/v6 6.7.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/centrifugal/centrifugo/v5: affected <= 5.4.9
- Go github.com/centrifugal/centrifugo/v4: affected <= 4.1.5
- Go github.com/centrifugal/centrifugo/v3: affected <= 3.2.3
- Go github.com/centrifugal/centrifugo/v6: affected <= 6.6.2; fixed in 6.7.0
- Go github.com/centrifugal/centrifugo: affected <= 2.4.0

## Suggested inspection (read-only)
- Go github.com/centrifugal/centrifugo/v5: check the installed version with your package manager.
- Go github.com/centrifugal/centrifugo/v4: check the installed version with your package manager.
- Go github.com/centrifugal/centrifugo/v3: check the installed version with your package manager.
- Go github.com/centrifugal/centrifugo/v6: check the installed version with your package manager.
- Go github.com/centrifugal/centrifugo: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/centrifugal/centrifugo/v5, github.com/centrifugal/centrifugo/v4, github.com/centrifugal/centrifugo/v3, github.com/centrifugal/centrifugo/v6, github.com/centrifugal/centrifugo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q926-c743-49qj (GitHub-reviewed advisory GHSA-q926-c743-49qj lists affected ranges: Go github.com/centrifugal/centrifugo/v6 >=0 =0 =0 =0 =0 <=5.4.9)

Commands are suggestions: review each one before running it.

Loading voting…