All changesredhatas of 2026-09-07
CVE-2025-0624
red hatred hat openshift container platform 4.14cve.org →this looks wrong →
Record history
10 dated edit eventsPublished
- 10 products named later, not at publication
20 days between eventsProduct addedSource 33e5ff6 — commit 33e5ff6e96ad in the CVE catalog
- not namedred hat enterprise linux 8.6 advanced mission critical update support
Same calendar dayProduct addedSource 0452446 — commit 04524468ddc3 in the CVE catalog
- not namedred hat enterprise linux 8.4 advanced mission critical update support
2 days between eventsProduct addedSource d5dcf84 — commit d5dcf844f554 in the CVE catalog
- not namedred hat enterprise linux 8.2 advanced update support
21 days between eventsProduct addedSource bcf2f52 — commit bcf2f5248d9b in the CVE catalog
- not namedred hat openshift container platform 4.17
Same calendar dayProduct addedSource eee9e40 — commit eee9e4099a78 in the CVE catalog
- not namedred hat openshift container platform 4.16
7 days between eventsProduct addedSource d96ddec — commit d96ddec02ec0 in the CVE catalog
- not namedred hat openshift container platform 4.12
Same calendar dayProduct addedSource 89ed8cc — commit 89ed8cc9fb7e in the CVE catalog
- not namedred hat openshift container platform 4.18
7 days between eventsProduct addedSource 25ac03b — commit 25ac03b4397c in the CVE catalog
- not namedred hat openshift container platform 4.13
22 days between eventsProduct addedSource 021742f — commit 021742f85e8f in the CVE catalog
- not namedred hat openshift container platform 4.15
12 days between eventsProduct addedSource 578b951 — commit 578b951655ec in the CVE catalog
- not namedred hat openshift container platform 4.14
474 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-2025-0624. 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.