# CVE-2026-77252: MCP Atlassian: JIRA_PROJECTS_FILTER and CONFLUENCE_SPACES_FILTER can be bypassed in search tools

> Attackers can bypass configured project and space filters in MCP Atlassian to access unauthorized Jira or Confluence data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-rqwg-9346-fjjv

## What is CVE-2026-77252?

CVE-2026-77252 is a medium-severity missing authorization vulnerability in sooperset mcp-atlassian, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, caller-supplied projects_filter and spaces_filter arguments can replace administrator-configured allowlists, and caller-provided project or space clauses can suppress the configured restriction. A caller can search projects or spaces outside the intended boundary when the configured Atlassian credentials can access them. The advisory traces the vulnerable input and processing flow through JIRA_PROJECTS_FILTER, CONFLUENCE_SPACES_FILTER, projects_filter, spaces_filter, SearchMixin.search_issues, and SearchMixin.search, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-77252?

It affects 1 product.


Products: Mcp-Atlassian Mcp Atlassian.

## How do I fix CVE-2026-77252?

No fix has been published for CVE-2026-77252 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-77252 being exploited?

There is no known exploitation of CVE-2026-77252 in the wild and no public exploit code.

## Other vulnerabilities in sooperset mcp-atlassian

- [CVE-2026-77244](https://insights.sbomify.com/CVE-2026-77244/): [mcp-atlassian] Authentication bypass in HTTP transport: AtlassianOpaqueTokenVerifier accepts any non-empty token (critical 10.0)
- [CVE-2026-77254](https://insights.sbomify.com/CVE-2026-77254/): MCP Atlassian: Unauthenticated HTTP MCP requests can use globally configured Jira and Confluence credentials (critical 9.1)
- [CVE-2026-27825](https://insights.sbomify.com/CVE-2026-27825/): MCP Atlassian has an arbitrary file write leading to arbitrary code execution via unconstrained download_path in confluence_download_attachment (critical 9.1)
- [CVE-2026-77243](https://insights.sbomify.com/CVE-2026-77243/): MCP Atlassian: ENABLED_TOOLS / Toolset authorization bypass (high 8.8)
- [CVE-2026-77274](https://insights.sbomify.com/CVE-2026-77274/): MCP Atlassian: SSRF Protection Bypass (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77252 and fix it if it is affected.

What it is: CVE-2026-77252 is a medium-severity missing authorization vulnerability in sooperset mcp-atlassian, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77252 in the wild and no public exploit code.

Affected product: sooperset mcp-atlassian. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77252/ (Markdown: https://insights.sbomify.com/CVE-2026-77252/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77252
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77252
- OSV: https://osv.dev/vulnerability/CVE-2026-77252

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77252/
Summaries are generated and may contain mistakes; the official description above is the record.