Skip to main content
VulnerabilityPublished

CVE-2026-64861: getprobo probo · Unthrottled Resource Allocation

Affects getprobo proboSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 0.222.0 when convenient.

Data as of 11 Nov 2026, 18:35 UTC

CVSS 3.1 base score
4.3Medium
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.3
Patch
Available – fixed in 0.222.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

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

    No attack traffic recorded by OffSeq Mirage sensors

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.222.0.

Affected software

ProductAffectedFixed in
getproboproboAffected
  • <0.222.0
Fixed in
  • 0.222.0

AI-suggested

Upgrade Probo to version 0.222.0 or later, where the vulnerability is patched by enforcing restrictions on alias count, query depth, and query complexity in the GraphQL endpoint. No other mitigation is required as the fix addresses the root cause.

Description

CVE-2026-64861 is a resource exhaustion vulnerability in the Probo GRC platform prior to version 0.222.0. The GraphQL endpoint does not limit alias count, query depth, or query complexity, allowing attackers to craft requests with thousands of aliased resolver calls. This can cause excessive server resource consumption and degrade service availability. The issue is fixed in version 0.222.0.

References

Community reviews

Loading reviews…