major vulnerability· requires attention

Allows unauthenticated network clients to act as the operator for Jira/Confluence, enabling org-wide data modification/exfiltration; affects widely-used Atlassian integrations.

Applications

CVE-2026-77244

10.0

Critical

EPSS 0.35%Patch available

Unauthenticated MCP server access lets attackers act as operator on Jira/Confluence

exploited

No known exploitation not in CISA KEV as of our last sync

fix

Patch available see the advisory in the references

likelihood

EPSS 0.35%top 72% of scored CVEs

Published 22 Sept 2026Analysed here 25 Sept 2026CVSS scored by the publisher (CNA)

common questions

Is CVE-2026-77244 being exploited?

Not confirmed. CVE-2026-77244 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.

How severe is CVE-2026-77244?

CVE-2026-77244 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-77244?

Yes. A fix has been recorded for CVE-2026-77244. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-77244 affect?

CVE-2026-77244 affects mcp-atlassian < 0.22.0, Atlassian Jira (via MCP integration), Atlassian Confluence (via MCP integration). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-77244?

Upgrade to mcp-atlassian v0.22.0, restrict MCP network access, rotate operator credentials

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary

technical analysis

affected

mcp-atlassian < 0.22.0Atlassian Jira (via MCP integration)Atlassian Confluence (via MCP integration)

impact

Unauthenticated network requests to MCP can perform read/write actions in Jira/Confluence using operator credentials.

action required

Immediate action required

affected versions

sooperset mcp-atlassian

affected< 0.22.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

cisa ssvc

exploitation: none
automatable: yes
technical impact: total

Assessed by CISA 22 Sept 2026 (SSVC 2.0.3).

timeline

22 Sept 2026Published
22 Sept 2026CISA SSVC assessment: exploitation none · same day later
23 Sept 2026CVE record last updated · 1 day later
25 Sept 2026Analysed by vulneraibility.com · 2 days later

also known as

GHSA-wrhw-j3f9-8vc6 PYSEC-2026-4103

how to fix

Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.

references

NVD CVE.org CVE Details Source

4 references in the CVE record: 4 links

Linkgithub.com /sooperset/mcp-atlassian/security/advisories/GHSA-wrhw-j3f9-8vc6
Linkgithub.com /sooperset/mcp-atlassian/pull/1448
Linkgithub.com /sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460
Linkgithub.com /sooperset/mcp-atlassian/releases/tag/v0.22.0

sources

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
OSV: advisory aliases and downstream package versions
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free