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.

47 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

Showing changes seen on 2026-01-08. Every day

Counted changes changed on 2026-01-08, 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 8 Jan 2026· 47 record changes
2026-01-08Product addedCVE-2025-7195not named as affected at publication, now names rhel-9-cnv-4.17 and 1 moreDays to revision 154
2026-01-08same kind of change as the line aboveCVE-2025-7195same vendor as the line abovenot named as affected at publication, now names rhel-9-cnv-4.17Days to revision 154
2026-01-08same kind of change as the line aboveCVE-2025-7195same vendor as the line abovenot named as affected at publication, now names rhel-9-cnv-4.20Days to revision 154
2026-01-08Product addedCVE-2026-0625VulnChecknot named as affected at publication, now names dir-600 and 12 moreDays to revision 3
2026-01-08same kind of change as the line aboveCVE-2026-0625same vendor as the line abovenot named as affected at publication, now names dir-600Days to revision 3
2026-01-08same kind of change as the line aboveCVE-2026-0625same vendor as the line abovenot named as affected at publication, now names dir-608Days to revision 3
2026-01-08same kind of change as the line aboveCVE-2026-0625same vendor as the line abovenot named as affected at publication, now names dir-610Days to revision 3
2026-01-08same kind of change as the line aboveCVE-2026-0625same vendor as the line abovenot named as affected at publication, now names dir-611Days to revision 3
2026-01-08same kind of change as the line aboveCVE-2026-0625same vendor as the line abovenot named as affected at publication, now names dir-615Days to revision 3
2026-01-08same kind of change as the line aboveCVE-2026-0625same vendor as the line abovenot named as affected at publication, now names dir-905lDays to revision 3
2026-01-08same kind of change as the line aboveCVE-2026-0625same vendor as the line abovenot named as affected at publication, now names dns-320Days to revision 3
2026-01-08same kind of change as the line aboveCVE-2026-0625same vendor as the line abovenot named as affected at publication, now names dns-325Days to revision 3
5 more rows in this change are not listed here. Open all 13 rows
2026-01-082 commitsProduct addedMitsubishinot named as affected at publication, now names iconics suiteBranches and original-value intervals are stated on each row.Days to revision 553
2026-01-08same kind of change as the line aboveCVE-2024-1573same vendor as the line abovesame change as the line aboveDays to revision 553
2026-01-08same kind of change as the line aboveCVE-2024-1574same vendor as the line abovesame change as the line aboveDays to revision 553
2026-01-08same kind of change as the line aboveCVE-2024-1182same vendor as the line abovesame change as the line aboveDays to revision 553
2026-01-082 commitsProduct addedMitsubishinot named as affected at publication, now names iconics suiteBranches and original-value intervals are stated on each row.Days to revision 553
2026-01-08same kind of change as the line aboveCVE-2024-1573same vendor as the line abovesame change as the line aboveDays to revision 553
2026-01-08same kind of change as the line aboveCVE-2024-1574same vendor as the line abovesame change as the line aboveDays to revision 553
2026-01-08same kind of change as the line aboveCVE-2024-1182same vendor as the line abovesame change as the line aboveDays to revision 553
2026-01-08Product addedCVE-2024-1574Mitsubishinot named as affected at publication, now names bizvizDays to revision 553
2026-01-082 commitsProduct addedMitsubishinot named as affected at publication, now names genesis32Branches and original-value intervals are stated on each row.Days to revision 553
2026-01-08same kind of change as the line aboveCVE-2024-1574same vendor as the line abovesame change as the line aboveDays to revision 553
2026-01-08same kind of change as the line aboveCVE-2024-1182same vendor as the line abovesame change as the line aboveDays to revision 553
2026-01-08Product addedCVE-2024-1574Mitsubishinot named as affected at publication, now names bizvizDays to revision 553
2026-01-082 commitsProduct addedMitsubishinot named as affected at publication, now names genesis32Branches and original-value intervals are stated on each row.Days to revision 553
2026-01-08same kind of change as the line aboveCVE-2024-1574same vendor as the line abovesame change as the line aboveDays to revision 553
2026-01-08same kind of change as the line aboveCVE-2024-1182same vendor as the line abovesame change as the line aboveDays to revision 553
2026-01-08Product addedCVE-2025-4953not named as affected at publication, now names red hat openshift container platform 4.15Days to revision 114
2026-01-08CVSS base score changedCVE-2026-22245
whole record
GitHub_M
stated at publication 8.7, now states 7.1CVSS v4.0 · base scoreHighHighDays to revision 0
2026-01-08CVSS base score changedCVE-2025-4056
whole record
redhat
stated at publication 3.7, now states 7.5CVSS v3.1 · base scoreLowHighDays to revision 164
2026-01-08CVSS base score changedCVE-2025-5915
whole record
redhat
stated at publication 3.9, now states 6.6CVSS v3.1 · base scoreLowMediumDays to revision 212
2026-01-08CVSS base score changedCVE-2024-7259
whole record
redhat
stated at publication 4.4, now states 4.9CVSS v3.1 · base scoreMediumMediumDays to revision 469
2026-01-08CVSS base score changedCVE-2025-0620
whole record
redhat
stated at publication 6.6, now states 4.9CVSS v3.1 · base scoreMediumMediumDays to revision 216
2026-01-08CVSS base score changed
whole record
redhat
stated at publication 6.4, now states 7.8CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2025-08-12; this value first seen 2026-01-08.Days to revision 162
2026-01-08same kind of change as the line aboveCVE-2025-0689same vendor as the line abovesame change as the line aboveOriginal value first replaced 2025-08-12; this value first seen 2026-01-08.Days to revision 162
2026-01-08same kind of change as the line aboveCVE-2025-1125same vendor as the line abovesame change as the line aboveOriginal value first replaced 2025-08-12; this value first seen 2026-01-08.Days to revision 162
2026-01-08CVSS base score changed
whole record
redhat
stated at publication 6.2, now states 5.5CVSS v3.1 · base scoreMediumMediumDays to revision 195 to 245
2026-01-08same kind of change as the line aboveCVE-2025-31177same vendor as the line abovesame change as the line aboveDays to revision 245
2026-01-08same kind of change as the line aboveCVE-2025-5731same vendor as the line abovesame change as the line aboveDays to revision 195
2026-01-08CVSS base score changed
whole record
redhat
stated at publication 4.3, now states 6.5CVSS v3.1 · base scoreMediumMediumDays to revision 166 to 213
2026-01-08same kind of change as the line aboveCVE-2025-47711same vendor as the line abovesame change as the line aboveDays to revision 213
2026-01-08same kind of change as the line aboveCVE-2025-47712same vendor as the line abovesame change as the line aboveDays to revision 213
2026-01-08same kind of change as the line aboveCVE-2025-5449same vendor as the line abovesame change as the line aboveDays to revision 166
2026-01-08CVSS base score changedCVE-2025-5351
whole record
redhat
stated at publication 4.2, now states 6.5CVSS v3.1 · base scoreMediumMediumDays to revision 188
2026-01-08CVSS base score changedCVE-2025-5987
whole record
redhat
stated at publication 5.0, now states 8.1CVSS v3.1 · base scoreMediumHighDays to revision 185
2026-01-08CVSS base score changedCVE-2025-6035
whole record
redhat
stated at publication 6.6, now states 6.1CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2025-12-01; this value first seen 2026-01-08.Days to revision 171
2026-01-08CVSS base score changedCVE-2025-7365
whole record
redhat
stated at publication 5.4, now states 7.1CVSS v3.1 · base scoreMediumHighDays to revision 182
2026-01-08CVSS base score changedCVE-2025-8419
whole record
redhat
stated at publication 6.5, now states 5.3CVSS v3.1 · base scoreMediumMediumDays to revision 154
2026-01-08CVSS base score changedCVE-2025-14874
whole record
redhat
stated at publication 5.3, now states 7.5CVSS v3.1 · base scoreMediumHighDays to revision 21
2026-01-08Record state changedCVE-2025-9173
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDDays to revision 141

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. 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.
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 →