All changesredhatas of 2026-09-07
CVE-2025-5987
red hatred hat openshift container platform 4.13CVSS 8.1 high nowcve.org →this looks wrong →
Record history
9 dated edit eventsPublished
- CVSS 5.0 medium
- 8 products named later, not at publication
185 days between eventsRescoredSource fd0892a — commit fd0892ac5885 in the CVE catalog
- Before5.0After8.1medium → highCVSS v3.1 · published base score
14 days between eventsProduct addedSource f6de096 — commit f6de096e4388 in the CVE catalog
- not namedred hat openshift container platform 4.17
5 days between eventsProduct addedSource cfe3430 — commit cfe3430ec57f in the CVE catalog
- not namedred hat openshift container platform 4.20
3 days between eventsProduct addedSource 4a424a7 — commit 4a424a7620d3 in the CVE catalog
- not namedred hat openshift container platform 4.14
Same calendar dayProduct addedSource 05b88f4 — commit 05b88f44d6fc in the CVE catalog
- not namedred hat openshift container platform 4.16
4 days between eventsProduct addedSource 30b063e — commit 30b063e9caa3 in the CVE catalog
- not namedred hat openshift container platform 4.18
1 day between eventsProduct addedSource e1c29b9 — commit e1c29b93b106 in the CVE catalog
- not namedred hat openshift container platform 4.19
1 day between eventsProduct addedSource 8edd85d — commit 8edd85d4a506 in the CVE catalog
- not namedred hat openshift container platform 4.15
28 days between eventsProduct addedSource 62f7378 — commit 62f7378ac3d3 in the CVE catalog
- not namedred hat openshift container platform 4.13
186 days to snapshotSnapshot
- CVSS 8.1 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-5987. 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.