Skip to content

Every change, newest first

What a record said when it was published, what it says now, and the commit that changed it.

20 changes behind one line · newest firstCSVJSONRSS

SinceClear all
ChangedSourceRows

One change, in full: Product added: autocad map 3d named as affected from autodesk. The same change in 20 CVE records. Back to the ledger

Counted changes from autodesk, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
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.KindRecord, 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 changedDays 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-04-11Product addedCVE-2024-7991not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-7992not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-9489not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-9826not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-9827not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-9996not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8599not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8600not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8589not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8590not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8591not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8592not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8593not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8594not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8595not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8596not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8597not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8598not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8587not named as affected at publication, now names autocad map 3dTime to revision 164 days
2025-04-11Product addedCVE-2024-8588not named as affected at publication, now names autocad map 3dTime to revision 164 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 →