# CVE-2026-63094: SigNoz < 0.134.0 SSO OAuth State Manipulation Session Token Theft

> Attackers can steal session tokens via open redirect in SSO flow, leading to account takeover on instances with OAuth or SAML enabled.

- **Severity:** High 7.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-xmw5-w4c2-cp2g

## What is CVE-2026-63094?

CVE-2026-63094 is a high-severity vulnerability in signoz, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SigNoz before 0.134.0 contains an open redirect vulnerability in the SSO authentication flow that allows unauthenticated attackers to steal session tokens from any user on instances configured with Google OAuth, SAML, or OIDC. Attackers can call the unauthenticated sessions context endpoint with a ref parameter pointing to an attacker-controlled host, deliver the resulting crafted login URL to a victim, and receive the victim's access and refresh tokens when they complete SSO authentication.

Weakness: CWE-601 (URL Redirection to Untrusted Site), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-63094?


## How do I fix CVE-2026-63094?

No fix has been published for CVE-2026-63094 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63094 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63094 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63094 and fix it if it is affected.

What it is: CVE-2026-63094 is a high-severity vulnerability in signoz, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63094 exists.

Affected product: signoz. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63094/ (Markdown: https://insights.sbomify.com/CVE-2026-63094/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63094
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63094
- OSV: https://osv.dev/vulnerability/CVE-2026-63094

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63094/
Summaries are generated and may contain mistakes; the official description above is the record.