CVE-2026-57956
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSigNoz 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSigNoz before 0.133.0 has a broken access control vulnerability in the alert rule store predicates that fail to filter queries by organization ID. Authenticated attackers can supply arbitrary alert rule UUIDs to access, modify, or delete alert rules belonging to other organizations, bypassing multi-tenant isolation controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify SigNoz installation versionRun the command to check the SigNoz version (commonly: helm list, docker images, or query the frontend/otel-collector version endpoint) and compare it to the affected range: versions 0.130.1 and earlierAffected if Running SigNoz version 0.130.1 or earlier
-
Confirm alert rules feature is in useCheck if any alert rules have been created in the SigNoz instance by querying the alert rules API endpoint or reviewing the database for records in the alert_rules tableAffected if Alert rules exist in the system, making the vulnerable code path reachable
-
Verify multi-organization isolation is configuredCheck if more than one organization exists in the SigNoz deployment by querying the organizations table or APIAffected if Multiple organizations are defined, creating a multi-tenant scenario where the vulnerability applies
-
Inspect alert rule store predicates for organization filteringReview the alert rule store code or database query logs to determine whether alert rule queries include organization_id filtering in their WHERE clauses for GET, UPDATE, and DELETE operationsAffected if Queries against alert_rules table do not filter by organization_id, allowing cross-tenant access
A user is affected if they run SigNoz version 0.130.1 or earlier, have alert rules configured, use multi-organization deployment, and the alert rule store queries lack organization ID filtering.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade SigNoz to version 0.133.0 or later. Until upgraded, monitor and restrict access to the alert rules API endpoints and consider implementing additional network-level isolation between tenants.
SigNoz version 0.133.0
- Upgrade SigNoz to version 0.133.0 or later to obtain the patched code with proper organization ID filtering
- After upgrading, verify that alert rule operations now correctly enforce tenant isolation by testing that users cannot access alert rules from other organizations
- Confirm the alert rule store predicates now include organization ID filtering for all CRUD operations (read, edit, delete)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57956 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57956 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data