Every change, newest first

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

147 record changes · 16 advisory changes · newest first · grouped by dayCSV JSON RSS

SinceKindVendorSortClear all

PublisherPublishedChangedSourceRows

Showing changes seen on 2026-03-30. Every day

Counted changes changed on 2026-03-30, 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 30 Mar 2026· 63 changes
2026-03-30	Product added	CVE-2026-20402	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20403	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20404	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20405	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20406	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20407	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20408	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20410	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20411	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20412	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20413	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20414	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20415	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20416	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20417	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20418	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20419	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20420	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20421	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20422	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2026-20423	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20424	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20425	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20426	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20427	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20428	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20429	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20430	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20434	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20435	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20436	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20437	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20438	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20439	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20440	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20441	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20442	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20443	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20444	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20445	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 28 days
2026-03-30	Product added	CVE-2026-20409	mediatek, inc. MediaTek	not named as affected at publication, now names mediatek chipset	Time to revision 56 days
2026-03-30	Product added	CVE-2024-3884	red hat	not named as affected at publication, now names red hat jboss enterprise application platform 7.1 eus for rhel 7	Time to revision 117 days
2026-03-30	Product added	CVE-2024-3884	red hat	not named as affected at publication, now names red hat jboss enterprise application platform 7.3 eus for rhel 7	Time to revision 117 days
2026-03-30	Product added	CVE-2026-0603	red hat	not named as affected at publication, now names red hat jboss enterprise application platform 7.1 eus for rhel 7	Time to revision 66 days
2026-03-30	Product added	CVE-2026-0603	red hat	not named as affected at publication, now names red hat jboss enterprise application platform 7.3 eus for rhel 7	Time to revision 66 days
2026-03-30	Record state changed	CVE-2026-4427	whole record redhat	stated at publication PUBLISHED, now states REJECTED	Time to revision 11 days
2026-03-30	Record state changed	CVE-2026-4645	whole record redhat	stated at publication PUBLISHED, now states REJECTED	Time to revision 7 days
2026-03-30published 2025-06-28	Advisory severity changed	GHSA-m964-fjrh-xxq2CVE-2025-32897	whole advisorylow	stated at publication CRITICAL, now states LOWCVSS versions were removed or replaced; no shared version's vector was rescored.	Time to revision 275 days
2026-03-30published 2026-03-03	Advisory severity changed	GHSA-h9xm-j4qg-fvpgCVE-2026-32007	whole advisoryhigh	stated at publication MODERATE, now states HIGHA CVSS version was added; the existing vectors stayed the same.	Time to revision 27 days
2026-03-30published 2026-03-03	Advisory severity changed	GHSA-25gx-x37c-7pphCVE-2026-32064	whole advisoryhigh	stated at publication MODERATE, now states HIGHA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.	Time to revision 27 days
2026-03-30published 2026-03-02	Advisory severity changed	GHSA-hwpq-rrpf-pgcqCVE-2026-32065	whole advisorymoderate	stated at publication HIGH, now states MODERATEA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.	Time to revision 28 days
2026-03-30published 2026-03-03	Advisory severity changed	GHSA-vvgp-4c28-m3jmCVE-2026-32057	whole advisorymoderate	stated at publication LOW, now states MODERATEA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.	Time to revision 27 days
2026-03-30published 2026-03-02	Advisory severity changed	GHSA-hjvp-qhm6-wrh2CVE-2026-32058	whole advisorylow	stated at publication MODERATE, now states LOWA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.	Time to revision 28 days
2026-03-30published 2026-03-03	Advisory severity changed	GHSA-6rcp-vxwf-3mfpCVE-2026-32052	whole advisorymoderate	stated at publication HIGH, now states MODERATEA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.	Time to revision 27 days
2026-03-30published 2026-03-03	Advisory severity changed	GHSA-mwcg-wfq3-4gjcCVE-2026-32043	whole advisorymoderate	stated at publication HIGH, now states MODERATEA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.	Time to revision 27 days
2026-03-30published 2026-03-02	Advisory severity changed	GHSA-rxxp-482v-7mrhCVE-2026-32049	whole advisoryhigh	stated at publication MODERATE, now states HIGHA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.	Time to revision 28 days
2026-03-30published 2026-03-09	Advisory severity changed	GHSA-r6qf-8968-wj9qCVE-2026-27183	whole advisorylow	stated at publication MODERATE, now states LOWA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.	Time to revision 21 days
2026-03-30published 2026-03-03	Advisory severity changed	GHSA-v865-p3gq-hw6mCVE-2026-32004	whole advisoryhigh	stated at publication MODERATE, now states HIGHA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.	Time to revision 27 days
2026-03-30published 2026-03-03	Advisory severity changed	GHSA-2ww6-868g-2c56CVE-2026-32040	whole advisorylow	stated at publication MODERATE, now states LOWA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.	Time to revision 27 days
2026-03-30published 2026-03-03	Advisory severity changed	GHSA-2fgq-7j6h-9rm4CVE-2026-32003	whole advisoryhigh	stated at publication MODERATE, now states HIGHA CVSS version was added; the existing vectors stayed the same.	Time to revision 28 days
2026-03-30published 2026-03-02	Advisory severity changed	GHSA-vpj2-69hf-rppwCVE-2026-32041	whole advisoryhigh	stated at publication MODERATE, now states HIGHA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.	Time to revision 28 days
2026-03-30published 2026-03-03	Advisory severity changed	GHSA-4gc7-qcvf-38wgCVE-2026-32010	whole advisorymoderate	stated at publication HIGH, now states MODERATEA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.	Time to revision 27 days
2026-03-30published 2026-03-19	Advisory withdrawn	GHSA-x6gf-mpr2-68h6CVE-2026-4427	whole advisoryhigh	withdrawn 2026-03-30	Time to revision 11 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.

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 →