Skip to content
patchdrift.
snapshot 2026-09-07

All changesredhatas of 2026-09-07

CVE-2026-4424

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

Record history

17 dated edit events

  1. Published

    • 18 products named later, not at publication
    21 days between events

  2. Product addedSource 5332663 — commit 5332663aa9b1 in the CVE catalog

    • not namedred hat hardened images
    7 days between events

  3. Product addedSource e7b4302 — commit e7b430289dc2 in the CVE catalog

    • not namedred hat enterprise linux 8.2 advanced update support
    4 days between events

  4. Product addedSource f7f6ca1 — commit f7f6ca157169 in the CVE catalog

    • not namedred hat enterprise linux 8.6 advanced mission critical update support
    2 days between events

  5. Product addedSource 23aaf93 — commit 23aaf93a845b in the CVE catalog

    • not namedred hat insights proxy 1.5
    Same calendar day

  6. Product addedSource 141f623 — commit 141f623b9093 in the CVE catalog

    • not namedred hat enterprise linux 8.4 advanced mission critical update support
    1 day between events

  7. Product addedSource c58bdee — commit c58bdeecc9cc in the CVE catalog

    • not namedred hat update infrastructure 5
    7 days between events

  8. Product addedSource daf4f70 — commit daf4f706ba30 in the CVE catalog

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

  9. Product addedSource 1097ac5 — commit 1097ac5b95ee in the CVE catalog

    • not namedrhel-8 based middleware containers
    2 days between events

  10. Product addedSource 594ad1d — commit 594ad1d137fb in the CVE catalog

    • not namedred hat discovery 2
    2 days between events

  11. Product addedSource cde436e — commit cde436e3652f in the CVE catalog

    • not namedred hat openshift container platform 4.12
    2 days between events

  12. Product addedSource 74d8f90 — commit 74d8f903601c in the CVE catalog

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

  13. Product addedSource 98c334d — commit 98c334d398a7 in the CVE catalog

    • not namedred hat ai inference server 3.3
    1 day between events

  14. Product addedSource 2c533c9 — commit 2c533c99b783 in the CVE catalog

    • not namedred hat openshift container platform 4.15
    Same calendar day

  15. Product addedSource a3b4709 — commit a3b470985427 in the CVE catalog

    • not namedred hat openshift container platform 4.14
    7 days between events

  16. Products addedSource 66b5fc3 — commit 66b5fc34dd64 in the CVE catalog

    • not namedred hat ai inference server 3.2and 1 more
    8 days between events

  17. Product addedSource 0c9aa0a — commit 0c9aa0aaa613 in the CVE catalog

    • not namedred hat openshift container platform 4.19
    7 days between events

  18. Product addedSource 50d2e54 — commit 50d2e5475d01 in the CVE catalog

    • not namedred hat openshift container platform 4.13
    95 days to snapshot

  19. 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-4424. 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.