MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, header-supplied Jira or Confluence URLs are resolved and validated before the HTTP client resolves the hostname again for the connection. An unauthenticated caller can use a DNS-rebinding hostname that returns a public address during validation and an internal address during connection, causing requests to internal or metadata services. The advisory traces the vulnerable input and processing flow through X-Atlassian-Jira-Url, X-Atlassian-Confluence-Url, validate_url_for_ssrf, and DNS rebinding, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.
CVE-2026-77265
MEDIUMPre-NVD 5.95.9—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(medium)
- EG Risk
- 31(Track)EG Risk 31/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity59% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 36%
- KEV
- Not listed
Published
September 22, 2026
Last Modified
September 23, 2026
Advisory Details (4)
Auto-updated Sep 22, 2026🔬 Proof of concept available. Patch available. Sources: github_pr, github_commit, github_release, github.
github_release Patch Available
v0.22.0
Patch available: sooperset/mcp-atlassian v0.22.0
https://github.com/sooperset/mcp-atlassian/releases/tag/v0.22.0github_commit Patch Available
commit b041733473f9 (sooperset/mcp-atlassian)
Patch available: sooperset/mcp-atlassian v0.22.0 (contains commit b041733473f9)
https://github.com/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460github_pr Patch Available
Security hardening across attachment, transport, SSRF, authorization, filter, and OAuth layers
Patch available: sooperset/mcp-atlassian v0.22.0 (PR #1448 merged 2026-07-10)
https://github.com/sooperset/mcp-atlassian/pull/1448github Patch Available🟡 PoC Available
SSRF via DNS Rebinding in Header-Based Authentication Flow · Advisory · sooperset/mcp-atlassian · GitHub
https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-49xv-9743-pw8wVendor Advisories for CVE-2026-77265(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| mcp-atlassian | 0.1.1 ... 0.9.0 (79 versions) | 0.22.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-23 18:37 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 18:31 UTCEG score recompute
- 2026-09-22 17:53 UTCEG score recompute
- 2026-09-22 17:53 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-77265?
CVE-2026-77265 is a medium vulnerability published on September 22, 2026. MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, header-supplied Jira or Confluence URLs are resolved and validated before the HTTP client resolves the hostname again for the connection. An unauthenticated caller can use a…
When was CVE-2026-77265 disclosed?
CVE-2026-77265 was first published in the National Vulnerability Database on September 22, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-77265 actively exploited?
CVE-2026-77265 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.9% of all scored CVEs.
What is the CVSS score of CVE-2026-77265?
CVE-2026-77265 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-77265?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77265, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-77265
Is Your Infrastructure Affected by CVE-2026-77265?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.