Intel

AIKIDO-2026-821691

mcp-atlassian is vulnerable to Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF)GHSA-v9m3-wfh8-5646 Published 6 days ago

53

Medium Risk

This Affects:

PYTHONmcp-atlassian
0.0.1 - 0.21.1
Fixed in 0.22.0
Are you affected? Scan for Free

TL;DR

The Jira user-permission lookup issues its request with the module-level requests.get instead of the SSRF-hooked session, so the redirect-validation hook never runs for that path. An unauthenticated client on the multi-user HTTP transport can supply a public base URL that passes validation and then redirect the follow-up request to an internal address. This yields a blind server-side request to arbitrary internal hosts and ports. The fix routes the lookup through the hardened session so redirects are re-validated.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you run the multi-user HTTP transport that accepts caller-supplied Atlassian URL headers.

Background info

mcp-atlassian is vulnerable to Server-Side Request Forgery (SSRF) in versions 0.0.1 - 0.21.1.

How to fix this

Upgrade the mcp-atlassian library to the patch version.