Every change, newest first
| 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. |
|---|---|---|---|---|---|
| Mon 10 Aug 2026· 4 changes | |||||
| 2026-08-10 | Affected range extended | CVE-2025-12026 | watchguardfireware os | stated at publication 12.11.4, now states 12.11.5Release branch starts at 12.0. | Time to revision 249 days |
| 2026-08-10 | Affected range extended | CVE-2025-11838 | watchguardfireware os | stated at publication 2025.1.2, now states 2025.1.3Release branch starts at 2025.1. | Time to revision 249 days |
| 2026-08-10 | Affected range extended | CVE-2025-1547 | watchguardfireware os | stated at publication 12.5.12+701324, now states 12.11.3Release branch starts at 12.0. | Time to revision 249 days |
| 2026-08-10 | Product added | CVE-2026-13079 | not named as affected at publication, now names mobile vpn with ssl client | Time to revision 39 days | |
| Sat 8 Aug 2026· 4 changes | |||||
| 2026-08-08 | Fix version moved | CVE-2025-4106 | watchguardfireware os | stated at publication 12.11.2, now states 12.11.3Release branch starts at 12.0. | Time to revision 287 days |
| 2026-08-08 | Affected range extended | CVE-2025-1239 | watchguardfireware os | stated at publication 12.5.12+701324, now states 12.11.1Release branch starts at 12.0. | Time to revision 540 days |
| 2026-08-08 | Affected range extended | CVE-2025-0178 | watchguardfireware os | stated at publication 12.5.12+701324, now states 12.11.1Release branch starts at 12.0. | Time to revision 540 days |
| 2026-08-08 | Affected range extended | CVE-2025-2781 | watchguardmobile vpn with ssl client | stated at publication 12.11, now states 12.11.2Release branch starts at 11.0. | Time to revision 497 days |
| Fri 7 Aug 2026· 6 changes | |||||
| 2026-08-07 | Affected range extended | CVE-2025-1071 | watchguardfireware os | stated at publication 12.5.12+701324, now states 12.11.1Release branch starts at 12.0. | Time to revision 539 days |
| 2026-08-07 | Product added | CVE-2024-6592 | not named as affected at publication, now names sso agent | Time to revision 682 days | |
| 2026-08-07 | Product added | CVE-2024-6592 | not named as affected at publication, now names sso client | Time to revision 682 days | |
| 2026-08-07 | Product added | CVE-2024-6593 | not named as affected at publication, now names sso agent | Time to revision 682 days | |
| 2026-08-07 | Product added | CVE-2024-6594 | not named as affected at publication, now names sso client | Time to revision 682 days | |
| 2026-08-07 | Product added | CVE-2024-8424 | not named as affected at publication, now names endpoint security | Time to revision 638 days | |
| Wed 29 Jul 2026· 1 change | |||||
| 2026-07-29 | Affected range extended | CVE-2024-4944 | watchguardmobile vpn with ssl client | stated at publication 12.10, now states 12.10.4Release branch starts at 0. | Time to revision 751 days |
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 →