All changesredhatas of 2026-09-07
CVE-2024-1394
red hatred hat certification program for red hat enterprise linux 9cve.org →this looks wrong →
Record history
8 dated edit eventsPublished
- 9 products named later, not at publication
12 days between eventsProduct addedSource 3c3462e — commit 3c3462e6d522 in the CVE catalog
- not namedred hat openshift container platform 4.15
1 day between eventsProduct addedSource 53b5a46 — commit 53b5a4632508 in the CVE catalog
- not namedred hat openshift container platform 4.14
Same calendar dayProduct addedSource 68616ca — commit 68616cabe1fd in the CVE catalog
- not namedred hat openshift container platform 4.12
22 days between eventsProduct addedSource ea0ed97 — commit ea0ed979d24a in the CVE catalog
- not namedred hat openshift container platform 4.13
27 days between eventsProducts addedSource 697ab8a — commit 697ab8a01d0c in the CVE catalog
- not namedred hat openstack platform 17.1 for rhel 8and 1 more
56 days between eventsProduct addedSource 44e9577 — commit 44e95774efdc in the CVE catalog
- not namedrhodf-4.16-rhel-9
8 days between eventsProduct addedSource 61f5b59 — commit 61f5b59b64fd in the CVE catalog
- not namedred hat openstack platform 18.0
350 days between eventsProduct addedSource aed88f2 — commit aed88f2b5cb6 in the CVE catalog
- not namedred hat certification program for red hat enterprise linux 9
424 days to snapshotSnapshot
Source record: View on CVE.org ↗
GitHub advisories naming this CVE
1 advisory row across 1 advisory, counted separately from the record's own rows above.
| Change | Advisory | Ecosystem / package | What the advisory says now | Severity |
|---|---|---|---|---|
| Package added to advisory | GHSA-78hx-gp6g-7mj6CVE-2024-1394 | not named as affected when the advisory was published, now names github.com/microsoft/go-crypto-openssl/openssl | high |
An advisory is an entry in the GitHub Advisory Database, the GHSA page a Dependabot alert links to. It is reached from a CVE id only when the advisory names that CVE id itself, and many advisories name none. So no advisory here means none was found among the advisories that name one of these ids. It does not mean there is nothing to find.
Check my CVEs
Add your patched version to compare it with the recorded boundary.
Change cards link to the source commit. Compare CVE values with the first mirrored record and KEV values with the preceding catalog snapshot. Verify one finding yourself →
Data sources and quality
CVE values compare the first mirrored record with later source states. Initial records may have been backfilled after publication. KEV events compare consecutive catalog snapshots. Dates identify the reported value’s first observed appearance; earlier intermediate revisions may exist. Only counted rows contribute to totals. as of the 2026-09-07 snapshot.
Not checked: a record published before 2023 cannot have its state at publication recovered, so the CVE-record checks never compared it. For such a record, silence on this page means it was not looked at, not that it held.
Not checked: a CISA KEV listing added before 2025-01-27 was never seen changing, so a record that has been in KEV for years carries no listing node here. A missing KEV node is not evidence that CISA has not listed it.
How every one of these figures is measured, in full →
A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.
Shipped snapshot computed 2026-09-07 from catalog commit ed5547afbae2. Real findings, not live ones: records amended since are not reflected. A later fix version is evidence that the record changed, not evidence that the first fix was incomplete.