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. |
|---|---|---|---|---|
| Mon 31 Aug 2026· 1 change | ||||
| 2026-08-31 | CVE-2024-7806 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 529 days |
| Tue 18 Aug 2026· 1 change | ||||
| 2026-08-18 | CVE-2026-12243 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 49 days |
| Thu 13 Aug 2026· 10 changes | ||||
| 2026-08-13 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 55 to 673 days | |
| 2026-08-13 | CVE-2024-12534 | same vendor as the line above | same change as the line above | Time to revision 511 days |
| 2026-08-13 | CVE-2024-12537 | same vendor as the line above | same change as the line above | Time to revision 511 days |
| 2026-08-13 | CVE-2024-7036 | same vendor as the line above | same change as the line above | Time to revision 511 days |
| 2026-08-13 | CVE-2024-7037 | same vendor as the line above | same change as the line above | Time to revision 673 days |
| 2026-08-13 | CVE-2024-7045 | same vendor as the line above | same change as the line above | Time to revision 511 days |
| 2026-08-13 | CVE-2024-7046 | same vendor as the line above | same change as the line above | Time to revision 511 days |
| 2026-08-13 | CVE-2024-7053 | same vendor as the line above | same change as the line above | Time to revision 511 days |
| 2026-08-13 | CVE-2024-7990 | same vendor as the line above | same change as the line above | Time to revision 511 days |
| 2 more rows in this change are not listed here. Open all 10 rows → | ||||
| Thu 16 Jul 2026· 6 changes | ||||
| 2026-07-16 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 483 to 645 days | |
| 2026-07-16 | CVE-2024-7033 | same vendor as the line above | same change as the line above | Time to revision 483 days |
| 2026-07-16 | CVE-2024-7034 | same vendor as the line above | same change as the line above | Time to revision 483 days |
| 2026-07-16 | CVE-2024-7038 | same vendor as the line above | same change as the line above | Time to revision 645 days |
| 2026-07-16 | CVE-2024-7039 | same vendor as the line above | same change as the line above | Time to revision 483 days |
| 2026-07-16 | CVE-2024-7040 | same vendor as the line above | same change as the line above | Time to revision 483 days |
| 2026-07-16 | CVE-2024-7959 | same vendor as the line above | same change as the line above | Time to revision 483 days |
| Tue 20 May 2025· 1 change | ||||
| 2025-05-20 | CVE-2025-0782 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 18 days |
| Tue 15 Apr 2025· 11 changes | ||||
| 2025-04-152 commits | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 26 days | |
| 2025-04-15 | CVE-2024-12759 | same vendor as the line above | same change as the line above | Time to revision 26 days |
| 2025-04-15 | CVE-2024-12760 | same vendor as the line above | same change as the line above | Time to revision 26 days |
| 2025-04-15 | CVE-2024-12868 | same vendor as the line above | same change as the line above | Time to revision 26 days |
| 2025-04-15 | CVE-2025-0313 | same vendor as the line above | same change as the line above | Time to revision 26 days |
| 2025-04-15 | CVE-2025-0655 | same vendor as the line above | same change as the line above | Time to revision 26 days |
| 2025-04-15 | CVE-2024-11040 | same vendor as the line above | same change as the line above | Time to revision 26 days |
| 2025-04-15 | CVE-2024-7773 | same vendor as the line above | same change as the line above | Time to revision 26 days |
| 2025-04-15 | CVE-2024-7999 | same vendor as the line above | same change as the line above | Time to revision 26 days |
| 3 more rows in this change are not listed here. Open all 11 rows → | ||||
| Thu 10 Apr 2025· 1 change | ||||
| 2025-04-10 | CVE-2024-9052 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 21 days |
| Tue 1 Apr 2025· 1 change | ||||
| 2025-04-01 | CVE-2024-7804 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 12 days |
| Wed 26 Mar 2025· 2 changes | ||||
| 2025-03-262 commits | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 6 days | |
| 2025-03-26 | CVE-2024-9880 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2025-03-26 | CVE-2024-10096 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| Wed 2 Oct 2024· 1 change | ||||
| 2024-10-02 | CVE-2024-5480 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 118 days |
| Wed 17 Jul 2024· 2 changes | ||||
| 2024-07-172 commits | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 14 to 23 days | |
| 2024-07-17 | CVE-2024-5887 | same vendor as the line above | same change as the line above | Time to revision 14 days |
| 2024-07-17 | CVE-2024-4460 | same vendor as the line above | same change as the line above | Time to revision 23 days |
| Fri 7 Jun 2024· 4 changes | ||||
| 2024-06-073 commits | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 1 to 58 days | |
| 2024-06-07 | CVE-2024-1665 | same vendor as the line above | same change as the line above | Time to revision 53 days |
| 2024-06-07 | CVE-2024-4153 | same vendor as the line above | same change as the line above | Time to revision 16 days |
| 2024-06-07 | CVE-2024-5132 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2024-06-07 | CVE-2024-1599 | same vendor as the line above | same change as the line above | Time to revision 58 days |
| Mon 20 May 2024· 1 change | ||||
| 2024-05-20 | CVE-2024-4642 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 4 days |
| Mon 8 Apr 2024· 1 change | ||||
| 2024-04-08 | CVE-2024-0968 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 37 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 →