{"items":[{"id":"NVI-00016458","kind":"vulnerability","title":"MCP Atlassian: HTTP upload tools accept arbitrary server-local file paths","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mrq8-fv7v-hhjg","CVE-2026-77257"],"plain_summary":"GitHub lists this reviewed advisory for mcp-atlassian. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-72d11e9fe4f7663091b6eba3adfa810a"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-72d11e9fe4f7663091b6eba3adfa810a","url":"https://github.com/advisories/GHSA-mrq8-fv7v-hhjg","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-mrq8-fv7v-hhjg","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T14:29:31.527Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-72d11e9fe4f7663091b6eba3adfa810a"],"technology":"mcp-atlassian","known_exclusions":[],"conditions_summary":"# sooperset/mcp-atlassian: HTTP upload tools can attach arbitrary server-local files\n\nDate: 2026-05-05\nTarget: `sooperset/mcp-atlassian`\nCommit: `d8bc78698a63cb6b321c7ca796d6329d448f7f6d`\n\n## Summary\n\n`mcp-atlassian` supports HTTP/SSE deployment for persistent, remote, and multi-user use. In that mode, write-capable Jira and Confluence attachment flows accept caller-controlled server-local file paths and read those paths without an upload-source allowlist or base directory restriction.\n\nAn authenticated caller, or a prompt-injected agent with tool-call capability, can cause the MCP server process to read a local file it can access and attach that file into a Jira issue or Confluence page using configured Atlassian credentials.\n\nThis is distinct from the prior download-path advisory: that issue was an arbitrary file write sink. This path is upload-source local file disclosure.\n\n## Impact\n\nImpact is local file disclosure through an authenticated Atlassian attachment write. In Docker/Kubernetes deployments that mount `.env` or token material into the service, exposed files may include API tokens, OAuth credentials, service configuration, or other local secrets readable by the MCP proc","public_affected_ranges":["< 0.22.0"]}],"null_published_at":"2026-11-04T10:04:35.892Z","source_updated_at":"2026-09-22T20:35:00.000Z","source_disclosed_at":"2026-09-22T20:34:58.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T14:29:31.527Z"}],"next_cursor":null,"snapshot_revision":"42594"}