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.

32 changes behind one line · newest first

SinceClear all
ChangedSourceRows

Showing changes seen on 2025-12-11. Every day

One change, in full: Package added to advisory: 23 packages named as affected in maven. The same change in 6 advisories, across 23 packages: 32 rows in all. Drawn here as 6 lines, one per package. Back to the ledger

Counted changes changed on 2025-12-11, 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.KindAdvisory, 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-12-11published 2021-09-02Package added to advisoryGHSA-52cf-226f-rhr6criticalnot named as affected when the advisory was published, now names org.http4s:http4s-server_2.10 and 5 moreDuration unknown
2025-12-11published 2021-09-02same kind of change as the line aboveGHSA-52cf-226f-rhr6CVE-2021-39185same package registry as the line abovecriticalnot named as affected when the advisory was published, now names org.http4s:http4s-server_2.10Duration unknown
2025-12-11published 2021-09-02same kind of change as the line aboveGHSA-52cf-226f-rhr6CVE-2021-39185same package registry as the line abovecriticalnot named as affected when the advisory was published, now names org.http4s:http4s-server_2.11Duration unknown
2025-12-11published 2021-09-02same kind of change as the line aboveGHSA-52cf-226f-rhr6CVE-2021-39185same package registry as the line abovecriticalnot named as affected when the advisory was published, now names org.http4s:http4s-server_2.12Duration unknown
2025-12-11published 2021-09-02same kind of change as the line aboveGHSA-52cf-226f-rhr6CVE-2021-39185same package registry as the line abovecriticalnot named as affected when the advisory was published, now names org.http4s:http4s-server_2.13Duration unknown
2025-12-11published 2021-09-02same kind of change as the line aboveGHSA-52cf-226f-rhr6CVE-2021-39185same package registry as the line abovecriticalnot named as affected when the advisory was published, now names org.http4s:http4s-server_2.13.0-m5Duration unknown
2025-12-11published 2021-09-02same kind of change as the line aboveGHSA-52cf-226f-rhr6CVE-2021-39185same package registry as the line abovecriticalnot named as affected when the advisory was published, now names org.http4s:http4s-server_3Duration unknown
2025-12-11published 2021-09-22Package added to advisoryGHSA-5vcm-3xc3-w7x3highnot named as affected when the advisory was published, now names org.http4s:http4s-client_2.12 and 8 moreDuration unknown
2025-12-11published 2021-09-22same kind of change as the line aboveGHSA-5vcm-3xc3-w7x3CVE-2021-41084same package registry as the line abovehighnot named as affected when the advisory was published, now names org.http4s:http4s-client_2.12Duration unknown
2025-12-11published 2021-09-22same kind of change as the line aboveGHSA-5vcm-3xc3-w7x3CVE-2021-41084same package registry as the line abovehighnot named as affected when the advisory was published, now names org.http4s:http4s-client_2.13Duration unknown
2025-12-11published 2021-09-22same kind of change as the line aboveGHSA-5vcm-3xc3-w7x3CVE-2021-41084same package registry as the line abovehighnot named as affected when the advisory was published, now names org.http4s:http4s-client_3Duration unknown
2025-12-11published 2021-09-22same kind of change as the line aboveGHSA-5vcm-3xc3-w7x3CVE-2021-41084same package registry as the line abovehighnot named as affected when the advisory was published, now names org.http4s:http4s-server_2.10Duration unknown
2025-12-11published 2021-09-22same kind of change as the line aboveGHSA-5vcm-3xc3-w7x3CVE-2021-41084same package registry as the line abovehighnot named as affected when the advisory was published, now names org.http4s:http4s-server_2.11Duration unknown
2025-12-11published 2021-09-22same kind of change as the line aboveGHSA-5vcm-3xc3-w7x3CVE-2021-41084same package registry as the line abovehighnot named as affected when the advisory was published, now names org.http4s:http4s-server_2.12Duration unknown
2025-12-11published 2021-09-22same kind of change as the line aboveGHSA-5vcm-3xc3-w7x3CVE-2021-41084same package registry as the line abovehighnot named as affected when the advisory was published, now names org.http4s:http4s-server_2.13Duration unknown
2025-12-11published 2021-09-22same kind of change as the line aboveGHSA-5vcm-3xc3-w7x3CVE-2021-41084same package registry as the line abovehighnot named as affected when the advisory was published, now names org.http4s:http4s-server_2.13.0-m5Duration unknown
1 more row in this change is not listed here. Open all 9 rows
2025-12-11published 2023-01-06Package added to advisoryGHSA-54w6-vxfh-fw7fhighnot named as affected when the advisory was published, now names org.http4s:http4s-core_2.10 and 3 moreTime to revision 1,070 days
2025-12-11published 2023-01-06same kind of change as the line aboveGHSA-54w6-vxfh-fw7fCVE-2023-22465same package registry as the line abovehighnot named as affected when the advisory was published, now names org.http4s:http4s-core_2.10Time to revision 1,070 days
2025-12-11published 2023-01-06same kind of change as the line aboveGHSA-54w6-vxfh-fw7fCVE-2023-22465same package registry as the line abovehighnot named as affected when the advisory was published, now names org.http4s:http4s-core_2.11Time to revision 1,070 days
2025-12-11published 2023-01-06same kind of change as the line aboveGHSA-54w6-vxfh-fw7fCVE-2023-22465same package registry as the line abovehighnot named as affected when the advisory was published, now names org.http4s:http4s-core_2.12Time to revision 1,070 days
2025-12-11published 2023-01-06same kind of change as the line aboveGHSA-54w6-vxfh-fw7fCVE-2023-22465same package registry as the line abovehighnot named as affected when the advisory was published, now names org.http4s:http4s-core_2.13Time to revision 1,070 days
2025-12-11published 2022-05-14Package added to advisoryGHSA-62g2-m955-v383highnot named as affected when the advisory was published, now names org.apache.spark:spark-core_2.10 and 1 moreDuration unknown
2025-12-11published 2022-05-14same kind of change as the line aboveGHSA-62g2-m955-v383CVE-2018-11804same package registry as the line abovehighnot named as affected when the advisory was published, now names org.apache.spark:spark-core_2.10Duration unknown
2025-12-11published 2022-05-14same kind of change as the line aboveGHSA-62g2-m955-v383CVE-2018-11804same package registry as the line abovehighnot named as affected when the advisory was published, now names org.apache.spark:spark-core_2.11Duration unknown
2025-12-11published 2025-06-10Package added to advisoryGHSA-76qp-h5mr-frr4highnot named as affected when the advisory was published, now names org.apache.kafka:kafka_2.11 and 2 moreTime to revision 185 days
2025-12-11published 2025-06-10same kind of change as the line aboveGHSA-76qp-h5mr-frr4CVE-2025-27818same package registry as the line abovehighnot named as affected when the advisory was published, now names org.apache.kafka:kafka_2.11Time to revision 185 days
2025-12-11published 2025-06-10same kind of change as the line aboveGHSA-76qp-h5mr-frr4CVE-2025-27818same package registry as the line abovehighnot named as affected when the advisory was published, now names org.apache.kafka:kafka_2.12Time to revision 185 days
2025-12-11published 2025-06-10same kind of change as the line aboveGHSA-76qp-h5mr-frr4CVE-2025-27818same package registry as the line abovehighnot named as affected when the advisory was published, now names org.apache.kafka:kafka_2.13Time to revision 185 days
2025-12-11published 2025-06-10Package added to advisoryGHSA-mcwh-c9pg-xw43highnot named as affected when the advisory was published, now names org.apache.kafka:kafka_2.10 and 7 moreTime to revision 185 days
2025-12-11published 2025-06-10same kind of change as the line aboveGHSA-mcwh-c9pg-xw43CVE-2025-27819same package registry as the line abovehighnot named as affected when the advisory was published, now names org.apache.kafka:kafka_2.10Time to revision 185 days
2025-12-11published 2025-06-10same kind of change as the line aboveGHSA-mcwh-c9pg-xw43CVE-2025-27819same package registry as the line abovehighnot named as affected when the advisory was published, now names org.apache.kafka:kafka_2.11Time to revision 185 days
2025-12-11published 2025-06-10same kind of change as the line aboveGHSA-mcwh-c9pg-xw43CVE-2025-27819same package registry as the line abovehighnot named as affected when the advisory was published, now names org.apache.kafka:kafka_2.12Time to revision 185 days
2025-12-11published 2025-06-10same kind of change as the line aboveGHSA-mcwh-c9pg-xw43CVE-2025-27819same package registry as the line abovehighnot named as affected when the advisory was published, now names org.apache.kafka:kafka_2.13Time to revision 185 days
2025-12-11published 2025-06-10same kind of change as the line aboveGHSA-mcwh-c9pg-xw43CVE-2025-27819same package registry as the line abovehighnot named as affected when the advisory was published, now names org.apache.kafka:kafka_2.8.0Time to revision 185 days
2025-12-11published 2025-06-10same kind of change as the line aboveGHSA-mcwh-c9pg-xw43CVE-2025-27819same package registry as the line abovehighnot named as affected when the advisory was published, now names org.apache.kafka:kafka_2.8.2Time to revision 185 days
2025-12-11published 2025-06-10same kind of change as the line aboveGHSA-mcwh-c9pg-xw43CVE-2025-27819same package registry as the line abovehighnot named as affected when the advisory was published, now names org.apache.kafka:kafka_2.9.1Time to revision 185 days
2025-12-11published 2025-06-10same kind of change as the line aboveGHSA-mcwh-c9pg-xw43CVE-2025-27819same package registry as the line abovehighnot named as affected when the advisory was published, now names org.apache.kafka:kafka_2.9.2Time to revision 185 days

Counted in advisories, never added to the CVE and KEV figures. Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. 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 →