SigNoz before 0.143.0 Insufficient Session Expiration Authentication Bypass (CVE-2026-97056) | HOL Guard CVE

High · CVSS 7.6CVE-2026-97056

SigNoz before 0.143.0 Insufficient Session Expiration Authentication Bypass

Answer in brief

CVE-2026-97056 records a High severity (CVSS 7.6) vulnerability in SigNoz before 0.143.0 Insufficient Session Expiration Authentication Bypass. The current sources do not mark it as known exploited. The current feed maps SigNoz/signoz (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 24, 2026Updated Sep 24, 2026Source checked Sep 24, 2026First seen by HOL Sep 24, 2026Material review Sep 24, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.6
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps SigNoz/signoz (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
SigNoz/signozgeneric	>=0.98.0 <0.143.0	0.143.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for SigNoz/signoz.
Review the reported fix. Update SigNoz/signoz to 0.143.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 24, 2026

Sources and claim methodology

Upstream source description

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 before v0.143.0), do not revoke a user's existing login sessions when the user's password is reset with a reset token (UpdatePasswordByResetPasswordToken, reachable via POST /api/v2/factor_password/reset) or when the user is deleted (DeleteUser, reachable via DELETE /api/v2/users/{id}). Neither code path calls the tokenizer's DeleteTokensByUserID, so cached tokens and identities are left in place. An attacker who already holds a session token for the account — for example from a stolen browser session or from a user being offboarded — retains the account's full access, up to administrator, after a password reset until the token reaches its configured maximum lifetime (30 days by default), and after user deletion until the token next rotates (30 minutes by default). This defeats password reset and user deletion as a means of terminating access. The issue is fixed in v0.143.0.

Quoted source text, attributed separately from HOL analysis.