Skip to main content
VulnerabilityPublished

CVE-2026-116672: Mcp atlassian · Authlib RFC 7592 examples omit registration-access-token client binding

Affects mcp-atlassianSource GCVE Database

0
Compare
Authoritative record:CVE-2026-116672· High 8.8

Not known to be exploited · CVSS 8.8 High : upgrade to 0.23.1_2 soon.

Data as of 31 Oct 2026, 16:53 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.8
Patch
Available – fixed in 0.23.1_2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade mcp-atlassian to 0.23.1_2.

Affected software

ProductAffectedFixed in
Homebrewmcp-atlassianpkg:brew/mcp-atlassianOther threatsAffected
  • >=0.11.11 <0.23.1_2
Fixed in
  • 0.23.1_2

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

AI-suggested

A fix is available in mcp-atlassian version 0.23.1_2. Users should upgrade to this version or later to ensure the registration_access_token is properly bound to the client being accessed, preventing authorization bypass. Until upgraded, implementations should not rely on the provided example code for authenticate_client and check_permission without adding explicit checks that the token belongs to the client identified in the request.

Description

CVE-2026-116672 is a vulnerability in Authlib's implementation of the OAuth 2.0 Dynamic Client Registration Management Protocol (RFC 7592). The provided example code for the ClientConfigurationEndpoint fails to enforce binding between the registration_access_token and the client being accessed, allowing an attacker with any valid token and knowledge of a client_id to bypass authorization and modify or delete client registrations. This flaw arises because the example implementations do not check that the token presented belongs to the client identified in the request. The issue affects versions >=0.11.11 and <0.23.1_2 of the mcp-atlassian product and is fixed in version 0.23.1_2.

References

Community reviews

Loading reviews…