Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-97056 medium CVSS 6.8

Vulnerability in SigNoz (CVE-2026-97056)

Summary

Vulnerability in SigNoz (CVE-2026-97056). Confidential information can be exposed externally. Exploitable via POST /api/v2/factor_password/reset. Mitigation: upgrade to 0.143.0 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-97056 has been found in SigNoz.
Attackers can target a specific entry point like POST /api/v2/factor_password/reset over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade SigNoz to 0.143.0 or later.
If unsure, ask your IT team or search "SigNoz CVE-2026-97056" on the vendor's site.

CVE-2026-97056 (SigNoz) — CWE-613 / CVSS v3 6.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v2/factor_password/reset / DELETE /api/v2/users/{id}
Patched: 0.143.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-613) exists in SigNoz. Attackers reach the vulnerable code path via POST /api/v2/factor_password/reset.

📍 Affected scope

Check the vendor advisory for the affected versions of SigNoz. Attack surface: POST /api/v2/factor_password/reset / DELETE /api/v2/users/{id}.

🔥 Severity

Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.143.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/v2/factor_password/reset requests with malformed payloads or SQL meta-characters. Run grep -r 'SigNoz' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'SigNoz' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で SigNoz を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /api/v2/factor_password/reset' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/v2/factor_password/reset への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade SigNoz to 0.143.0

    ステージング環境で 0.143.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/v2/factor_password/reset on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details