All changesredhatas of 2026-09-07
CVE-2024-11218
red hatred hat enterprise linux 10cve.org →this looks wrong →
Record history
9 dated edit eventsPublished
- 9 products named later, not at publication
15 days between eventsProduct addedSource a8906be — commit a8906bee59e6 in the CVE catalog
- not namedred hat openshift container platform 4.17
4 days between eventsProduct addedSource 433dc81 — commit 433dc81b8ab4 in the CVE catalog
- not namedred hat enterprise linux 8.6 advanced mission critical update support
Same calendar dayProduct addedSource 82acc00 — commit 82acc002ae20 in the CVE catalog
- not namedred hat openshift container platform 4.16
10 days between eventsProduct addedSource 5524561 — commit 5524561504c1 in the CVE catalog
- not namedred hat openshift container platform 4.14
7 days between eventsProduct addedSource 009dd46 — commit 009dd46522de in the CVE catalog
- not namedred hat openshift container platform 4.15
5 days between eventsProduct addedSource 2a117dd — commit 2a117dd77543 in the CVE catalog
- not namedred hat openshift container platform 4.18
9 days between eventsProduct addedSource e888973 — commit e8889730930b in the CVE catalog
- not namedred hat openshift container platform 4.12
7 days between eventsProduct addedSource a3d68b4 — commit a3d68b427816 in the CVE catalog
- not namedred hat openshift container platform 4.13
102 days between eventsProduct addedSource 17cbd5b — commit 17cbd5b74eee in the CVE catalog
- not namedred hat enterprise linux 10
434 days to snapshotSnapshot
Source record: View on CVE.org ↗
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.
The GitHub Advisory Database was read and carries no changed advisory naming CVE-2024-11218. 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.
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.