Skip to main content
Menu
CVEs

WatchAlert cross-tenant data access in datasource lookup API

CVE-2026-133173EUVD-2026-130206GHSA-6G3Q-QVP2-GGQQPublished November 19, 2026, updated

7.1HighCNA
Exploited
Proof of concept public, per CISA
Fix
Fix or patch referenced
Who is exposed
Specific setups only

Summary

WatchAlert, from vendor opsre, has an insecure direct object reference flaw in its datasource lookup endpoint that lets a logged-in user read other tenants' data sources. Reachable remotely by any account holding datasource view permission, it can expose stored basic auth passwords, AWS and Alibaba Cloud keys, and Kubernetes kubeconfigs belonging to other tenants.

Written by a model

Original 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.

Who should check

Teams running opsre WatchAlert versions 2.0.0 through 3.9.20 with multiple tenants where members hold datasource view permission.

“WatchAlert 2.0.0 through 3.9.20 contains an insecure direct object reference vulnerability”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affects WatchAlert 2.0.0 through 3.9.20. Attacker must be a tenant member with datasource view permission.
  2. Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133173 (WatchAlert 2.0.0 through 3.9.20 Cross-Tenant IDOR via dataSourceGet API), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133173 (entry last updated 2026-11-19):
Affected:
- opsre WatchAlert: from 2.0.0, through 3.9.20
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects WatchAlert 2.0.0 through 3.9.20. (source: https://www.vulncheck.com/advisories/watchalert-2.0.0-through-3.9.20-cross-tenant-idor-via-datasourceget-api)
- Attacker must be a tenant member with datasource view permission. (source: https://www.vulncheck.com/advisories/watchalert-2.0.0-through-3.9.20-cross-tenant-idor-via-datasourceget-api)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-133173 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133173 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/opsre/WatchAlert/commit/ae8c1af20b4f5b02b823482e4bf7d53eafeef369
- https://github.com/opsre/WatchAlert/issues/268
- https://hackmd.io/@hieund/watchalert-cross-tenant-datasource-credential-idor
- https://github.com/opsre/WatchAlert/blob/v3.9.20/internal/repo/datasource.go#L63-L65
- https://github.com/opsre/WatchAlert
- https://www.vulncheck.com/advisories/watchalert-2.0.0-through-3.9.20-cross-tenant-idor-via-datasourceget-api
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133173
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133173"}.

Affected versions

cve.now Index

30Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 37 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 10

Questions about CVE-2026-133173

Is CVE-2026-133173 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A tenant member with datasource view permission can request another tenant's datasource by its ID. The returned record exposes basic auth passwords, AWS and Alibaba Cloud keys, and Kubernetes kubeconfigs.

Source: vulncheck.com

Which versions are affected by CVE-2026-133173?

WatchAlert: from 2.0.0 through 3.9.20.

Source: cve.now feed data

Am I affected, and how do I check?

WatchAlert versions 2.0.0 through 3.9.20 are affected. The exposure requires a tenant member account that holds datasource view permission, so the installed WatchAlert version and the permissions assigned to tenant members are the things to check.

Source: vulncheck.com

How do I fix CVE-2026-133173?

The checked facts do not name a fixed version or vendor patch IDs, so no upgrade target can be confirmed from them. Check the vendor's advisory for a fix and for any workaround.

Source: vulncheck.com

No corrections so far. Something wrong on this page? Report an error.