Skip to content
patchdrift.
snapshot 2026-09-07

All changesredhatas of 2026-09-07

CVE-2025-5278

red hatred hat openshift distributed tracing 3.10.2cve.org →this looks wrong →

Record history

5 dated edit events

  1. Published

    • 5 products named later, not at publication
    399 days between events

  2. Product addedSource 6bf9e32 — commit 6bf9e32132f6 in the CVE catalog

    • not namedred hat discovery 2
    1 day between events

  3. Product addedSource c3ade37 — commit c3ade37440f1 in the CVE catalog

    • not namedred hat insights proxy 1.5
    14 days between events

  4. Product addedSource f412a64 — commit f412a64d8a76 in the CVE catalog

    • not namedcost management 4
    8 days between events

  5. Product addedSource 341a98a — commit 341a98a6a537 in the CVE catalog

    • not namedred hat update infrastructure 5
    3 days between events

  6. Product addedSource 3619c64 — commit 3619c6454232 in the CVE catalog

    • not namedred hat openshift distributed tracing 3.10.2
    43 days to snapshot

  7. 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-2025-5278. 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.