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.

28 record changes · 1 advisory changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

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

Counted changes changed on 2025-12-19, 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.
Fri 19 Dec 2025· 29 changes
2025-12-19Added to CISA KEVCVE-2025-14733
WatchGuardFirebox
CISA KEV
fix due 2025-12-26Duration unknown
2025-12-19Ransomware use confirmedCVE-2024-53704
SonicWallSonicOS
CISA KEV
stated at publication Unknown, now states KnownDuration unknown
2025-12-19Fix version movedCVE-2025-34441VulnCheckstated at publication 20.0, now states 20.1Release branch starts at 0.Time to revision 2 days
2025-12-19Fix version movedCVE-2025-34442VulnCheckstated at publication 20.0, now states 20.1Release branch starts at 0.Time to revision 2 days
2025-12-19Fix version movedCVE-2025-34440VulnCheckstated at publication 20.0, now states 20.1Release branch starts at 0.Time to revision 2 days
2025-12-19Fix version movedCVE-2025-34439VulnCheckstated at publication 20.0, now states 20.1Release branch starts at 0.Time to revision 2 days
2025-12-19Fix version movedCVE-2025-34434VulnCheckstated at publication 20.0, now states 20.1Release branch starts at 0.Time to revision 2 days
2025-12-19Fix version movedCVE-2025-34436VulnCheckstated at publication 20.0, now states 20.1Release branch starts at 0.Time to revision 2 days
2025-12-19Fix version movedCVE-2025-34435VulnCheckstated at publication 20.0, now states 20.1Release branch starts at 0.Time to revision 2 days
2025-12-19Fix version movedCVE-2025-34437VulnCheckstated at publication 20.0, now states 20.1Release branch starts at 0.Time to revision 2 days
2025-12-19Fix version movedCVE-2025-34438VulnCheckstated at publication 20.0, now states 20.1Release branch starts at 0.Time to revision 2 days
2025-12-19Fix version movedCVE-2025-14318
m-files corporationm-files server
stated at publication 25.12, now states 25.12.15491.7Release branch starts at 0.same dayTime to revision 1 days
2025-12-19Affected range extendedCVE-2023-44247
fortinetfortios
stated at publication 6.4.15, now states 6.4.16Release branch starts at 6.4.0.Time to revision 584 days
2025-12-19Product addedCVE-2025-12105redhatnot named as affected at publication, now names libsoupTime to revision 58 days
2025-12-19Product addedCVE-2025-5372redhatnot named as affected at publication, now names libsshTime to revision 169 days
2025-12-19Product addedCVE-2025-5731not named as affected at publication, now names infinispanTime to revision 176 days
2025-12-19Product addedCVE-2025-54770redhatnot named as affected at publication, now names grub2Time to revision 31 days
2025-12-19Product addedCVE-2025-54771redhatnot named as affected at publication, now names grub2Time to revision 31 days
2025-12-19Product addedCVE-2025-61661redhatnot named as affected at publication, now names grub2Time to revision 31 days
2025-12-19Product addedCVE-2025-61662redhatnot named as affected at publication, now names grub2Time to revision 31 days
2025-12-19Product addedCVE-2025-61663redhatnot named as affected at publication, now names grub2Time to revision 31 days
2025-12-19Product addedCVE-2025-61664redhatnot named as affected at publication, now names grub2Time to revision 31 days
2025-12-19Product addedCVE-2025-59089redhatnot named as affected at publication, now names kdcproxyTime to revision 37 days
2025-12-19Product addedCVE-2025-59088redhatnot named as affected at publication, now names kdcproxyTime to revision 37 days
2025-12-19CVSS base score changedCVE-2025-11921
whole record
Fluid Attacks
stated at publication 9.3, now states 8.5CVSS v4.0 · base scoreCriticalHighTime to revision 25 days
2025-12-19CVSS base score changedCVE-2025-13733
whole record
Fluid Attacks
stated at publication 8.4, now states 8.5CVSS v4.0 · base scoreHighHighTime to revision 7 days
2025-12-19CVSS base score changedCVE-2025-68388
whole record
elastic
stated at publication 7.5, now states 5.3CVSS v3.1 · base scoreHighMediumTime to revision 1 days
2025-12-19Record state changedCVE-2025-34294
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 52 days
2025-12-19published 2025-11-25Advisory withdrawnGHSA-93vm-mqpw-8wh3whole advisorymoderatewithdrawn 2025-12-19Time to revision 24 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.

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 →