Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The SSRF validation in mcp-atlassian versions before 0.22.0 can be bypassed with a crafted URL containing a backslash before userinfo-like syntax, so the URL check validates one host while requests go to another. An attacker who can supply the X-Atlassian-Jira-Url or X-Atlassian-Confluence-Url header can make the server send requests to loopback or internal services. Upgrade to mcp-atlassian 0.22.0 or later. The source gives few details on the exact trigger conditions.
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 |
|---|---|---|---|---|
| 8.8 | High | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0033, the 26th 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-hgcf-4mq8-5266
- OSV: GHSA-hgcf-4mq8-5266
- github.com/sooperset/mcp-atlassian/security/advisories/GHSA-hgcf-4mq8-5266
- nvd.nist.gov/vuln/detail/CVE-2026-77274
- 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