VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mcp-atlassian: vulnerability history, versions and safety

mcp-atlassian is a package in the PyPI ecosystem. Vulert records 58 vulnerabilities for it across 79 releases, from Mar 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
58 vulnerabilities recorded C2 H19 M9 U28
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
58 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mcp-atlassian vulnerabilities

Vulert verdict on mcp-atlassian 0.23.1 i

Updated on 23 Oct 2026

Good news: 0.23.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 58.

Package health score 49/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 0.23.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.23.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.23.1 — unaffected i
  • Vulnerabilities on record 58 over 1 year · 58 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Last release 2 months ago i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for mcp-atlassian, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.23.1 19 Aug 2026 none — — Details →
0.23.0 18 Jul 2026 none — — Details →
0.22.1 11 Jul 2026 none — — Details →
0.22.0 10 Jul 2026 none — — Details →
0.21.1 10 Apr 2026 C1 H18 M9 U26 — Yes Details →
0.21.0 02 Mar 2026 C1 H18 M9 U26 — Yes Details →
0.20.1 27 Feb 2026 C1 H18 M9 U26 — Yes Details →
0.20.0 27 Feb 2026 C1 H18 M9 U26 — Yes Details →
0.19.0 27 Feb 2026 C1 H18 M9 U26 — Yes Details →
0.18.1 25 Feb 2026 C1 H18 M9 U26 — Yes Details →
0.18.0 25 Feb 2026 C1 H18 M9 U26 — Yes Details →
0.17.0 24 Feb 2026 C1 H18 M9 U26 — Yes Details →
0.16.1 21 Feb 2026 C2 H19 M9 U28 — Yes Details →
0.16.0 21 Feb 2026 C2 H19 M9 U28 — Yes Details →
0.15.0 20 Feb 2026 C2 H19 M9 U28 — Yes Details →
0.14.3 20 Feb 2026 C2 H19 M9 U28 — Yes Details →
0.14.2 18 Feb 2026 C2 H19 M9 U28 — Yes Details →
0.14.1 18 Feb 2026 C2 H19 M9 U28 — Yes Details →
0.14.0 18 Feb 2026 C2 H19 M9 U28 — Yes Details →
0.13.1 18 Feb 2026 C2 H19 M9 U28 — Yes Details →
0.13.0 06 Jan 2026 C2 H19 M9 U28 — Yes Details →
0.12.0 30 Dec 2025 C2 H19 M9 U28 — Yes Details →
0.11.12 29 Dec 2025 C2 H19 M9 U28 — Yes Details →
0.11.11 29 Dec 2025 C2 H19 M9 U28 — Yes Details →
0.11.10 26 Nov 2025 C2 H19 M9 U28 — Yes Details →
0.11.9 29 Jun 2025 C2 H19 M9 U28 — Yes Details →
0.11.8 25 Jun 2025 C2 H19 M9 U28 — Yes Details →
0.11.7 19 Jun 2025 C2 H19 M9 U28 — Yes Details →
0.11.6 18 Jun 2025 C2 H19 M9 U28 — Yes Details →
0.11.5 18 Jun 2025 C2 H19 M9 U28 — Yes Details →
0.11.4 18 Jun 2025 C2 H19 M9 U28 — Yes Details →
0.11.3 17 Jun 2025 C2 H19 M9 U28 — Yes Details →
0.11.2 30 May 2025 C2 H19 M9 U28 — Yes Details →
0.11.2a2 30 May 2025 C2 H19 M9 U28 — Yes Details →
0.11.1 19 May 2025 C2 H19 M9 U28 — Yes Details →
0.11.0 17 May 2025 C2 H19 M9 U28 — Yes Details →
0.10.6 11 May 2025 C2 H19 M9 U28 — Yes Details →
0.10.5 10 May 2025 C2 H19 M9 U28 — Yes Details →
0.10.4 09 May 2025 C2 H19 M9 U28 — Yes Details →
0.10.3 06 May 2025 C2 H19 M9 U28 — Yes Details →
0.10.2 05 May 2025 C2 H19 M9 U28 — Yes Details →
0.10.1 05 May 2025 C2 H19 M9 U28 — Yes Details →
0.10.0 05 May 2025 C2 H19 M9 U28 — Yes Details →
0.9.0 01 May 2025 C2 H19 M9 U28 — Yes Details →
0.8.4 26 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.8.3 23 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.8.2 23 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.8.1 21 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.8.0 21 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.7.1 17 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.7.0 16 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.6.5 12 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.6.4 09 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.6.3 06 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.6.2 05 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.6.1 04 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.6.0 04 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.5.0 03 Apr 2025 C2 H19 M9 U28 — Yes Details →
0.4.0 27 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.3.1 26 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.3.0 23 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.2.6 22 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.2.5 18 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.2.4 16 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.2.3 16 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.2.2 13 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.2.1 12 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.2.0 11 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.1.16 08 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.1.15 08 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.1.14 04 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.1.13 04 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.1.12 04 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.1.11 03 Mar 2025 C2 H19 M9 U28 — Yes Details →
0.1.10 22 Feb 2025 C2 H19 M9 U28 — Yes Details →
0.1.9 21 Feb 2025 C2 H19 M9 U28 — Yes Details →
0.1.8 16 Feb 2025 C2 H19 M9 U28 — Yes Details →
0.1.7 20 Dec 2024 C2 H19 M9 U28 — Yes Details →
0.1.6 19 Dec 2024 C2 H19 M9 U28 — Yes Details →
0.1.4 15 Dec 2024 C2 H19 M9 U28 — Yes Details →
0.1.3 05 Dec 2024 C2 H19 M9 U28 — Yes Details →
0.1.2 05 Dec 2024 C2 H19 M9 U28 — Yes Details →
0.1.1 04 Dec 2024 C2 H19 M9 U28 — Yes Details →

All 83 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 58

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 58 of the 58 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for mcp-atlassian

The 5 most severe of 58 vulnerabilities recorded for this package

Search all 58 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-77244: mcp-atlassian Authentication Bypass Vulnerability 10.0 critical 0.22.0 22 Sep 2026
CVE-2026-77244: mcp-atlassian Authentication Bypass Vulnerability 10.0 critical 0.22.0 01 Oct 2026
CVE-2026-27825: mcp-atlassian Arbitrary File Write Leading to Code Execution 9.0 critical 0.17.0 10 Mar 2026
CVE-2026-27825: mcp-atlassian Arbitrary File Write Leading to Code Execution 9.0 critical 0.17.0 29 Jun 2026
CVE-2026-77243: mcp-atlassian Toolset Authorization Bypass Vulnerability 8.8 high 0.22.0 22 Sep 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About mcp-atlassian

Is mcp-atlassian safe to use?

Vulert records 58 vulnerabilities for mcp-atlassian in PyPI: 2 critical, 19 high, 9 medium and 0 low, plus 28 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is mcp-atlassian's Vulert package health score?

Vulert scores mcp-atlassian 49/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of mcp-atlassian affected?

No. 0.23.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of mcp-atlassian should I use?

0.23.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does mcp-atlassian have?

58 vulnerabilities are recorded for mcp-atlassian in the PyPI ecosystem: 2 critical, 19 high, 9 medium and 0 low, plus 28 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mcp-atlassian vulnerabilities disclosed?

58 vulnerabilities were recorded for mcp-atlassian in the last 12 months, and the oldest entry in this database dates to 10 Mar 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of mcp-atlassian are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor mcp-atlassian for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mcp-atlassian version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.