CVE-2026-54872

LOWPre-NVD 3.73.7—
EchelonGraph scoreHIGH confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-09-29. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — Patch released this week
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 3.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing.

Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key.

CWE: CWE-208: Observable Timing Discrepancy

Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce.

The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1.

Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue.

The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected.

FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path.

CVSS v3
3.7
EG Score
3.7LOWhigh confidence
EG Risk
17
EG Risk 17/100CISA SSVC

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
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 29, 2026

Last Modified

September 29, 2026

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl (1.0.2g-1ubuntu4.20+esm19) @ xenial2026-10-02ubuntu
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.6) @ resolute2026-10-02ubuntu
redhatopenssl-main-3.5.9-0.1.hum12026-09-30redhat
redhatopenssl3-main-3.5.9-0.1.hum12026-09-30redhat

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.

Additional Vendor Advisories

(2)

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 16× in last 7d / 16× 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-10-03 14:26 UTCEPSS rescore
  2. 2026-10-02 23:56 UTCEG score recompute
  3. 2026-10-02 23:56 UTCVendor advisory
  4. 2026-10-02 23:56 UTCGHSA enrichment
  5. 2026-10-02 17:56 UTCEPSS rescore
  6. 2026-10-01 19:50 UTCEPSS rescore
  7. 2026-09-30 15:03 UTCEPSS rescore
  8. 2026-09-29 22:00 UTCVendor advisory
  9. 2026-09-29 22:00 UTCGHSA enrichment
  10. 2026-09-29 18:32 UTCEG score recompute
  11. 2026-09-29 18:31 UTCGHSA enrichment
  12. 2026-09-29 17:45 UTCEG score recompute▲ 3.70
  13. 2026-09-29 17:38 UTCMITRE cvelistV5CVSS v3 → 3.7 · severity → LOW
  14. 2026-09-29 16:24 UTCNVD update
  15. 2026-09-29 15:38 UTCEG score recompute
  16. 2026-09-29 15:38 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54872?
CVE-2026-54872 is a low vulnerability published on September 29, 2026. Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn…
When was CVE-2026-54872 disclosed?
CVE-2026-54872 was first published on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54872 actively exploited?
CVE-2026-54872 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54872?
CVE-2026-54872 has a CVSS v3.1 base score of 3.7 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-54872?
A fix for CVE-2026-54872 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54872 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54872?

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