Skip to main content
VulnerabilityPublished

CVE-2026-128064: PHP · Cleartext Transmission

Affects PHPSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High · fixed in 8.5.13 : patch PHP soon.

Data as of 19 Nov 2026, 15:03 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (php)CVSS 4.08.2
Patch
Available – fixed in 8.5.13, 8.4.28, 8.3.37 +1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade PHP to 8.5.13, 8.4.28, 8.3.37 or 8.2.36.

Affected software

ProductAffectedFixed in
PHP GroupPHPAffected
  • >=8.5.0 <8.5.13
Fixed in
  • 8.5.13
PHP GroupPHPAffected
  • >=8.4.0 <8.4.28
Fixed in
  • 8.4.28
PHP GroupPHPAffected
  • >=8.3.0 <8.3.37
Fixed in
  • 8.3.37
PHP GroupPHPAffected
  • >=8.2.0 <8.2.36
Fixed in
  • 8.2.36

CPE configurations (1)

  • cpe:2.3:a:php:php:*:*:*:*:*:*:*:*

AI-suggested

Upgrade PHP to version 8.2.36, 8.3.37, 8.4.28, or 8.5.13 or later, where this issue is fixed. Applying these official fixes will ensure that TLS is correctly enabled regardless of URL scheme case. No additional mitigations are required once patched.

Description

A vulnerability in PHP versions before 8.2.36, 8.3.37, 8.4.28, and 8.5.13 causes mixed-case HTTPS and FTPS URLs to be handled without encryption. This occurs because the PHP HTTP and FTP stream wrappers enable TLS only when the scheme contains a lowercase 's' at a fixed position. URLs like HTTPS:// or FTPS:// are treated as unencrypted HTTP or FTP, exposing sensitive data such as credentials and transferred files to network observers.

References

Community reviews

Loading reviews…