Skip to content

Every change, newest first

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

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

SinceClear all

Showing changes seen on 2025-12-22. Every day

Counted changes changed on 2025-12-22, 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.
Mon 22 Dec 2025· 26 changes
2025-12-22Added to CISA KEVCVE-2023-52163
DigieverDS-2105 Pro
CISA KEV
fix due 2026-01-12Duration unknown
2025-12-22Product addedCVE-2025-14104redhatnot named as affected at publication, now names util-linuxTime to revision 17 days
2025-12-22Product addedCVE-2025-14946not named as affected at publication, now names libnbdTime to revision 3 days
2025-12-222 commitsProduct addedredhatnot named as affected at publication, now names nodemailerBranches and original-value intervals are stated on each row.Time to revision 5 to 38 days
2025-12-22same kind of change as the line aboveCVE-2025-14874same vendor as the line abovesame change as the line aboveTime to revision 5 days
2025-12-22same kind of change as the line aboveCVE-2025-13033same vendor as the line abovesame change as the line aboveTime to revision 38 days
2025-12-22Product addedCVE-2025-14010redhatnot named as affected at publication, now names ansible community general collectionTime to revision 19 days
2025-12-22Product addedredhatnot named as affected at publication, now names glibTime to revision 12 to 13 days
2025-12-22same kind of change as the line aboveCVE-2025-14087same vendor as the line abovesame change as the line aboveTime to revision 13 days
2025-12-22same kind of change as the line aboveCVE-2025-14512same vendor as the line abovesame change as the line aboveTime to revision 12 days
2025-12-222 commitsProduct addedredhatnot named as affected at publication, now names webkitgtkBranches and original-value intervals are stated on each row.Time to revision 18 to 28 days
2025-12-22same kind of change as the line aboveCVE-2025-13947same vendor as the line abovesame change as the line aboveTime to revision 20 days
2025-12-22same kind of change as the line aboveCVE-2025-66287same vendor as the line abovesame change as the line aboveTime to revision 18 days
2025-12-22same kind of change as the line aboveCVE-2025-13502same vendor as the line abovesame change as the line aboveTime to revision 28 days
2025-12-22Product addedCVE-2025-13609redhatnot named as affected at publication, now names keylimeTime to revision 28 days
2025-12-22Product addedCVE-2025-11568redhatnot named as affected at publication, now names luksmetaTime to revision 68 days
2025-12-22Product addedCVE-2025-12790redhatnot named as affected at publication, now names ruby-mqttTime to revision 46 days
2025-12-22Product addedredhatnot named as affected at publication, now names xwaylandTime to revision 54 days
2025-12-22same kind of change as the line aboveCVE-2025-62229same vendor as the line abovesame change as the line aboveTime to revision 54 days
2025-12-22same kind of change as the line aboveCVE-2025-62230same vendor as the line abovesame change as the line aboveTime to revision 54 days
2025-12-22same kind of change as the line aboveCVE-2025-62231same vendor as the line abovesame change as the line aboveTime to revision 54 days
2025-12-222 commitsProduct addednot named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update supportBranches and original-value intervals are stated on each row.Time to revision 18 to 342 days
2025-12-22same kind of change as the line aboveCVE-2024-12087same vendor as the line abovesame change as the line aboveTime to revision 342 days
2025-12-22same kind of change as the line aboveCVE-2025-13502same vendor as the line abovesame change as the line aboveTime to revision 27 days
2025-12-22same kind of change as the line aboveCVE-2025-13947same vendor as the line abovesame change as the line aboveTime to revision 19 days
2025-12-22same kind of change as the line aboveCVE-2025-66287same vendor as the line abovesame change as the line aboveTime to revision 18 days
2025-12-222 commitsProduct addedCVE-2024-12087not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support and 1 moreBranches and original-value intervals are stated on each row.Time to revision 342 days
2025-12-22same kind of change as the line aboveCVE-2024-12087same 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 342 days
2025-12-22same kind of change as the line aboveCVE-2024-12087same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.2 advanced update supportTime to revision 342 days
2025-12-22published 2025-06-23Advisory fix version movedGHSA-9623-mj7j-p9v4CVE-2025-49574
mavenio.quarkus:quarkus-vertx
moderate
stated at publication 3.24.0, now states 3.24.1Time to revision 182 days
2025-12-22published 2022-01-06Package added to advisoryGHSA-x8rq-rc7x-5fg5CVE-2022-0086highnot named as affected when the advisory was published, now names @uppy/companionDuration unknown
2025-12-22published 2025-12-15Advisory withdrawnGHSA-vr6p-vq2p-6j74whole advisorycriticalwithdrawn 2025-12-22Time to revision 7 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 →