Every change, newest first
Showing changes seen on 2026-01-08. 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. |
|---|---|---|---|---|---|
| Thu 8 Jan 2026· 48 changes | |||||
| 2026-01-08 | Product added | CVE-2025-7195 | not named as affected at publication, now names rhel-9-cnv-4.17 | Time to revision 154 days | |
| 2026-01-08 | Product added | CVE-2025-7195 | not named as affected at publication, now names rhel-9-cnv-4.20 | Time to revision 154 days | |
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dir-600 | Time to revision 3 days |
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dir-608 | Time to revision 3 days |
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dir-610 | Time to revision 3 days |
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dir-611 | Time to revision 3 days |
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dir-615 | Time to revision 3 days |
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dir-905l | Time to revision 3 days |
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dns-320 | Time to revision 3 days |
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dns-325 | Time to revision 3 days |
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dns-345 | Time to revision 3 days |
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dsl-2640t | Time to revision 3 days |
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dsl-500 | Time to revision 3 days |
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dsl-500g | Time to revision 3 days |
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dsl-502g | Time to revision 3 days |
| 2026-01-08 | Product added | CVE-2024-1573 | Mitsubishi | not named as affected at publication, now names iconics suite | Time to revision 553 days |
| 2026-01-08 | Product added | CVE-2024-1573 | Mitsubishi | not named as affected at publication, now names iconics suite | Time to revision 553 days |
| 2026-01-08 | Product added | CVE-2024-1574 | Mitsubishi | not named as affected at publication, now names bizviz | Time to revision 553 days |
| 2026-01-08 | Product added | CVE-2024-1574 | Mitsubishi | not named as affected at publication, now names genesis32 | Time to revision 553 days |
| 2026-01-08 | Product added | CVE-2024-1574 | Mitsubishi | not named as affected at publication, now names iconics suite | Time to revision 553 days |
| 2026-01-08 | Product added | CVE-2024-1574 | Mitsubishi | not named as affected at publication, now names bizviz | Time to revision 553 days |
| 2026-01-08 | Product added | CVE-2024-1574 | Mitsubishi | not named as affected at publication, now names genesis32 | Time to revision 553 days |
| 2026-01-08 | Product added | CVE-2024-1574 | Mitsubishi | not named as affected at publication, now names iconics suite | Time to revision 553 days |
| 2026-01-08 | Product added | CVE-2024-1182 | Mitsubishi | not named as affected at publication, now names genesis32 | Time to revision 553 days |
| 2026-01-08 | Product added | CVE-2024-1182 | Mitsubishi | not named as affected at publication, now names iconics suite | Time to revision 553 days |
| 2026-01-08 | Product added | CVE-2024-1182 | Mitsubishi | not named as affected at publication, now names genesis32 | Time to revision 553 days |
| 2026-01-08 | Product added | CVE-2024-1182 | Mitsubishi | not named as affected at publication, now names iconics suite | Time to revision 553 days |
| 2026-01-08 | Product added | CVE-2025-4953 | not named as affected at publication, now names red hat openshift container platform 4.15 | Time to revision 114 days | |
| 2026-01-08 | CVSS base score changed | CVE-2026-22245 | whole record GitHub_M | stated at publication 8.7, now states 7.1CVSS v4.0 · base scoreHighHigh | Time to revision 0 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-4056 | whole record redhat | stated at publication 3.7, now states 7.5CVSS v3.1 · base scoreLowHigh | Time to revision 164 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-5915 | whole record redhat | stated at publication 3.9, now states 6.6CVSS v3.1 · base scoreLowMedium | Time to revision 212 days |
| 2026-01-08 | CVSS base score changed | CVE-2024-7259 | whole record redhat | stated at publication 4.4, now states 4.9CVSS v3.1 · base scoreMediumMedium | Time to revision 469 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-0620 | whole record redhat | stated at publication 6.6, now states 4.9CVSS v3.1 · base scoreMediumMedium | Time to revision 216 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-0689 | whole record redhat | stated at publication 6.4, now states 7.8CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2025-08-12; this value first seen 2026-01-08. | Time to revision 162 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-1125 | whole record redhat | stated at publication 6.4, now states 7.8CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2025-08-12; this value first seen 2026-01-08. | Time to revision 162 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-31177 | whole record redhat | stated at publication 6.2, now states 5.5CVSS v3.1 · base scoreMediumMedium | Time to revision 245 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-47711 | whole record redhat | stated at publication 4.3, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 213 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-47712 | whole record redhat | stated at publication 4.3, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 213 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-5351 | whole record redhat | stated at publication 4.2, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 188 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-5449 | whole record redhat | stated at publication 4.3, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 166 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-5731 | whole record redhat | stated at publication 6.2, now states 5.5CVSS v3.1 · base scoreMediumMedium | Time to revision 195 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-5987 | whole record redhat | stated at publication 5.0, now states 8.1CVSS v3.1 · base scoreMediumHigh | Time to revision 185 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-6035 | whole record redhat | stated at publication 6.6, now states 6.1CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2025-12-01; this value first seen 2026-01-08. | Time to revision 171 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-7365 | whole record redhat | stated at publication 5.4, now states 7.1CVSS v3.1 · base scoreMediumHigh | Time to revision 182 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-8419 | whole record redhat | stated at publication 6.5, now states 5.3CVSS v3.1 · base scoreMediumMedium | Time to revision 154 days |
| 2026-01-08 | CVSS base score changed | CVE-2025-14874 | whole record redhat | stated at publication 5.3, now states 7.5CVSS v3.1 · base scoreMediumHigh | Time to revision 21 days |
| 2026-01-08 | Record state changed | CVE-2025-9173 | whole record VulDB | stated at publication PUBLISHED, now states REJECTED | Time to revision 141 days |
| 2026-01-08published 2026-01-07 | Advisory severity changed | GHSA-5f29-2333-h9c7CVE-2026-22244 | whole advisoryhigh | stated at publication CRITICAL, now states HIGHA CVSS version was added; the existing vectors stayed the same. | Time to revision 1 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.
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 →