All changesredhatas of 2026-09-07
CVE-2025-6021
red hatred hat hardened imagescve.org →this looks wrong →
Record history
10 dated edit eventsPublished
- 14 products named later, not at publication
47 days between eventsProduct addedSource fb46851 — commit fb46851b5b07 in the CVE catalog
- not namedred hat enterprise linux 8.6 advanced mission critical update support
1 day between eventsProduct addedSource 970fb2e — commit 970fb2edba8c in the CVE catalog
- not namedred hat enterprise linux 8.2 advanced update support
Same calendar dayProduct addedSource e007dce — commit e007dceb2873 in the CVE catalog
- not namedred hat enterprise linux 8.4 advanced mission critical update support
7 days between eventsProduct addedSource 92adf71 — commit 92adf71aef0f in the CVE catalog
- not namedred hat discovery 2
1 day between eventsProduct addedSource 0f3017f — commit 0f3017f1071a in the CVE catalog
- not namedred hat insights proxy 1.5
6 days between eventsProducts addedSource 831ad19 — commit 831ad19055ff in the CVE catalog
- not namedred hat openshift container platform 4.16and 1 more
1 day between eventsProduct addedSource ee43a71 — commit ee43a71a671b in the CVE catalog
- not namedred hat openshift container platform 4.14
84 days between eventsProducts addedSource 796cd70 — commit 796cd706701b in the CVE catalog
- not namedred hat openshift container platform 4.12and 3 more
23 days between eventsProduct addedSource 19994fb — commit 19994fbc7b11 in the CVE catalog
- not namedred hat openshift container platform 4.19
136 days between eventsProduct addedSource 2184caf — commit 2184cafc48f5 in the CVE catalog
- not namedred hat hardened images
146 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-2025-6021. 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.