CVE-2026-46338VulnerabilityPublished 13 Aug 2026Updated 29 Oct 2026

Mcp atlassian: Regression

Affects mcp-atlassianSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2023-32309

Authoritative record:CVE-2026-46338· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium : upgrade to 0.21.1_6 when convenient.

Data as of 30 Oct 2026, 08:16 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 0.21.1_6

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade mcp-atlassian to 0.21.1_6.

Affected software

Product	Affected	Fixed in
Homebrewmcp-atlassian`pkg:brew/mcp-atlassian`Other threats	Affected >=0.11.9 <0.21.1_6	Fixed in 0.21.1_6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in version 0.21.1_6 that fixes the regression by enforcing a directory boundary check rather than a simple string prefix match. Users should upgrade to this fixed version to remediate the vulnerability. The suggested fix involves verifying that the filename starts with the base path plus a path separator to prevent sibling directory bypass. No additional mitigation is required if the patch is applied.

Description

A regression vulnerability in pymdownx.snippets allows a path traversal bypass when restrict_base_path is enabled. The flawed check uses a string prefix match instead of a directory boundary check, enabling reading files from sibling directories with similar path prefixes. This affects versions from 10.0.1 through 10.21.2. The vulnerability permits arbitrary file reads within the host filesystem under certain path conditions, potentially exposing sensitive files during markdown processing in build pipelines.

Impact

Allows an attacker controlling markdown snippet directives to read arbitrary files from sibling directories whose paths share a prefix with the configured base path. This can lead to exposure of sensitive files on the host running the build, especially in CI environments where markdown content is processed and the output is published or secrets are present on disk. The scope is limited to file read (confidentiality impact) without integrity or availability impact.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 08:16 UTC

Technical details

References

Community reviews

Related threats