All changesredhatas of 2026-09-07
CVE-2025-7195
red hatmulticluster engine for kubernetes 2.8CVSS 6.4 medium nowcve.org →this looks wrong →
Record history
13 dated edit eventsPublished
- CVSS 5.2 medium
- 14 products named later, not at publication
24 days between eventsProduct addedSource e55dd3c — commit e55dd3c00502 in the CVE catalog
- not namedred hat fuse 7
60 days between eventsProduct addedSource 1a031cd — commit 1a031cd1f834 in the CVE catalog
- not namedred hat advanced cluster management for kubernetes 2.14
7 days between eventsProduct addedSource 796cd70 — commit 796cd706701b in the CVE catalog
- not namedmulticluster engine for kubernetes 2.9
4 days between eventsProducts addedSource 72f12d8 — commit 72f12d86c07b in the CVE catalog
- not namedmulticluster engine for kubernetes 2.7and 1 more
10 days between eventsProduct addedSource 0004978 — commit 0004978344b4 in the CVE catalog
- not namedcompliance operator 1
27 days between eventsProduct addedSource 5e8760f — commit 5e8760f1314d in the CVE catalog
- not namedred hat advanced cluster management for kubernetes 2.11
Same calendar dayProduct addedSource 3915553 — commit 39155539731d in the CVE catalog
- not namedmulticluster engine for kubernetes 2.6
6 days between eventsProduct addedSource 96d597a — commit 96d597a75cbf in the CVE catalog
- not namedoperator-sdk
14 days between eventsProduct addedSource c5a5201 — commit c5a52012e585 in the CVE catalog
- not namedrhel-9-cnv-4.18
2 days between eventsProducts addedSource 7c239f5 — commit 7c239f509d82 in the CVE catalog
- not namedrhel-9-cnv-4.17, rhel-9-cnv-4.20
6 days between eventsProduct addedSource 608875d — commit 608875d6b4a9 in the CVE catalog
- not namedred hat advanced cluster management for kubernetes 2.13
1 day between eventsProduct addedSource 4482998 — commit 4482998be982 in the CVE catalog
- not namedmulticluster engine for kubernetes 2.8
50 days between eventsRescoredSource f97a597 — commit f97a597e4b9d in the CVE catalog
- Before5.2After6.4stays mediumCVSS v3.1 · published base score
185 days to snapshotSnapshot
- CVSS 6.4 medium
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-7195. 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.