CVE-2026-77257: mcp-atlassian Local File Disclosure Vulnerability

mcp-atlassian Updated 23 Sep 2026

Summary

22/09/2026
Yes i
High
8.3

CVE-2026-77257: MCP Atlassian: HTTP upload tools accept arbitrary server-local file paths. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The mcp-atlassian package is designed for HTTP/SSE deployment, enabling persistent, remote, and multi-user interactions with Atlassian products like Jira and Confluence. It facilitates attachment flows that allow users to upload files to issues and pages. However, the package has a critical vulnerability that permits authenticated users to exploit the system by accessing arbitrary server-local file paths, potentially exposing sensitive information.

Vulnerability Detail

The vulnerability arises from the lack of proper validation on file paths provided by users when uploading attachments in the mcp-atlassian package. Specifically, the package allows authenticated users to specify any server-local file path without restrictions, leading to local file disclosure. This can result in sensitive data exposure, such as API tokens and configuration files, especially in environments where Docker or Kubernetes are used to mount sensitive files. The issue is particularly severe in multi-user deployments where the attacker can access files that should be restricted to their own user context.

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, consider disabling server-local upload tools in HTTP transport mode unless a specific upload directory is configured. This can be done by setting an environment variable or modifying the configuration to restrict access to local file paths.

Conclusion

The mcp-atlassian package has a significant vulnerability that allows for local file disclosure through improper validation of user-supplied file paths. It is crucial to update to the patched version and implement necessary security measures to mitigate risks associated with this vulnerability.

See every vulnerability recorded for mcp-atlassian →

Share this vulnerability

FAQ

CVE-2026-77257 is a vulnerability in the mcp-atlassian package that allows authenticated users to upload arbitrary server-local files, leading to potential local file disclosure.

The vulnerability can lead to the exposure of sensitive information such as API tokens, OAuth credentials, and other local secrets, especially in shared environments.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If immediate updating is not possible, consider implementing temporary workarounds such as disabling local file uploads or restricting access to sensitive directories.

The CVSS score of this vulnerability is 8.3, indicating a high severity level.

Related vulnerabilities

Recent vulnerabilities recorded for mcp-atlassian.

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