Skip to content
sooperset/mcp-atlassian·Indexed by this site · Originally published· Event →· Its place in the scan record →

mcp-atlassian 0.24.5 concurrent Markdown writes may mix in content from other requests, fixed in 0.24.6

Concurrent Confluence Markdown writes could mix content between requests

AI summary

mcp-atlassian published security advisory GHSA-3c26-hw8g-vvc9: in version 0.24.5, concurrent Markdown writes may mix in content from other requests, which has been fixed in 0.24.6. That version runs Jira and Confluence calls in worker threads, and the Confluence write tools (confluence_create_page, confluence_update_page and the comment tool) share the same Markdown converter; when two calls convert at the same time, the content stored by one of the calls may be corrupted or contain text from the other call. On multi-user shared servers (sse and streamable-http transports), a page or comment written by one user may contain content another user was writing at that time; a single client sending write calls in parallel is likewise affected. The issue does not read or change content already stored in Confluence, and earlier versions convert calls one at a time and are not affected. The issue was found by the project's internal security audit.

Read originalgithub.com