Skip to main content
VulnerabilityPublished Updated

CVE-2026-91769: Libphp · TLS Hostname Verification Falls Back to CN After SAN Mismatch

Affects libphpSource GCVE Database

0
Authoritative record:CVE-2026-91769· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium · fixed in 8.5.11 : update libphp when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.5.11, 8.4.26, 8.3.35 +1
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade libphp to 8.5.11, 8.4.26, 8.3.35 or 8.2.34.

Affected software

ProductAffectedFixed in
Bitnamilibphppkg:bitnami/libphpOther threatsAffected
  • >=8.2.0 <8.2.34
  • >=8.3.0 <8.3.35
  • >=8.4.0 <8.4.26
  • >=8.5.0 <8.5.11
Fixed in
  • 8.2.34
  • 8.3.35
  • 8.4.26
  • 8.5.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

PHP's OpenSSL stream peer verification checks the certificate's subjectAltName entries first and, whenever no entry matches, falls back to the Common Name. RFC 6125 requires the CN to be ignored once the certificate presents any service identity, so a certificate carrying a non-matching DNS SAN was still accepted when its CN matched the requested peer_name. A certificate trusted by the client for one name can therefore be used to impersonate another.

References

Community reviews

Loading reviews…