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… (CVE-2026-97056)
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.
AI Analysis
Technical Summary
In SigNoz versions >=0.98.0 and <0.143.0, when the opaque session tokenizer is enabled (not the default before 0.143.0), the system fails to call DeleteTokensByUserID during password reset or user deletion. Consequently, cached session tokens remain valid, allowing an attacker who already holds a session token to maintain full access to the account, including administrative privileges, after a password reset or user deletion. The default maximum token lifetime is 30 days for password reset and 30 minutes for user deletion token rotation. This vulnerability undermines the effectiveness of password reset and user deletion as methods to terminate access. The flaw is addressed in SigNoz version 0.143.0.
Potential Impact
An attacker with an existing session token can retain full access to a user's account, including administrative rights, even after the user resets their password or is deleted. This persistence of access lasts until the session token expires or rotates, which can be up to 30 days for password resets and 30 minutes for user deletions. This compromises account security by defeating standard access termination mechanisms.
Mitigation Recommendations
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.
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… (CVE-2026-97056)
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.
CVSS v3.1
Score 6.8medium
Affected software
pkg:github/signoz/signozRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In SigNoz versions >=0.98.0 and <0.143.0, when the opaque session tokenizer is enabled (not the default before 0.143.0), the system fails to call DeleteTokensByUserID during password reset or user deletion. Consequently, cached session tokens remain valid, allowing an attacker who already holds a session token to maintain full access to the account, including administrative privileges, after a password reset or user deletion. The default maximum token lifetime is 30 days for password reset and 30 minutes for user deletion token rotation. This vulnerability undermines the effectiveness of password reset and user deletion as methods to terminate access. The flaw is addressed in SigNoz version 0.143.0.
Potential Impact
An attacker with an existing session token can retain full access to a user's account, including administrative rights, even after the user resets their password or is deleted. This persistence of access lasts until the session token expires or rotates, which can be up to 30 days for password resets and 30 minutes for user deletions. This compromises account security by defeating standard access termination mechanisms.
Mitigation Recommendations
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.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-r949-5536-p6gg
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-97056"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6ab4be16f7a7c54106eee3cc
Added to database: 09/24/2026, 06:07:18 UTC
Last enriched: 09/24/2026, 06:11:42 UTC
Last updated: 09/25/2026, 01:47:46 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.