All changesredhatas of 2026-09-07
CVE-2025-10911
red hatred hat update infrastructure 5cve.org →this looks wrong →
Record history
9 dated edit eventsPublished
- 13 products named later, not at publication
200 days between eventsProduct addedSource 7de373a — commit 7de373a6a978 in the CVE catalog
- not namedred hat hardened images
73 days between eventsProduct addedSource 9867b5d — commit 9867b5d529a9 in the CVE catalog
- not namedred hat enterprise linux 9.6 extended update support
Same calendar dayProducts addedSource 3642f33 — commit 3642f33f856e in the CVE catalog
- not namedred hat enterprise linux 8.4 advanced mission critical update supportand 1 more
Same calendar dayProducts addedSource f16c52a — commit f16c52a3adac in the CVE catalog
- not namedred hat enterprise linux 9.2 update services for sap solutionsand 1 more
Same calendar dayProduct addedSource a7a5759 — commit a7a5759e6328 in the CVE catalog
- not namedred hat enterprise linux 10.0 extended update support
1 day between eventsProducts addedSource ff40fc6 — commit ff40fc633443 in the CVE catalog
- not namedred hat enterprise linux 8.8 telecommunications update serviceand 1 more
3 days between eventsProduct addedSource 1b78d53 — commit 1b78d53721a7 in the CVE catalog
- not namedred hat discovery 2
Same calendar dayProducts addedSource fd4fab2 — commit fd4fab230044 in the CVE catalog
- not namedred hat enterprise linux 8.6 advanced mission critical update supportand 1 more
24 days between eventsProduct addedSource 341a98a — commit 341a98a6a537 in the CVE catalog
- not namedred hat update infrastructure 5
46 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-10911. 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.