A URL scheme can select the wrong transport

CVE-2026-128064 affects PHP HTTP and FTP stream wrappers. The PHP advisory says a URL scheme with an uppercase S, such as HTTPS:// or FTPS://, could cause data to be sent without encryption. Applications that use file_get_contents(), fopen() or related stream functions may expose credentials, request data or files to a person who can observe the network.

PHP lists fixes in 8.2.36, 8.3.37, 8.4.28 and 8.5.13. The issue concerns URLs that reach these wrappers, so inspect code and configuration that construct remote URLs rather than checking only the web server.

Review outbound requests

Search PHP code for file_get_contents(), fopen() and stream context functions that use remote URLs. Check whether the scheme comes from a setting, user input or partner integration. Normalize and validate allowed schemes before the application makes a request.

Review logs and configuration for mixed-case `https` or `ftps` schemes. Do not put passwords or API keys in URLs. If a sensitive request may have crossed an untrusted network, ask the service owner whether the affected credential should be rotated.

Install the upstream fix

Upgrade PHP to a fixed branch release or install the supported operating-system package that contains the patch. Test outbound requests and confirm that HTTPS and FTPS connections use the expected secure transport.

Check that the runtime used by queue workers and scheduled tasks also receives the update. These processes may make remote requests outside the main website deployment.