MCP Python bearer authentication lacks resource audience enforcement
A token issued for a different service can be accepted when a shared authorization server is used and the application does not validate the intended resource. Upgrading provides the control, but the advisory says it must also be enabled and configured.
A token issued for a different service can be accepted when a shared authorization server is used and the application does not validate the intended resource. Upgrading provides the control, but the advisory says it must also be enabled and configured.
This is a maintainer-documented vulnerability disclosure, not evidence of exploitation against a named customer. Affected ranges: mcp >= 2.0.0, < 2.2.0; mcp >= 1.10.0, < 1.30.0. The maintainer lists patched releases: mcp 1.30.0; mcp 2.2.0.
Takeaway
Check the deployed package and its configuration against the advisory. Apply the listed fix on a supported release line and verify the trust boundary with an untrusted client or repository.