Every change, newest first

What a record said when it was published, what it says now, and the commit that changed it.

15 refused changes behind one line · newest firstCSV JSON RSS

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: Affected range extended: 2026.2 → 2026.2.1 from watchguard. The same change in 15 CVE records. Back to the ledger

Rows we checked and refused, counted nowhere published by WatchGuard, newest first, one line per change to a CVE record, 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.	Kind	Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on.	Vendor · product, 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-08-10	Affected range extended	CVE-2026-13050	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-13053	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-13054	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-13084	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-13728	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-8247	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-13368	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-13722	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-13373	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-13374	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-13376	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-13377	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-13383	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-13384	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39
2026-08-10	Affected range extended	CVE-2026-13371	watchguardfireware os	stated at publication 2026.2, now states 2026.2.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator	Days to revision 39

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.

Every kind of change

Each bar filters the ledger to that kind, and counts what it would show under the filters already on. Two units, one length scale, never a total.

To a CVE record or a KEV entry

To a GitHub advisory

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 →

Check my CVEs against these changes →