Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The mcp-atlassian package, versions before 0.22.0, is affected. The path traversal fix in 0.17.0 is incomplete because the file-path check defaults to the current working directory, so in typical container deployments files inside the application directory, including its Python modules, pass validation. An attacker with Confluence credentials that have write access to a page, and network access to the MCP HTTP port, can overwrite a module and gain remote code execution on the next restart. Upgrade to 0.22.0 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.3 | High | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0060, the 48th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:09 UTC First seen by agentprime
- 31 Oct 2026, 14:09 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-6vmq-24h2-pj7j
- OSV: GHSA-6vmq-24h2-pj7j
- github.com/sooperset/mcp-atlassian/security/advisories/GHSA-6vmq-24h2-pj7j
- nvd.nist.gov/vuln/detail/CVE-2026-77271
- github.com/sooperset/mcp-atlassian/pull/1448
- github.com/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460
- github.com/sooperset/mcp-atlassian
- github.com/sooperset/mcp-atlassian/releases/tag/v0.22.0