Security readout for executives and security teams
Plain-English summary
Capgo had an authorization boundary flaw in its webhook test feature. A user or attacker with an app-scoped API key could trigger organization-level webhook deliveries outside the app they were meant to access. This is not unauthenticated, but it can cross tenant or scope boundaries and may affect systems that trust signed Capgo webhooks.
Executive priority
Treat as a near-term fix, not an emergency, unless Capgo webhooks trigger sensitive business actions. The key concern is broken access boundaries: limited app credentials could cause trusted organization-level webhook activity. Prioritize upgrade and log review for environments using webhooks heavily.
Technical view
CVE-2026-56252 affects Capgo before 12.128.2. The POST /webhooks/test endpoint failed to enforce scope isolation, allowing app-scoped API keys to invoke org-scoped webhook operations and bypass the limited_to_apps authorization check. CVSS is 5.4, with network access, low complexity, low privileges, no user interaction, and limited confidentiality and integrity impact.
Likely exposure
Exposure is most relevant for Capgo deployments or hosted use where app-scoped API keys exist and organization webhooks are configured. Risk increases if downstream services trust Capgo-signed webhook events for sensitive workflows. The provided sources do not identify broader affected products or default exposure details.
Exploitation context
Exploitation requires valid app-scoped credentials. Sources state the flaw can trigger signed outbound webhook deliveries for arbitrary organization webhooks outside the declared app boundary. CISA KEV status is false in the provided bundle, and no cited source states active exploitation.
Researcher notes
This is CWE-863 improper authorization. The core issue is scope isolation failure between app-scoped API keys and org-scoped webhook operations. Evidence is limited to the CVE bundle, GitHub advisory, and VulnCheck advisory; no public exploit status or additional affected components are stated in the provided sources.
Mitigation direction
- Upgrade Capgo to version 12.128.2 or later where applicable.
- Review the GitHub advisory for vendor-specific remediation guidance.
- Rotate app-scoped API keys if misuse is suspected.
- Review organization webhook configurations and downstream trust assumptions.
- Monitor for unusual webhook test activity from app-scoped credentials.
Validation and detection
- Inventory Capgo versions and identify instances before 12.128.2.
- Confirm whether app-scoped API keys are enabled or distributed.
- Review logs for POST /webhooks/test activity by app-scoped keys.
- Check whether org webhooks received unexpected test deliveries.
- Verify authorization behavior after upgrading or applying vendor guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-56252 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
5.3MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-qvr7-f6j6-64wp)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Capgo - Scope Isolation Failure in Webhook Test EndpointCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.