Back to the CVE list
CVE-2026-116684

Model Context Protocol Python SDK: Server bearer-token authentication accepts tokens issued for a different resource server

CVSS score

6.8

EPSS probability

—

Risk score

0.7

Published

3 h ago

Patch status has not yet been verified

Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.

Impact on My Inventory

Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.

Checking session…

Vulnerability description

DayBreach AI Explanation

Verified against sources

CVE-2026-116684: Model Context Protocol Python SDK Authentication Vulnerability

Sources read

1

Source agreement

Tam uyum

Evidence confidence

%55

Short explanation

Model Context Protocol Python SDK versions from 1.10.0 to before 1.30.0 and version 2.2.0 allow server-side bearer authentication to accept valid tokens issued for a different resource server. This resource-confusion flaw lets a token holder authenticate to the wrong MCP server.

Why does it matter?

Unauthorized users can authenticate to an incorrect MCP server using a valid token issued for another service, enabling unintended access to sensitive resources.

What should be done?

  • Update Model Context Protocol Python SDK packages
  • Follow the vendor advisory for patch guidance
  • Verify token verification implementation
Chain of evidence and sources2 verified claims

Model Context Protocol Python SDK, 1.10.0 ile 1.30.0 arası ve 2.2.0 sürümlerinde bearer-token kimlik doğrulamasında kaynak karışıklığı zafiyeti barındırmaktadır.

Yetkilendirme sunucusu birden fazla kaynağa hizmet verdiğinde ve aud doğrulanmadığında, farklı bir servis için verilen token kabul edilir.

Show the technical text from the sources

The Model Context Protocol Python SDK is the official Python SDK for Model Context Protocol servers and clients. From 1.10.0 until 1.30.0 and 2.2.0, server-side bearer authentication configured through AuthSettings with token_verifier accepts a valid token issued for another service when the authorization server serves multiple resources and the TokenVerifier does not independently validate the aud audience. This resource-confusion flaw lets a token holder authenticate to the wrong MCP server and exercise that token's resulting access. This issue is fixed in versions 1.30.0 and 2.2.0.

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

CWE: CWE-863

This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.

IMPACT: Affected Products and Software

Affected Products

The following products are affected by CVE-2026-116684 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.

IDVENDORPRODUCTACTION
1modelcontextprotocolpython-sdk View
2pypimcp View
3pypimcp View
Total affected vendors: 2|Products: 3

RED HAT CSAF/VEX: Product Impact Check

Red Hat has not yet published a CSAF/VEX impact record for this CVE. This does not mean “not affected”.

SCORING: CVSS from Multiple Sources

CVSS Scores

The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.

SCOREVERSIONSEVERITYVECTORSOURCE
6.8CVSS V3_1MEDIUMCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:NCVE CNA
6.8CVSS V31MEDIUMCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:NNVD
6.8CVSS 3.x—Vector not publishedGitHub Advisory
0.0CVSS 4.0—Vector not publishedGitHub Advisory

Patch and Remediation Guide

Solution & Remediation Advisory

Patch status unknown

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Confirm the affected product and version against the source evidence above.
Restrict access to internet-facing services and apply network segmentation.
Until a patch is confirmed, follow the vendor advisory; do not read an unknown status as “no patch”.
Monitor server logs and network endpoints for signs of anomalous execution.

Public exploit and active exploitation status

Verified exploit intelligence

No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.

Weakness Classification and Attack Patterns (CWE & CAPEC)

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-116684 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-116684 weaknesses.

Attack Vector and Accessibility

ExposureAğ üzerinden
PermissionsLow
UserGerekmiyor

Official Sources and Advisories

CVSS Vector Radar Chart

6.8 / 10
Attack VectorNetworkComplexityHighPrivilegesLowUser Interact.NoneConfidentialityHighIntegrityNoneAvailabilityNone

Vulnerability Scoring Details

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredLow privileges
User InteractionNone required
Confidentiality (Gizlilik)High
Integrity (Bütünlük)None
Availability (Erişilebilirlik)None

Yama durumu bilinmiyor

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Follow the vendor

Weakness Type (CWE & CAPEC)

Similar Vulnerabilities

Get this vulnerability through the API

Affected products, version ranges, exploitation status and patch information in a single request, with a free key.

curl -H "x-api-key: $DAYBREACH_API_KEY" \
  "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-116684"
CVE-2026-116684 · Model Context Protocol Python SDK: Server…