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.

16 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
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.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.
Tue 23 Jun 2026· 1 record change
2026-06-23Product addedCVE-2026-45170palo_altonot named as affected at publication, now names vendor pamDays to revision 12
Fri 12 Jun 2026· 1 record change
2026-06-12CVSS base score changedCVE-2026-45171
whole record
palo_alto
stated at publication 9.3, now states 8.7CVSS v4.0 · base scoreCriticalHighDays to revision 0
Fri 29 May 2026· 1 record change
2026-05-29CVSS base score changedCVE-2026-0257
whole record
palo_alto
stated at publication 4.7, now states 7.8CVSS v4.0 · base scoreMediumHighDays to revision 16
Thu 2 Apr 2026· 3 record changes
2026-04-02Product addedCVE-2025-0133palo_altonot named as affected at publication, now names cloud ngfw and 1 moreDays to revision 323
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 ngfwDays to revision 323
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 accessDays to revision 323
2026-04-02CVSS base score changedCVE-2025-0133
whole record
palo_alto
stated at publication 6.9, now states 2.7CVSS v4.0 · base scoreMediumLowDays to revision 323
Wed 1 Apr 2026· 1 record change
2026-04-01CVSS base score changedCVE-2025-4615
whole record
palo_alto
stated at publication 7.0, now states 5.5CVSS v4.0 · base scoreHighMediumDays to revision 173
Mon 23 Jun 2025· 1 record change
2025-06-23Fix version movedCVE-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.Days to revision 40
Fri 13 Jun 2025· 1 record change
2025-06-13CVSS base score changedCVE-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.Days to revision 39
Tue 18 Mar 2025· 1 record change
2025-03-18CVSS base score changedCVE-2025-0116
whole record
palo_alto
stated at publication 5.1, now states 6.8CVSS v4.0 · base scoreMediumMediumDays to revision 5
Wed 12 Mar 2025· 1 record change
2025-03-12Fix version movedCVE-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 dayDays to revision 0
Wed 15 Jan 2025· 2 record changes
2025-01-15CVSS base score changedCVE-2024-5917
whole record
palo_alto
stated at publication 6.3, now states 2.1CVSS v4.0 · base scoreMediumLowDays to revision 63
2025-01-15CVSS base score changedCVE-2025-0107
whole record
palo_alto
stated at publication 6.3, now states 7.7CVSS v4.0 · base scoreMediumHighDays to revision 5
Thu 12 Dec 2024· 1 record change
2024-12-12Record state changedCVE-2023-6061
whole record
palo_alto
stated at publication PUBLISHED, now states REJECTEDDays to revision 371
Fri 12 Apr 2024· 1 record change
2024-04-12CVSS base score changedCVE-2024-3400
whole record
palo_alto
stated at publication 9.8, now states 10.0CVSS v3.1 · base scoreCriticalCriticalDays to revision 0
Mon 31 Jul 2023· 1 record change
2023-07-31CVSS base score changedCVE-2023-0009
whole record
palo_alto
stated at publication 6.7, now states 7.8CVSS v3.1 · base scoreMediumHighDays to revision 47

Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none. 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.
3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 03:47 UTC · scroll for earlierfewermore

Data sources and quality

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 →

Check my CVEs against these changes →