Read the docs
TI-2026-63930 Aliases CVE-2026-97055GHSA-m7r9-jq4r-hmr3

SigNoz before 0.143.0 Authentication Bypass via Empty JWT Secret

Priority HIGH 75CWE-1188Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.0053 45th percentileScored 2026-11-08
Fix Fixed signoz (SigNoz): 0.143.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
SigNozsignoz0.8.0 to before 0.143.00.143.0Patch availableCNA
  • signoz VendorSigNoz Affected 0.8.0 to before 0.143.0 Fixed in 0.143.0 Patch available CNA

Remediation

  • Fix · CNA signoz (SigNoz) Fixed in 0.143.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    signoz 0.143.0

    2 records Highest priority Priority HIGH 2 HIGH

    Other records, highest priority first

    • TI-2026-63931 SigNoz before 0.143.0 Insufficient Session Expiration Authentication BypassPriority HIGH 68
    Show all 2 records →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-97055
  2. 2026-10-03 Alias added: GHSA-m7r9-jq4r-hmr3

References

Patch 2

Advisory 1

  • TI-2026-62489 SigNoz 0.88.0 through 0.141.0 - Missing Authentication on Trace Funnel Analytics Endpoints CVSS 4.0HIGH 8.8
  • TI-2026-62973 SigNoz 0.87.0 before 0.142.0 - SQL Injection in v5 Query Builder Field Key Names CVSS 4.0HIGH 8.4
  • TI-2026-62911 SigNoz 0.88.0 before 0.142.1 - SQL Injection in Trace Funnel Analytics Query Builders CVSS 4.0HIGH 8.4
  • TI-2026-63931 SigNoz before 0.143.0 Insufficient Session Expiration Authentication Bypass CVSS 4.0HIGH 7.6
  • TI-2026-45044 SigNoz < 0.134.0 SSO OAuth State Manipulation Session Token Theft CVSS 4.0HIGH 7.6
  • TI-2026-41722 SigNoz < 0.133.0 - Cross-Organization Insecure Direct Object Reference in Alert Rules CVSS 4.0MEDIUM 6.1
See all 7 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences