Quick answers
- Is CVE-2026-77252 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77252 being exploited in the wild.
- How severe is CVE-2026-77252?
- Medium severity, with a CVSS score of 6.5, published 22 September 2026.
- Which products and versions are affected?
- Sooperset Mcp-Atlassian prior to 0.22.0.
- Is there a fix for CVE-2026-77252?
- A patch was published on 2026-07-10. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77252 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-77252?
- Check whether you run Sooperset Mcp-Atlassian at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass in versions prior to 0.22.0 where caller-supplied projects_filter and spaces_filter arguments replace administrator-configured allowlists (JIRA_PROJECTS_FILTER, CONFLUENCE_SPACES_FILTER), and caller-provided project or space clauses can suppress configured restrictions. The issue exists in SearchMixin.search_issues and SearchMixin.search code paths and affects any caller who can invoke the vulnerable search entry points with network access to the MCP server; the fix applies hard boundary logic where configured filters always AND into queries and tool arguments can only narrow, never replace, the allowlist.
Affected products
- sooperset mcp-atlassian prior to 0.22.0
Timeline
- 2026-09-22: disclosed
- 2026-07-10: patched