{"answers":{"affected":"3 open source packages ship an affected version, including mcp-atlassian. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-77261 in the wild and no public exploit code.","fix":"Upgrade mcp-atlassian to 0.22.0 or later.","what":"CVE-2026-77261 is a high-severity server-side request forgery vulnerability in sooperset mcp-atlassian, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77261 and fix it if it is affected.\n\nWhat it is: CVE-2026-77261 is a high-severity server-side request forgery vulnerability in sooperset mcp-atlassian, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-77261 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mcp-atlassian (PyPI): affected all versions; fixed in 0.22.0\n- mcp-atlassian (PyPI): affected all versions; fixed in 0.22.0\n- mcp-atlassian (PyPI): affected all versions; fixed in 0.22.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-77261/ (Markdown: https://insights.sbomify.com/CVE-2026-77261/index.md)","id":"CVE-2026-77261","markdown":"https://insights.sbomify.com/CVE-2026-77261/index.md","name":"CVE-2026-77261","record":{"aliases":["GHSA-6529-c226-h328","PYSEC-2026-4085"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MCP Atlassian server","requires_auth":"low_privilege","summary":"Attackers can force the MCP Atlassian server to access internal resources via redirects when using basic-auth or OAuth, bypassing SSRF protections.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mcp_atlassian","vendor":"mcp-atlassian"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, _make_ssrf_safe_hook is omitted from JiraFetcher and ConfluenceFetcher sessions created through the basic-auth and oauth_pat branches. If an attacker-controlled or compromised configured Atlassian instance returns a redirect to an internal address, those sessions can follow the redirect without revalidating its destination. This issue is fixed in version 0.22.0.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"MCP Atlassian: SSRF redirect protection missing for basic-auth and OAuth authentication branches","id":"CVE-2026-77261","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"MCP Atlassian: Path Traversal / Arbitrary File Read in confluence_upload_attachment MCP tool (incomplete fix of GHSA-xjgw-4wvw-rgm4)","id":"CVE-2026-77262"},"packages":[{"ecosystem":"PyPI","fixed":["0.22.0"],"introduced":["0"],"last_affected":[],"package":"mcp-atlassian","purl":null,"source":"GHSA-6529-c226-h328"},{"ecosystem":"PyPI","fixed":["0.22.0"],"introduced":["0"],"last_affected":[],"package":"mcp-atlassian","purl":"pkg:pypi/mcp-atlassian","source":"GHSA-6529-c226-h328"},{"ecosystem":"PyPI","fixed":["0.22.0"],"introduced":["0"],"last_affected":[],"package":"mcp-atlassian","purl":"pkg:pypi/mcp-atlassian","source":"PYSEC-2026-4085"}],"prev":{"headline":"MCP Atlassian: Arbitrary local file READ via unconstrained file_path in upload_attachment (Confluence + Jira)","id":"CVE-2026-77260"},"products":["mcp-atlassian"],"published":"2026-09-22","related":[{"cvss_score":10,"headline":"[mcp-atlassian] Authentication bypass in HTTP transport: AtlassianOpaqueTokenVerifier accepts any non-empty token","id":"CVE-2026-77244","kev_date_added":null,"published":"2026-09-22"},{"cvss_score":9.1,"headline":"MCP Atlassian: Unauthenticated HTTP MCP requests can use globally configured Jira and Confluence credentials","id":"CVE-2026-77254","kev_date_added":null,"published":"2026-09-22"},{"cvss_score":9.1,"headline":"MCP Atlassian has an arbitrary file write leading to arbitrary code execution via unconstrained download_path in confluence_download_attachment","id":"CVE-2026-27825","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":8.8,"headline":"MCP Atlassian: ENABLED_TOOLS / Toolset authorization bypass","id":"CVE-2026-77243","kev_date_added":null,"published":"2026-09-22"},{"cvss_score":8.8,"headline":"MCP Atlassian: SSRF Protection Bypass","id":"CVE-2026-77274","kev_date_added":null,"published":"2026-09-22"},{"cvss_score":8.6,"headline":"MCP Atlassian: Unauthenticated arbitrary local file read via upload_attachment file_path, chained with missing auth on streamable-http transport","id":"CVE-2026-77248","kev_date_added":null,"published":"2026-09-22"},{"cvss_score":8.6,"headline":"MCP Atlassian: Arbitrary File Read \u0026 Exfiltration (Confused Deputy) in JIRA update_issue","id":"CVE-2026-77255","kev_date_added":null,"published":"2026-09-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-23","vendors":["sooperset"]},"summary":"Attackers can force the MCP Atlassian server to access internal resources via redirects when using basic-auth or OAuth, bypassing SSRF protections.","url":"https://insights.sbomify.com/CVE-2026-77261/"}