Skip to content

Package added to advisory

What a record said when it was published, what it says now, and the commit that changed it.

18 changes behind one line · newest first

SinceClear all
ChangedSourceRows

One change, in full: Package added to advisory: 9 packages named as affected in packagist. The same change in 10 advisories, across 9 packages: 18 rows in all, one per advisory and package. Drawn here as 8 lines, one per package. Back to the ledger

Counted changes of "Package added to advisory", 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.
2024-02-08published 2022-05-14 to 2022-05-243 bandsnot named as affected when the advisory was published, now names symfony/securityDays to revision 625 to 636
2024-02-08published 2022-05-24GHSA-q87v-q8fw-gmj5CVE-2017-11365same package registry as the line abovecriticalsame change as the line aboveDays to revision 625
2024-02-08published 2022-05-17GHSA-jjx5-fq5g-8xpcCVE-2016-1902same package registry as the line abovehighsame change as the line aboveDays to revision 633
2024-02-08published 2022-05-14GHSA-g4g7-q726-v5hgCVE-2018-11406same package registry as the line abovehighsame change as the line aboveDays to revision 636
2024-02-08published 2022-05-14GHSA-g4rg-rw65-8hfgCVE-2018-11385same package registry as the line abovehighsame change as the line aboveDays to revision 636
2024-02-08published 2022-05-14GHSA-wvj5-r78r-hhfqCVE-2016-2403same package registry as the line abovecriticalsame change as the line aboveDays to revision 636
2024-02-08published 2022-05-14GHSA-j5jh-hpr4-h332CVE-2015-8124same package registry as the line abovelowsame change as the line aboveDays to revision 636
2024-02-08published 2022-05-14 to 2022-05-242 bandsnot named as affected when the advisory was published, now names symfony/security-coreDays to revision 625 to 636
2024-02-08published 2022-05-24GHSA-q87v-q8fw-gmj5CVE-2017-11365same package registry as the line abovecriticalsame change as the line aboveDays to revision 625
2024-02-08published 2022-05-17GHSA-jjx5-fq5g-8xpcCVE-2016-1902same package registry as the line abovehighsame change as the line aboveDays to revision 633
2024-02-08published 2022-05-14GHSA-wvj5-r78r-hhfqCVE-2016-2403same package registry as the line abovecriticalsame change as the line aboveDays to revision 636
2024-02-08published 2022-05-05GHSA-22pv-7v9j-hqxpCVE-2013-4752moderatenot named as affected when the advisory was published, now names symfony/http-foundationDays to revision 645
2024-02-08published 2022-05-13GHSA-8wgj-6wx8-h5hqCVE-2018-14773moderatenot named as affected when the advisory was published, now names symfony/symfonyDays to revision 637
2024-02-08published 2022-05-14GHSA-g4g7-q726-v5hgCVE-2018-11406highnot named as affected when the advisory was published, now names symfony/security-bundleDays to revision 636
2024-02-08published 2022-05-142 bandsnot named as affected when the advisory was published, now names symfony/security-httpDays to revision 636
2024-02-08published 2022-05-14GHSA-g4g7-q726-v5hgCVE-2018-11406same package registry as the line abovehighsame change as the line aboveDays to revision 636
2024-02-08published 2022-05-14GHSA-g4rg-rw65-8hfgCVE-2018-11385same package registry as the line abovehighsame change as the line aboveDays to revision 636
2024-02-08published 2022-05-14GHSA-j5jh-hpr4-h332CVE-2015-8124same package registry as the line abovelowsame change as the line aboveDays to revision 636
2024-02-08published 2022-05-17GHSA-qmqw-mpqp-mr54CVE-2015-4050moderatenot named as affected when the advisory was published, now names symfony/http-kernelDays to revision 633
2024-02-08published 2021-06-21GHSA-rgx6-rjj4-c388moderatenot named as affected when the advisory was published, now names drupal/core and 1 morenot dated
2024-02-08published 2021-06-21GHSA-rgx6-rjj4-c388CVE-2021-33829same package registry as the line abovemoderatenot named as affected when the advisory was published, now names drupal/corenot dated
2024-02-08published 2021-06-21GHSA-rgx6-rjj4-c388CVE-2021-33829same package registry as the line abovemoderatenot named as affected when the advisory was published, now names drupal/drupalnot dated

Counted in advisories, never added to the CVE and KEV figures. This kind is counted once per advisory and per package, so one advisory that named four further packages counts four times. 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.

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 →