Every change, newest first
Showing changes seen on 2025-12-19. Every day
| 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. | Kind | Record, 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 changed | Days 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· 26 record changes | |||||
| 2025-12-19 | Fix version moved | CVE-2025-34441 | VulnCheck | stated at publication 20.0, now states 20.1Release branch starts at 0. | Days to revision 2 |
| 2025-12-19 | Fix version moved | CVE-2025-34442 | VulnCheck | stated at publication 20.0, now states 20.1Release branch starts at 0. | Days to revision 2 |
| 2025-12-19 | Fix version moved | CVE-2025-34440 | VulnCheck | stated at publication 20.0, now states 20.1Release branch starts at 0. | Days to revision 2 |
| 2025-12-19 | Fix version moved | CVE-2025-34439 | VulnCheck | stated at publication 20.0, now states 20.1Release branch starts at 0. | Days to revision 2 |
| 2025-12-19 | Fix version moved | CVE-2025-34434 | VulnCheck | stated at publication 20.0, now states 20.1Release branch starts at 0. | Days to revision 2 |
| 2025-12-19 | Fix version moved | CVE-2025-34436 | VulnCheck | stated at publication 20.0, now states 20.1Release branch starts at 0. | Days to revision 2 |
| 2025-12-19 | Fix version moved | CVE-2025-34435 | VulnCheck | stated at publication 20.0, now states 20.1Release branch starts at 0. | Days to revision 2 |
| 2025-12-19 | Fix version moved | CVE-2025-34437 | VulnCheck | stated at publication 20.0, now states 20.1Release branch starts at 0. | Days to revision 2 |
| 2025-12-19 | Fix version moved | CVE-2025-34438 | VulnCheck | stated at publication 20.0, now states 20.1Release branch starts at 0. | Days to revision 2 |
| 2025-12-19 | Fix version moved | CVE-2025-14318 | m-files corporationm-files server | stated at publication 25.12, now states 25.12.15491.7Release branch starts at 0.same day | Days to revision 1 |
| 2025-12-19 | Affected range extended | CVE-2023-44247 | fortinetfortios | stated at publication 6.4.15, now states 6.4.16Release branch starts at 6.4.0. | Days to revision 584 |
| 2025-12-19 | Product added | CVE-2025-12105 | redhat | not named as affected at publication, now names libsoup | Days to revision 58 |
| 2025-12-19 | Product added | CVE-2025-5372 | redhat | not named as affected at publication, now names libssh | Days to revision 169 |
| 2025-12-19 | Product added | CVE-2025-5731 | not named as affected at publication, now names infinispan | Days to revision 176 | |
| 2025-12-19 | Product added | CVE-2025-54770 | redhat | not named as affected at publication, now names grub2 | Days to revision 31 |
| 2025-12-19 | Product added | CVE-2025-54771 | redhat | not named as affected at publication, now names grub2 | Days to revision 31 |
| 2025-12-19 | Product added | CVE-2025-61661 | redhat | not named as affected at publication, now names grub2 | Days to revision 31 |
| 2025-12-19 | Product added | CVE-2025-61662 | redhat | not named as affected at publication, now names grub2 | Days to revision 31 |
| 2025-12-19 | Product added | CVE-2025-61663 | redhat | not named as affected at publication, now names grub2 | Days to revision 31 |
| 2025-12-19 | Product added | CVE-2025-61664 | redhat | not named as affected at publication, now names grub2 | Days to revision 31 |
| 2025-12-19 | Product added | CVE-2025-59089 | redhat | not named as affected at publication, now names kdcproxy | Days to revision 37 |
| 2025-12-19 | Product added | CVE-2025-59088 | redhat | not named as affected at publication, now names kdcproxy | Days to revision 37 |
| 2025-12-19 | CVSS base score changed | CVE-2025-11921 | whole record Fluid Attacks | stated at publication 9.3, now states 8.5CVSS v4.0 · base scoreCriticalHigh | Days to revision 25 |
| 2025-12-19 | CVSS base score changed | CVE-2025-13733 | whole record Fluid Attacks | stated at publication 8.4, now states 8.5CVSS v4.0 · base scoreHighHigh | Days to revision 7 |
| 2025-12-19 | CVSS base score changed | CVE-2025-68388 | whole record elastic | stated at publication 7.5, now states 5.3CVSS v3.1 · base scoreHighMedium | Days to revision 1 |
| 2025-12-19 | Record state changed | CVE-2025-34294 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Days to revision 52 |
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 →