CVE-2026-79786 coroot CVE debrief

Who should care

Defenders responsible for Coroot instances, particularly those exposed to the internet or used by multiple users, should assess exposure and prioritize remediation. This includes verifying instance versions, reviewing and restricting redirect URIs for MCP OAuth clients, and monitoring for suspicious authorization code exchanges. Security teams and vulnerability management teams should also review the vulnerability and implement additional authentication,

Why it matters

CVE-2026-79786 allows attackers to hijack MCP sessions by registering clients with attacker-controlled redirect URIs, impacting Coroot instances with exposed or multi-user environments.

• Session hijacking through authorization code exchange
• Potential for lateral movement within affected systems
• Need for verification of vulnerable Coroot instances
• Possible impact on users with access to affected Coroot instances

Technical summary

Coroot's MCP OAuth dynamic client registration endpoint does not validate redirect URIs, allowing attackers to register clients pointing to attacker-controlled hosts and hijack MCP sessions. This vulnerability impacts Coroot instances with exposed or multi-user environments, enabling attackers to send authorization URLs to signed-in users, capture their authorization codes, and exchange them for access tokens. Defenders should prioritize verifying and remediating vulnerable Coroot instances, particularly those exposed to the internet or used by multiple users.

Defensive priority

Defenders should prioritize verifying and remediating vulnerable Coroot instances, particularly those exposed to the internet or used by multiple users.

Recommended defensive actions

• Verify Coroot instance version and exposure
• Review and restrict redirect URIs for MCP OAuth clients
• Monitor for suspicious authorization code exchanges
• Implement additional authentication and authorization controls
• Track exceptions and retest remediated assets
• Check relevant monitoring, detection, and logs for exposed assets
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the scope of affected versions and instances requires further verification. Coroot instances with exposed or multi-user environments are particularly at risk. Defenders should verify instance versions, review and restrict redirect URIs for MCP OAuth clients, and monitor for suspicious authorization code exchanges.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.