Skip to content

Every change, newest first

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

18 changes refused · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

Showing changes seen on 2026-08-19. Every day

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.

Rows we checked and refused, counted nowhere changed on 2026-08-19, 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.
Wed 19 Aug 2026· 18 changes
2026-08-19Affected range extendedCVE-2026-17183
grafanagrafana oss
stated at publication 13.1.1, now states 13.1.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 13.1.1 still holdsDuration unknown
2026-08-19Affected range extendedCVE-2026-19501
sureformssureforms
certcc
stated at publication 2.1.1, now states 2.12.1Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpTime to revision 1 days
2026-08-19Product addedCVE-2026-16828not named as affected at publication, now names power systems firmwareNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/server firmwareTime to revision 0 days
2026-08-19Product addedCVE-2026-16832not named as affected at publication, now names power systems firmwareNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/server firmwareTime to revision 0 days
2026-08-19Product addedCVE-2026-16930not named as affected at publication, now names power systems firmwareNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/power firmwareTime to revision 0 days
2026-08-19Product addedCVE-2026-16938not named as affected at publication, now names power systems firmwareNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/server firmwareTime to revision 0 days
2026-08-19Product addedCVE-2026-17093not named as affected at publication, now names power systems firmwareNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/power firmwareTime to revision 0 days
2026-08-19Product addedCVE-2026-17100not named as affected at publication, now names power systems firmwareNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/power firmwareTime to revision 0 days
2026-08-19Product addedCVE-2026-17429not named as affected at publication, now names power systems firmwareNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed ibm/power firmware; a new product identity is not establishedTime to revision 0 days
2026-08-19Product addedCVE-2026-17494not named as affected at publication, now names power systems firmwareNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/power firmwareTime to revision 0 days
2026-08-19Product addedCVE-2026-18848not named as affected at publication, now names power systems firmwareNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/server firmwareTime to revision 0 days
2026-08-19Product addedCVE-2026-19234not named as affected at publication, now names power systems firmwareNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/power firmwareTime to revision 0 days
2026-08-19Product addedCVE-2026-19321not named as affected at publication, now names power systems firmwareNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/power firmwareTime to revision 0 days
2026-08-19Product addedCVE-2026-59691not named as affected at publication, now names red hat enterprise linux 8.4 extended update support long-life add-onNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 8; the record does not establish whether this newly names affected scope or refines the existing product listingTime to revision 41 days
2026-08-19Product addedCVE-2026-59692not named as affected at publication, now names red hat enterprise linux 8.4 extended update support long-life add-onNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 8; the record does not establish whether this newly names affected scope or refines the existing product listingTime to revision 41 days
2026-08-19Product addedCVE-2026-59691not named as affected at publication, now names red hat enterprise linux 9.2 update services for sap solutionsNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 9; the record does not establish whether this newly names affected scope or refines the existing product listingTime to revision 41 days
2026-08-19Product addedCVE-2026-59692not named as affected at publication, now names red hat enterprise linux 9.2 update services for sap solutionsNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 9; the record does not establish whether this newly names affected scope or refines the existing product listingTime to revision 41 days
2026-08-19Product addedCVE-2026-18963not named as affected at publication, now names red hat build of keycloak 26.4.15Not 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 exposureTime to revision 0 days

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

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

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 →