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.

42 changes behind one line · newest firstCSVJSONRSS

SinceClear all
ChangedSourceRows

One change, in full: CVSS base score changed: 7.1 → 8.2. The same change in 42 CVE records. Back to the ledger

Counted changes published by INCIBE, 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.
2024-02-15CVSS base score changedCVE-2024-23868
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23869
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23870
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23871
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23872
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23873
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23874
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23875
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23876
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23877
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23878
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23879
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23880
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23881
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23882
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23883
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23884
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23885
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23886
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23887
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23888
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23889
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23890
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23891
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23892
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23893
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23894
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23895
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 13
2024-02-15CVSS base score changedCVE-2024-23896
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23855
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 21
2024-02-15CVSS base score changedCVE-2024-23856
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23857
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23858
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23859
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23860
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23861
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23862
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23863
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23864
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23865
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23866
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20
2024-02-15CVSS base score changedCVE-2024-23867
whole record
INCIBE
stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHighDays to revision 20

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.

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 →