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.

14 changes behind one line · newest firstCSVJSONRSS

SinceClear the filter

One change, in full: Product added: content credentials rust sdk named as affected from adobe. The same change in 14 CVE records. Back to all 9 products in this change · Back to the ledger

Counted changes from the last 30 days, newest first, one line per change to a CVE record or a GHSA advisory, 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 or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together.Vendor or package, 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.
2026-08-27Product addedCVE-2026-34665not named as affected at publication, now names content credentials rust sdkTime to revision 107 days
2026-08-27Product addedCVE-2026-34666not named as affected at publication, now names content credentials rust sdkTime to revision 107 days
2026-08-27Product addedCVE-2026-34667not named as affected at publication, now names content credentials rust sdkTime to revision 107 days
2026-08-27Product addedCVE-2026-34668not named as affected at publication, now names content credentials rust sdkTime to revision 107 days
2026-08-27Product addedCVE-2026-34669not named as affected at publication, now names content credentials rust sdkTime to revision 107 days
2026-08-27Product addedCVE-2026-34670not named as affected at publication, now names content credentials rust sdkTime to revision 107 days
2026-08-27Product addedCVE-2026-34671not named as affected at publication, now names content credentials rust sdkTime to revision 107 days
2026-08-27Product addedCVE-2026-34672not named as affected at publication, now names content credentials rust sdkTime to revision 107 days
2026-08-27Product addedCVE-2026-34673not named as affected at publication, now names content credentials rust sdkTime to revision 107 days
2026-08-27Product addedCVE-2026-34677not named as affected at publication, now names content credentials rust sdkTime to revision 107 days
2026-08-27Product addedCVE-2026-34678not named as affected at publication, now names content credentials rust sdkTime to revision 107 days
2026-08-27Product addedCVE-2026-34679not named as affected at publication, now names content credentials rust sdkTime to revision 107 days
2026-08-27Product addedCVE-2026-34680not named as affected at publication, now names content credentials rust sdkTime to revision 107 days
2026-08-27Product addedCVE-2026-34688not named as affected at publication, now names content credentials rust sdkTime to revision 107 days

Two units, never added: changes to a CVE record or KEV entry, and changes to a GitHub advisory. 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 →