Every change, newest first
One change, in full: Product added: 27 products named as affected from siemens. Products named as affected in 7 CVE records, across 27 products: 54 rows in all, one per record and product. Drawn here as 7 lines, one per product. Back to the ledger
| 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. |
|---|---|---|---|---|---|
| 2025-08-12 | Product added | not named as affected at publication, now names ruggedcom rsg2100p (32m) v4.x | Days to revision 399 to 735 | ||
| 2025-08-12 | same kind of change as the line above | CVE-2023-24845 | same vendor as the line above | same change as the line above | Days to revision 735 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-39269 | same vendor as the line above | same change as the line above | Days to revision 735 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-52237 | same vendor as the line above | same change as the line above | Days to revision 399 |
| 2025-08-12 | Product added | not named as affected at publication, now names ruggedcom rsg2100p (32m) v5.x | Days to revision 399 to 735 | ||
| 2025-08-12 | same kind of change as the line above | CVE-2023-24845 | same vendor as the line above | same change as the line above | Days to revision 735 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-39269 | same vendor as the line above | same change as the line above | Days to revision 735 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-52237 | same vendor as the line above | same change as the line above | Days to revision 399 |
| 2025-08-12 | same kind of change as the line above | CVE-2024-38278 | same vendor as the line above | same change as the line above | Days to revision 399 |
| 2025-08-12 | Product added | not named as affected at publication, now names ruggedcom rsg2100pnc (32m) v4.x | Days to revision 399 to 735 | ||
| 2025-08-12 | same kind of change as the line above | CVE-2023-24845 | same vendor as the line above | same change as the line above | Days to revision 735 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-39269 | same vendor as the line above | same change as the line above | Days to revision 735 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-52237 | same vendor as the line above | same change as the line above | Days to revision 399 |
| 2025-08-12 | Product added | not named as affected at publication, now names ruggedcom rsg2100pnc (32m) v5.x | Days to revision 399 to 735 | ||
| 2025-08-12 | same kind of change as the line above | CVE-2023-24845 | same vendor as the line above | same change as the line above | Days to revision 735 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-39269 | same vendor as the line above | same change as the line above | Days to revision 735 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-52237 | same vendor as the line above | same change as the line above | Days to revision 399 |
| 2025-08-12 | same kind of change as the line above | CVE-2024-38278 | same vendor as the line above | same change as the line above | Days to revision 399 |
| 2025-08-12 | Product added | CVE-2023-44318 | not named as affected at publication, now names scalance xb206-2 (sc) and 16 more | Days to revision 637 | |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44318 | same vendor as the line above | not named as affected at publication, now names scalance xb206-2 (sc) | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44318 | same vendor as the line above | not named as affected at publication, now names scalance xb206-2 (st/bfoc) | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44318 | same vendor as the line above | not named as affected at publication, now names scalance xb206-2 ld | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44318 | same vendor as the line above | not named as affected at publication, now names scalance xb206-2 sc | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44318 | same vendor as the line above | not named as affected at publication, now names scalance xb206-2 st | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44318 | same vendor as the line above | not named as affected at publication, now names scalance xb206-2ld | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44318 | same vendor as the line above | not named as affected at publication, now names scalance xf204g | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44318 | same vendor as the line above | not named as affected at publication, now names scalance xp208g | Days to revision 637 |
| 9 more rows in this change are not listed here. Open all 17 rows → | |||||
| 2025-08-12 | Product added | CVE-2023-44321 | not named as affected at publication, now names scalance xb206-2 (sc) and 16 more | Days to revision 637 | |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44321 | same vendor as the line above | not named as affected at publication, now names scalance xb206-2 (sc) | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44321 | same vendor as the line above | not named as affected at publication, now names scalance xb206-2 (st/bfoc) | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44321 | same vendor as the line above | not named as affected at publication, now names scalance xb206-2 ld | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44321 | same vendor as the line above | not named as affected at publication, now names scalance xb206-2 sc | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44321 | same vendor as the line above | not named as affected at publication, now names scalance xb206-2 st | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44321 | same vendor as the line above | not named as affected at publication, now names scalance xb206-2ld | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44321 | same vendor as the line above | not named as affected at publication, now names scalance xf204g | Days to revision 637 |
| 2025-08-12 | same kind of change as the line above | CVE-2023-44321 | same vendor as the line above | not named as affected at publication, now names scalance xp208g | Days to revision 637 |
| 9 more rows in this change are not listed here. Open all 17 rows → | |||||
| 2025-08-12 | Product added | CVE-2024-54015 | not named as affected at publication, now names siprotec 5 communication module eth-ba-2el (rev.2) v9.6 and 5 more | Days to revision 182 | |
| 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 communication module eth-ba-2el (rev.2) v9.6 | Days to revision 182 |
| 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 communication module eth-ba-2el (rev.2) v9.8 | Days to revision 182 |
| 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 communication module eth-bb-2fo (rev. 2) v9.6 | Days to revision 182 |
| 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 communication module eth-bb-2fo (rev. 2) v9.8 | Days to revision 182 |
| 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 communication module eth-bd-2fo v9.6 | Days to revision 182 |
| 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 communication module eth-bd-2fo v9.8 | Days to revision 182 |
Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
Data sources and quality
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 →