Every change, newest first
Showing changes seen on 2025-12-02. 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 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 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. |
|---|---|---|---|---|---|
| Tue 2 Dec 2025· 20 changes | |||||
| 2025-12-02 | Added to CISA KEV | AndroidFramework | fix due 2025-12-23 | Duration unknown | |
| 2025-12-02 | same kind of change as the line above | CVE-2025-48633 | same vendor as the line above | same change as the line above | Duration unknown |
| 2025-12-02 | same kind of change as the line above | CVE-2025-48572 | same vendor as the line above | same change as the line above | Duration unknown |
| 2025-12-02 | Fix version moved | CVE-2025-11578 | githubenterprise server GitHub_P | stated at publication 3.14.19, now states 3.14.20Release branch starts at 3.14. | Time to revision 22 days |
| 2025-12-02 | Fix version moved | CVE-2025-11578 | githubenterprise server GitHub_P | stated at publication 3.15.14, now states 3.15.15Release branch starts at 3.15. | Time to revision 22 days |
| 2025-12-02 | Fix version moved | CVE-2025-11578 | githubenterprise server GitHub_P | stated at publication 3.16.10, now states 3.16.11Release branch starts at 3.16. | Time to revision 22 days |
| 2025-12-02 | Fix version moved | CVE-2025-11578 | githubenterprise server GitHub_P | stated at publication 3.17.7, now states 3.17.8Release branch starts at 3.17. | Time to revision 22 days |
| 2025-12-02 | Fix version moved | CVE-2025-11578 | githubenterprise server GitHub_P | stated at publication 3.18.1, now states 3.18.2Release branch starts at 3.18. | Time to revision 22 days |
| 2025-12-02 | CVSS base score changed | CVE-2025-66399 | whole record GitHub_M | stated at publication 8.9, now states 7.4CVSS v4.0 · base scoreHighHigh | Time to revision 0 days |
| 2025-12-02 | CVSS base score changed | CVE-2025-13129 | whole record TR-CERT | stated at publication 3.5, now states 4.3CVSS v3.1 · base scoreLowMedium | Time to revision 1 days |
| 2025-12-02 | Record state changed | CVE-2025-34351 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 6 days |
| 2025-12-02 | Record state changed | CVE-2024-51999 | whole record GitHub_M | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| 2025-12-02 | Record state changed | whole record JetBrains | stated at publication PUBLISHED, now states REJECTED | Time to revision 22 days | |
| 2025-12-02 | same kind of change as the line above | CVE-2025-64686 | same vendor as the line above | same change as the line above | Time to revision 22 days |
| 2025-12-02 | same kind of change as the line above | CVE-2025-64687 | same vendor as the line above | same change as the line above | Time to revision 22 days |
| 2025-12-02 | same kind of change as the line above | CVE-2025-64688 | same vendor as the line above | same change as the line above | Time to revision 22 days |
| 2025-12-02 | same kind of change as the line above | CVE-2025-64689 | same vendor as the line above | same change as the line above | Time to revision 22 days |
| 2025-12-02 | same kind of change as the line above | CVE-2025-64690 | same vendor as the line above | same change as the line above | Time to revision 22 days |
| 2025-12-02published 2025-10-28 to 2025-12-01 | Advisory withdrawn | whole advisory3 bands | withdrawn 2025-12-02 | Time to revision 1 to 35 days | |
| 2025-12-02published 2025-12-01 | same kind of change as the line above | GHSA-pj86-cfqh-vqx6CVE-2024-51999 | same package and registry as the line abovelow | withdrawn 2025-12-02 | Time to revision 1 days |
| 2025-12-02published 2025-10-28 | same kind of change as the line above | GHSA-c6cm-5gc7-c3f4 | same package and registry as the line abovelow | withdrawn 2025-12-02 | Time to revision 35 days |
| 2025-12-02published 2025-10-30 | same kind of change as the line above | GHSA-28jp-44vh-q42h | same package and registry as the line abovehigh | withdrawn 2025-12-02 | Time to revision 32 days |
| 2025-12-02published 2025-11-13 | same kind of change as the line above | GHSA-7m9g-pmxf-m9m8 | same package and registry as the line abovemoderate | withdrawn 2025-12-02 | Time to revision 18 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.
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 →