PHP has fixed a mismatch between recognizing a secure URL and actually enabling encryption. Its HTTP and FTP stream wrappers accept mixed-case schemes, but vulnerable versions require a lowercase s to turn on TLS, the connection’s encryption. An application can therefore approve an HTTPS URL and still send its contents in plaintext.

The November 19 advisory identifies CVE-2026-128064. It covers functions such as file_get_contents() and fopen() when they open remote URLs through PHP’s stream wrappers. Install the repaired runtime for the deployed branch, and review automatic redirects if a temporary workaround is needed.

A secure-looking URL can select the wrong transport

URL schemes are case-insensitive. PHP’s wrapper selection follows that rule, while its vulnerable encryption check examines one character case-sensitively. Schemes such as HTTPS:// or httpS:// can consequently select unencrypted HTTP. The equivalent problem affects FTPS, FTP file transfer protected by TLS.

An attacker needs two conditions: an affected URL must reach the wrapper, and the attacker must be able to observe the resulting network traffic. Exposure depends on what the application sends. PHP lists passwords, bearer tokens, cookies, request bodies, FTP credentials and transferred files among the possible disclosures.

This is a specific PHP stream-wrapper flaw. The advisory does not establish that every PHP HTTP client, browser or HTTPS connection behaves this way.

Evidence status: vendor-confirmed vulnerability; no in-the-wild exploitation is reported in the reviewed advisory. The PHP-issued CVE record describes the same mechanism and version ranges. CISA’s recorded assessment labels exploitation none at its assessment time, which is a snapshot rather than proof that no abuse occurred.

Redirects make initial validation incomplete

The HTTP flaw also affects redirect destinations. A request can begin over valid HTTPS and then follow a redirect whose scheme contains an uppercase S. PHP explains that a 307 redirect, which preserves the request method and body, can expose a POST body and retained authentication headers.

A destination rejecting that unexpected plaintext connection does not undo data already transmitted. Checking only whether the request ultimately succeeded can therefore miss the disclosure.

The repair compares the complete scheme case-insensitively when deciding whether encryption is required. It covers both HTTP and FTP wrappers.

Match the repair to the running PHP branch

The advisory gives these fixed releases:

PHP branch Affected versions in that branch Fixed release
8.2 Before 8.2.36 8.2.36
8.3 Before 8.3.37 8.3.37
8.4 Before 8.4.28 8.4.28
8.5 Before 8.5.13 8.5.13

PHP’s November 19 changelog records this fix, and its 8.5.13 announcement confirms release availability. Older PHP lines also need attention: the advisory traces direct mixed-case URLs to PHP 5.2.0 and redirects to PHP 4.3.0, based on code inspection. It gives no upstream repair release for those old lines.

For operators and application maintainers:

  • Update the deployed runtime and verify the version actually serving requests. For distribution packages with backported repairs, check the distributor’s security notice rather than comparing the upstream version alone.
  • For a temporary workaround, normalize HTTPS and FTPS schemes to lowercase before calling stream functions. Preserve the rest of the URL, whose path and other components can be case-sensitive.
  • Disable automatic HTTP redirects and validate and normalize every target before following it. PHP explicitly warns that normalizing only the initial URL leaves redirects exposed.
  • Review sensitive outbound transfers if this path was used. Where credentials may have crossed an observable network unencrypted, investigate their use and replace exposed secrets. The advisory does not call for universal credential rotation across all PHP applications.

The same release batch fixes other vulnerabilities, including the timezone-cache flaw already covered here. Their code-execution conditions differ from this disclosure path; a workaround for one does not cover the whole release.

Caveat: A URL spelling that passes an application’s secure-scheme check is insufficient protection on vulnerable wrappers, especially when redirects are followed automatically.