Fix SSRF bypass of trusted_uri in {fetch} (PT-03-2026)#1187
Open
wisskid wants to merge 1 commit into
Open
Conversation
When a security policy is active and {fetch} is used with a non-http URL
scheme (https, ftp, ...), file_get_contents was called without a stream
context. PHP's HTTP wrapper follows redirects by default, so an Open
Redirect on a trusted host could be used to bypass the trusted_uri check
and reach arbitrary internal addresses (SSRF).
Pass a stream context with follow_location=0 and max_redirects=1 when a
security policy is configured. Behaviour is unchanged for users without
a security policy.
Reported by Aleksey Solovev (Positive Technologies), PT-03-2026.
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
1 participant
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.
Summary
{fetch}with anhttps://(or other non-http) URL calledfile_get_contentswithout a stream context. PHP's HTTP wrapper auto-follows redirects, so an Open Redirect on a trusted host could be used to bypass thetrusted_urisecurity policy and reach arbitrary internal addresses (SSRF).security_policyis active, the fetch now uses a stream context withfollow_location=0/max_redirects=1. Behaviour is unchanged for users without a security policy (no BC break).http://branch goes throughfsockopen, which never auto-followed redirects, so it was already safe.Report
Reported by Aleksey Solovev (Positive Technologies), advisory PT-03-2026. Handled as a normal patch release; no CVE filing requested.
Files
src/FunctionHandler/Fetch.php— add stream context disabling redirect following under security policy.changelog/ssrf-pt-03-2026.md— changelog snippet.Compatibility
enableSecurity()see no behaviour change.