Skip to main content
VulnerabilityPublished

CVE-2026-63505: getprobo probo · Insecure Direct Object Reference

Affects getprobo proboSource CVE Database V5

0
Compare

Public exploit available (Exploit-DB) · CVSS 4.9 Medium : upgrade to 0.223.1 as a priority.

Data as of 11 Nov 2026, 18:35 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.14.9
Patch
Available – fixed in 0.223.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by GitHub, Inc.

    , 118 days before disclosure

  2. , 86 days before disclosure

  3. CVE published

    on cve.org

    , t = 0

  4. In Threat Radar

    record ingested

    , 26 minutes after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade getprobo probo to 0.223.1.

Affected software

ProductAffectedFixed in
getproboproboAffected
  • <0.223.1
Fixed in
  • 0.223.1

AI-suggested

Upgrade Probo to version 0.223.1 or later, where this authorization bypass vulnerability has been fixed. No other mitigation is required as the patch addresses the root cause.

Description

CVE-2026-63505 is an authorization bypass vulnerability in the Probo GRC platform prior to version 0.223.1. It allows an authenticated user in one organization to read risk data belonging to another organization by exploiting improper validation of cross-tenant references in the GraphQL API. This also causes a denial of service by preventing the other organization from deleting its own risk entries. The issue is fixed in version 0.223.1.

Reports on CVE-2026-63505

References

Community reviews

Loading reviews…