CVSS 3.1
4.9 mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:NCVE-2026-63505 Probo: Cross-tenant IDOR via unvalidated FK references
Medium (4.9) in getprobo probo. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.
On this page
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.
Severity
- EPSS
- 0.6% estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-639 Authorization Bypass Through User-Controlled Key
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-63505 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63505?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63505?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-63505 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-63505)
HTML:
<a href="https://cve.bz/cve/CVE-2026-63505"><img src="https://cve.bz/cve/badge/CVE-2026-63505.svg" alt="CVE-2026-63505"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| getprobo probo | < 0.223.1 |
Public exploits
- Exploit-DB Probo 0.222.2 - IDOR
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.