Cross-scope webhook delivery via omitted app restriction
Published Jul 12, 2026 · Updated Jul 12, 2026
Incorrect authorization in Capgo before 12.128.2 allows remote authenticated users to trigger org-scoped webhook deliveries with app-scoped keys. The POST /webhooks/test path calls checkWebhookPermissionV2, whose apikeyHasOrgRight check accepts an empty limited_to_orgs list without enforcing limited_to_apps. An app-scoped key owned by an organization administrator can therefore send signed webhook traffic and obtain delivery metadata for organization webhooks outside its app boundary.
Summary
What happened
Incorrect authorization in Capgo before 12.128.2 allows remote authenticated users to trigger org-scoped webhook deliveries with app-scoped keys. The POST /webhooks/test path calls checkWebhookPermissionV2, whose apikeyHasOrgRight check accepts an empty limited_to_orgs list without enforcing limited_to_apps. An app-scoped key owned by an organization administrator can therefore send signed webhook traffic and obtain delivery metadata for organization webhooks outside its app boundary.
The record
- CVE
- CVE-2026-56252
- Published
- Jul 12, 2026
- Updated
- Jul 12, 2026
- Vendor
- Capgo
- Product
- Capgo
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 12, 2026CVE publishedPublication date reported by the CVE source.
- Jul 12, 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
- POST /webhooks/test reproductionproof 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