You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a88e728
Browse filesBrowse the repository at this point in the historyBrowse files
[Fix] Restrict header-supplied MCP OAuth metadata to the server origin
The WWW-Authenticate fallback fetched any resource_metadata URL, so a
server could direct the client to a loopback, private, or other host.
It now fetches only metadata on the MCP server's own origin. Servers
with cross-origin metadata keep the behavior they had before the
fallback existed.
A well-known lookup that timed out may still be running, so it no
longer starts the fallback.
Adds tests for a failed probe, a failed or timed-out fallback lookup,
no fallback after a timed-out first lookup, and rejected destinations.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
["a header that backtracks a naive parser",",bearer\t!="+"\t,!=".repeat(10_000)],
102
102
["an invalid URL",'Bearer resource_metadata="not a url"'],
103
+
["a URL on another origin",'Bearer resource_metadata="https://other.example.com/metadata"'],
0 commit comments