CVE-2026-97055 SigNoz before 0.143.0 Authentication Bypass via Empty JWT Secret

Critical 9.2 Published Updated

Unauthenticated attackers can forge session tokens for any user, including admins, due to a default empty JWT secret, leading to full account takeover.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-97055?

CVE-2026-97055 is a critical authentication bypass vulnerability in signoz, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

SigNoz from v0.8.0 before v0.143.0 defaults the JWT tokenizer signing secret (tokenizer::jwt::secret, set via SIGNOZ_TOKENIZER_JWT_SECRET or the deprecated SIGNOZ_JWT_SECRET) to an empty string, and Config.Validate() does not reject the empty value, so a deployment that does not configure a secret starts up and both signs and verifies session tokens with an empty HMAC key. Because the JWT tokenizer was the default provider, any such deployment is affected. An unauthenticated attacker who knows the ID of an existing user can forge a valid session token for that user — including an administrator — by signing the id, orgId and email claims with an empty key; the organization ID (and whether an email is registered) can be obtained without authentication from /api/v2/sessions/context. A forged refresh token can be exchanged at /api/v2/sessions/rotate for a new token pair and cannot be revoked, so it remains usable for its full lifetime (30 days by default). Fixed in v0.143.0, which requires a JWT secret when the jwt provider is selected and changes the default provider to opaque.

Weakness: CWE-1188

Which versions are affected by CVE-2026-97055?

How do I fix CVE-2026-97055?

No fix has been published for CVE-2026-97055 yet. Limit exposure of the affected software until one is available.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-97055 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-97055 exists.

Sources

Also known as GHSA-c26w-g4j8-39m2, GHSA-m7r9-jq4r-hmr3.

Is CVE-2026-97055 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free