---
id: CVE-2026-77242
title: >-
  MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products
  (Confluence and Jira)
summary: >-
  MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products
  (Confluence and Jira). Prior to 0.22.0, validate_url_for_ssrf checks a
  hostname's resolved addresses, but Requests and urllib3 resolve the hostname
  again when …
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N'
cwe:
  - CWE-367
  - CWE-918
vendor: sooperset
product: mcp-atlassian
affected:
  - mcp-atlassian < 0.22.0
published: '2026-09-22'
updated: '2026-09-23'
sourceUpdated: '2026-09-23T18:28:25.093'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-77242'
references:
  - url: >-
      https://github.com/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460
    label: security-advisories@github.com
  - url: 'https://github.com/sooperset/mcp-atlassian/pull/1448'
    label: security-advisories@github.com
  - url: 'https://github.com/sooperset/mcp-atlassian/releases/tag/v0.22.0'
    label: security-advisories@github.com
  - url: >-
      https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-72fm-whvq-jghf
    label: security-advisories@github.com
  - url: >-
      https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-72fm-whvq-jghf
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
  - cve.org
  - exploit-available
epss: 0.00293
epssPercentile: 0.19492
exploitAvailable: true
ssvc:
  exploitation: poc
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-09-22T18:48:54.750780Z'
ingestedAt: '2026-09-22T19:09:09.985Z'
---

## Overview

MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, validate_url_for_ssrf checks a hostname's resolved addresses, but Requests and urllib3 resolve the hostname again when connecting. A caller can use a short-lived DNS answer that is public during validation and private during connection, preserving unauthenticated access to internal or metadata endpoints despite the earlier CVE-2026-27826 remediation. The advisory traces the vulnerable input and processing flow through validate_url_for_ssrf, _check_dns_resolution, socket.getaddrinfo, and _make_ssrf_safe_hook, which identify the affected entry points, controls, and code paths. This issue is fixed in version 0.22.0.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.