Every change, newest first
| 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 13 Aug 2026· 1 record change | |||||
| 2026-08-13 | Product added | CVE-2026-59086 | not named as affected at publication, now names simcenter femap | Days to revision 2 | |
| Tue 9 Jun 2026· 1 record change | |||||
| 2026-06-09 | Product added | CVE-2025-40936 | not named as affected at publication, now names simcenter femap | Days to revision 204 | |
| Fri 29 May 2026· 2 record changes | |||||
| 2026-05-29 | Product added | CVE-2025-40946 | not named as affected at publication, now names blueplanet 125 nx3 m10 | Days to revision 17 | |
| 2026-05-29 | Product added | CVE-2026-41125 | not named as affected at publication, now names blueplanet 125 nx3 m10 | Days to revision 17 | |
| Tue 12 May 2026· 7 record changes | |||||
| 2026-05-12 | Product added | CVE-2025-23384 | not named as affected at publication, now names scalance sc622-2c | Days to revision 427 | |
| 2026-05-12 | Product added | CVE-2025-23384 | not named as affected at publication, now names scalance sc626-2c | Days to revision 427 | |
| 2026-05-12 | Product added | CVE-2025-23384 | not named as affected at publication, now names scalance sc632-2c | Days to revision 427 | |
| 2026-05-12 | Product added | CVE-2025-23384 | not named as affected at publication, now names scalance sc636-2c | Days to revision 427 | |
| 2026-05-12 | Product added | CVE-2025-23384 | not named as affected at publication, now names scalance sc642-2c | Days to revision 427 | |
| 2026-05-12 | Product added | CVE-2025-23384 | not named as affected at publication, now names scalance sc646-2c | Days to revision 427 | |
| 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 | Days to revision 63 | |
| Tue 14 Apr 2026· 30 record changes | |||||
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w721-1 rj45 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w722-1 rj45 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w734-1 rj45 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w734-1 rj45 (usa) | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w738-1 m12 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w748-1 m12 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w748-1 rj45 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w761-1 rj45 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w774-1 m12 eec | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w774-1 rj45 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w774-1 rj45 (usa) | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w778-1 m12 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w778-1 m12 eec | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w778-1 m12 eec (usa) | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w786-1 rj45 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w786-2 rj45 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w786-2 sfp | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w786-2ia rj45 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w788-1 m12 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w788-1 rj45 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w788-2 m12 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w788-2 m12 eec | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance w788-2 rj45 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance wam766-1 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance wam766-1 eec | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance wub762-1 ifeatures | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance wum766-1 | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2023-44373 | not named as affected at publication, now names scalance wum766-1 (usa) | Days to revision 882 | |
| 2026-04-14 | Product added | CVE-2025-40571 | not named as affected at publication, now names mendix oidc sso v4.2 (mendix 10 compatible) | Days to revision 336 | |
| 2026-04-14 | Product added | CVE-2025-40571 | not named as affected at publication, now names mendix oidc sso v4.3 (mendix 10 compatible) | Days to revision 336 | |
| Tue 10 Mar 2026· 1 record change | |||||
| 2026-03-10 | Product added | CVE-2026-22923 | not named as affected at publication, now names nx (managed mode) | Days to revision 28 | |
| Tue 10 Feb 2026· 1 record change | |||||
| 2026-02-10 | Product added | CVE-2025-40936 | not named as affected at publication, now names solid edge | Days to revision 85 | |
| Tue 13 Jan 2026· 57 record changes | |||||
| 2026-01-13 | Product added | CVE-2024-49775 | not named as affected at publication, now names opcenter rdnl | Days to revision 393 | |
| 2026-01-13 | Product added | CVE-2024-56835 | not named as affected at publication, now names ruggedcom rox mx5000 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56835 | not named as affected at publication, now names ruggedcom rox mx5000re | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56835 | not named as affected at publication, now names ruggedcom rox rx1400 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56835 | not named as affected at publication, now names ruggedcom rox rx1500 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56835 | not named as affected at publication, now names ruggedcom rox rx1501 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56835 | not named as affected at publication, now names ruggedcom rox rx1510 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56835 | not named as affected at publication, now names ruggedcom rox rx1511 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56835 | not named as affected at publication, now names ruggedcom rox rx1512 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56835 | not named as affected at publication, now names ruggedcom rox rx1524 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56835 | not named as affected at publication, now names ruggedcom rox rx1536 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56835 | not named as affected at publication, now names ruggedcom rox rx5000 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56836 | not named as affected at publication, now names ruggedcom rox mx5000 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56836 | not named as affected at publication, now names ruggedcom rox mx5000re | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56836 | not named as affected at publication, now names ruggedcom rox rx1400 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56836 | not named as affected at publication, now names ruggedcom rox rx1500 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56836 | not named as affected at publication, now names ruggedcom rox rx1501 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56836 | not named as affected at publication, now names ruggedcom rox rx1510 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56836 | not named as affected at publication, now names ruggedcom rox rx1511 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56836 | not named as affected at publication, now names ruggedcom rox rx1512 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56836 | not named as affected at publication, now names ruggedcom rox rx1524 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56836 | not named as affected at publication, now names ruggedcom rox rx1536 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56836 | not named as affected at publication, now names ruggedcom rox rx5000 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56837 | not named as affected at publication, now names ruggedcom rox mx5000 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56837 | not named as affected at publication, now names ruggedcom rox mx5000re | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56837 | not named as affected at publication, now names ruggedcom rox rx1400 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56837 | not named as affected at publication, now names ruggedcom rox rx1500 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56837 | not named as affected at publication, now names ruggedcom rox rx1501 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56837 | not named as affected at publication, now names ruggedcom rox rx1510 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56837 | not named as affected at publication, now names ruggedcom rox rx1511 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56837 | not named as affected at publication, now names ruggedcom rox rx1512 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56837 | not named as affected at publication, now names ruggedcom rox rx1524 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56837 | not named as affected at publication, now names ruggedcom rox rx1536 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56837 | not named as affected at publication, now names ruggedcom rox rx5000 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56838 | not named as affected at publication, now names ruggedcom rox mx5000 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56838 | not named as affected at publication, now names ruggedcom rox mx5000re | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56838 | not named as affected at publication, now names ruggedcom rox rx1400 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56838 | not named as affected at publication, now names ruggedcom rox rx1500 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56838 | not named as affected at publication, now names ruggedcom rox rx1501 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56838 | not named as affected at publication, now names ruggedcom rox rx1510 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56838 | not named as affected at publication, now names ruggedcom rox rx1511 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56838 | not named as affected at publication, now names ruggedcom rox rx1512 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56838 | not named as affected at publication, now names ruggedcom rox rx1524 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56838 | not named as affected at publication, now names ruggedcom rox rx1536 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56838 | not named as affected at publication, now names ruggedcom rox rx5000 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56839 | not named as affected at publication, now names ruggedcom rox mx5000 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56839 | not named as affected at publication, now names ruggedcom rox mx5000re | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56839 | not named as affected at publication, now names ruggedcom rox rx1400 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56839 | not named as affected at publication, now names ruggedcom rox rx1500 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56839 | not named as affected at publication, now names ruggedcom rox rx1501 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56839 | not named as affected at publication, now names ruggedcom rox rx1510 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56839 | not named as affected at publication, now names ruggedcom rox rx1511 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56839 | not named as affected at publication, now names ruggedcom rox rx1512 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56839 | not named as affected at publication, now names ruggedcom rox rx1524 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56839 | not named as affected at publication, now names ruggedcom rox rx1536 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56839 | not named as affected at publication, now names ruggedcom rox rx5000 | Days to revision 35 | |
| 2026-01-13 | Product added | CVE-2024-56840 | not named as affected at publication, now names ruggedcom rox mx5000 | Days to revision 35 | |
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.
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 →