Authenticated channel mutation via null trigger bypass
Published Jul 10, 2026 · Updated Jul 10, 2026
Authorization bypass in Capgo before 12.128.2 allows remote authenticated users to alter protected channel settings through PostgREST. The public.noupdate() trigger returns before enforcing field immutability when auth.uid() is null, while the channels RLS policy permits write-scoped API keys to update rows. Possession of a write-scoped key for the affected organization or app is required; successful exploitation changes rollout, exposure, or update-policy settings within that key's scope.
Summary
What happened
Authorization bypass in Capgo before 12.128.2 allows remote authenticated users to alter protected channel settings through PostgREST. The public.noupdate() trigger returns before enforcing field immutability when auth.uid() is null, while the channels RLS policy permits write-scoped API keys to update rows. Possession of a write-scoped key for the affected organization or app is required; successful exploitation changes rollout, exposure, or update-policy settings within that key's scope.
The record
- CVE
- CVE-2026-56335
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- Capgo
- Product
- Capgo
- Classifications
- CWE-284, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 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.
Public exploit references
- Authenticated PostgREST channel-mutation 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