CVE-2026-77243

8.8

sooperset · mcp-atlassian

A missing authorization vulnerability in the sooperset mcp-atlassian server allows authenticated clients to bypass tool restrictions and invoke unauthorized read, write, or delete operations.

Executive summary

An authorization bypass vulnerability in sooperset mcp-atlassian allows authenticated users to execute restricted Jira and Confluence operations, posing a significant risk to data integrity and security.

Vulnerability

This is a missing authorization flaw (CWE-862) occurring within the tool invocation workflow. While the server correctly filters tools during listing, it fails to revalidate these permissions during the tools/call request, allowing an authenticated client to access hidden or restricted functionality.

Business impact

The ability to perform unauthorized read, write, or delete operations on Atlassian products like Jira and Confluence can lead to critical data loss, unauthorized information disclosure, and disruption of project management workflows. With a CVSS score of 8.8, this high-severity flaw represents a major threat to organizational data integrity and compliance, as it effectively undermines configured least-privilege security policies.

Remediation

Immediate Action: Update the sooperset mcp-atlassian package to version 0.22.0 or later to resolve the authorization logic error.

Proactive Monitoring: Review application access logs for unexpected calls to sensitive tools or functions that should be restricted based on user roles.

Compensating Controls: Implement strict network-level access controls to limit the clients authorized to communicate with the MCP server until the update is applied.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

The risk posed by this vulnerability is significant due to the potential for unauthorized data manipulation within critical business environments. Security teams should prioritize the update to version 0.22.0 as soon as possible to restore proper authorization controls and prevent potential exploitation of the affected Atlassian integrations.

More sooperset CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources