CVE-2026-28390VulnerabilityPublished 7 Jul 2026Updated 29 Oct 2026

Red Hat Security Advisory: compat-openssl10 security update

Affects Red Hat compat-openssl10Source GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-45447

Not known to be exploited.

Data as of 29 Oct 2026, 08:12 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Jul 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

AI-suggested

Red Hat has released updated compat-openssl10 packages (version 1.0.2o-4.el8_8.1) that address these vulnerabilities. Users of affected Red Hat Enterprise Linux 8.8 variants should apply these updates promptly following Red Hat's official guidance at https://access.redhat.com/articles/11258. No additional mitigation steps are indicated or required beyond applying the official patches.

Description

Red Hat released a security update for the compat-openssl10 package addressing two vulnerabilities in OpenSSL libraries used for compatibility with older software. The first vulnerability (CVE-2026-28390) is a denial of service caused by a NULL pointer dereference in CMS EnvelopedData processing. The second (CVE-2026-45447) is a heap use-after-free in the PKCS7_verify() function. These issues could cause application crashes or instability when processing certain cryptographic data. The update is rated as important by Red Hat and affects Red Hat Enterprise Linux 8.8 variants. No CVSS score is provided, but the impact is considered high. Red Hat has issued patches for these vulnerabilities in version 1.0.2o-4.el8_8.1 of compat-openssl10.

Impact

Successful exploitation of CVE-2026-28390 can cause denial of service by crashing applications processing CMS EnvelopedData. CVE-2026-45447 can lead to heap use-after-free conditions, potentially causing application crashes or memory corruption. Both vulnerabilities impact the stability and reliability of applications relying on the affected OpenSSL compatibility libraries. There is no indication of remote code execution or data disclosure from the provided information. No known exploits in the wild have been reported.

CWE-476NULL Pointer Dereference (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #13OWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product dereferences a pointer that it expects to be valid but is NULL.
Implementation
For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished.
Requirements
Select a programming language that is not susceptible to these issues.
Implementation
Check the results of all functions that return a value and verify that the value is non-null before acting upon it.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-825Expired Pointer Dereference (opens in a new tab)
Base weakness
The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.
Architecture and Design
Choose a language that provides automatic memory management.
Implementation
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 29 Oct 2026, 08:12 UTC

WeaknessesCWE-476, CWE-825

Technical details

References

Community reviews

Related threats