NVD / CVE Program· CNA GitHub_M

CVE-2026-77262: MCP Atlassian: Path Traversal / Arbitrary File Read in confluence_upload_attachment MCP tool (incomplete fix of CVE-2026-27825)

Noroxi assessment

Priority: Monitor (action score 34/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 0.55% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: sooperset mcp-atlassian 0.22.0.

Low priority for now. Upgrade to sooperset mcp-atlassian 0.22.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, confluence_upload_attachment accepts an attacker-controlled file_path and does not apply the path restriction added for the earlier download vulnerability. A caller can traverse outside the workspace and upload arbitrary server-readable files to Confluence. The advisory traces the vulnerable input and processing flow through confluence_upload_attachment, file_path, and CVE-2026-27825, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.

HighCVSS 8.6 · v3.1—Proof of concept Fix available

Published: Sep 22, 2026
Updated: Sep 29, 2026
EPSS: 0.5% · 46th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 34 / 40 · 8.6 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: proof of concept
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 8.6; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
mcp-atlassian	mcp atlassian	cpe:2.3:a:mcp-atlassian:mcp_atlassian

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

mcp-atlassian mcp atlassianbefore 0.22.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

sooperset mcp-atlassian
- < 0.22.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
PyPI	mcp-atlassian	before 0.22.0	0.22.0

Same product

mcp-atlassian: all records

Other highest-scoring records for the same primary product.

CVE-2026-77244[mcp-atlassian] Authentication bypass in HTTP transport: AtlassianOpaqueTokenVerifier accepts any non-empty token
40Plan
CVE-2026-77254MCP Atlassian: Unauthenticated HTTP MCP requests can use globally configured Jira and Confluence credentials
36Monitor
CVE-2026-27825MCP Atlassian has an arbitrary file write leading to arbitrary code execution via unconstrained download_path in confluence_download_attachment
36Monitor

Published before and after this one in the same product

← EarlierCVE-2026-77257Sep 22, 2026 · MCP Atlassian: HTTP upload tools accept arbitrary server-local file paths
33Monitor
← EarlierCVE-2026-77259Sep 22, 2026 · MCP Atlassian: Arbitrary file read via confluence_upload_attachment allows exfiltration of server credentials
30Monitor
Later →CVE-2026-77268Sep 22, 2026 · MCP Atlassian: Insecure File Permissions on OAuth Token Storage
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
sooperset mcp-atlassian	0.22.0 · description	Vendor (CNA)
PyPI:mcp-atlassian	0.22.0	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:0	2026-04-29

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

First PoCApr 29, 2026-147 d
PublishedSep 22, 2026
TodayOct 26, 2026+34 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-27825196 days apartMCP Atlassian has an arbitrary file write leading to arbitrary code execution via unconstrained download_path in confluence_download_attachment
36Monitor
CVE-2026-772460 days apartMCP Atlassian: MCP HTTP Client Server-Local File Exfiltration via Unvalidated Attachment Upload Path
34Monitor
CVE-2026-772480 days apartMCP Atlassian: Unauthenticated arbitrary local file read via upload_attachment file_path, chained with missing auth on streamable-http transport
34Monitor
CVE-2026-772550 days apartMCP Atlassian: Arbitrary File Read & Exfiltration (Confused Deputy) in JIRA update_issue
34Monitor
CVE-2026-772570 days apartMCP Atlassian: HTTP upload tools accept arbitrary server-local file paths
33Monitor
CVE-2026-772600 days apartMCP Atlassian: Arbitrary local file READ via unconstrained file_path in upload_attachment (Confluence + Jira)
33Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Changed
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC
SSVC exploitation— → pocSep 28, 2026, 8:49 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records

Noroxi analysis

What does it mean in your environment?

We use this product, ask for help

Data sources and verification

CNA: GitHub_M

CVE.org (CNA)Sep 28, 2026, 5:20 PM UTC
CISA ADPSep 28, 2026, 5:20 PM UTC
NVDSep 29, 2026, 6:59 PM UTC
FIRST EPSSOct 25, 2026, 12:00 AM UTC
OSV / GHSAOct 26, 2026, 3:19 AM UTC
PoC-in-GitHubOct 26, 2026, 3:19 AM UTC

Each line is when that source was last processed for this record.