Every change, newest first

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

15 record changes · 2 advisory changes · newest first · grouped by dayCSV JSON RSS

SinceKindVendorSortClear all

PublisherPublishedChangedSourceRows

Showing changes seen on 2026-07-20. Every day

Counted changes changed on 2026-07-20, 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.	Kind	Record 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 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.
Mon 20 Jul 2026· 17 changes
2026-07-20	Affected range extended	CVE-2026-57956	signozsignoz VulnCheck	stated at publication 0.130.1, now states 0.133.0Release branch starts at 0.	Time to revision 21 days
2026-07-20	Affected range extended	CVE-2026-57080	sankonet::bittorrent CPANSec	stated at publication 2.0.1, now states 2.1.0Release branch starts at 0.	Time to revision 20 days
2026-07-20	Affected range extended	CVE-2026-57081	sankonet::bittorrent CPANSec	stated at publication 2.0.1, now states 2.1.0Release branch starts at 0.	Time to revision 20 days
2026-07-20	Product added	CVE-2026-10649	red hat	not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support	Time to revision 34 days
2026-07-20	Product added	CVE-2026-10649	red hat	not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support	Time to revision 34 days
2026-07-20	Product added	CVE-2026-11332	red hat	not named as affected at publication, now names red hat ansible automation platform 2.6 for rhel 10	Time to revision 46 days
2026-07-20	Product added	CVE-2026-11332	red hat	not named as affected at publication, now names red hat ansible automation platform 2.6 for rhel 9	Time to revision 46 days
2026-07-20	Product added	CVE-2026-12701	red hat	not named as affected at publication, now names red hat ansible automation platform 2.6 for rhel 9	Time to revision 0 days
2026-07-20	Product added	CVE-2026-11332	red hat	not named as affected at publication, now names red hat ansible automation platform 2.5 for rhel 8	Time to revision 46 days
2026-07-20	Product added	CVE-2026-11332	red hat	not named as affected at publication, now names red hat ansible automation platform 2.5 for rhel 9	Time to revision 46 days
2026-07-20	Product added	CVE-2026-12701	red hat	not named as affected at publication, now names red hat ansible automation platform 2.5 for rhel 8	Time to revision 0 days
2026-07-20	Product added	CVE-2026-12701	red hat	not named as affected at publication, now names red hat ansible automation platform 2.5 for rhel 9	Time to revision 0 days
2026-07-20	Product added	CVE-2026-11332	red hat	not named as affected at publication, now names red hat ansible automation platform 2.7 for rhel 10	Time to revision 45 days
2026-07-20	Product added	CVE-2026-11332	red hat	not named as affected at publication, now names red hat ansible automation platform 2.7 for rhel 9	Time to revision 45 days
2026-07-20	CVSS base score changed	CVE-2026-34632	whole record adobe	stated at publication 8.2, now states 8.6CVSS v3.1 · base scoreHighHigh	Time to revision 96 days
2026-07-20published 2025-08-26	Advisory severity changed	GHSA-8r4j-24qv-fmq9CVE-2025-71361	whole advisoryhigh	stated at publication MODERATE, now states HIGHNo CVSS vector was stated in the first observed version.	Time to revision 328 days
2026-07-20published 2026-06-05	Advisory severity changed	GHSA-jr54-jwhj-55gpCVE-2026-47380	whole advisorymoderate	stated at publication LOW, now states MODERATENo CVSS vector was stated in the first observed version.	Time to revision 45 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.

4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

Every kind of change

Each bar filters the ledger to that kind, and counts what it would show under the filters already on. Two units, one length scale, never a total.

To a CVE record or a KEV entry

To a GitHub 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 →