Every change, newest first
These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.
One change, in full: Product added: 6 products named as affected from lantronix. Products named as affected in 8 CVE records, across 6 products: 18 rows in all, one per record and product. Drawn here as 5 lines, one per product. Back to the ledger
| 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. |
|---|---|---|---|---|---|
| 2026-09-042 commits | Product added | mitre | not named as affected at publication, now names eds3000ps seriesBranches and original-value intervals are stated on each row.not counted: No products named at publication | Days to revision 178 | |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67041 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-70082 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67039 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | Product added | CVE-2025-67038 | mitre | not named as affected at publication, now names e210 series and 1 morenot counted: No products named at publication | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67038 | same vendor as the line above | not named as affected at publication, now names e210 seriesNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67038 | same vendor as the line above | not named as affected at publication, now names e220 seriesNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-044 commits | Product added | mitre | not named as affected at publication, now names eds5000 seriesBranches and original-value intervals are stated on each row.not counted: No products named at publication | Days to revision 178 | |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67038 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67036 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67037 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67035 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67034 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-043 commits | Product added | mitre | not named as affected at publication, now names g520 seriesBranches and original-value intervals are stated on each row.not counted: No products named at publication | Days to revision 178 | |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67038 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67036 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67037 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67034 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-043 commits | Product added | mitre | not named as affected at publication, now names x300 seriesBranches and original-value intervals are stated on each row.not counted: No products named at publication | Days to revision 178 | |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67038 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67036 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67037 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
| 2026-09-04 | same kind of change as the line above | CVE-2025-67034 | same vendor as the line above | same change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Days to revision 178 |
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 or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
Data sources and quality
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 →