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.

9 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

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

Counted changes changed on 2026-03-06, 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.
Fri 6 Mar 2026· 9 record changes
2026-03-06Product addedCVE-2025-15033WPScannot named as affected at publication, now names woocommerceDays to revision 74
2026-03-06CVSS base score changedCVE-2025-57852
whole record
redhat
stated at publication 5.2, now states 6.4CVSS v3.1 · base scoreMediumMediumDays to revision 157
2026-03-06CVSS base score changedCVE-2025-58712
whole record
redhat
stated at publication 5.2, now states 6.4CVSS v3.1 · base scoreMediumMediumDays to revision 135
2026-03-06CVSS base score changedCVE-2025-57848
whole record
redhat
stated at publication 5.2, now states 6.4CVSS v3.1 · base scoreMediumMediumDays to revision 134
2026-03-06CVSS base score changedCVE-2025-57850
whole record
redhat
stated at publication 5.2, now states 6.4CVSS v3.1 · base scoreMediumMediumDays to revision 94
2026-03-06CVSS base score changedCVE-2025-7195
whole record
redhat
stated at publication 5.2, now states 6.4CVSS v3.1 · base scoreMediumMediumDays to revision 211
2026-03-06CVSS base score changedCVE-2025-12107
whole record
WSO2
stated at publication 10.0, now states 8.4CVSS v3.1 · base scoreCriticalHighDays to revision 15
2026-03-06CVSS base score changedCVE-2026-22687
whole record
GitHub_M
stated at publication 8.1, now states 5.6CVSS v3.1 · base scoreHighMediumDays to revision 56
2026-03-06Record state changedCVE-2026-28484
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDDays to revision 1

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.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 03:47 UTC · scroll for earlierfewermore

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 →

Check my CVEs against these changes →