CVE-2026-77250: MCP Atlassian OAuth Fallback Token Storage Writes Vulnerability
MODERATECVE-2026-77250 is a MODERATE (CVSS 6.1) oauth fallback token storage writes vulnerability (CWE-312: Cleartext Storage of Sensitive Information) affecting MCP Atlassian libraries in the PyPI ecosystem. The issue involves oauth fallback token storage writes plaintext access and refresh tokens with group-readable permissions. Remediation is available by upgrading affected packages to version 0.22.0.
CVE-2026-77250 at a Glance
Security Impact
CVSS: 6.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N).
How to Fix CVE-2026-77250
To remediate this vulnerability, upgrade all affected MCP Atlassian dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install mcp-atlassian>=0.22.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show mcp-atlassian
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2026-77250, inspect your installed packages using pip:
pip show mcp-atlassian
Analyze the terminal output to locate any version of MCP Atlassian in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.22.0), your application is affected.
Note: The pip show mcp-atlassian command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-312: Cleartext Storage of Sensitive Information, where the product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. In MCP Atlassian, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-77250 Affected MCP Atlassian Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
mcp-atlassian
|
PyPI |
< 0.22.0
|
0.22.0
|
References
Frequently Asked Questions
What is CVE-2026-77250?
Which MCP Atlassian versions are affected?
What version fixes CVE-2026-77250?
Is mcp-atlassian affected?
What is the CVSS score of CVE-2026-77250?
What CWE is associated with CVE-2026-77250?
How can I check PyPI dependencies for CVE-2026-77250?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-g5xv-mhgm-v5f6",
"modified" : "2026-09-22T20:36:34Z",
"published" : "2026-09-22T20:36:34Z",
"aliases" : [ "CVE-2026-77250" ],
"summary" : "MCP Atlassian: OAuth fallback token storage writes plaintext access and refresh tokens with group-readable permissions",
"details" : "### Summary\n\nWhen OAuth tokens are saved, MCP Atlassian always writes a plaintext fallback copy under `~/.mcp-atlassian/oauth-<client_id>.json`. The fallback file is created with the process default umask rather than restrictive permissions. In this environment the file was created as mode `0664`, exposing access and refresh tokens to same-group local users and any process that can read the home directory.\n\n### Details\n\n`OAuthConfig._save_tokens()` stores OAuth token data in keyring, but it also unconditionally maintains a plaintext file fallback for backwards compatibility in `src/mcp_atlassian/utils/oauth.py:350-386`. If keyring saving fails it also falls back to the same file path in `src/mcp_atlassian/utils/oauth.py:387-391`.\n\nThe fallback writer creates `~/.mcp-atlassian` and then writes `oauth-<client_id>.json` with a normal `open(token_path, \"w\")` call in `src/mcp_atlassian/utils/oauth.py:392-420`. No `mode=0o600`, `os.open(..., 0o600)`, `chmod`, or owner-only directory permission is applied. The file contains both `access_token` and `refresh_token` (`src/mcp_atlassian/utils/oauth.py:360-367`) and is later loaded from the same plaintext path in `src/mcp_atlassian/utils/oauth.py:450-470`.\n\nThe security policy warns that OAuth client credentials and secrets should not be exposed (`SECURITY.md:39-44`), but the current implementation creates a persistent plaintext token copy even when keyring succeeds.\n\n### PoC\n\nThe following safe local proof uses a temporary `HOME` and mocked keyring writes. It creates and deletes only temporary files.\n\n```bash\nuv run python - <<'PY'\nimport json, os, shutil, stat, tempfile\nfrom pathlib import Path\nfrom unittest.mock import patch\nfrom mcp_atlassian.utils.oauth import OAuthConfig\n\nhome = tempfile.mkdtemp(prefix='mcp-atlassian-oauth-poc-')\nold_home = os.environ.get('HOME')\nos.environ['HOME'] = home\ntry:\n cfg = OAuthConfig(client_id='poc-client', client_secret='client-secret', redirect_uri='http://localhost/callback', scope='offline_access', cloud_id='cloud-id')\n cfg.access_token = 'poc-access-token'\n cfg.refresh_token = 'poc-refresh-token'\n cfg.expires_at = 2000000000\n with patch('keyring.set_password', return_value=None):\n cfg._save_tokens()\n token_file = Path(home) / '.mcp-atlassian' / 'oauth-poc-client.json'\n mode = stat.S_IMODE(token_file.stat().st_mode)\n data = json.loads(token_file.read_text())\n print(json.dumps({\n 'token_file_exists': token_file.exists(),\n 'token_file_mode_octal': oct(mode),\n 'contains_access_token': data.get('access_token') == 'poc-access-token',\n 'contains_refresh_token': data.get('refresh_token') == 'poc-refresh-token',\n 'token_file_path': str(token_file),\n }, indent=2, sort_keys=True))\nfinally:\n if old_home is not None:\n os.environ['HOME'] = old_home\n else:\n os.environ.pop('HOME', None)\n shutil.rmtree(home)\nPY\n```\n\nObserved output from this environment:\n\n```json\n{\n \"contains_access_token\": true,\n \"contains_refresh_token\": true,\n \"token_file_exists\": true,\n \"token_file_mode_octal\": \"0o664\",\n \"token_file_path\": \"/tmp/mcp-atlassian-oauth-poc-9m9wvktp/.mcp-atlassian/oauth-poc-client.json\"\n}\n```\n\nThe proof confirms that a plaintext file containing both access and refresh tokens is created and is not owner-only.\n\n### Impact\n\nA local user, container sidecar, compromised dependency, backup job, or other process with filesystem read access to the account's home directory can recover OAuth access and refresh tokens. Refresh tokens can allow continued Atlassian API access until revoked or expired, depending on the OAuth app and token policy. In shared hosts, Kubernetes volumes, developer workstations, and CI runners, this can lead to persistent Atlassian account compromise.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "mcp-atlassian"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.22.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/sooperset/mcp-atlassian/security/advisories/GHSA-g5xv-mhgm-v5f6"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-77250"
}, {
"type" : "WEB",
"url" : "https://github.com/sooperset/mcp-atlassian/pull/1448"
}, {
"type" : "WEB",
"url" : "https://github.com/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/sooperset/mcp-atlassian"
}, {
"type" : "WEB",
"url" : "https://github.com/sooperset/mcp-atlassian/releases/tag/v0.22.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-312" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-22T20:36:34Z",
"nvd_published_at" : "2026-09-22T18:17:17Z"
}
}