CVE-2026-35189VulnerabilityPublished 14 Oct 2026Updated 10 Nov 2026

SUSE · Security update for openssl-3

Affects SUSESource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-35189· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in SUSE package updates : update SUSE openssl when convenient.

Data as of 10 Nov 2026, 20:17 UTC

CVSS 3.1 base score

5.3Medium

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

Thin evidence

One scorer or none

CVSS scores by source
CISA-ADP	CVSS 3.1	5.3

Patch: Available – fixed in 4.0.3, 3.6.5, 3.5.9 +4

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

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

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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Sep 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 10 Nov 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 to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
OpenSSLOpenSSL	Affected >=4.0.0 <4.0.3	Fixed in 4.0.3
OpenSSLOpenSSL	Affected >=3.6.0 <3.6.5	Fixed in 3.6.5
OpenSSLOpenSSL	Affected >=3.5.0 <3.5.9	Fixed in 3.5.9
OpenSSLOpenSSL	Affected >=3.4.0 <3.4.8	Fixed in 3.4.8
OpenSSLOpenSSL	Affected >=3.0.0 <3.0.23	Fixed in 3.0.23
OpenSSLOpenSSL	Affected >=1.1.1 <1.1.1zj	Fixed in 1.1.1zj

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

AI-suggested

A security update for OpenSSL 3 has been released that addresses all listed vulnerabilities. Users and administrators should apply this update promptly to mitigate these risks. Since the vendor advisory indicates a fixed update is available, no additional temporary mitigations are specified.

Description

This security update for OpenSSL 3 addresses multiple vulnerabilities including excessive memory allocation, timing side-channel attacks, out-of-bounds access, denial of service, and flow control issues affecting various cryptographic operations and protocols such as QUIC and DTLS. The update fixes a range of issues identified by CVE identifiers CVE-2026-35189 through CVE-2026-84784.

Impact

The vulnerabilities collectively impact the confidentiality, integrity, and availability of systems using OpenSSL 3. They include risks of excessive memory allocation potentially leading to resource exhaustion, timing side-channel leaks that could expose cryptographic keys, out-of-bounds memory access causing potential crashes or memory corruption, denial of service conditions via malformed DTLS records, and protocol-level issues in QUIC that could affect connection stability and security. No known exploits in the wild have been reported at this time.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 20:17 UTC

Technical details

References

Community reviews

Related threats