CVE-2026-73497

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% 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
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). From 0.17.0 until 0.22.0, validate_url_for_ssrf resolves the attacker-controlled X-Atlassian-Jira-Url and X-Atlassian-Confluence-Url header host once at middleware time, but the outbound request is built with the raw hostname and resolves it again at connection time with no IP pinning. An attacker-controlled DNS-rebinding name can return a public IP during validation and 169.254.169.254 or another internal IP during connection, enabling unauthenticated server-side requests to cloud metadata or internal services. The flaw spans src/mcp_atlassian/utils/urls.py, src/mcp_atlassian/servers/main.py, and src/mcp_atlassian/servers/dependencies.py; validate_url_for_ssrf returns only a verdict rather than a pinned IP, UserTokenMiddleware processes the attacker-controlled headers before fetcher creation, and the Jira and Confluence fetchers use the raw hostname. This issue is fixed in version 0.22.0.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/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 computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

September 14, 2026

Last Modified

September 15, 2026

Advisory Details (4)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_pr, github_commit.
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.0
github_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/b041733473f95119dd539542a43c280737a8e460
github_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/1448
github Patch Available🟡 PoC Available

DNS-rebinding TOCTOU bypass of the SSRF fix (GHSA-7r34): unauthenticated SSRF to cloud metadata on patched ≥0.17.0 · Advisory · sooperset/mcp-atlassian · GitHub

https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-489g-7rxv-6c8q

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× 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.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-19 17:19 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 16:38 UTCEG score recompute
  5. 2026-09-16 15:16 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 14:35 UTCEG score recompute
  9. 2026-09-15 14:03 UTCEG score recompute
  10. 2026-09-14 20:21 UTCEG score recompute
  11. 2026-09-14 19:55 UTCEG score recompute
  12. 2026-09-14 19:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73497?
CVE-2026-73497 is a medium vulnerability published on September 14, 2026. MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). From 0.17.0 until 0.22.0, validateurlforssrf resolves the attacker-controlled X-Atlassian-Jira-Url and X-Atlassian-Confluence-Url header host once at middleware time, but the outbound request is…
When was CVE-2026-73497 disclosed?
CVE-2026-73497 was first published in the National Vulnerability Database on September 14, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73497 actively exploited?
CVE-2026-73497 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 85.7% of all scored CVEs.
What is the CVSS score of CVE-2026-73497?
CVE-2026-73497 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-73497?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73497, 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

Explore the affected products and dependency analysis for CVE-2026-73497

Explore →

Is Your Infrastructure Affected by CVE-2026-73497?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.