Record state changed
| 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. | 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. |
|---|---|---|---|---|
| Fri 4 Sep 2026· 1 change | ||||
| 2026-09-04 | CVE-2026-18745 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 0 days |
| Thu 3 Sep 2026· 1 change | ||||
| 2026-09-03 | CVE-2026-76848 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 10 days |
| Wed 2 Sep 2026· 1 change | ||||
| 2026-09-02 | CVE-2026-39909 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 12 days |
| Tue 1 Sep 2026· 5 changes | ||||
| 2026-09-01 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 7 days | |
| 2026-09-01 | CVE-2024-58377 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | CVE-2024-58378 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | CVE-2025-71346 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | CVE-2025-71406 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | CVE-2025-71407 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| Wed 26 Aug 2026· 1 change | ||||
| 2026-08-26 | CVE-2026-74234 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 9 days |
| Wed 19 Aug 2026· 1 change | ||||
| 2026-08-19 | CVE-2026-73682 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 5 days |
| Tue 18 Aug 2026· 1 change | ||||
| 2026-08-18 | CVE-2026-73692 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 0 days |
| Mon 17 Aug 2026· 1 change | ||||
| 2026-08-17 | CVE-2026-73327 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 5 days |
| Wed 12 Aug 2026· 2 changes | ||||
| 2026-08-12 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days | |
| 2026-08-12 | CVE-2026-72745 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2026-08-12 | CVE-2026-72746 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| Thu 6 Aug 2026· 1 change | ||||
| 2026-08-06 | CVE-2026-56699 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 22 days |
| Wed 29 Jul 2026· 1 change | ||||
| 2026-07-29 | CVE-2026-62389 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 14 days |
| Fri 24 Jul 2026· 1 change | ||||
| 2026-07-24 | CVE-2026-58054 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 27 days |
| Wed 15 Jul 2026· 1 change | ||||
| 2026-07-15 | CVE-2026-56401 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 7 days |
| Thu 9 Jul 2026· 1 change | ||||
| 2026-07-09 | CVE-2026-40500 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 85 days |
| Tue 23 Jun 2026· 1 change | ||||
| 2026-06-23 | CVE-2026-56120 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 0 days |
| Fri 29 May 2026· 3 changes | ||||
| 2026-05-29 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 53 days | |
| 2026-05-29 | CVE-2026-35020 | same vendor as the line above | same change as the line above | Time to revision 53 days |
| 2026-05-29 | CVE-2026-35021 | same vendor as the line above | same change as the line above | Time to revision 53 days |
| 2026-05-29 | CVE-2026-35022 | same vendor as the line above | same change as the line above | Time to revision 53 days |
| Wed 13 May 2026· 1 change | ||||
| 2026-05-13 | CVE-2026-8449 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| Wed 1 Apr 2026· 2 changes | ||||
| 2026-04-01 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days | |
| 2026-04-01 | CVE-2026-34508 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2026-04-01 | CVE-2026-34509 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| Wed 25 Mar 2026· 1 change | ||||
| 2026-03-25 | CVE-2025-71275 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| Mon 23 Mar 2026· 17 changes | ||||
| 2026-03-23 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 0 days | |
| 2026-03-23 | CVE-2026-22173 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | CVE-2026-28455 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | CVE-2026-28483 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | CVE-2026-32012 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | CVE-2026-32047 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | CVE-2026-32066 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | CVE-2026-32900 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | CVE-2026-32901 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 9 more rows in this change are not listed here. Open all 17 rows → | ||||
| Fri 6 Mar 2026· 1 change | ||||
| 2026-03-06 | CVE-2026-28484 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| Thu 19 Feb 2026· 6 changes | ||||
| 2026-02-192 commits | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 0 days | |
| 2026-02-19 | CVE-2025-71247 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-02-19 | CVE-2025-71248 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-02-19 | CVE-2025-71249 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-02-19 | CVE-2025-71250 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-02-19 | CVE-2025-71245 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-02-19 | CVE-2025-71246 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| Sat 3 Jan 2026· 1 change | ||||
| 2026-01-03 | CVE-2025-34171 | whole record VulnCheck | stated at publication REJECTED, now states PUBLISHED | Time to revision 0 days |
| Wed 24 Dec 2025· 2 changes | ||||
| 2025-12-24 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 9 days | |
| 2025-12-24 | CVE-2025-34411 | same vendor as the line above | same change as the line above | Time to revision 9 days |
| 2025-12-24 | CVE-2025-34412 | same vendor as the line above | same change as the line above | Time to revision 9 days |
| Fri 19 Dec 2025· 1 change | ||||
| 2025-12-19 | CVE-2025-34294 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 52 days |
| Thu 4 Dec 2025· 1 change | ||||
| 2025-12-04 | CVE-2025-34138 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 132 days |
| Tue 2 Dec 2025· 1 change | ||||
| 2025-12-02 | CVE-2025-34351 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 6 days |
| Mon 10 Nov 2025· 1 change | ||||
| 2025-11-10 | CVE-2024-58272 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 11 days |
| Fri 7 Nov 2025· 2 changes | ||||
| 2025-11-07 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 8 days | |
| 2025-11-07 | CVE-2025-34249 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2025-11-07 | CVE-2025-34269 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| Thu 9 Oct 2025· 2 changes | ||||
| 2025-10-092 commits | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 2 to 100 days | |
| 2025-10-09 | CVE-2025-34252 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2025-10-09 | CVE-2025-34052 | same vendor as the line above | same change as the line above | Time to revision 100 days |
| Thu 24 Jul 2025· 3 changes | ||||
| 2025-07-24 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 21 days | |
| 2025-07-24 | CVE-2025-34090 | same vendor as the line above | same change as the line above | Time to revision 21 days |
| 2025-07-24 | CVE-2025-34091 | same vendor as the line above | same change as the line above | Time to revision 21 days |
| 2025-07-24 | CVE-2025-34092 | same vendor as the line above | same change as the line above | Time to revision 21 days |
| Wed 16 Jul 2025· 3 changes | ||||
| 2025-07-16 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 8 days | |
| 2025-07-16 | CVE-2025-34083 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2025-07-16 | CVE-2025-34084 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2025-07-16 | CVE-2025-34085 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| Thu 10 Jul 2025· 1 change | ||||
| 2025-07-10 | CVE-2025-34075 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 7 days |
| Fri 4 Apr 2025· 1 change | ||||
| 2025-04-04 | CVE-2025-2825 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 9 days |
This kind is counted once per CVE record, so changes and records are the same number here. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
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 →