Improper Certificate Validation Affecting php-dba package, versions <0:8.5.11-2.hum1


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.14% (3rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-PHPDBA-20234606
  • published29 Sept 2026
  • disclosed25 Sept 2026

Introduced: 25 Sep 2026

NewCVE-2026-91769  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

Upgrade RHEL:10 php-dba to version 0:8.5.11-2.hum1 or higher.
This issue was patched in RHSA-2026:70720.

NVD Description

Note: Versions mentioned in the description apply only to the upstream php-dba package and not the php-dba package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1