Every change, newest first
These rows are not counted anywhere on this site. 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. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.
One change, in full: Product added: 6 products named as affected from red hat. Products named as affected in 10 CVE records, across 6 products. Drawn here as 6 lines, one per product. Back to the ledger
| 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. | Kind | Record, 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 changed | Days 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-09-03 | Product added | CVE-2026-16493 | not named as affected at publication, now names red hat satellite 6.17 for rhel 9Not counted: Product relabelled. probable relabelling of red hat/red hat satellite 6, not a newly affected product | Days to revision 44 | |
| 2026-09-03 | Product added | CVE-2026-15563 | not named as affected at publication, now names red hat fuse 7Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure | Days to revision 24 | |
| 2026-09-03 | Product added | CVE-2026-15927 | not named as affected at publication, now names red hat quay 3.15Not counted: Product relabelled. probable relabelling of red hat/red hat quay 3, not a newly affected product | Days to revision 45 | |
| 2026-09-03 | Product added | not named as affected at publication, now names red hat build of apache camel 3.33 for quarkus 3.33.3.sp1not counted: Added entry does not state affected status | Days to revision 3 | ||
| 2026-09-03 | same kind of change as the line above | CVE-2026-12894 | same vendor as the line above | same change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure | Days to revision 3 |
| 2026-09-03 | same kind of change as the line above | CVE-2026-17615 | same vendor as the line above | same change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure | Days to revision 3 |
| 2026-09-03 | Product added | not named as affected at publication, now names red hat openshift container platform 4.17not counted: Product relabelled | Days to revision 23 to 37 | ||
| 2026-09-03 | same kind of change as the line above | CVE-2026-49332 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/red hat openshift container platform 4, not a newly affected product | Days to revision 37 |
| 2026-09-03 | same kind of change as the line above | CVE-2026-50236 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/red hat openshift container platform 4, not a newly affected product | Days to revision 23 |
| 2026-09-03 | same kind of change as the line above | CVE-2026-50237 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/red hat openshift container platform 4, not a newly affected product | Days to revision 23 |
| 2026-09-03 | Product added | not named as affected at publication, now names red hat advanced cluster management for kubernetes 2.17not counted: Product relabelled | Days to revision 13 | ||
| 2026-09-03 | same kind of change as the line above | CVE-2026-66787 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/red hat advanced cluster management for kubernetes 2, not a newly affected product | Days to revision 13 |
| 2026-09-03 | same kind of change as the line above | CVE-2026-66788 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/red hat advanced cluster management for kubernetes 2, not a newly affected product | Days to revision 13 |
Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
Data sources and quality
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 →