Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of mcp-atlassian before 0.22.0 are vulnerable to server-side request forgery through DNS rebinding in the header-based authentication flow. The SSRF check resolves the hostname once, but the actual request resolves it again later, so a remote, unauthenticated attacker could point the request at internal addresses such as cloud metadata services. The source describes the attack as probabilistic and limited to deployments that accept header-based personal access tokens. Upgrade to mcp-atlassian 0.22.0 or later. No workaround is listed.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.9 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0029, the 21st percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:09 UTC First seen by agentprime
- 31 Oct 2026, 14:09 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-49xv-9743-pw8w
- OSV: GHSA-49xv-9743-pw8w
- github.com/sooperset/mcp-atlassian/security/advisories/GHSA-49xv-9743-pw8w
- nvd.nist.gov/vuln/detail/CVE-2026-77265
- github.com/sooperset/mcp-atlassian/pull/1448
- github.com/sooperset/mcp-atlassian/commit/b041733473f95119dd539542a43c280737a8e460
- github.com/sooperset/mcp-atlassian
- github.com/sooperset/mcp-atlassian/releases/tag/v0.22.0