VulnerabilityPublished 29 Oct 2026

CVE-2026-54875: openssl security update

Affects opensslSource GCVE Database

Compare

Not known to be exploited · CVSS 3.7 Low : upgrade to 3.0.12-55.oe2403sp1 when convenient.

Data as of 29 Oct 2026, 10:47 UTC

CVSS 3.1 base score

3.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.0.12-55.oe2403sp1

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade openssl to 3.0.12-55.oe2403sp1.

Affected software

Product	Affected	Fixed in
openEuler 24.03-LTS-SP1openssl`pkg:rpm/openEuler/openssl&distro=openEuler-24.03-LTS-SP1`Other threats	Affected <3.0.12-55.oe2403sp1	Fixed in 3.0.12-55.oe2403sp1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Fixed versions of OpenSSL have been released: upgrade to OpenSSL 4.0.3 if using 4.0, 3.6.5 if using 3.6, 3.5.9 if using 3.5, or 3.4.8 if using 3.4. Versions 3.0, 1.1.1, and 1.0.2 are not affected and do not require action. Applying these updates will mitigate the timing and cache side-channel vulnerability. No additional mitigations are specified or required.

Description

A timing and cache side-channel vulnerability exists in OpenSSL's SM2 private key operations on ARM64 and RISC-V platforms due to a non-constant-time scalar multiplication implementation. This flaw allows attackers who can measure execution time or observe cache access patterns during SM2 signing or decryption to potentially learn secret scalar information. The issue affects OpenSSL versions 4.0, 3.6, 3.5, and 3.4 on these platforms. Versions 3.0, 1.1.1, and 1.0.2 are not affected. Fixed versions have been released to address this vulnerability.

Impact

The vulnerability allows attackers with the capability to measure timing or cache-line access patterns during SM2 signing or decryption on affected ARM64 and RISC-V platforms to gain information about secret scalar values. This could potentially lead to key recovery or cryptographic compromise of SM2 operations. The CVSS score is low (3.7) indicating limited impact, requiring network access with high attack complexity and no privileges or user interaction. There is no impact on confidentiality, integrity, or availability beyond the potential leakage of secret scalar information.

Summary

CVE-2026-54875 describes a side-channel vulnerability in OpenSSL's SM2 cryptographic operations on ARM64 and RISC-V architectures. The scalar multiplication implementation used for SM2 private key operations is optimized with conditional branches and table lookups dependent on secret scalar bits, causing observable timing and cache access patterns. An attacker capable of measuring these can infer secret scalar values used in SM2 signing or decryption. This vulnerability does not affect FIPS modules as SM2 is not a FIPS algorithm. OpenSSL versions 4.0, 3.6, 3.5, and 3.4 are vulnerable, with fixes available in OpenSSL 4.0.3, 3.6.5, 3.5.9, and 3.4.8 respectively. Earlier versions 3.0, 1.1.1, and 1.0.2 are unaffected.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 10:47 UTC

Technical details

References

Community reviews

Related threats