Cross-tenant risk read via unvalidated references in Probo
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-639.
Summary
Probo before 0.223.1 contains an authorization bypass through a user-controlled key (CWE-639). It stores a finding's risk reference without checking that the risk belongs to the caller's organization. An authenticated member of one organization can attach another organization's risk to a finding they own and then read that risk's name, description, treatment, category, severity and owner.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade getprobo probo to version 0.223.1, which fixes the issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
- Fix · CNA probo (getprobo) Fixed in 0.223.1
Timeline
- 2026-11-11 Threatist record created from CVE-2026-63505
- 2026-11-16 CISA SSVC decision points changed
References
More getprobo vulnerabilities
- TI-2026-89878 Vertical privilege escalation in Probo lets admins grant owner role CVSS 3.1HIGH 7.2
- TI-2026-89879 Probo public Trust Center API leaks hidden objects across tenants CVSS 3.1LOW 3.7
- TI-2026-36726 Probo has an open redirect bypass via path normalization CVSS 3.1MEDIUM 4.7
- TI-2026-89876 Application layer denial of service in Probo GraphQL endpoint CVSS 3.1MEDIUM 4.3
- TI-2026-89877 Broken access control in Probo public e-signature API CVSS 3.1LOW 3.1
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences