All changesredhatas of 2026-09-07
CVE-2026-33845
red hatred hat openshift container platform 4.17cve.org →this looks wrong →
Record history
11 dated edit eventsPublished
- 12 products named later, not at publication
47 days between eventsProduct addedSource 8cc6c33 — commit 8cc6c33eda6c in the CVE catalog
- not namedred hat update infrastructure 5
8 days between eventsProduct addedSource 049b02e — commit 049b02ef17c9 in the CVE catalog
- not namedred hat discovery 2
5 days between eventsProduct addedSource 0b71666 — commit 0b7166696dc6 in the CVE catalog
- not namedred hat enterprise linux 8.4 advanced mission critical update support
Same calendar dayProduct addedSource cfa5fc3 — commit cfa5fc32f5ad in the CVE catalog
- not namedred hat enterprise linux 8.6 advanced mission critical update support
7 days between eventsProduct addedSource b30dd81 — commit b30dd813f69a in the CVE catalog
- not namedred hat ai inference server 3.2
14 days between eventsExcluded comparisonnot countedSource bab2ad7 — commit bab2ad77526c in the CVE catalog
- not namedred hat enterprise linux 9.2 update services for sap solutions
Filtered, not counted: support or installation label under already affected red hat/red hat enterprise linux 9; the record does not establish whether this newly names affected scope or refines the existing product listing.
37 days between eventsProduct addedSource 17be745 — commit 17be745c1d7e in the CVE catalog
- not namedred hat openshift container platform 4.19
Same calendar dayProduct addedSource 0fd6c0a — commit 0fd6c0a84190 in the CVE catalog
- not namedred hat openshift container platform 4.18
5 days between eventsProducts addedSource 4a7d7cf — commit 4a7d7cfc721c in the CVE catalog
- not namedred hat openshift container platform 4.14and 2 more
3 days between eventsProduct addedSource fb94329 — commit fb94329f1e9c in the CVE catalog
- not namedred hat openshift container platform 4.17
Same calendar dayProduct addedSource d8887b6 — commit d8887b68b844 in the CVE catalog
- not namedred hat openshift container platform 4.12
4 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.
1 row marked filtered, not counted is on the rail and counted nowhere. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site.
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-2026-33845. 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.