Skip to content
patchdrift.
snapshot 2026-09-07

Every change, newest first

What a record said when it was published, what it says now, and the commit that changed it.

16 changes behind one line · newest firstCSVJSONRSS

SinceClear all
ChangedSourceRows

One change, in full: Product added: red hat discovery 2 named as affected from red hat. The same change in 16 CVE records. Back to the ledger

Counted changes from Red Hat, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.KindRecord, Which record was edited, by its CVE id, or how many records one collapsed line stands on.Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry.What changedDays to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
2026-06-24Product addedCVE-2024-12086
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 526 days
2026-06-24Product addedCVE-2025-14087
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 196 days
2026-06-24Product addedCVE-2025-14512
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 195 days
2026-06-24Product addedCVE-2026-33845
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 55 days
2026-06-24Product addedCVE-2026-33846
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 51 days
2026-06-24Product addedCVE-2026-3832
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 55 days
2026-06-24Product addedCVE-2026-3833
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 55 days
2026-06-24Product addedCVE-2026-42009
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 37 days
2026-06-24Product addedCVE-2026-42010
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 48 days
2026-06-24Product addedCVE-2026-42011
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 48 days
2026-06-24Product addedCVE-2026-42012
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 29 days
2026-06-24Product addedCVE-2026-42013
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 29 days
2026-06-24Product addedCVE-2026-42014
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 9 days
2026-06-24Product addedCVE-2026-42015
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 29 days
2026-06-24Product addedCVE-2026-5260
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 29 days
2026-06-24Product addedCVE-2026-5419
red hat
not named as affected at publication, now names red hat discovery 2Time to revision 23 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.

What this page cannot see

Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.

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.

The units, the refusals, the cut-offs and every source, in full →

Paste your closed CVE tickets and see which of these changes hit them →