Summary
CVE-2026-63094 is a high-severity open redirect vulnerability (CWE-601) in SigNoz, an open-source, OpenTelemetry-native observability platform, affecting all versions through 0.133.0. The flaw resides in the SSO authentication flow and allows unauthenticated remote attackers to steal victims’ access and refresh tokens by delivering a crafted login URL, enabling full account takeover on any instance configured with Google OAuth, SAML, or OIDC. The vulnerability carries a CVSS v3.1 score of 8.1 (HIGH).
Technical details
- Root cause: The
GET /api/v2/sessions/contextendpoint accepts arefparameter without validation or cryptographic binding. The application embeds this attacker-supplied value directly into the OAuth state, and after a successful SSO login the server appends the victim’s access and refresh tokens to a redirect to that URL. - Trigger conditions: The instance must have SSO configured — Google OAuth (available in all editions including Community), SAML, or OIDC (available in Cloud and Enterprise Self-Hosted editions). SSO is a non-default, operator-configured feature.
- Attack vector: An unauthenticated attacker calls the
/api/v2/sessions/contextendpoint withrefset to an attacker-controlled host, obtaining a fully-formed crafted login URL. The attacker delivers this URL to a target user (e.g., via phishing). When the victim completes SSO authentication normally, the server redirects their browser to the attacker’s domain and appends the session credentials as URL parameters. - Impact: Complete theft of the victim’s access and refresh tokens, enabling the attacker to hijack the victim’s SigNoz session and perform any action the victim is authorized to perform — including accessing telemetry data, alert rules, dashboards, and administrative settings. The CVSS v4.0 vector reflects high confidentiality and integrity impact on the victim account (VC:H/VI:H).
Affected software
- SigNoz (signoz): all versions from 0 through 0.133.0 (inclusive)
- Community Edition: Google OAuth SSO is available and affected
- SigNoz Cloud and Enterprise Self-Hosted: Google OAuth, SAML, and OIDC are all affected
Severity
- CVSS v3.1 Base Score: 8.1 (HIGH)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
- Vector:
- CVSS v4.0 Score: 7.6 (HIGH)
- Vector:
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Vector:
Mitigation and recommended actions
- No patched release is currently available. As of July 17, 2026, version 0.133.0 is the latest release and remains vulnerable. A fix (PR #11844) implementing allowlist validation of the
refparameter and HMAC-SHA256 signing of OAuth state is under review in the SigNoz repository. - Immediate workaround — disable or restrict SSO: If SSO is not operationally required, disable it in Organization Settings until a patched version is available. This eliminates the attack surface entirely.
- Network-level control: Restrict access to the
/api/v2/sessions/contextendpoint at the network perimeter or reverse proxy layer so it is not reachable from untrusted networks. - User awareness: Alert users on SSO-enabled instances to treat any unexpected SigNoz login link with suspicion, particularly links received via email or messaging platforms.
- Monitor for patch: Track the SigNoz GitHub repository and changelog for a release that includes the fix from PR #11844. Upgrade immediately upon release.
IONIX Status
The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

