Is CVE-2026-63094 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63094 being exploited in the wild.

How severe is CVE-2026-63094?

High severity, with a CVSS score of 8.1, published 17 July 2026.

Is there a fix for CVE-2026-63094?

A patch was published on 2026-06-24: Pull request with fix submitted Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-63094 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-63094?

Check whether you run Signoz at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63094: SigNoz open redirect and session token theft in SSO flow

CVE-2026-63094 · Severity: high · CVSS 8.1 · Published 2026-07-17

SigNoz is an open-source observability platform used to monitor application performance. A security flaw in its Single Sign-On (SSO) system allows attackers to create malicious login links that, when clicked by a legitimate user, send that user's private login session tokens directly to the attacker. This could allow an unauthorized person to take over user accounts and access sensitive monitoring data.

Technologies: Signoz. Vendors: SigNoz.

Quick answers

Is CVE-2026-63094 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63094 being exploited in the wild.
How severe is CVE-2026-63094?: High severity, with a CVSS score of 8.1, published 17 July 2026.
Which products and versions are affected?: Signoz through 0.133.0.
Is there a fix for CVE-2026-63094?: A patch was published on 2026-06-24: Pull request with fix submitted Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63094 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-63094?: Check whether you run Signoz at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An open redirect vulnerability exists in the unauthenticated GET /api/v2/sessions/context endpoint due to insufficient validation of the 'ref' parameter. This parameter is embedded into the OAuth state without cryptographic signing or origin allowlisting. An attacker can craft a login URL containing a 'ref' parameter pointing to a malicious domain; when a victim completes the SSO flow (Google, SAML, or OIDC), the SigNoz server appends the victim's access and refresh tokens to the redirect URL. This allows the attacker to exfiltrate session tokens. A fix has been proposed involving HMAC-SHA256 signing of the OAuth state and strict validation of redirect origins.

Affected products

SigNoz SigNoz through 0.133.0

Timeline

2026-05-23: disclosed: Initial report to vendor security email
2026-06-17: disclosed: Public issue opened on GitHub
2026-06-24: patched: Pull request with fix submitted
2026-07-17: advisory: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.