CVE-2026-64861 · Other
NO FIX YET · SEE WHAT TO DO
Probo, a self-hosted governance, risk and compliance platform, does not limit alias count, query depth or complexity on its GraphQL endpoint. A single crafted request with thousands of aliased calls can exhaust server resources and degrade the service.
first public Jul 3, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams that self-host Probo and expose its GraphQL endpoint to users or networks outside their control are exposed. Instances on a patched version or reachable only from trusted internal networks carry less risk. The sources do not say whether the flaw needs an account.
Not affected if managed-hosting, version-0.222.0-or-later
Who cares graphql, probo, self-hosted
0.222.00.222.0 or laterProbo is a self-hostable governance, risk, and compliance (GRC) platform built for engineering and security teams. Prior to version 0.222.0, the GraphQL endpoint does not enforce restrictions on alias count, query depth, or query complexity. An attacker can send a single request containing thousands of aliased resolver calls, causing excessive server-side resource consumption and service degradation. This issue has been patched in version 0.222.0.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.