Skip to content

Every change, newest first

Compare earlier and later source statements, with the dates and evidence behind each measured change.

8 record changes · 1 advisory changes · newest first · grouped by dayCSVJSONRSS

SinceClear all

Showing changes seen on 2026-02-11. Every day

Counted changes changed on 2026-02-11, newest first, one line per change to a CVE record or a GHSA advisory, 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 or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together.Vendor or package, 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 11 Feb 2026· 9 changes
2026-02-11Product addednot named as affected at publication, now names red hat update infrastructure 5Time to revision 68 to 77 days
2026-02-11same kind of change as the line aboveCVE-2025-13601same vendor as the line abovesame change as the line aboveTime to revision 77 days
2026-02-11same kind of change as the line aboveCVE-2025-14104same vendor as the line abovesame change as the line aboveTime to revision 68 days
2026-02-11Product addednot named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update supportTime to revision 9 to 34 days
2026-02-11same kind of change as the line aboveCVE-2026-0719same vendor as the line abovesame change as the line aboveTime to revision 34 days
2026-02-11same kind of change as the line aboveCVE-2026-1761same vendor as the line abovesame change as the line aboveTime to revision 9 days
2026-02-11Product addedCVE-2025-6830TR-CERTnot named as affected at publication, now names password moduleTime to revision 2 days
2026-02-11Product addedCVE-2025-13601not named as affected at publication, now names red hat openshift container platform 4.18Time to revision 77 days
2026-02-11CVSS base score changedCVE-2025-0875
whole record
TR-CERT
stated at publication 4.2, now states 6.5CVSS v3.1 · base scoreMediumMediumTime to revision 142 days
2026-02-11CVSS base score changedCVE-2026-21517
whole record
microsoft
stated at publication 7.0, now states 4.7CVSS v3.1 · base scoreHighMediumTime to revision 0 days
2026-02-11published 2019-06-06Advisory severity changedGHSA-w7q7-vjp8-7jv4whole advisorycriticalstated at publication HIGH, now states CRITICALNo CVSS vector was stated in the first observed version.Duration unknown

Two units, never added: changes to a CVE record or KEV entry, and changes to a GitHub advisory. Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

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 →