Disclosed weakness · no CVE recorded

Atlassian markup conversion could monopolize a shared MCP server

mcp-atlassian maintainers · mcp-atlassian · Jira and Confluence MCP server

First documented disclosure · Review checkpoint

Summary

Processing a stored Jira issue or Confluence page could take disproportionate CPU time on each read.

Severity and exploitation evidence

Medium · numeric CVSS score not recorded. Severity source.

Exploitation not established: The maintainer reports an internal audit finding. The advisory identifies no malicious use.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The markup-to-Markdown converter repeatedly scanned portions of the input.

Conditions required

A party can change content that the MCP server later reads.

Potential impact

Repeated reads could interrupt other callers on a shared server.

Affected versions and configurations

Before 0.24.5.

Fix and mitigation status

0.24.5.

Practical next steps

Upgrade to 0.24.6 or later. Upgrade the converter with the server.

Operating lesson

Bound parsing costs for stored content read by an AI tool.

Evidence and limits

The maintainer traced this issue to an internal audit and published the patch and advisory November 16. The advisory provides a severity label without a numeric score.

Sources