All changesredhatas of 2026-09-07
CVE-2025-5914
red hatopenshift file integrity operator - fio 1CVSS 7.8 high nowcve.org →this looks wrong →
Record history
16 dated edit eventsPublished
- CVSS 3.9 low
- 20 products named later, not at publication
77 days between eventsProduct addedSource eca1af2 — commit eca1af25da2a in the CVE catalog
- not namedred hat enterprise linux 8.2 advanced update support
1 day between eventsProduct addedSource 8cea144 — commit 8cea144bcfac in the CVE catalog
- not namedred hat openshift distributed tracing 3.5.3
1 day between eventsProduct addedSource d7b34ac — commit d7b34ac810b2 in the CVE catalog
- not namedred hat insights proxy 1.5
1 day between eventsProducts addedSource 3420c31 — commit 3420c3119f3a in the CVE catalog
- not namedred hat enterprise linux 8.4 advanced mission critical update supportand 1 more
14 days between eventsProduct addedSource a4cf1a5 — commit a4cf1a5f14d0 in the CVE catalog
- not namedred hat openshift sandboxed containers 1.1
4 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
8 days between eventsProduct addedSource cef604d — commit cef604d8ae2c in the CVE catalog
- not namedred hat discovery 2
23 days between eventsProduct addedSource 071aedd — commit 071aedd705c3 in the CVE catalog
- not namedcert-manager operator for red hat openshift 1.16
26 days between eventsProducts addedSource 0393aa4 — commit 0393aa41bedc in the CVE catalog
- not namedred hat openshift container platform 4.14and 4 more
9 days between eventsProduct addedSource f725b94 — commit f725b9464c56 in the CVE catalog
- not namedcompliance operator 1
48 days between eventsRescoredSource 0dd9fd0 — commit 0dd9fd02aa0e in the CVE catalog
- Before3.9After7.8low → highCVSS v3.1 · published base score
8 days between eventsProduct addedSource 4ef46da — commit 4ef46dad93e6 in the CVE catalog
- not namedred hat openshift container platform 4.16
7 days between eventsProduct addedSource 7a3ba82 — commit 7a3ba82c6256 in the CVE catalog
- not namedrhoss-1.36-rhel-8
14 days between eventsProduct addedSource 94a496c — commit 94a496c41f1f in the CVE catalog
- not namedred hat openshift container platform 4.15
120 days between eventsProduct addedSource 0725ac2 — commit 0725ac20e1c2 in the CVE catalog
- not namedopenshift file integrity operator - fio 1
94 days to snapshotSnapshot
- CVSS 7.8 high
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-5914. 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.