cve.bz

CVE-2026-27826 (MCPwnfluence) sooperset mcp atlassian: SSRF

8.2 highExploit referenceEPSS 14%Fix available

Known as MCPwnfluence

High (8.2) in sooperset mcp atlassian. EPSS 14% estimated probability of exploitation activity in the next 30 days. Fixed in mcp-atlassian 0.17.0.

On this page
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to version 0.17.0, an unauthenticated attacker who can reach the mcp-atlassian HTTP endpoint can force the server process to make outbound HTTP requests to an arbitrary attacker-controlled URL by supplying two custom HTTP headers without an `Authorization` header. No authentication is required. The vulnerability exists in the HTTP middleware and dependency injection layer — not in any MCP tool handler - making it invisible to tool-level code analysis. In cloud deployments, this could enable theft of IAM role credentials via the instance metadata endpoint (`169[.]254[.]169[.]254`). In any HTTP deployment it enables internal network reconnaissance and injection of attacker-controlled content into LLM tool results. Version 0.17.0 fixes the issue.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
EPSS
14% (unchanged from 14% a week ago; 1.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 97th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-03-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-27826 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-27826?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-27826?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-27826 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
sooperset:mcp_atlassianbefore 0.17.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7r34-79r5-rcc9PyPImcp-atlassian<0.17.00.17.0
PYSEC-2026-2621PyPImcp-atlassian<0.17.00.17.0

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Nuclei template mcp-atlassian < 0.17.0 - Server-Side Request Forgery
  • Emerging Threats Open ET WEB_SPECIFIC_APPS Atlassian MCP Server-side Request Forgery via HTTP Headers (CVE-2026-27826) M1 sid 2071904
  • Emerging Threats Open ET WEB_SPECIFIC_APPS Atlassian MCP Server-side Request Forgery via HTTP Headers (CVE-2026-27826) M2 sid 2071905

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON