Skip to content
patchdrift.
snapshot 2026-09-07

All changesredhatas of 2026-09-07

CVE-2026-16242

red hatred hat openshift container platform 4.15cve.org →this looks wrong →

Record history

14 dated edit events

  1. Published

    • 15 products named later, not at publication
    9 days between events

  2. Products addedSource 0c79354 — commit 0c793543d139 in the CVE catalog

    • not namedmulticluster engine for kubernetes 2.11and 1 more
    Same calendar day

  3. Product addedSource 41425d1 — commit 41425d132287 in the CVE catalog

    • not namedmulticluster engine for kubernetes 2.9
    Same calendar day

  4. Product addedSource ab00a66 — commit ab00a662168d in the CVE catalog

    • not namedmulticluster engine for kubernetes 2.8
    1 day between events

  5. Product addedSource 4d40bbb — commit 4d40bbb47181 in the CVE catalog

    • not namedmulticluster engine for kubernetes 2.17
    3 days between events

  6. Product addedSource 646be26 — commit 646be2678d92 in the CVE catalog

    • not namedmulticluster engine for kubernetes 2.1
    2 days between events

  7. Product addedSource c4a2b24 — commit c4a2b2450ecd in the CVE catalog

    • not namedred hat openshift container platform 4.22
    1 day between events

  8. Product addedSource d8e6427 — commit d8e64276ccc0 in the CVE catalog

    • not namedred hat openshift container platform 4.18
    Same calendar day

  9. Product addedSource ae6de14 — commit ae6de14fb1ff in the CVE catalog

    • not namedred hat openshift container platform 4.19
    Same calendar day

  10. Product addedSource f433faf — commit f433fafe89f6 in the CVE catalog

    • not namedred hat openshift container platform 4.21
    1 day between events

  11. Product addedSource aeb98c6 — commit aeb98c63d201 in the CVE catalog

    • not namedred hat openshift container platform 4.17
    3 days between events

  12. Product addedSource 95c9ab7 — commit 95c9ab70466b in the CVE catalog

    • not namedred hat openshift container platform 4.2
    3 days between events

  13. Product addedSource 358623a — commit 358623a96db5 in the CVE catalog

    • not namedred hat openshift container platform 4.16
    14 days between events

  14. Product addedSource 0fd6c0a — commit 0fd6c0a84190 in the CVE catalog

    • not namedred hat openshift container platform 4.15
    Same calendar day

  15. Product addedSource f57c98f — commit f57c98fb3040 in the CVE catalog

    • not namedred hat openshift container platform 4.14
    12 days to snapshot

  16. Snapshot

    Source record: View on CVE.org ↗

Check your tickets

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. 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-2026-16242. 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.