{"answers":{"affected":"3 open source packages ship an affected version, including mcp-atlassian. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77250 exists.","fix":"Upgrade mcp-atlassian to 0.22.0 or later.","what":"CVE-2026-77250 is a medium-severity vulnerability in sooperset mcp-atlassian, published on 22 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77250 and fix it if it is affected.\n\nWhat it is: CVE-2026-77250 is a medium-severity vulnerability in sooperset mcp-atlassian, published on 22 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77250 exists.\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-77250/ (Markdown: https://insights.sbomify.com/CVE-2026-77250/index.md)","id":"CVE-2026-77250","markdown":"https://insights.sbomify.com/CVE-2026-77250/index.md","name":"CVE-2026-77250","record":{"aliases":["GHSA-g5xv-mhgm-v5f6","PYSEC-2026-4094"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"MCP Atlassian server","requires_auth":"low_privilege","summary":"Local attackers can read plaintext OAuth tokens from insecurely stored files to hijack Atlassian accounts.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mcp_atlassian","vendor":"mcp-atlassian"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, OAuthConfig writes a plaintext fallback file containing access and refresh tokens under the user's .mcp-atlassian directory using process-default permissions. On systems with a permissive umask, same-group or other local users and processes can read the persisted tokens and reuse the associated Atlassian access. The advisory traces the vulnerable input and processing flow through OAuthConfig._save_tokens, ~/.mcp-atlassian/oauth-\u003cclient_id\u003e.json, access_token, and refresh_token, which identify the affected entry points, controls, and code paths. 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":"weaponised"},"has_fix":true,"headline":"MCP Atlassian: OAuth fallback token storage writes plaintext access and refresh tokens with group-readable permissions","id":"CVE-2026-77250","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"MCP Atlassian: JIRA_PROJECTS_FILTER / CONFLUENCE_SPACES_FILTER allow forbidden-project content exfiltration (one LIVE-proven on Atlassian Cloud)","id":"CVE-2026-77251"},"packages":[{"ecosystem":"PyPI","fixed":["0.22.0"],"introduced":["0"],"last_affected":[],"package":"mcp-atlassian","purl":null,"source":"GHSA-g5xv-mhgm-v5f6"},{"ecosystem":"PyPI","fixed":["0.22.0"],"introduced":["0"],"last_affected":[],"package":"mcp-atlassian","purl":"pkg:pypi/mcp-atlassian","source":"GHSA-g5xv-mhgm-v5f6"},{"ecosystem":"PyPI","fixed":["0.22.0"],"introduced":["0"],"last_affected":[],"package":"mcp-atlassian","purl":"pkg:pypi/mcp-atlassian","source":"PYSEC-2026-4094"}],"prev":{"headline":"MCP Atlassian: Incomplete fix for GHSA-7r34-79r5-rcc9: redirect-based SSRF via unhooked requests session in Jira user-permission lookup","id":"CVE-2026-77249"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["sooperset"]},"summary":"Local attackers can read plaintext OAuth tokens from insecurely stored files to hijack Atlassian accounts.","url":"https://insights.sbomify.com/CVE-2026-77250/"}