CVE-2026-63505: Probo: Cross-tenant IDOR via unvalidated FK references
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Probo is a self-hostable governance, risk, and compliance (GRC) platform built for engineering and security teams. Prior to version 0.223.1, Probo’s console GraphQL API is a multi-tenant GRC platform where all data is scoped to an organization. A Finding can reference a Risk via finding.riskId. That reference is stored without validating that the risk belongs to the caller’s organization, and the Finding.risk field resolver authorizes the finding (caller’s org) instead of the risk, then loads the risk with a tenant scope derived from the risk’s own global ID. As a result, an authenticated member of organization A can attach an arbitrary organization B risk GID to a finding they own and then read organization B’s Risk (name, description, treatment, category, severity, owner), with no membership in B. The stored cross-tenant reference also blocks B from deleting its own risk (ON DELETE RESTRICT), a cross-tenant integrity/DoS. This issue has been patched in version 0.223.1.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-11-11).
Weakness: CWE-639: Authorization Bypass Through User-Controlled Key
How it can be exploited
Exploitable over the network with high attack complexity needing low privileges and no user interaction. Impact: confidentiality low, integrity low, availability none. CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
Public exploit evidence (Exploit Observer)
Exploit Observer found 1 Exploit-DB entry naming this CVE.
See all 2 references on Exploit Observer
Live scores
- EPSS
- 0.000
low predicted chance of attack - VEDAS
- 0.986
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| getprobo probo | version < 0.223.1 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
References
Other references
- https://github.com/getprobo/probo/security/advisories/GHSA-c74x-79w6-63jh (x_refsource_CONFIRM)
- https://github.com/getprobo/probo/commit/d03f6077ddf85ad448cbcb2145341d9543fc4711 (x_refsource_MISC)
- https://github.com/getprobo/probo/releases/tag/probod%2Fv0.223.1 (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
