MCP Atlassian Security Update Addresses 25 Vulnerabilities
Tech GuruQuick Answer
MCP Atlassian versions before 0.22.0 are covered by these 25 advisories, which overlap across file access, HTTP authentication, tool and project restrictions, server-side request forgery (SSRF), and OAuth handling. All list 0.22.0 as a patched release. Prioritize reachable HTTP/SSE deployments holding operator credentials: an upgrade does not by itself revoke secrets already exposed. Keep the endpoint restricted while selecting and validating a supported fixed release.
Confirm Scope And Apply The Supported Fix
What to do now: inventory each MCP server's transport, authenticated callers, mounted files, Atlassian credentials and enabled tools. Restrict or stop untrusted access before upgrading. Review potential credential and attachment exposure, preserving evidence and revoking or rotating affected secrets through the incident-response process where warranted.
Source recheck: October 2, 2026 UTC. The linked project advisories were checked for this revision; deployment applicability and successful remediation still require local evidence. Recheck the supported release before changing production.
Scope And Authority
| Product scope | MCP Atlassian packages and release streams identified in the project advisories |
|---|---|
| Advisory | GHSA-cc5h-2pwp-pvcc / GHSA-wv8v-v4c5-v75j / GHSA-w66g-j6c4-hcfc / GHSA-vc25-24vv-fxxm / GHSA-2xj6-xx86-cwwc / GHSA-3r68-hf9h-887v / GHSA-mrq8-fv7v-hhjg / GHSA-f4p7-qx46-wc5j / GHSA-h7wj-5v37-59r2 / GHSA-mfv2-4wvm-9pgp / GHSA-49xv-9743-pw8w / GHSA-f26r-j276-ggg4 / GHSA-6529-c226-h328 / GHSA-6cr4-ccf3-x7h4 / GHSA-4596-2p6p-28cv / GHSA-p6hp-93wp-fh6p / GHSA-g2r2-3j32-j27x / GHSA-5wf4-jqxh-8gm3 / GHSA-6vmq-24h2-pj7j / GHSA-hgcf-4mq8-5266 / GHSA-wrhw-j3f9-8vc6 / GHSA-f6pj-qv47-g96w / GHSA-v9m3-wfh8-5646 / GHSA-g5xv-mhgm-v5f6 / GHSA-93xw-j965-9mx3 |
| CVEs | CVE-2026-77243, CVE-2026-77244, CVE-2026-77246, CVE-2026-77247, CVE-2026-77248, CVE-2026-77249, CVE-2026-77250, CVE-2026-77251, CVE-2026-77253, CVE-2026-77255, CVE-2026-77257, CVE-2026-77258, CVE-2026-77259, CVE-2026-77260, CVE-2026-77261, CVE-2026-77262, CVE-2026-77265, CVE-2026-77266, CVE-2026-77267, CVE-2026-77268, CVE-2026-77269, CVE-2026-77270, CVE-2026-77271, CVE-2026-77272, CVE-2026-77274 |
| Authoritative release date | 2026-07-10 UTC (project advisory dates, not database ingestion) |
| Authority revision date | 2026-08-20 UTC (project advisory dates, not database ingestion) |
| Affected versions | mcp-atlassian < 0.22.0 |
| Fixed version | mcp-atlassian 0.22.0 |
| CVSS base score | 5.3 / 5.4 / 5.5 / 5.9 / 6.1 / 6.5 / 7.1 / 7.4 / 7.7 / 8.3 / 8.6 / 8.8 / 10 (official CVSS v3/v4 scores) |
| CVSS severity | Medium to Critical |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
Several reports describe the same missing upload-path boundary, including Jira attachments supplied through update_issue. Others describe HTTP authentication fallback to operator credentials, filters enforced only when listing tools, project/space-filter bypasses, SSRF checks missing on certain request or redirect paths, overly readable OAuth token files, and callback HTML injection. A separate download-path report permits application-module overwrite within the working directory, with execution on restart. These conditions are not identical: transport, caller access, filesystem permissions and Atlassian permissions determine the reachable impact. The reports include author-run demonstrations, not a statement that TechGeeks tested them or that all were exploited in the wild.
What To Validate Now
- Inventory. Record transport/listen addresses, reverse-proxy authentication, per-user versus shared Atlassian credentials, container mounts, writable application directories and token-file ownership/permissions without copying secrets into the change record.
- Establish applicability. The structured fields of all 25 linked advisories list
mcp-atlassian <0.22.0. Some historical descriptions differ: one names test version 2.14.5, and Jira tool reachability varies between reports. Use the running build and tool registry to resolve those conditions; do not treat earlier partial fixes as comprehensive protection. - Remediate. Use a supported build containing the 0.22.0 fixes. Keep least-privilege filesystem and Atlassian access, restrict outbound destinations and review token storage separately. Do not rely on
ENABLED_TOOLS,TOOLSETSor project/space filters as authorization on the vulnerable build. - Validate. In an isolated environment with synthetic files and disposable Jira/Confluence content, check rejected unauthenticated calls, disallowed tools, out-of-scope projects, file paths and outbound destinations, plus normal authorized use. Verify OAuth storage and callback access without submitting real credentials or production files.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Several reports revisit incomplete earlier fixes identified as CVE-2026-27825, GHSA-xjgw-4wvw-rgm4 and GHSA-7r34-79r5-rcc9; those earlier patch records alone do not establish protection against this later set. The tool-filter advisory explicitly says READ_ONLY_MODE has separate enforcement and is not affected by that particular bypass; it is not a fix for the entire advisory set. Single-user stdio and multi-user HTTP deployments have different trust boundaries. If application files may have been overwritten, preserve evidence and rebuild from trusted artifacts rather than assuming a routine restart clears compromise.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
- GHSA-cc5h-2pwp-pvcc
- GHSA-wv8v-v4c5-v75j
- GHSA-w66g-j6c4-hcfc
- GHSA-vc25-24vv-fxxm
- GHSA-2xj6-xx86-cwwc
- GHSA-3r68-hf9h-887v
- GHSA-mrq8-fv7v-hhjg
- GHSA-f4p7-qx46-wc5j
- GHSA-h7wj-5v37-59r2
- GHSA-mfv2-4wvm-9pgp
- GHSA-49xv-9743-pw8w
- GHSA-f26r-j276-ggg4
- GHSA-6529-c226-h328
- GHSA-6cr4-ccf3-x7h4
- GHSA-4596-2p6p-28cv
- GHSA-p6hp-93wp-fh6p
- GHSA-g2r2-3j32-j27x
- GHSA-5wf4-jqxh-8gm3
- GHSA-6vmq-24h2-pj7j
- GHSA-hgcf-4mq8-5266
- GHSA-wrhw-j3f9-8vc6
- GHSA-f6pj-qv47-g96w
- GHSA-v9m3-wfh8-5646
- GHSA-g5xv-mhgm-v5f6
- GHSA-93xw-j965-9mx3
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
