CVE-2026-14457

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Issue summary: In a server or client configuration with RFC7250 Raw Public Keys (RPKs) enabled, and only the private key (with no associated certificate) configured locally, a NULL pointer dereference may occur when the remote peer solicits raw public keys and also sends the typically omitted "signature_algorithms_cert" TLS extension.

Impact summary: The impact is limited to a possible Denial of Service as a result of an application abort, no data disclosure or remote command execution are possible.

CWE: CWE-476: NULL Pointer Dereference

Description: While a passing comment in sample code in the documentation suggests that key-only RPK configurations are supported, the best-practice RPK configuration is to always configure a corresponding certificate (possibly self-signed or signed by any convenient CA).

When the private key is configured along with a matching certificate, the "signature_algorithms_cert" extension is handled reliably even without the fix, and peer clients or servers that don't support raw public keys may be able to complete a TLS connection by pinning or verifying the corresponding certificate or its public key.

Deployments that prefer to configure just a private key with no certificate need to upgrade to an updated release as noted below.

FIPS impact: no

No FIPS modules are affected by this issue, as the SSL protocol implementation is outside the OpenSSL FIPS module boundary.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
60%
KEV
Not listed

Published

August 25, 2026

Last Modified

August 25, 2026

Advisory Details (5)

Auto-updated Aug 25, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic
https://openssl-library.org/news/secadv/20260825.txt
github_commit

commit dad836b071da (openssl/openssl)

Fix landed in openssl/openssl commit dad836b071da — awaiting tagged release

https://github.com/openssl/openssl/commit/dad836b071da6579510c968615848ba03cac593b
github_commit

commit d0af20478688 (openssl/openssl)

Fix landed in openssl/openssl commit d0af20478688 — awaiting tagged release

https://github.com/openssl/openssl/commit/d0af20478688a6aa2f59d61caa3f82136b181d7f
github_commit

commit 581aaa0f0a35 (openssl/openssl)

Fix landed in openssl/openssl commit 581aaa0f0a35 — awaiting tagged release

https://github.com/openssl/openssl/commit/581aaa0f0a35d214740f0fe1f5283ec41f1212e1
github_commit

commit 1e8c398db674 (openssl/openssl)

Fix landed in openssl/openssl commit 1e8c398db674 — awaiting tagged release

https://github.com/openssl/openssl/commit/1e8c398db67404babd3e5af999bb6bd86f720c76

Vendor Advisories for CVE-2026-14457(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.4) @ resolute2026-08-26ubuntu

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.

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-26 15:27 UTCEG score recompute
  2. 2026-08-26 15:27 UTCVendor advisory
  3. 2026-08-26 15:27 UTCGHSA enrichment
  4. 2026-08-26 02:53 UTCEG score recompute
  5. 2026-08-26 02:53 UTCVendor advisory
  6. 2026-08-26 02:53 UTCGHSA enrichment
  7. 2026-08-25 14:15 UTCEG score recompute▲ 7.50
  8. 2026-08-25 14:14 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  9. 2026-08-25 13:21 UTCNVD update
  10. 2026-08-25 13:16 UTCEG score recompute
  11. 2026-08-25 13:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-14457?
CVE-2026-14457 is a high vulnerability published on August 25, 2026. Issue summary: In a server or client configuration with RFC7250 Raw Public Keys (RPKs) enabled, and only the private key (with no associated certificate) configured locally, a NULL pointer dereference may occur when the remote peer solicits raw public keys and also sends the typically omitted…
When was CVE-2026-14457 disclosed?
CVE-2026-14457 was first published in the National Vulnerability Database on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14457 actively exploited?
CVE-2026-14457 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 40.3% of all scored CVEs.
What is the CVSS score of CVE-2026-14457?
CVE-2026-14457 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-14457?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14457, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-14457

Explore →

Is Your Infrastructure Affected by CVE-2026-14457?

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

Start Free Scan →Browse All CVEs