Authenticated service degradation via unlimited demo creation
Published Jun 22, 2026 · Updated Jun 22, 2026
Resource exhaustion in Capgo before 12.128.2 allows remote authenticated users to degrade service availability via POST /app/demo. The createDemoApp() handler verifies organization write access but applies neither rate limiting nor an app or demo quota before using supabaseAdmin to perform roughly 138 database writes per request. Sustained requests from any user with organization write rights can inflate metadata, latency, storage, and compute costs and destabilize the service.
Summary
What happened
Resource exhaustion in Capgo before 12.128.2 allows remote authenticated users to degrade service availability via POST /app/demo. The createDemoApp() handler verifies organization write access but applies neither rate limiting nor an app or demo quota before using supabaseAdmin to perform roughly 138 database writes per request. Sustained requests from any user with organization write rights can inflate metadata, latency, storage, and compute costs and destabilize the service.
The record
- CVE
- CVE-2026-56255
- Published
- Jun 22, 2026
- Updated
- Jun 22, 2026
- Vendor
- Capgo
- Product
- Capgo
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 22, 2026CVE publishedPublication date reported by the CVE source.
- Jun 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <12.128.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Two-request POST /app/demo proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo