# CVE-2026-133173: WatchAlert 2.0.0 through 3.9.20 Cross-Tenant IDOR via dataSourceGet API


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-6g3q-qvp2-ggqq

## What is CVE-2026-133173?

CVE-2026-133173 is a high-severity vulnerability in opsre WatchAlert, published on 19 Nov 2026. 

### Official description

WatchAlert 2.0.0 through 3.9.20 contains an insecure direct object reference vulnerability in the /api/w8t/datasource/dataSourceGet endpoint that lets authenticated users read other tenants' datasources because lookups omit tenant_id filtering. Tenant members with datasource view permission can request another tenant's datasource ID to obtain basic auth passwords, AWS and Alibaba Cloud keys, and Kubernetes kubeconfigs.

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

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

1 open source package ship an affected version, including opsre/watchalert.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `opsre/watchalert` | GitHub | `pkg:github/opsre/watchalert` | From 2.0.0 to 3.9.20 | None |

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

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

## Is CVE-2026-133173 being exploited?

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

Public exploit code:

- CVE-2026-133173 -- WatchAlert <=3.9.20 IDOR Cross-Tenant Data Source Access. CVSS 8.6 High. (github_poc): https://github.com/LLCForge/CVE-2026-133173

## Fix prompt for AI coding agents

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

What it is: CVE-2026-133173 is a high-severity vulnerability in opsre WatchAlert, published on 19 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-133173 exists.

Affected packages and fixed versions:
- opsre/watchalert (GitHub): affected from 2.0.0 up to 3.9.20; no fix listed

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-133173/ (Markdown: https://insights.sbomify.com/CVE-2026-133173/index.md)
```

## Sources

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

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