Skip to content

All changesredhatas of 2026-09-07

CVE-2026-14474

red hatred hat openshift container platform 4.17cve.orgthis looks wrong →

Record history

11 dated edit events
  1. Published

    • 13 products named later, not at publication
    20 days between events
  2. Excluded comparisonnot countedSource 3fc46d7commit 3fc46d7716e9 in the CVE catalog

    • not namedred hat enterprise linux 10.0 extended update support

    Filtered, not counted: support or installation label under already affected red hat/red hat enterprise linux 10; the record does not establish whether this newly names affected scope or refines the existing product listing.

    8 days between events
  3. Excluded comparisonnot countedSource 06e447fcommit 06e447f03ff8 in the CVE catalog

    • not namedred hat enterprise linux 9.6 extended update support

    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.

    Same calendar day
  4. Products addedSource ef73165commit ef73165d565d in the CVE catalog

    • not namedred hat enterprise linux 8.4 advanced mission critical update supportand 1 more
    • not namedred hat enterprise linux 8.4 extended update support long-life add-onand 3 more
    • not namedred hat enterprise linux 9.2 update services for sap solutionsand 1 more
    14 days between events
  5. Products addedSource ccb2482commit ccb24821a75c in the CVE catalog

    • not namedred hat openshift container platform 4.20and 1 more
    Same calendar day
  6. Product addedSource b1e297bcommit b1e297b2c2ed in the CVE catalog

    • not namedred hat openshift container platform 4.21
    1 day between events
  7. Product addedSource 7f49084commit 7f49084717c2 in the CVE catalog

    • not namedred hat openshift container platform 4.19
    1 day between events
  8. Product addedSource 050d160commit 050d1603c7c7 in the CVE catalog

    • not namedred hat openshift container platform 4.13
    6 days between events
  9. Product addedSource 0fd6c0acommit 0fd6c0a84190 in the CVE catalog

    • not namedred hat openshift container platform 4.18
    5 days between events
  10. Products addedSource 4a7d7cfcommit 4a7d7cfc721c in the CVE catalog

    • not namedred hat openshift container platform 4.14and 2 more
    3 days between events
  11. Product addedSource fb94329commit fb94329f1e9c in the CVE catalog

    • not namedred hat openshift container platform 4.17
    Same calendar day
  12. Product addedSource d8887b6commit d8887b68b844 in the CVE catalog

    • not namedred hat openshift container platform 4.12
    4 days to snapshot
  13. Snapshot

    Source record: View on CVE.org ↗

Check my CVEs

Add your patched version to compare it with the recorded boundary.

One per line · up to 500 IDs

Versions & supported formats

Add a patched version beside a CVE to compare it. GHSA versions are not compared. Product names are also supported. Results include a watchlist link, RSS and JSON.

Privacy & sharingData & methodology

Change cards link to the source commit. Compare CVE values with the first mirrored record and KEV values with the preceding catalog snapshot. Verify one finding yourself →

Data sources and quality

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.

8 rows marked filtered, not counted are 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-14474. 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.