Skip to content
Noroxi
OSV ecosystem advisory

GHSA-q926-c743-49qj: Centrifugo's InsecureSkipTokenSignatureVerify flag silently disables JWT verification with no warning

CVSS 0.0 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: github.com/centrifugal/centrifugo/v6 (Go) 6.7.0.

Low priority for now. Upgrade to github.com/centrifugal/centrifugo/v6 (Go) 6.7.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

### Summary Centrifugo supports a configuration flag `insecure_skip_token_signature_verify` 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 insecure_skip_token_signature_verify=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`: ``` InsecureSkipTokenSignatureVerify bool `mapstructure:"insecure_skip_token_signature_verify"` ``` It is passed directly to token verification in `internal/client/handler.go`: ``` token, err := h.tokenVerifier.VerifyConnectToken(e.Token, cfg.Client.InsecureSkipTokenSignatureVerify) ``` In `token_verifier_jwt.go`, when `skipVerify=true` the entire signature block is bypassed: ```go if !skipVerify { // This block never executes err = verifier.verifySignature(token) } ``` The flag is configurable via multiple vectors making accidental exposure likely: - Config file: `insecure_skip_token_signature_verify: true` - Environment variable: `CENTRIFUGO_INSECURE_SKIP_TOKEN_SIGNATURE_VERIFY=true` - YAML, TOML config formats Despite `hmac_secret_key` being configured, startup logs show `"enabled JWT verifiers"` — falsely implying verification is active. ### PoC Config with legitimate HMAC key but skip flag enabled: ```json { "client": { "insecure_skip_token_signature_verify": true, "token": { "hmac_secret_key": "legitimate-production-secret-key" } } } ``` Token signed with completely wrong key is fully accepted: ``` VULNERABILITY CONFIRMED! Connected as user: {'client': '899dec73...', 'version': '0.0.0 OSS'} ``` No security warning emitted when insecure_skip_token_signature_verify=true: ![1](https://github.com/user-attachments/assets/606acae0-e6f7-467f-b512-b5350ec6cf38) Token signed with wrong key accepted, authentication bypass confirmed: ![2](https://github.com/user-attachments/assets/a400c0bf-b78c-40cf-8c73-07fdabb0c672) skipVerify flag propagated from config to all token verification calls: ![3](https://github.com/user-attachments/assets/4141eb05-0371-46e1-acb7-8a9091c45693) ### Impact - Any unauthenticated user can connect as any arbitrary user ID - Complete authentication bypass — attacker sets any `sub` claim value - No indicators in logs that the server is operating insecurely - Easily triggered accidentally via environment variable injection in containerized deployments (e.g. misconfigured Kubernetes secrets) - Affects all connection types: WebSocket, HTTP-streaming, SSE, GRPC ### Suggested Fix 1. Emit a loud startup warning when flag is enabled: ```go if cfg.Client.InsecureSkipTokenSignatureVerify { log.Warn().Msg("SECURITY WARNING: JWT signature verification is " + "DISABLED via insecure_skip_token_signature_verify - " + "DO NOT use in production!") } ``` 2. Consider requiring an additional explicit `insecure_mode: true` flag to prevent accidental single-flag misconfiguration 3. Log a warning on every accepted token when skip is active

Published
Mar 13, 2026
Updated
Mar 27, 2026
EPSS
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · 0.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-q926-c743-49qj

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
Gogithub.com/centrifugal/centrifugo/v6
Gogithub.com/centrifugal/centrifugo
Gogithub.com/centrifugal/centrifugo/v3
Gogithub.com/centrifugal/centrifugo/v4
Gogithub.com/centrifugal/centrifugo/v5

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/centrifugal/centrifugofrom 0—
Gogithub.com/centrifugal/centrifugoup to and including 2.4.0—
Gogithub.com/centrifugal/centrifugo/v3from 0—
Gogithub.com/centrifugal/centrifugo/v3up to and including 3.2.3—
Gogithub.com/centrifugal/centrifugo/v4from 0—
Gogithub.com/centrifugal/centrifugo/v4up to and including 4.1.5—
Gogithub.com/centrifugal/centrifugo/v5from 0—
Gogithub.com/centrifugal/centrifugo/v5up to and including 5.4.9—
Gogithub.com/centrifugal/centrifugo/v6before 6.7.06.7.0

Same product

Go: all records

Other highest-scoring records for the same primary product.

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/centrifugal/centrifugo/v66.7.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:N

osv

References

All records