CVE-2026-91769

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-87346 (ENISA EUVD)Source: ENISA EUVD

4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 25, 2026

Last Modified

October 23, 2026

Advisory Details (1)

Auto-updated Sep 25, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

TLS Hostname Verification Falls Back to CN After SAN Mismatch · Advisory · php/php-src · GitHub

https://github.com/php/php-src/security/advisories/GHSA-vvx9-73fr-5jjx

Vendor Advisories for CVE-2026-91769(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuphp7.2-zip (7.2.24-0ubuntu0.18.04.17+esm13) @ bionic2026-10-23ubuntu
redhatphp:7.4-8100020261021081045.f79986652026-10-21redhat
redhatphp-main-8.5.11-2.hum12026-09-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
php8.28.2.10-1 ... 8.2.7-1~deb12u1 (29 versions)
  • every version up to 8.2.34-1~deb12u1: fixed in 8.2.34-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
php8.48.4.11-1 ... 8.4.24-1~deb13u1 (11 versions)
  • every version up to 8.4.26-1~deb13u1: fixed in 8.4.26-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
php8.48.4.11-1 ... 8.4.26-1~deb13u1 (12 versions)
  • every version up to 8.4.26-1: fixed in 8.4.26-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 58× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 80 is merged into the row it repeats.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  9. 2026-10-25 13:51 UTCEG score recompute
  10. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-23 13:28 UTCEG score recompute
  13. 2026-10-23 13:28 UTCVendor advisory
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-22 12:30 UTCEG score recompute
  16. 2026-10-22 12:30 UTCVendor advisory
  17. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-18 03:00 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 54 more
  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-12 14:45 UTCEG score recompute
  4. 2026-10-11 19:13 UTCEG score recompute
  5. 2026-10-11 16:30 UTCEG score recompute
  6. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-11 13:44 UTCEG score recompute
  8. 2026-10-11 09:35 UTCEG score recompute
  9. 2026-10-11 09:35 UTCVendor advisory
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-10 10:57 UTCEG score recompute
  12. 2026-10-10 10:57 UTCVendor advisory
  13. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-09 12:22 UTCEG score recompute
  15. 2026-10-09 12:22 UTCVendor advisory
  16. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-08 11:55 UTCEG score recompute
  18. 2026-10-08 11:55 UTCVendor advisory
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-07 13:08 UTCEG score recompute
  21. 2026-10-07 13:08 UTCVendor advisory
  22. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-06 14:33 UTCEG score recompute
  24. 2026-10-06 14:33 UTCVendor advisory
  25. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-10-05 15:56 UTCEG score recompute
  27. 2026-10-05 15:56 UTCVendor advisory
  28. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-10-04 17:19 UTCEG score recompute
  30. 2026-10-04 17:19 UTCVendor advisory
  31. 2026-10-04 15:10 UTCVendor advisory
  32. 2026-10-03 16:32 UTCEG score recompute
  33. 2026-10-03 16:32 UTCVendor advisory
  34. 2026-10-02 17:58 UTCEG score recompute
  35. 2026-10-02 17:58 UTCVendor advisory
  36. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-10-01 19:24 UTCVendor advisory
  38. 2026-09-30 20:49 UTCEG score recompute
  39. 2026-09-30 20:49 UTCVendor advisory
  40. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  41. 2026-09-29 22:16 UTCEG score recompute
  42. 2026-09-29 22:16 UTCVendor advisory
  43. 2026-09-29 13:00 UTCEG score recompute
  44. 2026-09-29 13:00 UTCVendor advisory
  45. 2026-09-28 14:26 UTCEG score recompute
  46. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  47. 2026-09-28 13:44 UTCEG score recompute
  48. 2026-09-27 18:28 UTCEG score recompute
  49. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  50. 2026-09-26 19:54 UTCEG score recompute
  51. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  52. 2026-09-25 21:18 UTCEG score recompute
  53. 2026-09-25 21:04 UTCEG score recomputeFirst assessed: 4.3 MEDIUM
  54. 2026-09-25 21:04 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-91769?
CVE-2026-91769 is a medium-severity vulnerability; its CVE record was published on September 25, 2026. 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…
When was the CVE record for CVE-2026-91769 published?
The CVE record for CVE-2026-91769 was published on September 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-91769 actively exploited?
CVE-2026-91769 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-91769?
CVE-2026-91769 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-91769?
A fix for CVE-2026-91769 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-91769 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-91769

Explore →

Is Your Infrastructure Affected by CVE-2026-91769?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs