mcp-atlassian is vulnerable to Server-Side Request Forgery (SSRF)
53
Medium Risk
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.
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.
mcp-atlassian is vulnerable to Server-Side Request Forgery (SSRF) in versions 0.0.1 - 0.21.1.
Upgrade the mcp-atlassian library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant