CVE-2026-97056: SigNoz versions from v0.98.0 up to (but not including) v0.143.0, when configured to use the opaque session tokenizer (which was not the default
Affects signozSource GCVE Database
Not known to be exploited · CVSS 6.8 Medium : upgrade to 0.143.0 when convenient.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% 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:L/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Upgrade signoz/signoz to 0.143.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubsignoz/signozpkg:github/signoz/signozOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to SigNoz version 0.143.0 or later, where this issue is fixed. Prior to upgrading, be aware that password resets and user deletions do not revoke existing session tokens when using the opaque session tokenizer. No other mitigation is indicated by the vendor advisory.
Description
SigNoz versions from 0.98.0 up to but not including 0.143.0, when configured to use the opaque session tokenizer, do not revoke existing user login sessions upon password reset or user deletion. This allows an attacker with an existing session token to retain full account access after these actions until the token expires or rotates. The issue is fixed in version 0.143.0.
References
- github.com/SigNoz/signoz/security/advisories/GHSA-xrgp-3fq4-xg83 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-97056 (opens in a new tab)
- github.com/SigNoz/signoz/commit/b02aae2db3 (opens in a new tab)
- github.com/SigNoz/signoz/commit/c122bc09b4 (opens in a new tab)
- github.com/SigNoz/signoz/commit/e2e9173986 (opens in a new tab)
- github.com/SigNoz/signoz/commit/faaed20dbd (opens in a new tab)
- vulncheck.com/advisories/signoz-before-0.143.0-insufficient-session-expiration-authentication-bypass (opens in a new tab)