<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 21:16:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-54872 — Timing Side-Channel in Scalar Multiplication for Non-NIST EC Curves</title>
      <link>https://db.gcve.eu/vuln/cve-2026-54872</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenSSL&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;CWE: CWE-208: Observable Timing Discrepancy&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The NIST curves P-256, P-384 and P-521 use dedicated constant-time
implementations and are not affected.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenSSL&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;CWE: CWE-208: Observable Timing Discrepancy&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The NIST curves P-256, P-384 and P-521 use dedicated constant-time
implementations and are not affected.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-54872</guid>
    </item>
  </channel>
</rss>
