{{ message }}
Repository navigation
fix: prevent SSRF via push notification URL validation - #1096
Merged
Merged
Conversation
kabir
approved these changes
Aug 26, 2026
ehsavoie
force-pushed
the
advisory-fix-2
branch
2 times, most recently
from
August 26, 2026 13:22
7b443b3 to
2592457
Compare
- Add PushNotificationUrlValidator with SSRF-safe default (scheme allowlist, private-network blocking incl. IPv4-mapped IPv6) - Disable HTTP redirect following on push notification POST requests - Add a2a.push-notifications.enabled config to gate push config storage Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
ehsavoie
force-pushed
the
advisory-fix-2
branch
from
August 26, 2026 13:47
2592457 to
3821d72
Compare
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.
Fixes #GHSA-q78c-5jjq-57g8 🦕