Skip to content

Every change, newest first

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

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

SinceClear all

Showing changes seen on 2026-05-13. Every day

Counted changes changed on 2026-05-13, 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 13 May 2026· 38 changes
2026-05-13Fix version moved
microsoftmicrosoft dynamics 365 (on-premises) version 9.1
stated at publication 9.1.44.15, now states 9.1.45.11Release branch starts at 9.0.same dayTime to revision 1 days
2026-05-13same kind of change as the line aboveCVE-2026-42898same vendor as the line abovesame change as the line aboveRelease branch starts at 9.0.same dayTime to revision 1 days
2026-05-13same kind of change as the line aboveCVE-2026-42833same vendor as the line abovesame change as the line aboveRelease branch starts at 9.0.same dayTime to revision 1 days
2026-05-13Product addednot named as affected at publication, now names safariTime to revision 2 days
2026-05-13same kind of change as the line aboveCVE-2026-28847same vendor as the line abovesame change as the line aboveTime to revision 2 days
2026-05-13same kind of change as the line aboveCVE-2026-28883same vendor as the line abovesame change as the line aboveTime to revision 2 days
2026-05-13same kind of change as the line aboveCVE-2026-28901same vendor as the line abovesame change as the line aboveTime to revision 2 days
2026-05-13same kind of change as the line aboveCVE-2026-28902same vendor as the line abovesame change as the line aboveTime to revision 2 days
2026-05-13same kind of change as the line aboveCVE-2026-28903same vendor as the line abovesame change as the line aboveTime to revision 2 days
2026-05-13same kind of change as the line aboveCVE-2026-28904same vendor as the line abovesame change as the line aboveTime to revision 2 days
2026-05-13same kind of change as the line aboveCVE-2026-28905same vendor as the line abovesame change as the line aboveTime to revision 2 days
2026-05-13same kind of change as the line aboveCVE-2026-28907same vendor as the line abovesame change as the line aboveTime to revision 2 days
13 more rows in this change are not listed here. Open all 21 rows
2026-05-132 commitsProduct added8 rows, one per record and productnot named as affected at publication, now names red hat openshift container platform 4.15 and 1 moreBranches and original-value intervals are stated on each row.Time to revision 44 to 176 days
2026-05-13same kind of change as the line aboveCVE-2025-61662same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.15Time to revision 176 days
2026-05-13same kind of change as the line aboveCVE-2026-4111same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.15Time to revision 61 days
2026-05-13same kind of change as the line aboveCVE-2026-4424same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.15Time to revision 55 days
2026-05-13same kind of change as the line aboveCVE-2026-5121same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.15Time to revision 44 days
2026-05-13same kind of change as the line aboveCVE-2025-61662same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.14Time to revision 176 days
2026-05-13same kind of change as the line aboveCVE-2026-4111same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.14Time to revision 61 days
2026-05-13same kind of change as the line aboveCVE-2026-4424same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.14Time to revision 55 days
2026-05-13same kind of change as the line aboveCVE-2026-5121same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.14Time to revision 44 days
2026-05-13CVSS base score changed
whole record
adobe
stated at publication 5.5, now states 7.8CVSS v3.1 · base scoreMediumHighTime to revision 1 days
2026-05-13same kind of change as the line aboveCVE-2026-34683same vendor as the line abovesame change as the line aboveTime to revision 1 days
2026-05-13same kind of change as the line aboveCVE-2026-34684same vendor as the line abovesame change as the line aboveTime to revision 1 days
2026-05-13CVSS base score changedCVE-2026-44113
whole record
VulnCheck
stated at publication 6.0, now states 8.3CVSS v4.0 · base scoreMediumHighTime to revision 7 days
2026-05-13CVSS base score changedCVE-2025-15101
whole record
ASUS
stated at publication 8.5, now states 8.6CVSS v4.0 · base scoreHighHighTime to revision 48 days
2026-05-13KEV required action changedCVE-2026-0300CISA KEVstated at publication Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Until the vendor releases an official fix, the following workaround should be implemented: - Restrict User-ID Authentication Portal access to only trusted zones. - Disable User-ID Authentication Portal if not required., now states Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Until the vendor releases an official fix, the following workaround should be implemented: - Restrict User-ID Authentication Portal access to only trusted zones. - Disable User-ID Authentication Portal if not required. 5/13/2026: Palo Alto has released a variety of patches. If these are relevant to your environment, please apply the designated patch.Time to revision 7 days
2026-05-13Record state changedCVE-2026-8449
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 1 days
2026-05-13published 2026-05-05Advisory severity changedGHSA-wv26-88m5-6h59CVE-2026-42875whole advisorymoderatestated at publication LOW, now states MODERATENo CVSS vector was stated in the first observed version.Time to revision 8 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.

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 →