Skip to content
patchdrift.
snapshot 2026-09-07

Advisory severity changed

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

14 advisory changes · newest first · grouped by day

SinceClear all
ChangedSourceRows

Showing changes seen on 2026-03-06. Every day

Counted changes of "Advisory severity changed" changed on 2026-03-06, newest first, one line per change to 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.Advisory, Which advisory was edited, by its GHSA id.Package, The package the advisory names, and the registry it comes from.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.
Fri 6 Mar 2026· 14 changes
2026-03-06published 2025-07-10whole advisoryhighstated at publication MODERATE, now states HIGHCVSS versions were removed or replaced; no shared version's vector was rescored.Time to revision 239 days
2026-03-06published 2025-07-10GHSA-wr62-c79q-cv37CVE-2025-52520same package and registry as the line abovehighsame change as the line aboveTime to revision 239 days
2026-03-06published 2025-07-10GHSA-25xr-qj8w-c4vfCVE-2025-53506same package and registry as the line abovehighsame change as the line aboveTime to revision 239 days
2026-03-06published 2026-02-24GHSA-78qv-3mpx-9cqqCVE-2026-27156whole advisorymoderatestated at publication HIGH, now states MODERATECVSS versions were removed or replaced; no shared version's vector was rescored.Time to revision 10 days
2026-03-06published 2026-01-09 to 2026-03-05whole advisorymoderatestated at publication HIGH, now states MODERATEA vector changed on a shared CVSS version. The band and vector edits may have occurred separately.Time to revision 1 to 56 days
2026-03-06published 2026-03-05GHSA-595m-wc8g-6qgcCVE-2026-30247same package and registry as the line abovemoderatesame change as the line aboveTime to revision 1 days
2026-03-06published 2026-01-09GHSA-pcwc-3fw3-8cqvCVE-2026-22687same package and registry as the line abovemoderatesame change as the line aboveTime to revision 56 days
2026-03-06published 2026-02-17 to 2026-03-02whole advisorymoderatestated at publication HIGH, now states MODERATEA CVSS version was added; the existing vectors stayed the same.Time to revision 3 to 16 days
2026-03-06published 2026-03-02GHSA-xw4p-pw82-hqr7CVE-2026-28457same package and registry as the line abovemoderatesame change as the line aboveTime to revision 3 days
2026-03-06published 2026-02-17GHSA-7vwx-582j-j332CVE-2026-28481same package and registry as the line abovemoderatesame change as the line aboveTime to revision 16 days
2026-03-06published 2026-02-17 to 2026-03-03whole advisoryhighstated at publication MODERATE, now states HIGHA CVSS version was added; the existing vectors stayed the same.Time to revision 2 to 16 days
2026-03-06published 2026-03-02GHSA-jmm5-fvh5-gf4pCVE-2026-28464same package and registry as the line abovehighsame change as the line aboveTime to revision 3 days
2026-03-06published 2026-02-19GHSA-fh3f-q9qw-93j9CVE-2026-28479same package and registry as the line abovehighsame change as the line aboveTime to revision 14 days
2026-03-06published 2026-02-18GHSA-5xfq-5mr7-426qCVE-2026-28482same package and registry as the line abovehighsame change as the line aboveTime to revision 16 days
2026-03-06published 2026-02-18GHSA-xvhf-x56f-2hppCVE-2026-28463same package and registry as the line abovehighsame change as the line aboveTime to revision 16 days
2026-03-06published 2026-03-03GHSA-7xhj-55q9-pc3mCVE-2026-28393same package and registry as the line abovehighsame change as the line aboveTime to revision 2 days
2026-03-06published 2026-02-17GHSA-3m3q-x3gj-f79xCVE-2026-28465same package and registry as the line abovehighsame change as the line aboveTime to revision 16 days
2026-03-06published 2026-02-17GHSA-xc7w-v5x6-cc87CVE-2026-29613same package and registry as the line abovehighsame change as the line aboveTime to revision 16 days

Counted in advisories, never added to the CVE and KEV figures. This kind is counted once per advisory, so changes and advisories are the same number here. 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 →