CVSS 3.1
3.7 lowCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NCVE-2026-76080 Probo: Unauthenticated cross-tenant and hidden-item disclosure via Query.node in the public Trust Center API
Low (3.7) in getprobo probo. EPSS 0.3% 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.224.0, the public Trust Center GraphQL API exposes Query.node(id:) with @authentication(required: OPTIONAL) — an unauthenticated internet visitor to any published trust center can call it. Six of its type branches — Organization, Framework, Audit, ThirdParty (subprocessor), TrustCenter, and TrustCenterReference — resolve the object with a tenant scope derived from the client-supplied GID itself (coredata.NewScopeFromObjectID(id)) and load it with a bare Get(scope, id) that performs no comparison to the current trust center's OrganizationID and no showOnTrustCenter/visibility check. (The Document and File branches, by contrast, correctly pass trustCenter.OrganizationID and check visibility). This issue has been patched in version 0.224.0.
Severity
- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 26th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- 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-76080 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-76080?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-76080?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-76080 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-76080)
HTML:
<a href="https://cve.bz/cve/CVE-2026-76080"><img src="https://cve.bz/cve/badge/CVE-2026-76080.svg" alt="CVE-2026-76080"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| getprobo probo | < 0.224.0 |
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.