# CVE-2026-57956: SigNoz < 0.133.0 - Cross-Organization Insecure Direct Object Reference in Alert Rules

> Authenticated users can read, edit, and delete alert rules from other organizations due to missing tenant isolation checks in SigNoz.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-3vgg-7h5g-62mm

## What is CVE-2026-57956?

CVE-2026-57956 is a medium-severity missing authorization vulnerability in signoz, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SigNoz before 0.133.0 contains a broken access control vulnerability that allows authenticated users to access other organizations' alert rules by supplying a target rule UUID, as the alert rule store predicates fail to filter by organization ID. Attackers can read, edit, and delete alert rules belonging to other organizations by exploiting the missing tenant isolation check, bypassing multi-tenant access controls.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-57956 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57956 is a medium-severity missing authorization vulnerability in signoz, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57956 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-57956/ (Markdown: https://insights.sbomify.com/CVE-2026-57956/index.md)
```

## Sources

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

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