CVE-2026-97056

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 6.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.8
EG Score
6.8(low)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity68% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

September 24, 2026

Last Modified

September 24, 2026

Advisory Details (5)

Auto-updated Sep 24, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
generic

SigNoz before 0.143.0 Insufficient Session Expiration Authentication Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/signoz-before-0.143.0-insufficient-session-expiration-authentication-bypass
github_commit

commit b02aae2db3 (SigNoz/signoz)

Fix landed in SigNoz/signoz commit b02aae2db3 — awaiting tagged release

https://github.com/SigNoz/signoz/commit/b02aae2db3
github_commit

commit e2e9173986 (SigNoz/signoz)

Fix landed in SigNoz/signoz commit e2e9173986 — awaiting tagged release

https://github.com/SigNoz/signoz/commit/e2e9173986
github_commit

commit faaed20dbd (SigNoz/signoz)

Fix landed in SigNoz/signoz commit faaed20dbd — awaiting tagged release

https://github.com/SigNoz/signoz/commit/faaed20dbd
github Patch Available🟡 PoC Available

Authenticated insufficient session expiration after password reset and user deletion · Advisory · SigNoz/signoz · GitHub

https://github.com/SigNoz/signoz/security/advisories/GHSA-xrgp-3fq4-xg83

Vendor Advisories for CVE-2026-97056(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 3× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 02:23 UTCEG score recompute
  2. 2026-09-24 01:57 UTCEG score recompute
  3. 2026-09-24 01:56 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-97056?
CVE-2026-97056 is a medium vulnerability published on September 24, 2026. 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,…
When was CVE-2026-97056 disclosed?
CVE-2026-97056 was first published in the National Vulnerability Database on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-97056?
CVE-2026-97056 has a CVSS v3 base score of 6.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-97056?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-97056, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-97056

Explore →

Is Your Infrastructure Affected by CVE-2026-97056?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs