Every change, newest first

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

16 changes · newest first · grouped by dayCSV JSON RSS

PublisherPublishedChangedSourceRows

Counted changes published by palo_alto, 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.	Kind	Record, 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 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.
Tue 23 Jun 2026· 1 change
2026-06-23	Product added	CVE-2026-45170	cyberark software, a palo alto networks company palo_alto	not named as affected at publication, now names vendor pam	Time to revision 12 days
Fri 12 Jun 2026· 1 change
2026-06-12	CVSS base score changed	CVE-2026-45171	whole record palo_alto	stated at publication 9.3, now states 8.7CVSS v4.0 · base scoreCriticalHigh	Time to revision 0 days
Fri 29 May 2026· 1 change
2026-05-29	CVSS base score changed	CVE-2026-0257	whole record palo_alto	stated at publication 4.7, now states 7.8CVSS v4.0 · base scoreMediumHigh	Time to revision 16 days
Thu 2 Apr 2026· 3 changes
2026-04-02	Product added	CVE-2025-0133Show all 2 products in this change: Product added: 2 products named as affected in CVE-2025-0133Hide the 2 products in this change: Product added: 2 products named as affected in CVE-2025-0133	palo alto networks palo_alto	not named as affected at publication, now names cloud ngfw and 1 more	Time to revision 323 days
2026-04-02	same kind of change as the line above	CVE-2025-0133	same vendor as the line above	not named as affected at publication, now names cloud ngfw	Time to revision 323 days
2026-04-02	same kind of change as the line above	CVE-2025-0133	same vendor as the line above	not named as affected at publication, now names prisma access	Time to revision 323 days
2026-04-02	CVSS base score changed	CVE-2025-0133	whole record palo_alto	stated at publication 6.9, now states 2.7CVSS v4.0 · base scoreMediumLow	Time to revision 323 days
Wed 1 Apr 2026· 1 change
2026-04-01	CVSS base score changed	CVE-2025-4615	whole record palo_alto	stated at publication 7.0, now states 5.5CVSS v4.0 · base scoreHighMedium	Time to revision 173 days
Mon 23 Jun 2025· 1 change
2025-06-23	Fix version moved	CVE-2025-0138	palo alto networksprisma cloud compute edition palo_alto	stated at publication 34.00.141, now states 34.01.129Release branch starts at 1.	Time to revision 40 days
Fri 13 Jun 2025· 1 change
2025-06-13	CVSS base score changed	CVE-2025-0129	whole record palo_alto	stated at publication 9.4, now states 9.3CVSS v4.0 · base scoreCriticalCriticalOriginal value first replaced 2025-05-20; this value first seen 2025-06-13.	Time to revision 39 days
Tue 18 Mar 2025· 1 change
2025-03-18	CVSS base score changed	CVE-2025-0116	whole record palo_alto	stated at publication 5.1, now states 6.8CVSS v4.0 · base scoreMediumMedium	Time to revision 5 days
Wed 12 Mar 2025· 1 change
2025-03-12	Fix version moved	CVE-2025-0118	palo alto networksglobalprotect app palo_alto	stated at publication 6.0.10, now states 6.0.11Release branch starts at 6.0.0.same day	Time to revision 0 days
Wed 15 Jan 2025· 2 changes
2025-01-15	CVSS base score changed	CVE-2024-5917	whole record palo_alto	stated at publication 6.3, now states 2.1CVSS v4.0 · base scoreMediumLow	Time to revision 63 days
2025-01-15	CVSS base score changed	CVE-2025-0107	whole record palo_alto	stated at publication 6.3, now states 7.7CVSS v4.0 · base scoreMediumHigh	Time to revision 5 days
Thu 12 Dec 2024· 1 change
2024-12-12	Record state changed	CVE-2023-6061	whole record palo_alto	stated at publication PUBLISHED, now states REJECTED	Time to revision 371 days
Fri 12 Apr 2024· 1 change
2024-04-12	CVSS base score changed	CVE-2024-3400	whole record palo_alto	stated at publication 9.8, now states 10.0CVSS v3.1 · base scoreCriticalCritical	Time to revision 0 days
Mon 31 Jul 2023· 1 change
2023-07-31	CVSS base score changed	CVE-2023-0009	whole record palo_alto	stated at publication 6.7, now states 7.8CVSS v3.1 · base scoreMediumHigh	Time to revision 47 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.

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 →