Every change, newest first
Showing changes seen on 2026-05-08. 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 | Record or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together. | Vendor or package, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry. | 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. |
|---|---|---|---|---|---|
| Fri 8 May 2026· 18 changes | |||||
| 2026-05-08 | Added to CISA KEV | CVE-2026-42208 | BerriAILiteLLM CISA KEV | fix due 2026-05-11 | Duration unknown |
| 2026-05-08 | Product added | CVE-2026-5588 | bcorg | not named as affected at publication, now names bcpix-lts | Time to revision 23 days |
| 2026-05-08 | Record state changed | CVE-2026-7448 | whole record Wordfence | stated at publication PUBLISHED, now states REJECTED | Time to revision 2 days |
| 2026-05-08published 2026-05-04 | Advisory severity changed | GHSA-67wx-r9xr-x75xCVE-2026-41648 | whole advisorymoderate | stated at publication LOW, now states MODERATENo CVSS vector was stated in the first observed version. | Time to revision 4 days |
| 2026-05-08published 2026-05-04 | Advisory severity changed | GHSA-4m88-wxj4-9qj6CVE-2026-40251 | whole advisoryhigh | stated at publication MODERATE, now states HIGHA CVSS version was added; the existing vectors stayed the same. | Time to revision 4 days |
| 2026-05-08published 2026-05-04 | Advisory severity changed | GHSA-r7w7-mmxr-47r9CVE-2026-40197 | whole advisoryhigh | stated at publication MODERATE, now states HIGHA CVSS version was added; the existing vectors stayed the same. | Time to revision 4 days |
| 2026-05-08published 2026-05-04 | Advisory severity changed | GHSA-gc7j-g665-rxr9CVE-2026-40195 | whole advisoryhigh | stated at publication MODERATE, now states HIGHA CVSS version was added; the existing vectors stayed the same. | Time to revision 4 days |
| 2026-05-08published 2026-05-04 | Advisory severity changed | GHSA-78fc-9688-w8xwCVE-2026-40076 | whole advisorycritical | stated at publication HIGH, now states CRITICALA CVSS version was added; the existing vectors stayed the same. | Time to revision 4 days |
| 2026-05-08published 2026-03-31 | Advisory severity changed | GHSA-5h2w-qmfp-ggp6CVE-2026-41344 | whole advisorymoderate | stated at publication HIGH, now states MODERATEA vector changed on a shared CVSS version. The band and vector edits may have occurred separately. | Time to revision 38 days |
| 2026-05-08published 2026-04-07 | Advisory severity changed | GHSA-767m-xrhc-fxm7CVE-2026-41359 | whole advisoryhigh | stated at publication LOW, now states HIGHA vector changed on a shared CVSS version. The band and vector edits may have occurred separately. | Time to revision 31 days |
| 2026-05-08published 2026-05-05 | Advisory severity changed | GHSA-gwfr-jfjf-92vvCVE-2026-7317 | whole advisorylow | stated at publication HIGH, now states LOWA vector changed on a shared CVSS version. The band and vector edits may have occurred separately. | Time to revision 3 days |
| 2026-05-08published 2026-05-05 | Advisory severity changed | GHSA-5mrq-x3x5-8v8fCVE-2026-40934 | whole advisoryhigh | stated at publication MODERATE, now states HIGHA CVSS version was added; the existing vectors stayed the same. | Time to revision 3 days |
| 2026-05-08published 2026-04-30 | Advisory severity changed | GHSA-5vh4-rgv7-p9g4CVE-2026-39383 | whole advisorymoderate | stated at publication HIGH, now states MODERATEA CVSS version was added; the existing vectors stayed the same. | Time to revision 8 days |
| 2026-05-08published 2026-04-30 | Advisory severity changed | GHSA-5q7p-7jgv-ww56CVE-2026-40280 | whole advisoryhigh | stated at publication CRITICAL, now states HIGHA CVSS version was added; the existing vectors stayed the same. | Time to revision 8 days |
| 2026-05-08published 2026-04-29 | Advisory severity changed | GHSA-q4q6-r8wh-5cghCVE-2026-34084 | whole advisorycritical | stated at publication HIGH, now states CRITICALNo CVSS vector was stated in the first observed version. | Time to revision 9 days |
| 2026-05-08published 2026-04-17 | Advisory severity changed | GHSA-mr34-9552-qr95CVE-2026-41389 | whole advisorymoderate | stated at publication HIGH, now states MODERATEA vector changed on a shared CVSS version. The band and vector edits may have occurred separately. | Time to revision 20 days |
| 2026-05-08published 2023-11-27 | Advisory withdrawn | GHSA-jpr7-q523-hx25 | whole advisoryhigh | withdrawn 2026-05-08 | Time to revision 893 days |
| 2026-05-08published 2024-03-02 | Advisory withdrawn | GHSA-jr22-8qgm-4q87 | whole advisoryhigh | withdrawn 2026-05-08 | Time to revision 798 days |
Two units, never added: changes to a CVE record or KEV entry, and changes to a GitHub advisory. 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 →