All changesredhatas of 2026-09-07
CVE-2024-1488
red hatred hat enterprise linux 10cve.org →this looks wrong →
Record history
5 dated edit eventsPublished
- 11 products named later, not at publication
56 days between eventsProduct addedSource 3807e72 — commit 3807e72bf9ae in the CVE catalog
- not namedred hat enterprise linux 9.2 extended update support
4 days between eventsProducts addedSource e0e00ee — commit e0e00ee0663a in the CVE catalog
- not namedred hat enterprise linux 8.6 extended update supportand 2 more
15 days between eventsProducts addedSource 9a8f5af — commit 9a8f5afeeba1 in the CVE catalog
- not namedred hat enterprise linux 8.4 advanced mission critical update supportand 2 more
8 days between eventsProducts addedSource 4ed82be — commit 4ed82be8d290 in the CVE catalog
- not namedred hat enterprise linux 8.2 advanced update supportand 2 more
423 days between eventsProduct addedSource 63ca5f7 — commit 63ca5f7ff484 in the CVE catalog
- not namedred hat enterprise linux 10
429 days to snapshotSnapshot
Source record: View on CVE.org ↗
Check your tickets
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. The full recipe →
Data coverage & methodology
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-1488. 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.