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.

36 changes behind one line · newest first

SinceClear all
ChangedSourceRows

One change, in full: Package added to advisory: 36 packages named as affected in maven. The same change in 6 advisories, across 36 packages: 36 rows in all. Drawn here as 6 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.
2025-09-30published 2022-05-17GHSA-jf9v-fxfq-wm76moderatenot named as affected when the advisory was published, now names net.liftweb:lift-webkit_2.7.7 and 6 moreTime to revision 1,233 days
2025-09-30published 2022-05-17GHSA-jf9v-fxfq-wm76CVE-2013-3300same package registry as the line abovemoderatenot named as affected when the advisory was published, now names net.liftweb:lift-webkit_2.7.7Time to revision 1,233 days
2025-09-30published 2022-05-17GHSA-jf9v-fxfq-wm76CVE-2013-3300same package registry as the line abovemoderatenot named as affected when the advisory was published, now names net.liftweb:lift-webkit_2.8.0Time to revision 1,233 days
2025-09-30published 2022-05-17GHSA-jf9v-fxfq-wm76CVE-2013-3300same package registry as the line abovemoderatenot named as affected when the advisory was published, now names net.liftweb:lift-webkit_2.8.1Time to revision 1,233 days
2025-09-30published 2022-05-17GHSA-jf9v-fxfq-wm76CVE-2013-3300same package registry as the line abovemoderatenot named as affected when the advisory was published, now names net.liftweb:lift-webkit_2.8.2Time to revision 1,233 days
2025-09-30published 2022-05-17GHSA-jf9v-fxfq-wm76CVE-2013-3300same package registry as the line abovemoderatenot named as affected when the advisory was published, now names net.liftweb:lift-webkit_2.9.0Time to revision 1,233 days
2025-09-30published 2022-05-17GHSA-jf9v-fxfq-wm76CVE-2013-3300same package registry as the line abovemoderatenot named as affected when the advisory was published, now names net.liftweb:lift-webkit_2.9.0-1Time to revision 1,233 days
2025-09-30published 2022-05-17GHSA-jf9v-fxfq-wm76CVE-2013-3300same package registry as the line abovemoderatenot named as affected when the advisory was published, now names net.liftweb:lift-webkit_2.9.1Time to revision 1,233 days
2025-09-30published 2022-06-28GHSA-ww3v-6xjf-jv28moderatenot named as affected when the advisory was published, now names io.spray:spray-json_2.10 and 11 moreDuration unknown
2025-09-30published 2022-06-28GHSA-ww3v-6xjf-jv28CVE-2018-18855same package registry as the line abovemoderatenot named as affected when the advisory was published, now names io.spray:spray-json_2.10Duration unknown
2025-09-30published 2022-06-28GHSA-ww3v-6xjf-jv28CVE-2018-18855same package registry as the line abovemoderatenot named as affected when the advisory was published, now names io.spray:spray-json_2.11Duration unknown
2025-09-30published 2022-06-28GHSA-ww3v-6xjf-jv28CVE-2018-18855same package registry as the line abovemoderatenot named as affected when the advisory was published, now names io.spray:spray-json_2.11.0-rc4Duration unknown
2025-09-30published 2022-06-28GHSA-ww3v-6xjf-jv28CVE-2018-18855same package registry as the line abovemoderatenot named as affected when the advisory was published, now names io.spray:spray-json_2.12Duration unknown
2025-09-30published 2022-06-28GHSA-ww3v-6xjf-jv28CVE-2018-18855same package registry as the line abovemoderatenot named as affected when the advisory was published, now names io.spray:spray-json_2.12.0-m3Duration unknown
2025-09-30published 2022-06-28GHSA-ww3v-6xjf-jv28CVE-2018-18855same package registry as the line abovemoderatenot named as affected when the advisory was published, now names io.spray:spray-json_2.12.0-m5Duration unknown
2025-09-30published 2022-06-28GHSA-ww3v-6xjf-jv28CVE-2018-18855same package registry as the line abovemoderatenot named as affected when the advisory was published, now names io.spray:spray-json_2.12.0-rc1Duration unknown
2025-09-30published 2022-06-28GHSA-ww3v-6xjf-jv28CVE-2018-18855same package registry as the line abovemoderatenot named as affected when the advisory was published, now names io.spray:spray-json_2.12.0-rc2Duration unknown
4 more rows in this change are not listed here. Open all 12 rows
2025-09-30published 2023-04-27GHSA-55vq-xpjf-r2xcmoderatenot named as affected when the advisory was published, now names com.typesafe.akka:akka-stream-kafka_2.11 and 3 moreTime to revision 887 days
2025-09-30published 2023-04-27GHSA-55vq-xpjf-r2xcCVE-2023-29471same package registry as the line abovemoderatenot named as affected when the advisory was published, now names com.typesafe.akka:akka-stream-kafka_2.11Time to revision 887 days
2025-09-30published 2023-04-27GHSA-55vq-xpjf-r2xcCVE-2023-29471same package registry as the line abovemoderatenot named as affected when the advisory was published, now names com.typesafe.akka:akka-stream-kafka_2.12Time to revision 887 days
2025-09-30published 2023-04-27GHSA-55vq-xpjf-r2xcCVE-2023-29471same package registry as the line abovemoderatenot named as affected when the advisory was published, now names com.typesafe.akka:akka-stream-kafka_2.13Time to revision 887 days
2025-09-30published 2023-04-27GHSA-55vq-xpjf-r2xcCVE-2023-29471same package registry as the line abovemoderatenot named as affected when the advisory was published, now names com.typesafe.akka:akka-stream-kafka_3Time to revision 887 days
2025-09-30published 2022-05-24GHSA-3hw2-h67c-wq66highnot named as affected when the advisory was published, now names com.typesafe.akka:aakka-http-core_2.13.0-m3 and 6 moreDuration unknown
2025-09-30published 2022-05-24GHSA-3hw2-h67c-wq66CVE-2021-42697same package registry as the line abovehighnot named as affected when the advisory was published, now names com.typesafe.akka:aakka-http-core_2.13.0-m3Duration unknown
2025-09-30published 2022-05-24GHSA-3hw2-h67c-wq66CVE-2021-42697same package registry as the line abovehighnot named as affected when the advisory was published, now names com.typesafe.akka:akka-http-core_2.11Duration unknown
2025-09-30published 2022-05-24GHSA-3hw2-h67c-wq66CVE-2021-42697same package registry as the line abovehighnot named as affected when the advisory was published, now names com.typesafe.akka:akka-http-core_2.12Duration unknown
2025-09-30published 2022-05-24GHSA-3hw2-h67c-wq66CVE-2021-42697same package registry as the line abovehighnot named as affected when the advisory was published, now names com.typesafe.akka:akka-http-core_2.13Duration unknown
2025-09-30published 2022-05-24GHSA-3hw2-h67c-wq66CVE-2021-42697same package registry as the line abovehighnot named as affected when the advisory was published, now names com.typesafe.akka:akka-http-core_2.13.0-m5Duration unknown
2025-09-30published 2022-05-24GHSA-3hw2-h67c-wq66CVE-2021-42697same package registry as the line abovehighnot named as affected when the advisory was published, now names com.typesafe.akka:akka-http-core_2.13.0-rc2Duration unknown
2025-09-30published 2022-05-24GHSA-3hw2-h67c-wq66CVE-2021-42697same package registry as the line abovehighnot named as affected when the advisory was published, now names com.typesafe.akka:akka-http-core_2.13.0-rc3Duration unknown
2025-09-30published 2022-07-29GHSA-2cpx-6pqp-wf35criticalnot named as affected when the advisory was published, now names co.fs2:fs2-io_2.12 and 4 moreDuration unknown
2025-09-30published 2022-07-29GHSA-2cpx-6pqp-wf35CVE-2022-31183same package registry as the line abovecriticalnot named as affected when the advisory was published, now names co.fs2:fs2-io_2.12Duration unknown
2025-09-30published 2022-07-29GHSA-2cpx-6pqp-wf35CVE-2022-31183same package registry as the line abovecriticalnot named as affected when the advisory was published, now names co.fs2:fs2-io_2.13Duration unknown
2025-09-30published 2022-07-29GHSA-2cpx-6pqp-wf35CVE-2022-31183same package registry as the line abovecriticalnot named as affected when the advisory was published, now names co.fs2:fs2-io_3Duration unknown
2025-09-30published 2022-07-29GHSA-2cpx-6pqp-wf35CVE-2022-31183same package registry as the line abovecriticalnot named as affected when the advisory was published, now names co.fs2:fs2-io_sjs1_2.13Duration unknown
2025-09-30published 2022-07-29GHSA-2cpx-6pqp-wf35CVE-2022-31183same package registry as the line abovecriticalnot named as affected when the advisory was published, now names co.fs2:fs2-io_sjs1_3Duration unknown
2025-09-30published 2023-11-22GHSA-5xqm-hc45-f2g2CVE-2021-37942highnot named as affected when the advisory was published, now names co.elastic.apm:elastic-apm-agentTime to revision 679 days

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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

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 →