Skip to main content
VulnerabilityPublished

CVE-2026-97055: 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

Affects signozSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.1 High · fixed in 0.143.0 : patch signoz soon.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.143.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubsignoz/signozpkg:github/signoz/signozOther threatsAffected–Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in SigNoz version 0.143.0, which requires a JWT secret when the JWT provider is selected and changes the default token provider to opaque tokens. Users should upgrade to version 0.143.0 or later to remediate this vulnerability. Until upgraded, ensure that the JWT signing secret is explicitly configured to a non-empty value to prevent exploitation.

Description

SigNoz versions from 0.8.0 up to but not including 0.143.0 have a vulnerability where the JWT tokenizer signing secret defaults to an empty string if not configured. This allows an unauthenticated attacker who knows a user ID to forge valid session tokens, including for administrators, by signing claims with an empty key. The vulnerability also permits token refresh without revocation, enabling continued unauthorized access. The issue is fixed in version 0.143.0, which enforces a required JWT secret and changes the default token provider.

References

Community reviews

Loading reviews…