tighten SSRF protection - #2449
Open
pngwn wants to merge 1 commit into
Open
Conversation
pngwn
force-pushed
the
blissful-spence-f4e007
branch
from
July 24, 2026 08:30
2250601 to
803dc44
Compare
Collaborator
|
this was discussed a lot with @rtrompier (adding him) |
Member
Author
|
For reference, 10.0.0.0/8 which is used by internal load baancers is still allowed with this PR, and the existing tests for it still pass. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hardens the server-side ssrf guard so raw IP literals and ipv6 edge-cases can no longer slip past the private-range blocklist before a request leaves the box. General hardneing and prep for mcp oauth.