CVE-2026-77255

8.6

Sooperset · mcp-atlassian

A path traversal vulnerability in the mcp-atlassian server allows unauthenticated attackers to read arbitrary local files by exploiting improper workspace validation in the Jira update_issue function.

Executive summary

An unauthenticated path traversal vulnerability in Sooperset mcp-atlassian allows for arbitrary local file exfiltration, presenting a high risk to data confidentiality.

Vulnerability

The vulnerability exists due to a lack of workspace validation when processing attachment arguments in the Jira update_issue function, allowing an unauthenticated attacker to act as a confused deputy to read arbitrary files from the host filesystem.

Business impact

The ability to read arbitrary local files on the server hosting the MCP instance poses a severe threat to business operations, as it may lead to the exposure of sensitive configuration files, credentials, or proprietary source code. Given the CVSS score of 8.6, this vulnerability is classified as high severity and requires immediate attention to prevent unauthorized access to internal system data.

Remediation

Immediate Action: Update the mcp-atlassian package to version 0.22.0 or later to include the necessary workspace validation logic.

Proactive Monitoring: Review system and application logs for unusual file access patterns or unexpected attachment upload requests that deviate from standard operational behavior.

Compensating Controls: If immediate patching is not feasible, restrict network access to the MCP server endpoint to trusted internal networks only, or implement Web Application Firewall rules to inspect and sanitize incoming attachment paths.

Exploitation status

Public Exploit Available: No (exploit_available: false)

Analyst recommendation

The high CVSS score of 8.6 reflects the significant risk posed by this unauthenticated file read vulnerability. Security teams should prioritize updating all instances of mcp-atlassian to version 0.22.0 immediately to eliminate the path traversal vector and prevent potential exfiltration of sensitive server-side files.

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