CVE-2026-77267: mcp-atlassian Incomplete SSRF Remediation Vulnerability

mcp-atlassian Updated 23 Sep 2026

Summary

22/09/2026
Yes i
High
8.3

CVE-2026-77267: mcp-atlassian has an incomplete SSRF remediation. Affects mcp-atlassian versions < 0.22.0. Fixed in 0.22.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

mcp-atlassian is a Python package designed to facilitate interactions with Atlassian products such as Jira and Confluence. It provides a set of APIs that allow developers to automate tasks and integrate these services into their applications. However, the package has a vulnerability related to Server-Side Request Forgery (SSRF), which can lead to unauthorized access to internal services.

Vulnerability Detail

The vulnerability arises from the UserTokenMiddleware, which extracts URLs from the HTTP headers X-Atlassian-Jira-Url and X-Atlassian-Confluence-Url without proper validation. This means that an attacker can manipulate these headers to direct the application to make requests to arbitrary URLs, including internal services or sensitive endpoints like AWS instance metadata. The lack of validation allows for potential exploitation, leading to unauthorized data access and security breaches.

How To Fix

Latest published version: 0.23.1 as of 23 Oct 2026

pip install --upgrade "mcp-atlassian==0.23.1"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.22.0

This is the first release that contains the fix.

pip install --upgrade "mcp-atlassian==0.22.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, you can implement your own validation for the URLs extracted from the headers before they are passed to the API client constructors. This can be done by checking the URLs against an allowlist of permitted hostnames or rejecting private/loopback/link-local IP ranges. Here is a sample code snippet for URL validation:

import re

def validate_url(url):
    # Example allowlist
    allowlist = ["https://your-allowed-domain.com"]
    if any(re.match(pattern, url) for pattern in allowlist):
        return True
    return False

# Usage
if validate_url(jira_url_str):
    service_headers["X-Atlassian-Jira-Url"] = jira_url_str
else:
    raise ValueError("Invalid URL")

Conclusion

The mcp-atlassian package has a significant SSRF vulnerability that can be exploited by attackers to access unauthorized resources. It is crucial to update to the patched version to secure your application. Implementing URL validation can serve as a temporary measure until the update is applied.

See every vulnerability recorded for mcp-atlassian →

Share this vulnerability

FAQ

Server-Side Request Forgery (SSRF) is a security vulnerability that allows an attacker to send crafted requests from a vulnerable server to internal or external resources.

An attacker can exploit this vulnerability to access internal services or sensitive data, potentially leading to data breaches or unauthorized actions within your network.

Yes, the vulnerability has been patched in versions of mcp-atlassian greater than or equal to commit 5cd697dfce91.

Implement URL validation as a temporary workaround to mitigate the risk until you can update to the patched version.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software without requiring access to the code or installation.

Related vulnerabilities

Recent vulnerabilities recorded for mcp-atlassian.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Latest published version: 0.23.1 as of 23 Oct 2026

pip install --upgrade "mcp-atlassian==0.23.1"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.22.0

This is the first release that contains the fix.

pip install --upgrade "mcp-atlassian==0.22.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback