7.5

CVE-2026-14457: RPK Server Signature Algorithm Selection Can Dereference a Missing Certificate

Analyzed
AliasesALPINE-CVE-2026-14457UBUNTU-CVE-2026-14457DEBIAN-CVE-2026-14457
Published 25-08-2026Last modified 25-08-2026

Vulnerability summary

CVE-2026-14457 is a high (CVSS 7.5) NULL Pointer Dereference vulnerability in openssl. EPSS estimates a 1.17% chance of exploitation in the next 30 days, higher than 67.3% of scored vulnerabilities.

Priority
Prioritisesevere

Severe, CVSS 7.5 (CVE.org); no exploitation reported by the 5 checked sources; EPSS 1% (FIRST, 03-11-2026)

Source freshness unavailable

How is this decided?
CVSS score
7.5/10
010
High · v3.1 (CVE.org)
EPSS score
1.17%
0%100%
Low · +0.15 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 17 · Related 12
MGASA-2026-0353OPENSUSE-SU-2026:11623-1OPENSUSE-SU-2026:21744-1RHSA-2026:59635RHSA-2026:59641RHSA-2026:67154

Timeline

  1. 25-08-2026
    PublishedVulnerability first disclosed.
  2. 25-08-2026
    Last modifiedVulnerability information updated.

Description

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 metrics

7 scores · 7 sources · 1 version

EPSS trend

Probability

1.17%

Chance of exploitation in the next 30 days

Percentile

67%

Versus all other CVEs

30-day change

Increase +0.15 pp

From 1.02% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.

Chainguard14 products
  • eco-python-openssl-4< 4.0.2-r0
  • eco-python-openssl-4-pyca< 4.0.2-r0
  • eco-python-openssl-4-pyca-dev< 4.0.2-r0
  • openssl-3.5< 3.5.8-r0
  • openssl-3.5-libcrypto< 3.5.8-r0
Ubuntu4 products
  • edk2All versions (No fix recorded)
  • edk2-hweAll versions (No fix recorded)
  • nodejsAll versions (No fix recorded)
  • openssl< 3.5.5-1ubuntu3.4
Wolfi3 products
  • openssl-4.0< 4.0.2-r0
  • openssl-4.0-libcrypto< 4.0.2-r0
  • openssl-4.0-libssl< 4.0.2-r0
Alpine1 product
  • openssl≥ 3.4.0, < 3.5.8-r0
Debian1 product
  • openssl< 3.5.7-1~deb13u2 | < 3.6.4-1
Openssl1 product
  • openssl≥ 3.4.0, < 3.4.7 | ≥ 3.5.0, < 3.5.8 | ≥ 3.6.0, < 3.6.4 | ≥ 4.0.0, < 4.0.2

6 vendors · 24 products

References

12 links
Show all 12 references