Every change, newest first
These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.
| 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 14 Jul 2026· 54 changes | |||||
| 2026-07-14 | Fix version moved | 54 rows, one per record and product | siemens18 products | stated at publication V2.9.9, now states V4.1.6Release branch starts at *.not counted: Another branch advanced | Duration unknown |
| 2026-07-14 | same kind of change as the line above | CVE-2026-25786 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so V2.9.9 still holds | Duration unknown |
| 2026-07-14 | same kind of change as the line above | CVE-2026-25786 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so V2.9.9 still holds | Duration unknown |
| 2026-07-14 | same kind of change as the line above | CVE-2026-25786 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so V2.9.9 still holds | Duration unknown |
| 2026-07-14 | same kind of change as the line above | CVE-2026-25786 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so V2.9.9 still holds | Duration unknown |
| 2026-07-14 | same kind of change as the line above | CVE-2026-25786 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so V2.9.9 still holds | Duration unknown |
| 2026-07-14 | same kind of change as the line above | CVE-2026-25786 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so V2.9.9 still holds | Duration unknown |
| 2026-07-14 | same kind of change as the line above | CVE-2026-25786 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so V2.9.9 still holds | Duration unknown |
| 2026-07-14 | same kind of change as the line above | CVE-2026-25786 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so V2.9.9 still holds | Duration unknown |
| 46 more rows in this change are not listed here. Open all 54 rows → | |||||
| Fri 29 May 2026· 6 changes | |||||
| 2026-05-29 | Product added | CVE-2025-40946 | not named as affected at publication, now names blueplanet gridsave 110 tl3-s and 2 morenot counted: Product identity rewritten with unchanged scope | Time to revision 17 days | |
| 2026-05-29 | same kind of change as the line above | CVE-2025-40946 | same vendor as the line above | not named as affected at publication, now names blueplanet gridsave 110 tl3-sNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed siemens/blueplanet gridsafe 110 tl3-s; a new product identity is not established | Time to revision 17 days |
| 2026-05-29 | same kind of change as the line above | CVE-2025-40946 | same vendor as the line above | not named as affected at publication, now names blueplanet gridsave 137 tl3-sNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed siemens/blueplanet gridsafe 137 tl3-s; a new product identity is not established | Time to revision 17 days |
| 2026-05-29 | same kind of change as the line above | CVE-2025-40946 | same vendor as the line above | not named as affected at publication, now names blueplanet gridsave 92.0 tl3-sNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed siemens/blueplanet gridsafe 92.0 tl3-s; a new product identity is not established | Time to revision 17 days |
| 2026-05-29 | Product added | CVE-2026-41125 | not named as affected at publication, now names blueplanet gridsave 110 tl3-s and 2 morenot counted: Product identity rewritten with unchanged scope | Time to revision 17 days | |
| 2026-05-29 | same kind of change as the line above | CVE-2026-41125 | same vendor as the line above | not named as affected at publication, now names blueplanet gridsave 110 tl3-sNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed siemens/blueplanet gridsafe 110 tl3-s; a new product identity is not established | Time to revision 17 days |
| 2026-05-29 | same kind of change as the line above | CVE-2026-41125 | same vendor as the line above | not named as affected at publication, now names blueplanet gridsave 137 tl3-sNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed siemens/blueplanet gridsafe 137 tl3-s; a new product identity is not established | Time to revision 17 days |
| 2026-05-29 | same kind of change as the line above | CVE-2026-41125 | same vendor as the line above | not named as affected at publication, now names blueplanet gridsave 92.0 tl3-sNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed siemens/blueplanet gridsafe 92.0 tl3-s; a new product identity is not established | Time to revision 17 days |
| Mon 18 Aug 2025· 1 change | |||||
| 2025-08-18 | CVSS base score changed | CVE-2023-28831 | whole record siemens | stated at publication 7.5, now states 8.7Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 706 days |
| Tue 12 Aug 2025· 3 changes | |||||
| 2025-08-12 | Product added | CVE-2024-54015 | not named as affected at publication, now names siprotec 5 6md89 (cp300) v9.6x and 2 morenot counted: Release branch added to an existing product name | Time to revision 182 days | |
| 2025-08-12 | same kind of change as the line above | CVE-2024-54015 | same vendor as the line above | not named as affected at publication, now names siprotec 5 6md89 (cp300) v9.6xNot counted: Release branch added to an existing product name. release-line label added to siemens/siprotec 5 6md89 (cp300), already named at publication; a newly affected product is not established | Time to revision 182 days |
| 2025-08-12 | same kind of change as the line above | CVE-2024-54015 | same vendor as the line above | not named as affected at publication, now names siprotec 5 7st85 (cp300) v9.6xNot counted: Release branch added to an existing product name. release-line label added to siemens/siprotec 5 7st85 (cp300), already named at publication; a newly affected product is not established | Time to revision 182 days |
| 2025-08-12 | same kind of change as the line above | CVE-2024-54015 | same vendor as the line above | not named as affected at publication, now names siprotec 5 7st86 (cp300) v9.8xNot counted: Release branch added to an existing product name. release-line label added to siemens/siprotec 5 7st86 (cp300), already named at publication; a newly affected product is not established | Time to revision 182 days |
| Tue 11 Feb 2025· 1 change | |||||
| 2025-02-11 | CVSS base score changed | CVE-2024-35212 | whole record siemens | stated at publication 7.5, now states 6.9Assessments not comparable · base scoreHighMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Time to revision 245 days |
| Tue 14 Jan 2025· 4 changes | |||||
| 2025-01-14 | CVSS base score changed | CVE-2023-44317 | whole record siemens | stated at publication 7.2, now states 8.6Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 427 days |
| 2025-01-14 | CVSS base score changed | whole record siemens | stated at publication 4.9, now states 6.9Assessments not comparable · base scoreMediumMediumnot counted: CVSS version set changed | Time to revision 427 days | |
| 2025-01-14 | same kind of change as the line above | CVE-2023-44318 | same vendor as the line above | same change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 427 days |
| 2025-01-14 | same kind of change as the line above | CVE-2023-44319 | same vendor as the line above | same change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 427 days |
| 2025-01-14 | CVSS base score changed | CVE-2023-44374 | whole record siemens | stated at publication 6.5, now states 7.1Assessments not comparable · base scoreMediumHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 427 days |
| Tue 10 Sep 2024· 1 change | |||||
| 2024-09-10 | CVSS base score changed | CVE-2024-21483 | whole record siemens | stated at publication 4.6, now states 5.1Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 182 days |
| Tue 13 Aug 2024· 2 changes | |||||
| 2024-08-13 | CVSS base score changed | CVE-2023-44373 | whole record siemens | stated at publication 9.1, now states 9.4Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 273 days |
| 2024-08-13 | CVSS base score changed | CVE-2024-32637 | whole record siemens | stated at publication 3.3, now states 4.8Assessments not comparable · base scoreLowMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 91 days |
| Tue 9 Jul 2024· 2 changes | |||||
| 2024-07-09 | CVSS base score changed | CVE-2023-46280 | whole record siemens | stated at publication 6.5, now states 8.2Assessments not comparable · base scoreMediumHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 56 days |
| 2024-07-09 | CVSS base score changed | CVE-2023-50821 | whole record siemens | stated at publication 6.2, now states 6.9Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 91 days |
| Tue 11 Jun 2024· 14 changes | |||||
| 2024-06-11 | CVSS base score changed | CVE-2023-38380 | whole record siemens | stated at publication 7.5, now states 8.7Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 182 days |
| 2024-06-11 | CVSS base score changed | CVE-2023-38532 | whole record siemens | stated at publication 6.6, now states 4.8Assessments not comparable · base scoreMediumMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Time to revision 308 days |
| 2024-06-11 | CVSS base score changed | CVE-2023-44321 | whole record siemens | stated at publication 2.7, now states 5.1Assessments not comparable · base scoreLowMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 210 days |
| 2024-06-11 | CVSS base score changed | whole record siemens | stated at publication 6.5, now states 7.1Assessments not comparable · base scoreMediumHighnot counted: CVSS version set changed | Time to revision 28 to 119 days | |
| 2024-06-11 | same kind of change as the line above | CVE-2023-48363 | same vendor as the line above | same change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 119 days |
| 2024-06-11 | same kind of change as the line above | CVE-2023-48364 | same vendor as the line above | same change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 119 days |
| 2024-06-11 | same kind of change as the line above | CVE-2024-33495 | same vendor as the line above | same change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 28 days |
| 2024-06-11 | CVSS base score changed | whole record siemens | stated at publication 3.3, now states 4.8Assessments not comparable · base scoreLowMediumnot counted: CVSS version set changed | Time to revision 28 to 63 days | |
| 2024-06-11 | same kind of change as the line above | CVE-2024-26276 | same vendor as the line above | same change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 63 days |
| 2024-06-11 | same kind of change as the line above | CVE-2024-26277 | same vendor as the line above | same change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 63 days |
| 2024-06-11 | same kind of change as the line above | CVE-2024-33583 | same vendor as the line above | same change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 28 days |
| 2024-06-11 | CVSS base score changed | CVE-2024-31485 | whole record siemens | stated at publication 7.2, now states 8.6Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 28 days |
| 2024-06-11 | CVSS base score changed | CVE-2024-31486 | whole record siemens | stated at publication 5.3, now states 6.0Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 28 days |
| 2024-06-11 | CVSS base score changed | CVE-2024-33494 | whole record siemens | stated at publication 6.5, now states 6.9Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 28 days |
| 2024-06-11 | CVSS base score changed | CVE-2024-33498 | whole record siemens | stated at publication 5.3, now states 6.9Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 28 days |
| 2024-06-11 | CVSS base score changed | CVE-2024-33499 | whole record siemens | stated at publication 9.1, now states 9.4Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 28 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 →