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. |
|---|---|---|---|---|---|
| Fri 4 Sep 2026· 4 changes | |||||
| 2026-09-04 | Product added | VulnCheck | not named as affected at publication, now names gfi clearview | Time to revision 0 days | |
| 2026-09-04 | same kind of change as the line above | CVE-2026-74235 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-09-04 | same kind of change as the line above | CVE-2026-74236 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-09-04 | same kind of change as the line above | CVE-2026-74237 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-09-04 | Record state changed | 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 | Record state changed | 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 | Record state changed | 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 | Record state changed | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 7 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2024-58377 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2024-58378 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2025-71346 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2025-71406 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2025-71407 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| Mon 31 Aug 2026· 2 changes | |||||
| 2026-08-31 | Product added | CVE-2026-71960 | VulnCheck | not named as affected at publication, now names p5 v1.1 | Time to revision 12 days |
| 2026-08-31 | CVSS base score changed | CVE-2026-73055 | whole record VulnCheck | stated at publication 9.3, now states 6.3CVSS v4.0 · base scoreCriticalMedium | Time to revision 16 days |
| Fri 28 Aug 2026· 3 changes | |||||
| 2026-08-28 | CVSS base score changed | CVE-2026-74887 | whole record VulnCheck | stated at publication 9.3, now states 6.3CVSS v4.0 · base scoreCriticalMedium | Time to revision 11 days |
| 2026-08-28 | CVSS base score changed | CVE-2026-73626 | whole record VulnCheck | stated at publication 0.0, now states 7.7CVSS v4.0 · base scoreNoneHigh | Time to revision 15 days |
| 2026-08-28 | CVSS base score changed | CVE-2026-80200 | whole record VulnCheck | stated at publication 0.0, now states 5.3CVSS v4.0 · base scoreNoneMedium | Time to revision 3 days |
| Wed 26 Aug 2026· 2 changes | |||||
| 2026-08-26 | CVSS base score changed | CVE-2026-5917 | whole record VulnCheck | stated at publication 9.6, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 15 days |
| 2026-08-26 | Record state changed | CVE-2026-74234 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 9 days |
| Mon 24 Aug 2026· 13 changes | |||||
| 2026-08-24 | CVSS base score changed | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 to 190 days | |
| 2026-08-24 | same kind of change as the line above | CVE-2026-26369 | same vendor as the line above | same change as the line above | Time to revision 190 days |
| 2026-08-24 | same kind of change as the line above | CVE-2026-34100 | same vendor as the line above | same change as the line above | Time to revision 54 days |
| 2026-08-24 | same kind of change as the line above | CVE-2026-34101 | same vendor as the line above | same change as the line above | Time to revision 54 days |
| 2026-08-24 | same kind of change as the line above | CVE-2026-34102 | same vendor as the line above | same change as the line above | Time to revision 54 days |
| 2026-08-24 | same kind of change as the line above | CVE-2026-34103 | same vendor as the line above | same change as the line above | Time to revision 54 days |
| 2026-08-24 | same kind of change as the line above | CVE-2026-34104 | same vendor as the line above | same change as the line above | Time to revision 54 days |
| 2026-08-24 | same kind of change as the line above | CVE-2026-34105 | same vendor as the line above | same change as the line above | Time to revision 54 days |
| 2026-08-24 | same kind of change as the line above | CVE-2026-39910 | same vendor as the line above | same change as the line above | Time to revision 77 days |
| 5 more rows in this change are not listed here. Open all 13 rows → | |||||
| Wed 19 Aug 2026· 1 change | |||||
| 2026-08-19 | Record state changed | 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 | Record state changed | 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 | Record state changed | CVE-2026-73327 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 5 days |
| Fri 14 Aug 2026· 1 change | |||||
| 2026-08-14 | Product added | CVE-2026-73039 | VulnCheck | not named as affected at publication, now names streama | Time to revision 1 days |
| Thu 13 Aug 2026· 1 change | |||||
| 2026-08-13 | Affected range extended | CVE-2026-70556 | hubzillahubzilla VulnCheck | stated at publication 11.2.1, now states 11.4Release branch starts at 0. | Time to revision 7 days |
| Wed 12 Aug 2026· 2 changes | |||||
| 2026-08-12 | Record state changed | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days | |
| 2026-08-12 | same kind of change as the line above | CVE-2026-72745 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-72746 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| Tue 11 Aug 2026· 2 changes | |||||
| 2026-08-11 | Fix version moved | usmannasircyberpanel VulnCheck | stated at publication 2.4.4, now states 2.4.5Release branch starts at 0. | Time to revision 109 days | |
| 2026-08-11 | same kind of change as the line above | CVE-2026-41472 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 109 days |
| 2026-08-11 | same kind of change as the line above | CVE-2026-41473 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 109 days |
| Mon 10 Aug 2026· 1 change | |||||
| 2026-08-10 | CVSS base score changed | CVE-2026-66738 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 0 days |
| Thu 6 Aug 2026· 1 change | |||||
| 2026-08-06 | Record state changed | CVE-2026-56699 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 22 days |
| Fri 31 Jul 2026· 1 change | |||||
| 2026-07-31 | Product added | CVE-2026-66420 | VulnCheck | not named as affected at publication, now names meshcentral | Time to revision 1 days |
| Wed 29 Jul 2026· 1 change | |||||
| 2026-07-29 | Record state changed | 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 | Record state changed | CVE-2026-58054 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 27 days |
| Thu 23 Jul 2026· 1 change | |||||
| 2026-07-23 | CVSS base score changed | CVE-2026-63764 | whole record VulnCheck | stated at publication 9.3, now states 8.6CVSS v3.1 · base scoreCriticalHigh | Time to revision 2 days |
| Tue 21 Jul 2026· 1 change | |||||
| 2026-07-21 | Fix version moved | CVE-2026-64824 | home-assistanthome assistant core VulnCheck | stated at publication 2026.6.0, now states 2026.7.0Release branch starts at 0.same day | Time to revision 0 days |
| Mon 20 Jul 2026· 1 change | |||||
| 2026-07-20 | Affected range extended | CVE-2026-57956 | signozsignoz VulnCheck | stated at publication 0.130.1, now states 0.133.0Release branch starts at 0. | Time to revision 21 days |
| Sat 18 Jul 2026· 1 change | |||||
| 2026-07-18 | CVSS base score changed | CVE-2026-57857 | whole record VulnCheck | stated at publication 7.2, now states 5.1CVSS v4.0 · base scoreHighMedium | Time to revision 0 days |
| Wed 15 Jul 2026· 1 change | |||||
| 2026-07-15 | Record state changed | 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 | Record state changed | CVE-2026-40500 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 85 days |
| Wed 8 Jul 2026· 1 change | |||||
| 2026-07-08 | CVSS base score changed | CVE-2026-60104 | whole record VulnCheck | stated at publication 8.5, now states 9.3CVSS v4.0 · base scoreHighCritical | Time to revision 0 days |
| Thu 2 Jul 2026· 2 changes | |||||
| 2026-07-02 | CVSS base score changed | CVE-2026-56371 | whole record VulnCheck | stated at publication 0.0, now states 6.9CVSS v4.0 · base scoreNoneMedium | Time to revision 9 days |
| 2026-07-02 | CVSS base score changed | CVE-2026-56379 | whole record VulnCheck | stated at publication 0.0, now states 9.2CVSS v4.0 · base scoreNoneCritical | Time to revision 9 days |
| Tue 30 Jun 2026· 1 change | |||||
| 2026-06-30 | Product added | CVE-2026-54371 | VulnCheck | not named as affected at publication, now names attr | Time to revision 1 days |
| Thu 25 Jun 2026· 1 change | |||||
| 2026-06-25 | Product added | CVE-2026-56115 | VulnCheck | not named as affected at publication, now names bootimus | Time to revision 2 days |
| Wed 24 Jun 2026· 1 change | |||||
| 2026-06-24 | Product added | CVE-2026-56274 | VulnCheck | not named as affected at publication, now names flowise components | Time to revision 1 days |
| Tue 23 Jun 2026· 4 changes | |||||
| 2026-06-23 | Fix version moved | CVE-2026-56784 | openremoteopenremote VulnCheck | stated at publication 1.24.2, now states 1.25.0Release branch starts at 0.same day | Time to revision 0 days |
| 2026-06-23 | Product added | CVE-2026-49494 | VulnCheck | not named as affected at publication, now names xcitium client security (xcs) | Time to revision 16 days |
| 2026-06-23 | CVSS base score changed | CVE-2026-56104 | whole record VulnCheck | stated at publication 9.1, now states 8.8CVSS v4.0 · base scoreCriticalHigh | Time to revision 1 days |
| 2026-06-23 | Record state changed | CVE-2026-56120 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 0 days |
| Wed 17 Jun 2026· 1 change | |||||
| 2026-06-17 | CVSS base score changed | CVE-2026-55202 | whole record VulnCheck | stated at publication 9.3, now states 8.8CVSS v4.0 · base scoreCriticalHigh | Time to revision 0 days |
| Sat 13 Jun 2026· 1 change | |||||
| 2026-06-13 | Product added | CVE-2026-53833 | VulnCheck | not named as affected at publication, now names openclaw | Time to revision 1 days |
| Fri 29 May 2026· 3 changes | |||||
| 2026-05-29 | Record state changed | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 53 days | |
| 2026-05-29 | same kind of change as the line above | CVE-2026-35020 | same vendor as the line above | same change as the line above | Time to revision 53 days |
| 2026-05-29 | same kind of change as the line above | CVE-2026-35021 | same vendor as the line above | same change as the line above | Time to revision 53 days |
| 2026-05-29 | same kind of change as the line above | CVE-2026-35022 | same vendor as the line above | same change as the line above | Time to revision 53 days |
| Thu 28 May 2026· 2 changes | |||||
| 2026-05-28 | Product added | CVE-2026-40034 | VulnCheck | not named as affected at publication, now names gix and 1 more | Time to revision 2 days |
| 2026-05-28 | same kind of change as the line above | CVE-2026-40034 | same vendor as the line above | not named as affected at publication, now names gix | Time to revision 2 days |
| 2026-05-28 | same kind of change as the line above | CVE-2026-40034 | same vendor as the line above | not named as affected at publication, now names gix-submodule | Time to revision 2 days |
| Tue 26 May 2026· 1 change | |||||
| 2026-05-26 | CVSS base score changed | CVE-2026-41947 | whole record VulnCheck | stated at publication 9.1, now states 9.3CVSS v4.0 · base scoreCriticalCritical | Time to revision 8 days |
| Wed 13 May 2026· 2 changes | |||||
| 2026-05-13 | CVSS base score changed | CVE-2026-44113 | whole record VulnCheck | stated at publication 6.0, now states 8.3CVSS v4.0 · base scoreMediumHigh | Time to revision 7 days |
| 2026-05-13 | Record state changed | CVE-2026-8449 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| Tue 12 May 2026· 7 changes | |||||
| 2026-05-12 | CVSS base score changed | CVE-2023-53878 | whole record VulnCheck | stated at publication 7.3, now states 6.9CVSS v4.0 · base scoreHighMedium | Time to revision 148 days |
| 2026-05-12 | CVSS base score changed | CVE-2023-53879 | whole record VulnCheck | stated at publication 5.3, now states 6.7CVSS v4.0 · base scoreMediumMedium | Time to revision 148 days |
| 2026-05-12 | CVSS base score changed | whole record VulnCheck | stated at publication 7.2, now states 8.6CVSS v4.0 · base scoreHighHigh | Time to revision 148 days | |
| 2026-05-12 | same kind of change as the line above | CVE-2023-53883 | same vendor as the line above | same change as the line above | Time to revision 148 days |
| 2026-05-12 | same kind of change as the line above | CVE-2023-53885 | same vendor as the line above | same change as the line above | Time to revision 148 days |
| 2026-05-12 | same kind of change as the line above | CVE-2023-53888 | same vendor as the line above | same change as the line above | Time to revision 148 days |
| 2026-05-12 | same kind of change as the line above | CVE-2023-53889 | same vendor as the line above | same change as the line above | Time to revision 148 days |
| 2026-05-12 | CVSS base score changed | CVE-2023-53886 | whole record VulnCheck | stated at publication 5.7, now states 5.1CVSS v4.0 · base scoreMediumMedium | Time to revision 148 days |
| Fri 1 May 2026· 1 change | |||||
| 2026-05-01 | Affected range extended | CVE-2026-39911 | hashgraphguardian VulnCheck | stated at publication 3.5.0, now states 3.5.1Release branch starts at 0. | Time to revision 22 days |
| Wed 22 Apr 2026· 3 changes | |||||
| 2026-04-22 | Product added | CVE-2026-22191 | VulnCheck | not named as affected at publication, now names sicuroweb (sicuro24) | Time to revision 41 days |
| 2026-04-22 | Product added | VulnCheck | not named as affected at publication, now names snmp web pro | Time to revision 41 days | |
| 2026-04-22 | same kind of change as the line above | CVE-2026-22192 | same vendor as the line above | same change as the line above | Time to revision 41 days |
| 2026-04-22 | same kind of change as the line above | CVE-2026-22199 | same vendor as the line above | same change as the line above | Time to revision 41 days |
| Thu 2 Apr 2026· 2 changes | |||||
| 2026-04-02 | Product added | CVE-2024-14033 | VulnCheck | not named as affected at publication, now names hirschmann eaglesdv | Time to revision 0 days |
| 2026-04-02 | CVSS base score changed | CVE-2023-7343 | whole record VulnCheck | stated at publication 7.8, now states 8.5CVSS v4.0 · base scoreHighHigh | Time to revision 0 days |
| Wed 1 Apr 2026· 2 changes | |||||
| 2026-04-01 | Record state changed | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days | |
| 2026-04-01 | same kind of change as the line above | CVE-2026-34508 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2026-04-01 | same kind of change as the line above | CVE-2026-34509 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| Wed 25 Mar 2026· 8 changes | |||||
| 2026-03-25 | CVSS base score changed | CVE-2026-22181 | whole record VulnCheck | stated at publication 6.4, now states 7.6CVSS v3.1 · base scoreMediumHigh | Time to revision 8 days |
| 2026-03-25 | CVSS base score changed | CVE-2026-27183 | whole record VulnCheck | stated at publication 4.5, now states 5.3CVSS v3.1 · base scoreMediumMedium | Time to revision 2 days |
| 2026-03-25 | CVSS base score changed | CVE-2026-27524 | whole record VulnCheck | stated at publication 3.1, now states 4.3CVSS v3.1 · base scoreLowMedium | Time to revision 8 days |
| 2026-03-25 | CVSS base score changed | CVE-2026-31996 | whole record VulnCheck | stated at publication 3.6, now states 4.4CVSS v3.1 · base scoreLowMedium | Time to revision 7 days |
| 2026-03-25 | CVSS base score changed | CVE-2026-32000 | whole record VulnCheck | stated at publication 6.3, now states 7.1CVSS v3.1 · base scoreMediumHigh | Time to revision 7 days |
| 2026-03-25 | CVSS base score changed | CVE-2026-32019 | whole record VulnCheck | stated at publication 6.0, now states 7.4CVSS v3.1 · base scoreMediumHigh | Time to revision 6 days |
| 2026-03-25 | CVSS base score changed | CVE-2026-32034 | whole record VulnCheck | stated at publication 6.8, now states 8.1CVSS v3.1 · base scoreMediumHigh | Time to revision 6 days |
| 2026-03-25 | Record state changed | 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 | Record state changed | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 0 days | |
| 2026-03-23 | same kind of change as the line above | CVE-2026-22173 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | same kind of change as the line above | CVE-2026-28455 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | same kind of change as the line above | CVE-2026-28483 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | same kind of change as the line above | CVE-2026-32012 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | same kind of change as the line above | CVE-2026-32047 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | same kind of change as the line above | CVE-2026-32066 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | same kind of change as the line above | CVE-2026-32900 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-03-23 | same kind of change as the line above | 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 → | |||||
| Tue 10 Mar 2026· 1 change | |||||
| 2026-03-10 | CVSS base score changed | CVE-2026-29000 | whole record VulnCheck | stated at publication 10.0, now states 9.3CVSS v4.0 · base scoreCriticalCritical | Time to revision 6 days |
| Fri 6 Mar 2026· 1 change | |||||
| 2026-03-06 | Record state changed | CVE-2026-28484 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| Mon 2 Mar 2026· 4 changes | |||||
| 2026-03-02 | CVSS base score changed | whole record VulnCheck | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 6 to 11 days | |
| 2026-03-02 | same kind of change as the line above | CVE-2025-71241 | same vendor as the line above | same change as the line above | Time to revision 11 days |
| 2026-03-02 | same kind of change as the line above | CVE-2026-26223 | same vendor as the line above | same change as the line above | Time to revision 11 days |
| 2026-03-02 | same kind of change as the line above | CVE-2026-27474 | same vendor as the line above | same change as the line above | Time to revision 11 days |
| 2026-03-02 | same kind of change as the line above | CVE-2026-27517 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| Tue 24 Feb 2026· 1 change | |||||
| 2026-02-24 | Product added | CVE-2026-23693 | VulnCheck | not named as affected at publication, now names elementskit elementor addons – advanced widgets & templates addons for elementor | Time to revision 1 days |
| Thu 19 Feb 2026· 6 changes | |||||
| 2026-02-192 commits | Record state changed | 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 | same kind of change as the line above | CVE-2025-71247 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-02-19 | same kind of change as the line above | CVE-2025-71248 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-02-19 | same kind of change as the line above | CVE-2025-71249 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-02-19 | same kind of change as the line above | CVE-2025-71250 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-02-19 | same kind of change as the line above | CVE-2025-71245 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-02-19 | same kind of change as the line above | CVE-2025-71246 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| Mon 2 Feb 2026· 1 change | |||||
| 2026-02-02 | CVSS base score changed | CVE-2023-54328 | whole record VulnCheck | stated at publication 9.8, now states 6.5CVSS v3.1 · base scoreCriticalMedium | Time to revision 20 days |
| Mon 26 Jan 2026· 1 change | |||||
| 2026-01-26 | CVSS base score changed | CVE-2023-54337 | whole record VulnCheck | stated at publication 7.5, now states 9.1CVSS v3.1 · base scoreHighCritical | Time to revision 13 days |
| Thu 15 Jan 2026· 1 change | |||||
| 2026-01-15 | CVSS base score changed | CVE-2026-22184 | whole record VulnCheck | stated at publication 9.3, now states 4.6CVSS v4.0 · base scoreCriticalMedium | Time to revision 8 days |
| Wed 14 Jan 2026· 5 changes | |||||
| 2026-01-14 | Affected range extended | gestsupgestsup VulnCheck | stated at publication 3.2.56, now states 3.2.60Release branch starts at 0. | Time to revision 5 days | |
| 2026-01-14 | same kind of change as the line above | CVE-2026-22194 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 5 days |
| 2026-01-14 | same kind of change as the line above | CVE-2026-22195 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 5 days |
| 2026-01-14 | same kind of change as the line above | CVE-2026-22197 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 5 days |
| 2026-01-14 | same kind of change as the line above | CVE-2026-22198 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 5 days |
| 2026-01-14 | same kind of change as the line above | CVE-2026-22196 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 5 days |
| Mon 12 Jan 2026· 1 change | |||||
| 2026-01-12 | CVSS base score changed | CVE-2026-22185 | whole record VulnCheck | stated at publication 7.0, now states 4.6CVSS v4.0 · base scoreHighMediumOriginal value first replaced 2026-01-08; this value first seen 2026-01-12. | Time to revision 1 days |
| Thu 8 Jan 2026· 13 changes | |||||
| 2026-01-08 | Product added | CVE-2026-0625 | VulnCheck | not named as affected at publication, now names dir-600 and 12 more | Time to revision 3 days |
| 2026-01-08 | same kind of change as the line above | CVE-2026-0625 | same vendor as the line above | not named as affected at publication, now names dir-600 | Time to revision 3 days |
| 2026-01-08 | same kind of change as the line above | CVE-2026-0625 | same vendor as the line above | not named as affected at publication, now names dir-608 | Time to revision 3 days |
| 2026-01-08 | same kind of change as the line above | CVE-2026-0625 | same vendor as the line above | not named as affected at publication, now names dir-610 | Time to revision 3 days |
| 2026-01-08 | same kind of change as the line above | CVE-2026-0625 | same vendor as the line above | not named as affected at publication, now names dir-611 | Time to revision 3 days |
| 2026-01-08 | same kind of change as the line above | CVE-2026-0625 | same vendor as the line above | not named as affected at publication, now names dir-615 | Time to revision 3 days |
| 2026-01-08 | same kind of change as the line above | CVE-2026-0625 | same vendor as the line above | not named as affected at publication, now names dir-905l | Time to revision 3 days |
| 2026-01-08 | same kind of change as the line above | CVE-2026-0625 | same vendor as the line above | not named as affected at publication, now names dns-320 | Time to revision 3 days |
| 2026-01-08 | same kind of change as the line above | CVE-2026-0625 | same vendor as the line above | not named as affected at publication, now names dns-325 | Time to revision 3 days |
| 5 more rows in this change are not listed here. Open all 13 rows → | |||||
| Sat 3 Jan 2026· 1 change | |||||
| 2026-01-03 | Record state changed | CVE-2025-34171 | whole record VulnCheck | stated at publication REJECTED, now states PUBLISHED | Time to revision 0 days |
| Sat 27 Dec 2025· 17 changes | |||||
| 2025-12-27 | CVSS base score changed | CVE-2023-53905 | whole record VulnCheck | stated at publication 8.8, now states 8.0CVSS v3.1 · base scoreHighHigh | Time to revision 10 days |
| 2025-12-27 | CVSS base score changed | CVE-2023-53930 | whole record VulnCheck | stated at publication 9.8, now states 7.5CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2025-12-272 commits | CVSS base score changed | whole record VulnCheck | stated at publication 6.4, now states 5.4CVSS v3.1 · base scoreMediumMediumBranches and original-value intervals are stated on each row. | Time to revision 5 to 8 days | |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53976 | same vendor as the line above | same change as the line above | Time to revision 5 days |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53977 | same vendor as the line above | same change as the line above | Time to revision 5 days |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53978 | same vendor as the line above | same change as the line above | Time to revision 5 days |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53953 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2025-12-27 | CVSS base score changed | whole record VulnCheck | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 9 to 10 days | |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53918 | same vendor as the line above | same change as the line above | Time to revision 10 days |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53925 | same vendor as the line above | same change as the line above | Time to revision 10 days |
| 2025-12-27 | same kind of change as the line above | CVE-2023-53931 | same vendor as the line above | same change as the line above | Time to revision 10 days |
| 2025-12-27 | same kind of change as the line above | CVE-2024-58318 | same vendor as the line above | same change as the line above | Time to revision 9 days |
| 2025-12-27 | same kind of change as the line above | CVE-2024-58319 | same vendor as the line above | same change as the line above | Time to revision 9 days |
| 2025-12-27 | CVSS base score changed | CVE-2023-53927 | whole record VulnCheck | stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium | Time to revision 10 days |
| 2025-12-27 | CVSS base score changed | CVE-2025-2292 | whole record VulnCheck | stated at publication 4.9, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 271 days |
| 2025-12-27 | CVSS base score changed | CVE-2025-2748 | whole record VulnCheck | stated at publication 6.5, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 278 days |
| 2025-12-27 | CVSS base score changed | CVE-2025-30004 | whole record VulnCheck | stated at publication 9.1, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 271 days |
| 2025-12-27 | CVSS base score changed | CVE-2025-30005 | whole record VulnCheck | stated at publication 6.7, now states 8.3CVSS v3.1 · base scoreMediumHigh | Time to revision 271 days |
| 2025-12-27 | CVSS base score changed | CVE-2025-34509 | whole record VulnCheck | stated at publication 6.5, now states 7.5CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2025-06-17; this value first seen 2025-12-27. | Time to revision 0 days |
| Wed 24 Dec 2025· 2 changes | |||||
| 2025-12-24 | Record state changed | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 9 days | |
| 2025-12-24 | same kind of change as the line above | CVE-2025-34411 | same vendor as the line above | same change as the line above | Time to revision 9 days |
| 2025-12-24 | same kind of change as the line above | CVE-2025-34412 | same vendor as the line above | same change as the line above | Time to revision 9 days |
| Tue 23 Dec 2025· 2 changes | |||||
| 2025-12-23 | Affected range extended | wb2oszdire wolf VulnCheck | stated at publication 1.8, now states 1.8.1Release branch starts at 0.same day | Time to revision 1 days | |
| 2025-12-23 | same kind of change as the line above | CVE-2025-34458 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 1 days |
| 2025-12-23 | same kind of change as the line above | CVE-2025-34457 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.same day | Time to revision 1 days |
| Fri 19 Dec 2025· 10 changes | |||||
| 2025-12-19 | Fix version moved | VulnCheck | stated at publication 20.0, now states 20.1Release branch starts at 0. | Time to revision 2 days | |
| 2025-12-19 | same kind of change as the line above | CVE-2025-34441 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | same kind of change as the line above | CVE-2025-34442 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | same kind of change as the line above | CVE-2025-34440 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | same kind of change as the line above | CVE-2025-34439 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | same kind of change as the line above | CVE-2025-34434 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | same kind of change as the line above | CVE-2025-34436 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | same kind of change as the line above | CVE-2025-34435 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 2025-12-19 | same kind of change as the line above | CVE-2025-34437 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 2 days |
| 1 more row in this change is not listed here. Open all 9 rows → | |||||
| 2025-12-19 | Record state changed | CVE-2025-34294 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 52 days |
| Thu 18 Dec 2025· 1 change | |||||
| 2025-12-18 | CVSS base score changed | CVE-2023-53741 | whole record VulnCheck | stated at publication 7.1, now states 5.1CVSS v4.0 · base scoreHighMedium | Time to revision 8 days |
| Mon 15 Dec 2025· 2 changes | |||||
| 2025-12-15 | CVSS base score changed | whole record VulnCheck | stated at publication 6.8, now states 8.4CVSS v4.0 · base scoreMediumHigh | Time to revision 5 days | |
| 2025-12-15 | same kind of change as the line above | CVE-2025-34427 | same vendor as the line above | same change as the line above | Time to revision 5 days |
| 2025-12-15 | same kind of change as the line above | CVE-2025-34428 | same vendor as the line above | same change as the line above | Time to revision 5 days |
| Thu 4 Dec 2025· 1 change | |||||
| 2025-12-04 | Record state changed | 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 | Record state changed | 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 | Record state changed | 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 | Record state changed | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 8 days | |
| 2025-11-07 | same kind of change as the line above | CVE-2025-34249 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2025-11-07 | same kind of change as the line above | CVE-2025-34269 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| Mon 3 Nov 2025· 1 change | |||||
| 2025-11-03 | CVSS base score changed | CVE-2025-34164 | whole record VulnCheck | stated at publication 8.8, now states 9.3CVSS v4.0 · base scoreHighCritical | Time to revision 66 days |
Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. 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 →