# MCP Atlassian: Arbitrary server-local file upload to Jira/Confluence attachments via unrestricted file_path parameters

Advisory record · `GHSA-f6pj-qv47-g96w`

- **Identifiers:** `GHSA-f6pj-qv47-g96w` · `CVE-2026-77247` · `PYSEC-2026-4092`
- **State:** Confirmed
- **Severity:** CVSS 8.3 High
- **Critical:** No
- **Weakness (CWE):** [CWE-73](https://cwe.mitre.org/data/definitions/73.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 22 Sept 2026
- **Updated:** 1 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Sept 2026, 20:36 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `mcp-atlassian` (PyPI): affected `<0.22.0`; fixed in `0.22.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> mcp-atlassian versions before 0.22.0 let callers of the Jira and Confluence attachment upload tools supply a file path that the server reads from its own filesystem and uploads as an attachment. An attacker who can invoke these upload tools, such as a malicious or compromised MCP client in an HTTP/SSE or multi-user deployment, can read files readable by the server process and send them to Jira or Confluence. Upgrade to version 0.22.0 or later. The source lists no other workaround.

Written 1 Nov 2026.

## 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

- 8.3 High, CVSS 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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0039, the 33rd 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](https://osv.dev/vulnerability/GHSA-f6pj-qv47-g96w)

## Sources

- [GitHub Advisory Database: GHSA-f6pj-qv47-g96w](https://github.com/advisories/GHSA-f6pj-qv47-g96w)
- [OSV: GHSA-f6pj-qv47-g96w](https://osv.dev/vulnerability/GHSA-f6pj-qv47-g96w)
- <https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-f6pj-qv47-g96w>
- <https://github.com/sooperset/mcp-atlassian/pull/1448>
- <https://github.com/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460>
- <https://github.com/sooperset/mcp-atlassian>
- <https://github.com/sooperset/mcp-atlassian/releases/tag/v0.22.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-f6pj-qv47-g96w>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-f6pj-qv47-g96w/>. Everything for agents: <https://agentprime.io/llms.txt>.