Every change, newest first
What a record said when it was published, what it says now, and the commit that changed it.
10 advisory changes · newest first · grouped by day
Showing changes seen on 2026-05-20. 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. | Kind | 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. |
|---|---|---|---|---|---|
| Wed 20 May 2026· 10 changes | |||||
| 2026-05-20published 2024-10-09 | Advisory fix version moved | GHSA-pfr9-2p92-qrhq | crates.iodbn moderate | stated at publication 0.22.0, now states 0.22.1 | Time to revision 587 days |
| 2026-05-20published 2023-06-14 | Package added to advisory | GHSA-5wfc-hjrc-gq87CVE-2023-34620 | high | not named as affected when the advisory was published, now names github.com/hjson/hjson-go/v4 | Time to revision 1,071 days |
| 2026-05-20published 2023-06-14 | Package added to advisory | GHSA-5wfc-hjrc-gq87CVE-2023-34620 | high | not named as affected when the advisory was published, now names laktak/hjson | Time to revision 1,071 days |
| 2026-05-20published 2026-04-09 | Package added to advisory | GHSA-69cc-cv78-qc8gCVE-2026-29129 | high | not named as affected when the advisory was published, now names org.apache.tomcat:tomcat-coyote | Time to revision 41 days |
| 2026-05-20published 2026-04-09 | Package added to advisory | GHSA-95jq-rwvf-vjx4CVE-2026-29145 | critical | not named as affected when the advisory was published, now names org.apache.tomcat:tomcat-coyote-ffm | Time to revision 41 days |
| 2026-05-20published 2024-12-17 | Package added to advisory | GHSA-653p-vg55-5652CVE-2024-54677 | moderate | not named as affected when the advisory was published, now names org.apache.tomcat:tomcat | Time to revision 519 days |
| 2026-05-20published 2020-06-15 | Package added to advisory | GHSA-qcxh-w3j9-58qrCVE-2019-0199 | high | not named as affected when the advisory was published, now names org.apache.tomcat:tomcat-coyote | Duration unknown |
| 2026-05-20published 2026-04-09 | Package added to advisory | GHSA-24j9-x2wg-9qv6CVE-2026-34500 | moderate | not named as affected when the advisory was published, now names org.apache.tomcat:tomcat-coyote-ffm | Time to revision 40 days |
| 2026-05-20published 2026-03-31 | Package added to advisory | GHSA-rvhj-8chj-8v3cCVE-2026-0596 | critical | not named as affected when the advisory was published, now names mlflow | Time to revision 49 days |
| 2026-05-20published 2026-04-16 | Advisory severity changed | GHSA-v92g-xgxw-vvmmCVE-2026-41205 | whole advisoryhigh | stated at publication MODERATE, now states HIGHA vector changed on a shared CVSS version. The band and vector edits may have occurred separately. | Time to revision 33 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.
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 →