Every change, newest first
Showing changes seen on 2025-10-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, 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. |
|---|---|---|---|---|---|
| Thu 2 Oct 2025· 23 changes | |||||
| 2025-10-02 | Added to CISA KEV | CVE-2014-6278 | GNUGNU Bash CISA KEV | fix due 2025-10-23 | Duration unknown |
| 2025-10-02 | Added to CISA KEV | CVE-2017-1000353 | JenkinsJenkins CISA KEV | fix due 2025-10-23 | Duration unknown |
| 2025-10-02 | Added to CISA KEV | CVE-2015-7755 | JuniperScreenOS CISA KEV | fix due 2025-10-23 | Duration unknown |
| 2025-10-02 | Added to CISA KEV | CVE-2025-21043 | SamsungMobile Devices CISA KEV | fix due 2025-10-23 | Duration unknown |
| 2025-10-02 | Added to CISA KEV | CVE-2025-4008 | SmartbeddedMeteobridge CISA KEV | fix due 2025-10-23 | Duration unknown |
| 2025-10-02 | Fix version moved | CVE-2025-38709 | linuxlinux | stated at publication 6.6.103, now states 6.6.109Release branch starts at 6.6.*.Original value first replaced 2025-09-25; this value first seen 2025-10-02. | Time to revision 21 days |
| 2025-10-02 | Fix version moved | CVE-2023-53431 | linuxlinux | stated at publication 4.19.276, now states 4.19.281Release branch starts at 4.19.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | Fix version moved | CVE-2023-53431 | linuxlinux | stated at publication 5.10.173, now states 5.10.178Release branch starts at 5.10.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | Fix version moved | CVE-2023-53431 | linuxlinux | stated at publication 5.15.99, now states 5.15.108Release branch starts at 5.15.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | Fix version moved | CVE-2023-53431 | linuxlinux | stated at publication 5.4.235, now states 5.4.241Release branch starts at 5.4.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | Fix version moved | CVE-2023-53431 | linuxlinux | stated at publication 6.1.16, now states 6.1.25Release branch starts at 6.1.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | Fix version moved | CVE-2023-53431 | linuxlinux | stated at publication 6.2.3, now states 6.2.12Release branch starts at 6.2.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | Product added | 4 rows, one per record and product | not named as affected at publication, now names red hat openshift ai 2.16 and 1 more | Time to revision 2 days | |
| 2025-10-02 | same kind of change as the line above | CVE-2025-10725 | same vendor as the line above | not named as affected at publication, now names red hat openshift ai 2.16 | Time to revision 2 days |
| 2025-10-02 | same kind of change as the line above | CVE-2025-10725 | same vendor as the line above | not named as affected at publication, now names red hat openshift ai 2.22 | Time to revision 2 days |
| 2025-10-02 | same kind of change as the line above | CVE-2025-57852 | same vendor as the line above | not named as affected at publication, now names red hat openshift ai 2.16 | Time to revision 2 days |
| 2025-10-02 | same kind of change as the line above | CVE-2025-57852 | same vendor as the line above | not named as affected at publication, now names red hat openshift ai 2.22 | Time to revision 2 days |
| 2025-10-02 | CVSS base score changed | CVE-2025-54261 | whole record adobe | stated at publication 9.0, now states 10.0CVSS v3.1 · base scoreCriticalCritical | Time to revision 23 days |
| 2025-10-02 | CVSS base score changed | whole record INCIBE | stated at publication 6.9, now states 5.1CVSS v4.0 · base scoreMediumMedium | Time to revision 0 days | |
| 2025-10-02 | same kind of change as the line above | CVE-2025-59750 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-10-02 | same kind of change as the line above | CVE-2025-59751 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-10-02 | same kind of change as the line above | CVE-2025-59752 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-10-02 | same kind of change as the line above | CVE-2025-59753 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-10-02 | same kind of change as the line above | CVE-2025-59754 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-10-02 | same kind of change as the line above | CVE-2025-59756 | same vendor as the line above | same change as the line above | Time to revision 0 days |
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 →