All changesredhatas of 2026-09-07
CVE-2025-7425
red hatopenshift file integrity operator - fio 1cve.org →this looks wrong →
Record history
12 dated edit eventsPublished
- 22 products named later, not at publication
27 days between eventsProduct addedSource 0a3f86f — commit 0a3f86f0cabf in the CVE catalog
- not namedred hat discovery 2
1 day between eventsProducts addedSource 0f3017f — commit 0f3017f1071a in the CVE catalog
- not namedred hat enterprise linux 8.2 advanced update supportand 3 more
20 days between eventsProduct addedSource 01e0849 — commit 01e08491fe26 in the CVE catalog
- not namedred hat openshift distributed tracing 3.5.3
19 days between eventsProduct addedSource 670ef83 — commit 670ef8361c1a in the CVE catalog
- not namedred hat web terminal 1.12 on rhel 9
Same calendar dayProduct addedSource ec809f3 — commit ec809f3371ce in the CVE catalog
- not namedred hat web terminal 1.11 on rhel 9
31 days between eventsProduct addedSource 071aedd — commit 071aedd705c3 in the CVE catalog
- not namedcert-manager operator for red hat openshift 1.16
21 days between eventsProducts addedSource 10f2b5b — commit 10f2b5bd00bb in the CVE catalog
- not namedred hat openshift container platform 4.12and 7 more
14 days between eventsProduct addedSource f725b94 — commit f725b9464c56 in the CVE catalog
- not namedcompliance operator 1
34 days between eventsProduct addedSource 3d4ce6d — commit 3d4ce6d51704 in the CVE catalog
- not namedlibxml2
29 days between eventsProduct addedSource 7a3ba82 — commit 7a3ba82c6256 in the CVE catalog
- not namedrhoss-1.36-rhel-8
82 days between eventsProduct addedSource 5105e6c — commit 5105e6cdcab7 in the CVE catalog
- not namedred hat hardened images
53 days between eventsProduct addedSource a3eacdd — commit a3eacdd5fd55 in the CVE catalog
- not namedopenshift file integrity operator - fio 1
93 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-7425. 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 f5f9fc6fd7dc. 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.