Skip to content
Noroxi
CVE-2025-9231· NVD / CVE Program· CNA openssl

Timing side-channel in SM2 algorithm on 64 bit ARM

Noroxi assessment

Priority: Monitor (action score 27/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.2% (FIRST EPSS); higher than 82.3% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: OpenSSL OpenSSL 3.2.6, 3.3.5, 3.4.3.

Low priority for now. Upgrade to OpenSSL OpenSSL 3.2.6, 3.3.5, 3.4.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms. Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker.. While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack. OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support for such certificates via a custom provider, coupled with the fact that in such a custom provider context the private key may be recoverable via remote timing measurements, we consider this to be a Moderate severity issue. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as SM2 is not an approved algorithm.

MediumCVSS 6.5 · v3.1—No exploit Fix available
Published
Sep 30, 2025
Updated
Jul 14, 2026
EPSS
2.2% · 82th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-9231

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.

  • OpenSSL OpenSSL

    • 3.5.0 and later · before 3.5.4affected · semver
    • 3.4.0 and later · before 3.4.3affected · semver
    • 3.3.0 and later · before 3.3.5affected · semver
    • 3.2.0 and later · before 3.2.6affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.20opensslbefore 3.3.5-r03.3.5-r0
Alpine:v3.22opensslbefore 3.5.4-r03.5.4-r0
Debian:13opensslbefore 3.5.1-1+deb13u13.5.1-1+deb13u1
Debian:14opensslbefore 3.5.4-13.5.4-1
openSUSE:Leap 16.0openssl-3before 3.5.0-160000.4.13.5.0-160000.4.1
openSUSE:Tumbleweedopenssl-3before 3.5.3-2.13.5.3-2.1
openSUSE:Tumbleweedregclientbefore 0.10.0-1.10.10.0-1.1
Red Hat:hummingbird:1opensslbefore 0:3.5.6-0.1.hum10:3.5.6-0.1.hum1
Red Hat:hummingbird:1openssl-config-fipsbefore 0:3.5.6-0.1.hum10:3.5.6-0.1.hum1
Red Hat:hummingbird:1openssl-develbefore 0:3.5.6-0.1.hum10:3.5.6-0.1.hum1
Red Hat:hummingbird:1openssl-devel-enginebefore 0:3.5.6-0.1.hum10:3.5.6-0.1.hum1
Red Hat:hummingbird:1openssl-libsbefore 0:3.5.6-0.1.hum10:3.5.6-0.1.hum1
Red Hat:hummingbird:1openssl-perlbefore 0:3.5.6-0.1.hum10:3.5.6-0.1.hum1
SUSE:Linux Enterprise Module for Basesystem 15 SP7opensslbefore 3.5.0-150700.3.4.13.5.0-150700.3.4.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7openssl-3before 3.5.0-150700.5.45.23.5.0-150700.5.45.2
SUSE:Linux Enterprise Module for Web and Scripting 15 SP7nodejs24before 24.18.1-150700.15.18.124.18.1-150700.15.18.1
SUSE:Linux Enterprise Server 16.0openssl-3before 3.5.0-160000.4.13.5.0-160000.4.1

Other highest-scoring records for the same primary product.

  • CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This week
  • CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code
    65This week
  • CVE-2016-2108The ASN.1 implementation in OpenSSL before 1.0.1o and 1.0.2 before 1.0.2c allows remote attackers to execute arbitrary code or cause a denia
    62This week
  • CVE-2016-6309statem/statem.c in OpenSSL 1.1.0a does not consider memory-block movement after a realloc call, which allows remote attackers to cause a den
    60This week
  • CVE-2022-3786X.509 Email Address Variable Length Buffer Overflow
    58Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
OpenSSL OpenSSL3.2.6Vendor (CNA)
OpenSSL OpenSSL3.3.5Vendor (CNA)
OpenSSL OpenSSL3.4.3Vendor (CNA)
OpenSSL OpenSSL3.5.4Vendor (CNA)
alpine:openssl3.3.5-r0 · Alpine:v3.20Package registry (OSV)
debian:openssl3.5.1-1+deb13u1 · Debian:13Package registry (OSV)
opensuse:openssl-33.5.0-160000.4.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:regclient0.10.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:openssl0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:openssl-config-fips0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:openssl-devel0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:openssl-devel-engine0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:openssl-libs0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:openssl-perl0:3.5.6-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
suse:nodejs2424.18.1-150700.15.18.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 SP7Package registry (OSV)
suse:openssl3.5.0-150700.3.4.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:openssl-33.5.0-160000.4.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-13176253 days apartTiming side-channel in ECDSA signature computation
    16Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records