Approved changes feed: RSS · Atom

cpe:2.3:a:sooperset:mcp_atlassian:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorSooperset (11b8c0a5-4fe8-58fe-8753-b4c51b45a808)
ProductMcp Atlassian (802156a5-194b-5674-95b8-a94cc2c2fa62)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
pkg:github/sooperset/mcp-atlassian purl2cpe 2026-07-28 16:41:16.971881
pkg:pypi/mcp-atlassian purl2cpe 2026-07-28 16:41:16.971883

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-27826 vulnerable 2026-06-08 07:55:14.024343 MCP Atlassian has SSRF via unvalidated X-Atlassian-Jira-Url / X-Atlassian-Confluence-Url headers
HIGH (8.2)
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.
Published: 2026-03-10T18:46:12.069Z
Updated: 2026-03-10T19:15:10.505Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.