Every change, newest first
Showing changes seen on 2026-05-12. 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. |
|---|---|---|---|---|---|
| Tue 12 May 2026· 81 changes | |||||
| 2026-05-12 | Affected range extended | CVE-2025-65084 | ashlar-vellumargon icscert | stated at publication 12.6.1204.207, now states 12.6.1204.216Release branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | Affected range extended | CVE-2025-65084 | ashlar-vellumcobalt icscert | stated at publication 12.6.1204.207, now states 12.6.1204.216Release branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | Affected range extended | CVE-2025-65084 | ashlar-vellumcobalt share icscert | stated at publication 12.6.1204.207, now states 12.6.1204.216Release branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | Affected range extended | CVE-2025-65084 | ashlar-vellumlithium icscert | stated at publication 12.6.1204.207, now states 12.6.1204.216Release branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | Affected range extended | CVE-2025-65084 | ashlar-vellumxenon icscert | stated at publication 12.6.1204.207, now states 12.6.1204.216Release branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | Affected range extended | CVE-2025-65085 | ashlar-vellumargon icscert | stated at publication 12.6.1204.207, now states 12.6.1204.216Release branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | Affected range extended | CVE-2025-65085 | ashlar-vellumcobalt icscert | stated at publication 12.6.1204.207, now states 12.6.1204.216Release branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | Affected range extended | CVE-2025-65085 | ashlar-vellumcobalt share icscert | stated at publication 12.6.1204.207, now states 12.6.1204.216Release branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | Affected range extended | CVE-2025-65085 | ashlar-vellumlithium icscert | stated at publication 12.6.1204.207, now states 12.6.1204.216Release branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | Affected range extended | CVE-2025-65085 | ashlar-vellumxenon icscert | stated at publication 12.6.1204.207, now states 12.6.1204.216Release branch starts at 0. | Time to revision 168 days |
| 2026-05-12 | Affected range extended | CVE-2025-62631 | fortinetfortios | stated at publication 7.2.11, now states 7.2.13Release branch starts at 7.2.0. | Time to revision 154 days |
| 2026-05-12 | Product added | CVE-2026-25836 | not named as affected at publication, now names fortisandbox paas | Time to revision 63 days | |
| 2026-05-12 | Product added | CVE-2025-23384 | not named as affected at publication, now names scalance sc622-2c | Time to revision 427 days | |
| 2026-05-12 | Product added | CVE-2025-23384 | not named as affected at publication, now names scalance sc626-2c | Time to revision 427 days | |
| 2026-05-12 | Product added | CVE-2025-23384 | not named as affected at publication, now names scalance sc632-2c | Time to revision 427 days | |
| 2026-05-12 | Product added | CVE-2025-23384 | not named as affected at publication, now names scalance sc636-2c | Time to revision 427 days | |
| 2026-05-12 | Product added | CVE-2025-23384 | not named as affected at publication, now names scalance sc642-2c | Time to revision 427 days | |
| 2026-05-12 | Product added | CVE-2025-23384 | not named as affected at publication, now names scalance sc646-2c | Time to revision 427 days | |
| 2026-05-12 | Product added | CVE-2025-40943 | not named as affected at publication, now names simatic et 200sp open controller cpu 1515sp pc3 v4 cpus | Time to revision 63 days | |
| 2026-05-12 | Product added | CVE-2026-4424 | not named as affected at publication, now names red hat ai inference server 3.3 | Time to revision 54 days | |
| 2026-05-12 | Product added | CVE-2026-5121 | not named as affected at publication, now names red hat ai inference server 3.3 | Time to revision 43 days | |
| 2026-05-12 | Product added | CVE-2026-5201 | not named as affected at publication, now names red hat ai inference server 3.3 | Time to revision 42 days | |
| 2026-05-12 | Product added | CVE-2023-39454 | jpcert | not named as affected at publication, now names wmc-2lx-b | Time to revision 998 days |
| 2026-05-12 | Product added | CVE-2023-39454 | jpcert | not named as affected at publication, now names wmc-2lx2-b | Time to revision 998 days |
| 2026-05-12 | Product added | CVE-2023-39454 | jpcert | not named as affected at publication, now names wmc-x1800gst-b | Time to revision 998 days |
| 2026-05-12 | Product added | CVE-2023-39454 | jpcert | not named as affected at publication, now names wmc-x1800gst2-b | Time to revision 998 days |
| 2026-05-12 | Product added | CVE-2023-39454 | jpcert | not named as affected at publication, now names wrc-x3000gs3-b | Time to revision 998 days |
| 2026-05-12 | Product added | CVE-2023-39454 | jpcert | not named as affected at publication, now names wrc-x3000gs3a-b | Time to revision 998 days |
| 2026-05-12 | Product added | CVE-2023-39454 | jpcert | not named as affected at publication, now names wsc-x1800gs-b | Time to revision 998 days |
| 2026-05-12 | Product added | CVE-2023-39454 | jpcert | not named as affected at publication, now names wsc-x1800gs2-b | Time to revision 998 days |
| 2026-05-12 | Product added | CVE-2024-10771 | not named as affected at publication, now names tdc-x401gl | Time to revision 522 days | |
| 2026-05-12 | Product added | CVE-2024-22372 | jpcert | not named as affected at publication, now names wrc-x3000gst2-b | Time to revision 839 days |
| 2026-05-12 | Product added | CVE-2024-26258 | jpcert | not named as affected at publication, now names wmc-2lx-b | Time to revision 768 days |
| 2026-05-12 | Product added | CVE-2024-26258 | jpcert | not named as affected at publication, now names wmc-x1800gst-b | Time to revision 768 days |
| 2026-05-12 | Product added | CVE-2024-26258 | jpcert | not named as affected at publication, now names wsc-x1800gs-b | Time to revision 768 days |
| 2026-05-12 | Product added | CVE-2024-29225 | jpcert | not named as affected at publication, now names wmc-2lx-b | Time to revision 768 days |
| 2026-05-12 | Product added | CVE-2024-29225 | jpcert | not named as affected at publication, now names wmc-x1800gst-b | Time to revision 768 days |
| 2026-05-12 | Product added | CVE-2024-29225 | jpcert | not named as affected at publication, now names wsc-x1800gs-b | Time to revision 768 days |
| 2026-05-12 | Product added | CVE-2024-34021 | jpcert | not named as affected at publication, now names wmc-2lx-b | Time to revision 649 days |
| 2026-05-12 | Product added | CVE-2024-34021 | jpcert | not named as affected at publication, now names wmc-x1800gst-b | Time to revision 649 days |
| 2026-05-12 | Product added | CVE-2024-34021 | jpcert | not named as affected at publication, now names wrc-g01-w | Time to revision 649 days |
| 2026-05-12 | Product added | CVE-2024-34021 | jpcert | not named as affected at publication, now names wrc-x3200gst3-b | Time to revision 649 days |
| 2026-05-12 | Product added | CVE-2024-34577 | jpcert | not named as affected at publication, now names wrc-x3000gst2-b | Time to revision 620 days |
| 2026-05-12 | Product added | CVE-2024-39607 | jpcert | not named as affected at publication, now names wrc-x3000gst2-b | Time to revision 649 days |
| 2026-05-12 | Product added | CVE-2024-40883 | jpcert | not named as affected at publication, now names wrc-x3000gst2-b | Time to revision 649 days |
| 2026-05-12 | Product added | CVE-2025-32471 | not named as affected at publication, now names tdc-x401gl | Time to revision 379 days | |
| 2026-05-12 | Product added | CVE-2026-20704 | jpcert | not named as affected at publication, now names wrc-x1800gs-b | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-20704 | jpcert | not named as affected at publication, now names wrc-x1800gsa-b | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-20704 | jpcert | not named as affected at publication, now names wrc-x1800gsh-b | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-20704 | jpcert | not named as affected at publication, now names wrc-x3000gs2-b | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-20704 | jpcert | not named as affected at publication, now names wrc-x3000gs2-w | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-20704 | jpcert | not named as affected at publication, now names wrc-x3000gs2a-b | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-20704 | jpcert | not named as affected at publication, now names wrc-x3000gst2-b | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-20704 | jpcert | not named as affected at publication, now names wrc-x6000qs-g | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-20704 | jpcert | not named as affected at publication, now names wrc-x6000qsa-g | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-20704 | jpcert | not named as affected at publication, now names wrc-x6000xs-g | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-20704 | jpcert | not named as affected at publication, now names wrc-x6000xst-g | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-20704 | jpcert | not named as affected at publication, now names wrc-xe5400gs-g | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-20704 | jpcert | not named as affected at publication, now names wrc-xe5400gsa-g | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-22550 | jpcert | not named as affected at publication, now names wrc-x1800gs-b | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-22550 | jpcert | not named as affected at publication, now names wrc-x1800gsa-b | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-22550 | jpcert | not named as affected at publication, now names wrc-x1800gsh-b | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-22550 | jpcert | not named as affected at publication, now names wrc-x3000gs2-b | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-22550 | jpcert | not named as affected at publication, now names wrc-x3000gs2-w | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-22550 | jpcert | not named as affected at publication, now names wrc-x3000gs2a-b | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-22550 | jpcert | not named as affected at publication, now names wrc-x3000gst2-b | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-22550 | jpcert | not named as affected at publication, now names wrc-x6000qs-g | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-22550 | jpcert | not named as affected at publication, now names wrc-x6000qsa-g | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-22550 | jpcert | not named as affected at publication, now names wrc-x6000xs-g | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-22550 | jpcert | not named as affected at publication, now names wrc-x6000xst-g | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-22550 | jpcert | not named as affected at publication, now names wrc-xe5400gs-g | Time to revision 98 days |
| 2026-05-12 | Product added | CVE-2026-22550 | jpcert | not named as affected at publication, now names wrc-xe5400gsa-g | Time to revision 98 days |
| 2026-05-12 | CVSS base score changed | CVE-2026-29204 | whole record hackerone | stated at publication 10.0, now states 9.1CVSS v3.1 · base scoreCriticalCritical | Time to revision 0 days |
| 2026-05-12 | CVSS base score changed | CVE-2023-53878 | whole record VulnCheck | stated at publication 7.3, now states 6.9CVSS v4.0 · base scoreHighMedium | Time to revision 148 days |
| 2026-05-12 | CVSS base score changed | CVE-2023-53879 | whole record VulnCheck | stated at publication 5.3, now states 6.7CVSS v4.0 · base scoreMediumMedium | Time to revision 148 days |
| 2026-05-12 | CVSS base score changed | CVE-2023-53883 | whole record VulnCheck | stated at publication 7.2, now states 8.6CVSS v4.0 · base scoreHighHigh | Time to revision 148 days |
| 2026-05-12 | CVSS base score changed | CVE-2023-53885 | whole record VulnCheck | stated at publication 7.2, now states 8.6CVSS v4.0 · base scoreHighHigh | Time to revision 148 days |
| 2026-05-12 | CVSS base score changed | CVE-2023-53886 | whole record VulnCheck | stated at publication 5.7, now states 5.1CVSS v4.0 · base scoreMediumMedium | Time to revision 148 days |
| 2026-05-12 | CVSS base score changed | CVE-2023-53888 | whole record VulnCheck | stated at publication 7.2, now states 8.6CVSS v4.0 · base scoreHighHigh | Time to revision 148 days |
| 2026-05-12 | CVSS base score changed | CVE-2023-53889 | whole record VulnCheck | stated at publication 7.2, now states 8.6CVSS v4.0 · base scoreHighHigh | Time to revision 148 days |
| 2026-05-12 | Record state changed | CVE-2026-22920 | whole record SICK AG | stated at publication PUBLISHED, now states REJECTED | Time to revision 117 days |
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 →