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.

13 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

Showing changes seen on 2026-07-23. Every day

Counted changes changed on 2026-07-23, 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.
Thu 23 Jul 2026· 13 changes
2026-07-23Product addedCVE-2026-11332not named as affected at publication, now names migration toolkit for applications 8Time to revision 49 days
2026-07-23Product addedCVE-2026-11332not named as affected at publication, now names migration toolkit for virtualizationTime to revision 49 days
2026-07-23Product addedCVE-2026-11332not named as affected at publication, now names red hat ansible automation platform ansible core 2Time to revision 49 days
2026-07-23Product addedCVE-2026-11332not named as affected at publication, now names red hat openshift container platform 4Time to revision 49 days
2026-07-23Product addedCVE-2026-11332not named as affected at publication, now names self-service automation portal 2Time to revision 49 days
2026-07-23Product addedCVE-2026-16615redhatnot named as affected at publication, now names librestTime to revision 1 days
2026-07-23Product addedCVE-2025-10911not named as affected at publication, now names red hat update infrastructure 5Time to revision 301 days
2026-07-23Product addedCVE-2025-5278not named as affected at publication, now names red hat update infrastructure 5Time to revision 422 days
2026-07-23Product addedCVE-2025-6170not named as affected at publication, now names red hat update infrastructure 5Time to revision 402 days
2026-07-23Product addedCVE-2026-48864not named as affected at publication, now names red hat update infrastructure 5Time to revision 58 days
2026-07-23Product addedCVE-2026-58016not named as affected at publication, now names red hat update infrastructure 5Time to revision 23 days
2026-07-23CVSS base score changedCVE-2026-63764
whole record
VulnCheck
stated at publication 9.3, now states 8.6CVSS v3.1 · base scoreCriticalHighTime to revision 2 days
2026-07-23Record state changedCVE-2026-16552
whole record
redhat
stated at publication PUBLISHED, now states REJECTEDTime to revision 1 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 →