Quick answers
- Is CVE-2026-97056 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-97056 being exploited in the wild.
- How severe is CVE-2026-97056?
- Medium severity, with a CVSS score of 6.8, published 24 September 2026.
- Which products and versions are affected?
- Signoz v0.98.0 to v0.142.x.
- Is there a fix for CVE-2026-97056?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-97056 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-97056?
- Check whether you run Signoz at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the password reset (UpdatePasswordByResetPasswordToken via POST /api/v2/factor_password/reset) and user deletion (DeleteUser via DELETE /api/v2/users/{id}) code paths, which fail to call the tokenizer's DeleteTokensByUserID function when using the opaque session tokenizer. This leaves cached tokens and session identities in place, allowing token reuse even after access should be revoked. The issue only affects deployments explicitly configured to use the opaque tokenizer and is fixed in v0.143.0.
Affected products
- SigNoz SigNoz v0.98.0 to v0.142.x
Timeline
- 2026-09-24: disclosed