Skip to content

Every change, newest first

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

3 record changes · 4 advisory changes · newest first · grouped by dayCSVJSONRSS

SinceClear all

Showing changes seen on 2026-03-12. Every day

Counted changes changed on 2026-03-12, 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.
Thu 12 Mar 2026· 7 changes
2026-03-123 commitsProduct addedCVE-2025-14242not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support and 2 moreBranches and original-value intervals are stated on each row.Time to revision 57 days
2026-03-12same kind of change as the line aboveCVE-2025-14242same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update supportTime to revision 57 days
2026-03-12same kind of change as the line aboveCVE-2025-14242same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.2 advanced update supportTime to revision 57 days
2026-03-12same kind of change as the line aboveCVE-2025-14242same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update supportTime to revision 57 days
2026-03-12published 2026-03-10Package added to advisoryGHSA-hhfx-wfvq-7g9cCVE-2026-26118highnot named as affected when the advisory was published, now names @azure/mcpTime to revision 2 days
2026-03-12published 2026-03-10Package added to advisoryGHSA-hhfx-wfvq-7g9cCVE-2026-26118highnot named as affected when the advisory was published, now names msmcp-azureTime to revision 2 days
2026-03-12published 2026-01-22Advisory severity changedGHSA-hx9q-6w63-j58vCVE-2025-67221whole advisoryhighstated at publication MODERATE, now states HIGHA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.Time to revision 49 days
2026-03-12published 2026-03-12Advisory severity changedGHSA-g5xx-pwrp-g3fvCVE-2026-31860whole advisorymoderatestated at publication HIGH, now states MODERATENo CVSS vector was stated in the first observed version.Time to revision 0 days

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 →