PT-2026-127758

تاريخ النشر

2026-10-27

·

تاريخ التحديث

2026-10-27

الوصف من

CVSS 3.1
6.8
متوسطة
المقاييسAV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Summary

In affected versions, the SDK's server-side bearer authentication had no way to check that a token was issued for your server (its audience). Where one authorization server issues tokens for several services, a valid token for another service was also accepted by your MCP server.

Am I affected?

Yes, if your HTTP server uses the SDK's bearer authentication (auth=AuthSettings(...) with token verifier=), its authorization server also issues tokens for other services, and your TokenVerifier does not check the token's audience (aud) itself.
Affected versions:
  • mcp 1.10.0 through 1.29.1
  • mcp 2.0.0 through 2.1.1

Fix

Upgrade to:
  • 1.x: mcp 1.30.0 or later
  • 2.x: mcp 2.2.0 or later
Upgrading alone changes nothing. The patched versions add a validate token resource setting that is off unless you set it. To turn the check on, make both of these changes together:
  1. Set validate token resource=True in AuthSettings, with resource server url set to the audience your authorization server puts in tokens for your server.
  2. Return the token's audience from verify token() as AccessToken.resource.
A token for another service then gets 401. With only the first change, every request gets 401.
If your TokenVerifier already checks the audience, set validate token resource=False to silence the deprecation warning. The setting will default to True in 3.0.
If you cannot upgrade yet, reject any token whose aud does not include your server inside verify token(). That closes the issue on every version.
قابلية الاستغلال
إصلاح
التأثيرات
المورّدون
المنتجات المتأثرة
تصنيف نقاط الضعف
CWE-863: Incorrect Authorization
المعرّفات ذات الصلة
GHSA-W4FH-QVV9-3V23
وجدت خطأً في الوصف؟ لديك ما تضيفه؟ لا تتردد في مراسلتنا 👾
dbugs@ptsecurity.com