Package added to advisory
Compare earlier and later source statements, with the dates and evidence behind each measured change.
32 advisory changes · newest first · grouped by day
Showing changes seen on 2025-12-11. Every day
| 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 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. |
|---|---|---|---|---|
| Thu 11 Dec 2025· 32 changes | ||||
| 2025-12-11published 2021-09-02 to 2025-06-10 | 32 rows, one per advisory and package | 2 bands | not named as affected when the advisory was published, now names org.http4s:http4s-server_2.10 and 22 more | Time to revision 185 to 1,070 days |
| 2025-12-11published 2021-09-02 | GHSA-52cf-226f-rhr6CVE-2021-39185 | same package registry as the line abovecritical | not named as affected when the advisory was published, now names org.http4s:http4s-server_2.10 | Duration unknown |
| 2025-12-11published 2021-09-02 | GHSA-52cf-226f-rhr6CVE-2021-39185 | same package registry as the line abovecritical | not named as affected when the advisory was published, now names org.http4s:http4s-server_2.11 | Duration unknown |
| 2025-12-11published 2021-09-02 | GHSA-52cf-226f-rhr6CVE-2021-39185 | same package registry as the line abovecritical | not named as affected when the advisory was published, now names org.http4s:http4s-server_2.12 | Duration unknown |
| 2025-12-11published 2021-09-02 | GHSA-52cf-226f-rhr6CVE-2021-39185 | same package registry as the line abovecritical | not named as affected when the advisory was published, now names org.http4s:http4s-server_2.13 | Duration unknown |
| 2025-12-11published 2021-09-02 | GHSA-52cf-226f-rhr6CVE-2021-39185 | same package registry as the line abovecritical | not named as affected when the advisory was published, now names org.http4s:http4s-server_2.13.0-m5 | Duration unknown |
| 2025-12-11published 2021-09-02 | GHSA-52cf-226f-rhr6CVE-2021-39185 | same package registry as the line abovecritical | not named as affected when the advisory was published, now names org.http4s:http4s-server_3 | Duration unknown |
| 2025-12-11published 2021-09-22 | GHSA-5vcm-3xc3-w7x3CVE-2021-41084 | same package registry as the line abovehigh | not named as affected when the advisory was published, now names org.http4s:http4s-client_2.12 | Duration unknown |
| 2025-12-11published 2021-09-22 | GHSA-5vcm-3xc3-w7x3CVE-2021-41084 | same package registry as the line abovehigh | not named as affected when the advisory was published, now names org.http4s:http4s-client_2.13 | Duration unknown |
| 24 more rows in this change are not listed here. Open all 32 rows → | ||||
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 →