Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-97055— SigNoz before 0.143.0 Authentication Bypass via Empty JWT Secret

Quick assessment

Affected
SigNoz signoz
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

在 SigNoz v0.8.0 至 v0.143.0（不含 v0.143.0）版本中，JWT 令牌签发密钥（tokenizer::jwt::secret，可通过环境变量 SIGNOZ_TOKENIZER_JWT_SECRET 或已弃用的 SIGNOZ_JWT_SECRET 设置）默认被设置为空字符串。同时，Config.Validate() 函数并未拒绝该空值，导致未配置密钥的部署实例能够正常启动，并使用空的 HMAC 密钥对会话令牌进行签发和验证。由于 JWT 令牌提供者是默认选项，所有此类部署均受到影响。 未认

CVSS 8.1 · High EPSS 0.41% · P32

Affected Version Matrix 2

VendorProduct Version RangeStatus
SigNoz signoz 0.8.0< 0.143.0 affected
0.143.0 unaffected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-97055

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
SigNoz before 0.143.0 Authentication Bypass via Empty JWT Secret
Source: CVE Program / CVE List V5
Vulnerability Description
SigNoz from v0.8.0 before v0.143.0 defaults the JWT tokenizer signing secret (tokenizer::jwt::secret, set via SIGNOZ_TOKENIZER_JWT_SECRET or the deprecated SIGNOZ_JWT_SECRET) to an empty string, and Config.Validate() does not reject the empty value, so a deployment that does not configure a secret starts up and both signs and verifies session tokens with an empty HMAC key. Because the JWT tokenizer was the default provider, any such deployment is affected. An unauthenticated attacker who knows the ID of an existing user can forge a valid session token for that user — including an administrator — by signing the id, orgId and email claims with an empty key; the organization ID (and whether an email is registered) can be obtained without authentication from /api/v2/sessions/context. A forged refresh token can be exchanged at /api/v2/sessions/rotate for a new token pair and cannot be revoked, so it remains usable for its full lifetime (30 days by default). Fixed in v0.143.0, which requires a JWT secret when the jwt provider is selected and changes the default provider to opaque.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
不安全的默认资源初始化
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
SigNoz signoz 0.8.0 ~ 0.143.0 -

II. Public POCs for CVE-2026-97055

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-97055

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-97055 (2)

Vendor Advisories for CVE-2026-97055 (2)

IV. Related Vulnerabilities

Same product: signoz
Same vendor: SigNoz
Same weakness: CWE-1188

V. Comments for CVE-2026-97055

No comments yet

Leave a comment