Skip to content

Every change, newest first

Compare earlier and later source statements, with the dates and evidence behind each measured change.

138 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all

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

Counted changes changed on 2026-04-02, 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.
Thu 2 Apr 2026· 138 changes
2026-04-02Added to CISA KEVCVE-2026-3502
TrueConfClient
CISA KEV
fix due 2026-04-16Duration unknown
2026-04-02Fix version movedCVE-2025-24213
appleipados
stated at publication 17.7, now states 17.7.7Release branch starts at 0.Time to revision 367 days
2026-04-02Fix version movedCVE-2025-24220
appleipados
stated at publication 17.7, now states 17.7.9Release branch starts at 0.Original value first replaced 2025-05-20; this value first seen 2026-04-02.Time to revision 8 days
2026-04-02Product addedCVE-2025-0133palo_altonot named as affected at publication, now names cloud ngfw and 1 moreTime to revision 323 days
2026-04-02same kind of change as the line aboveCVE-2025-0133same vendor as the line abovenot named as affected at publication, now names cloud ngfwTime to revision 323 days
2026-04-02same kind of change as the line aboveCVE-2025-0133same vendor as the line abovenot named as affected at publication, now names prisma accessTime to revision 323 days
2026-04-02Product addedCVE-2025-31675not named as affected at publication, now names linkTime to revision 367 days
2026-04-02Product addedCVE-2024-14033VulnChecknot named as affected at publication, now names hirschmann eaglesdvTime to revision 0 days
2026-04-02Product added103 rows, one per record and productnot named as affected at publication, now names macos and 6 moreTime to revision 50 to 758 days
2026-04-02same kind of change as the line aboveCVE-2024-23225same vendor as the line abovenot named as affected at publication, now names macosTime to revision 758 days
2026-04-02same kind of change as the line aboveCVE-2024-23225same vendor as the line abovenot named as affected at publication, now names tvosTime to revision 758 days
2026-04-02same kind of change as the line aboveCVE-2024-23225same vendor as the line abovenot named as affected at publication, now names visionosTime to revision 758 days
2026-04-02same kind of change as the line aboveCVE-2024-23225same vendor as the line abovenot named as affected at publication, now names watchosTime to revision 758 days
2026-04-02same kind of change as the line aboveCVE-2024-23296same vendor as the line abovenot named as affected at publication, now names macosTime to revision 758 days
2026-04-02same kind of change as the line aboveCVE-2024-23296same vendor as the line abovenot named as affected at publication, now names tvosTime to revision 758 days
2026-04-02same kind of change as the line aboveCVE-2024-23296same vendor as the line abovenot named as affected at publication, now names visionosTime to revision 758 days
2026-04-02same kind of change as the line aboveCVE-2024-23296same vendor as the line abovenot named as affected at publication, now names watchosTime to revision 758 days
95 more rows in this change are not listed here. Open all 103 rows
2026-04-02Product addedCVE-2025-8065TPLinknot named as affected at publication, now names tapo c520ws v2.6Time to revision 104 days
2026-04-02Product addedCVE-2026-0651TPLinknot named as affected at publication, now names tapo c520ws v2.6Time to revision 51 days
2026-04-02Product addedCVE-2026-28727not named as affected at publication, now names acronis true imageTime to revision 28 days
2026-04-02Product addedCVE-2025-12801not named as affected at publication, now names red hat openshift container platform 4.16Time to revision 29 days
2026-04-02Product addedCVE-2024-51982rapid7not named as affected at publication, now names ads-2400n and 16 moreTime to revision 281 days
2026-04-02same kind of change as the line aboveCVE-2024-51982same vendor as the line abovenot named as affected at publication, now names ads-2400nTime to revision 281 days
2026-04-02same kind of change as the line aboveCVE-2024-51982same vendor as the line abovenot named as affected at publication, now names ads-2800wTime to revision 281 days
2026-04-02same kind of change as the line aboveCVE-2024-51982same vendor as the line abovenot named as affected at publication, now names ads-3000nTime to revision 281 days
2026-04-02same kind of change as the line aboveCVE-2024-51982same vendor as the line abovenot named as affected at publication, now names ads-3600wTime to revision 281 days
2026-04-02same kind of change as the line aboveCVE-2024-51982same vendor as the line abovenot named as affected at publication, now names dcp-b7520dw (china)Time to revision 281 days
2026-04-02same kind of change as the line aboveCVE-2024-51982same vendor as the line abovenot named as affected at publication, now names dcp-b7535dw (china)Time to revision 281 days
2026-04-02same kind of change as the line aboveCVE-2024-51982same vendor as the line abovenot named as affected at publication, now names dcp-j973n w/bTime to revision 281 days
2026-04-02same kind of change as the line aboveCVE-2024-51982same vendor as the line abovenot named as affected at publication, now names dcp-j978n w/bTime to revision 281 days
9 more rows in this change are not listed here. Open all 17 rows
2026-04-02Product addednot named as affected at publication, now names red hat build of keycloak 26.4Time to revision 22 to 72 days
2026-04-02same kind of change as the line aboveCVE-2026-1180same vendor as the line abovesame change as the line aboveTime to revision 72 days
2026-04-02same kind of change as the line aboveCVE-2026-3429same vendor as the line abovesame change as the line aboveTime to revision 22 days
2026-04-02Product addedCVE-2025-15400WPScannot named as affected at publication, now names openpix for woocommerceTime to revision 50 days
2026-04-02CVSS base score changedCVE-2025-0133
whole record
palo_alto
stated at publication 6.9, now states 2.7CVSS v4.0 · base scoreMediumLowTime to revision 323 days
2026-04-02CVSS base score changedCVE-2023-7343
whole record
VulnCheck
stated at publication 7.8, now states 8.5CVSS v4.0 · base scoreHighHighTime to revision 0 days
2026-04-02CVSS base score changedCVE-2025-8065
whole record
TPLink
stated at publication 7.1, now states 8.7CVSS v4.0 · base scoreHighHighTime to revision 104 days
2026-04-02CVSS base score changedCVE-2026-0651
whole record
TPLink
stated at publication 5.3, now states 6.9CVSS v4.0 · base scoreMediumMediumTime to revision 51 days

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.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

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 →