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

Mcp atlassian: Authlib OAuth 2.0 has Open Redirect in Authorization API that allows attacker-controlled redirect_uri

Affects mcp-atlassianSource GCVE Database

Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 0.23.0 when convenient.

Data as of 30 Oct 2026, 08:32 UTC

CVSS 3.1 base score

5.4Medium

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

Patch: Available – fixed in 0.23.0

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 13 Aug 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.23.0.

Affected software

Product	Affected	Fixed in
Homebrewmcp-atlassian`pkg:brew/mcp-atlassian`Other threats	Affected <0.23.0	Fixed in 0.23.0

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 Authlib version 0.23.0 that addresses this open redirect vulnerability. Users should upgrade to version 0.23.0 or later to remediate the issue. No additional mitigation steps are required if the patch is applied.

Description

Authlib's OAuth 2.0 authorization endpoint contains an open redirect vulnerability triggered by an unsupported response_type parameter combined with an attacker-controlled redirect_uri. This flaw occurs before client validation, allowing unauthenticated attackers to cause the server to redirect to arbitrary URLs. The issue affects versions prior to 0.23.0 and has been confirmed in version 1.6.6 and current HEAD code. A patch is available in version 0.23.0.

Impact

An attacker can exploit this vulnerability to perform an open redirect attack without needing a valid client registration or authenticated user. This could be used to redirect victims to malicious sites, potentially facilitating phishing or other social engineering attacks. The vulnerability has a CVSS 3.1 score of 5.4 (medium severity), reflecting limited confidentiality and integrity impact and no availability impact.

Summary

The vulnerability arises because Authlib's AuthorizationServer.get_authorization_grant() method raises an UnsupportedResponseTypeError that includes the raw redirect_uri from the request before any client lookup or redirect URI validation occurs. The OAuth2Error handler then automatically issues a 302 redirect to this attacker-controlled URI. This allows an unauthenticated attacker to craft a single request with an unsupported response_type and a malicious redirect_uri to cause an open redirect, bypassing client registration and validation checks. The issue was confirmed in tag v1.6.6 and reproduced locally on the current HEAD. The fix is included in version 0.23.0.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats