CVE-2026-56249
Deferred Deferred - Pending Action

Authorization Bypass in Capgo Channel Creation

Vulnerability report for CVE-2026-56249, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-30

Last updated on: 2026-07-01

Assigner: VulnCheck

Description

Capgo before 12.128.2 contains an authorization bypass vulnerability in the channel creation endpoint that allows authenticated users to overwrite existing channels by reusing their names. Attackers with app.create_channel permission can exploit a logic mismatch between existence validation and upsert operations to reassign channel ownership and modify critical production channel configurations.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-30
Last Modified
2026-07-01
Generated
2026-07-21
AI Q&A
2026-07-01
EPSS Evaluated
2026-07-19
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
capgo capgo to 12.128.2 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-285 The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in Capgo versions before 12.128.2 and involves an authorization bypass in the channel creation endpoint.

Authenticated users who have the app.create_channel permission can exploit a logic mismatch between the validation that checks if a channel exists and the operation that creates or updates channels.

By reusing existing channel names, attackers can overwrite existing channels, reassign channel ownership, and modify important production channel configurations.

Detection Guidance

Detection of this vulnerability involves monitoring for unauthorized channel overwrite attempts via the POST /channel endpoint, especially by users with the app.create_channel permission.

Since the vulnerability exploits a logic mismatch in the channel creation endpoint allowing reuse of existing channel names, you can audit logs for POST requests to /channel where the channel name already exists but ownership changes.

Commands to detect such activity would depend on your logging and monitoring setup, but examples include searching application logs or API gateway logs for suspicious POST /channel requests with repeated channel names or ownership changes.

  • Use grep or similar tools to search logs for POST /channel requests: grep 'POST /channel' /path/to/logfile
  • Filter logs for repeated channel names being created or updated by different users.
  • Monitor for changes in channel ownership fields in your database or audit logs.
Impact Analysis

This vulnerability can lead to unauthorized modification of critical production channels.

Attackers with certain permissions can overwrite existing channels, potentially disrupting communication or operations.

It can result in loss of integrity and availability of channel configurations, which may impact business processes relying on these channels.

Compliance Impact

The vulnerability allows attackers with certain permissions to overwrite existing channels and reassign ownership, enabling unauthorized changes to critical production configurations. This improper authorization and potential unauthorized access could lead to violations of compliance requirements related to data integrity, access control, and auditability under standards such as GDPR and HIPAA.

Specifically, unauthorized modification of production channels may compromise system integrity and confidentiality, which are key aspects of regulatory frameworks that mandate strict access controls and protection of sensitive data.

Mitigation Strategies

Immediate mitigation steps include updating Capgo to version 12.128.2 or later where the vulnerability is fixed.

If an immediate update is not possible, restrict or audit users with the app.create_channel permission to prevent unauthorized channel creation or modification.

Implement additional authorization checks on the channel creation endpoint to ensure ownership cannot be overwritten by reusing channel names.

Review and align existence validation logic with upsert operations to prevent bypassing ownership constraints.

Prevent modification of the created_by field after channel creation to maintain ownership integrity.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-56249. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart