Disclosed weakness · no CVE recorded
Concurrent Confluence writes could mix different users’ Markdown
mcp-atlassian maintainers · mcp-atlassian · Jira and Confluence MCP server
First documented disclosure · Review checkpoint
Summary
The MCP server could store text from one in-flight request in another user’s Confluence page or comment.
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.
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
Version 0.24.5 moved upstream calls to worker threads while sharing a stateful Markdown converter among them.
Conditions required
Two Markdown write operations overlap on one server, whether from several users or a single parallel client.
Potential impact
Pages or comments being written could contain another request’s text or have damaged formatting. Previously stored content was outside the affected operation.
Affected versions and configurations
0.24.5 only.
Fix and mitigation status
0.24.6.
Practical next steps
Upgrade to 0.24.6 or later. Review pages and comments written during use of 0.24.5. Serialize Markdown writes until the upgrade is complete.
Operating lesson
Give each simultaneous conversion its own state.
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
- mcp-atlassian public correction
Primary source ·
- mcp-atlassian 0.24.6 release notes
Primary source ·
- mcp-atlassian advisory GHSA-3c26-hw8g-vvc9
Primary source ·