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.

681 record changes · 1 advisory changes · newest first · grouped by dayCSVJSONRSS

SinceClear all

Showing changes seen on 2026-04-01. Every day

Counted changes changed on 2026-04-01, 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.
Wed 1 Apr 2026· 22 changes
2026-04-01Product addedCVE-2024-37213Patchstacknot named as affected at publication, now names alinextTime to revision 628 days
2026-04-01Product addedCVE-2024-43334Patchstacknot named as affected at publication, now names zilomTime to revision 268 days
2026-04-01Product addedCVE-2024-47647Patchstacknot named as affected at publication, now names helpie faqTime to revision 543 days
2026-04-01Product addedCVE-2024-49703Patchstacknot named as affected at publication, now names wpeventlyTime to revision 524 days
2026-04-01Product addedCVE-2024-50459Patchstacknot named as affected at publication, now names aidwpTime to revision 519 days
2026-04-01Product addedPatchstacknot named as affected at publication, now names repairbuddyTime to revision 456 to 506 days
2026-04-01same kind of change as the line aboveCVE-2024-51793same vendor as the line abovesame change as the line aboveTime to revision 506 days
2026-04-01same kind of change as the line aboveCVE-2024-56061same vendor as the line abovesame change as the line aboveTime to revision 456 days
2026-04-01Product addedCVE-2024-55994Patchstacknot named as affected at publication, now names 畅言评论系统Time to revision 471 days
2026-04-01Product addedCVE-2024-56281Patchstacknot named as affected at publication, now names 워드프레스 결제 심플페이Time to revision 449 days
2026-04-01Product addedCVE-2025-22282Patchstacknot named as affected at publication, now names ez form calculator premiumTime to revision 362 days
2026-04-01Product addedCVE-2025-22524Patchstacknot named as affected at publication, now names فرم ساز فرم افزارTime to revision 449 days
2026-04-01Product addedCVE-2025-22530Patchstacknot named as affected at publication, now names 아임포트 결제버튼 생성 플러그인Time to revision 449 days
2026-04-01Product addedCVE-2025-60235Patchstacknot named as affected at publication, now names support ticket system for woocommerce (premium)Time to revision 146 days
2026-04-01Product addedCVE-2025-68568Patchstacknot named as affected at publication, now names claspo – popups, spin the wheel & email captureTime to revision 98 days
2026-04-01Product addedCVE-2025-68989Patchstacknot named as affected at publication, now names contact-form-7-mailchimp-extensionTime to revision 92 days
2026-04-012 commitsProduct addedCVE-2025-12801not named as affected at publication, now names red hat openshift container platform 4.19 and 1 moreBranches and original-value intervals are stated on each row.Time to revision 28 days
2026-04-01same kind of change as the line aboveCVE-2025-12801same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.19Time to revision 28 days
2026-04-01same kind of change as the line aboveCVE-2025-12801same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.17Time to revision 28 days
2026-04-01CVSS base score changedCVE-2026-20963
whole record
microsoft
stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCriticalTime to revision 78 days
2026-04-01CVSS base score changedCVE-2025-4615
whole record
palo_alto
stated at publication 7.0, now states 5.5CVSS v4.0 · base scoreHighMediumTime to revision 173 days
2026-04-01Record state changed
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 1 days
2026-04-01same kind of change as the line aboveCVE-2026-34508same vendor as the line abovesame change as the line aboveTime to revision 1 days
2026-04-01same kind of change as the line aboveCVE-2026-34509same vendor as the line abovesame change as the line aboveTime to revision 1 days
2026-04-01published 2024-11-12Advisory withdrawnGHSA-g5vp-j278-8pjhwhole advisoryhighwithdrawn 2026-04-01Time to revision 504 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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

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 →