← Search results
CVE-LINKED INVENTORY34 SECURITY RECORDS
sooperset
mcp-atlassian
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at mcp-atlassian, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-77246 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77248 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77256 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77249 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77259 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77268 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77247 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77272 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77269 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77266 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77255 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77262 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77254 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77253 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77257 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77261 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77260 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77271 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77242 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77243 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77251 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77252 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77267 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77250 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77244 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77265 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77270 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77258 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-77274 | 22 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-73497 | 14 Sep 2026 | mcp-atlassian: >= 0.17.0, < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-73496 | 14 Sep 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-73498 | 12 Aug 2026 | mcp-atlassian: < 0.22.0 | 0.22.0. | Update reference ↗ |
| CVE-2026-27825 | 10 Mar 2026 | < 0.17.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-27826 | 10 Mar 2026 | < 0.17.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.