CVSS base score 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-13732 | whole record redhat | stated at publication 7.8, now states 7.0CVSS v3.1 · base scoreHighHigh | Time to revision 4 days |
| Wed 2 Sep 2026· 2 changes | ||||
| 2026-09-02 | CVE-2026-71474 | whole record redhat | stated at publication 6.3, now states 7.1CVSS v3.1 · base scoreMediumHigh | Time to revision 22 days |
| 2026-09-02 | CVE-2026-71475 | whole record redhat | stated at publication 5.0, now states 6.8CVSS v3.1 · base scoreMediumMedium | Time to revision 22 days |
| Tue 1 Sep 2026· 9 changes | ||||
| 2026-09-01 | CVE-2026-66795 | whole record redhat | stated at publication 9.1, now states 9.9CVSS v3.1 · base scoreCriticalCritical | Time to revision 15 days |
| 2026-09-01 | CVE-2026-66783 | whole record redhat | stated at publication 8.2, now states 4.4CVSS v3.1 · base scoreHighMedium | Time to revision 14 days |
| 2026-09-01 | CVE-2026-66785 | whole record redhat | stated at publication 9.9, now states 2.5CVSS v3.1 · base scoreCriticalLow | Time to revision 12 days |
| 2026-09-01 | CVE-2026-66787 | whole record redhat | stated at publication 8.7, now states 5.4CVSS v3.1 · base scoreHighMedium | Time to revision 12 days |
| 2026-09-01 | CVE-2026-66788 | whole record redhat | stated at publication 9.9, now states 3.7CVSS v3.1 · base scoreCriticalLow | Time to revision 12 days |
| 2026-09-01 | CVE-2026-66781 | whole record redhat | stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 14 days |
| 2026-09-01 | CVE-2026-66782 | whole record redhat | stated at publication 7.8, now states 5.8CVSS v3.1 · base scoreHighMedium | Time to revision 14 days |
| 2026-09-01 | CVE-2026-66780 | whole record redhat | stated at publication 9.9, now states 6.5CVSS v3.1 · base scoreCriticalMedium | Time to revision 14 days |
| 2026-09-01 | CVE-2026-6876 | whole record SN | stated at publication 8.7, now states 10.0CVSS v4.0 · base scoreHighCritical | Time to revision 5 days |
| Mon 31 Aug 2026· 2 changes | ||||
| 2026-08-31 | CVE-2026-77956 | whole record EEF | stated at publication 10.0, now states 8.9CVSS v4.0 · base scoreCriticalHigh | Time to revision 1 days |
| 2026-08-31 | 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 | 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 | 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 | CVE-2026-80200 | whole record VulnCheck | stated at publication 0.0, now states 5.3CVSS v4.0 · base scoreNoneMedium | Time to revision 3 days |
| Thu 27 Aug 2026· 4 changes | ||||
| 2026-08-27 | CVE-2026-13097 | whole record redhat | stated at publication 9.1, now states 8.7CVSS v3.1 · base scoreCriticalHigh | Time to revision 7 days |
| 2026-08-27 | CVE-2026-65660 | whole record microsoft | stated at publication 6.5, now states 8.8CVSS v3.1 · base scoreMediumHigh | Time to revision 16 days |
| 2026-08-27 | CVE-2026-10573 | whole record Rockwell | stated at publication 8.7, now states 6.3CVSS v4.0 · base scoreHighMedium | Time to revision 44 days |
| 2026-08-27 | CVE-2026-59354 | whole record vmware | stated at publication 6.1, now states 9.6CVSS v3.1 · base scoreMediumCritical | Time to revision 0 days |
| Wed 26 Aug 2026· 1 change | ||||
| 2026-08-26 | CVE-2026-5917 | whole record VulnCheck | stated at publication 9.6, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 15 days |
| Mon 24 Aug 2026· 16 changes | ||||
| 2026-08-24 | CVE-2026-78555 | whole record CIRCL | stated at publication 10.0, now states 9.4CVSS v4.0 · base scoreCriticalCritical | Time to revision 0 days |
| 2026-08-24 | CVE-2023-50176 | whole record fortinet | stated at publication 7.1, now states 4.0CVSS v3.1 · base scoreHighMedium | Time to revision 650 days |
| 2026-08-24 | CVE-2026-26369 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 190 days |
| 2026-08-24 | CVE-2026-34100 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34101 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34102 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34103 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34104 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34105 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVE-2026-39910 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 77 days |
| 2026-08-24 | CVE-2026-72822 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVE-2026-72824 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVE-2026-72826 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVE-2026-72829 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVE-2026-72830 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVE-2026-18652 | whole record rapid7 | stated at publication 4.9, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 12 days |
| Sun 23 Aug 2026· 1 change | ||||
| 2026-08-23 | CVE-2026-76613 | whole record Joomla | stated at publication 9.2, now states 8.6CVSS v4.0 · base scoreCriticalHigh | Time to revision 2 days |
| Thu 20 Aug 2026· 4 changes | ||||
| 2026-08-20 | CVE-2026-76956 | whole record mitre | stated at publication 7.5, now states 5.9CVSS v3.1 · base scoreHighMedium | Time to revision 1 days |
| 2026-08-20 | CVE-2026-54117 | whole record microsoft | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 37 days |
| 2026-08-20 | CVE-2026-54118 | whole record microsoft | stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 37 days |
| 2026-08-20 | CVE-2026-19550 | whole record redhat | stated at publication 4.3, now states 8.2CVSS v3.1 · base scoreMediumHigh | Time to revision 9 days |
| Tue 18 Aug 2026· 1 change | ||||
| 2026-08-18 | CVE-2026-73669 | whole record cisa-cg | stated at publication 6.3, now states 7.3CVSS v3.1 · base scoreMediumHigh | Time to revision 5 days |
| Fri 14 Aug 2026· 3 changes | ||||
| 2026-08-14 | CVE-2026-65796 | whole record microsoft | stated at publication 5.9, now states 8.1CVSS v3.1 · base scoreMediumHigh | Time to revision 3 days |
| 2026-08-14 | CVE-2026-44962 | whole record hackerone | stated at publication 10.0, now states 9.9CVSS v3.1 · base scoreCriticalCritical | Time to revision 77 days |
| 2026-08-14 | CVE-2026-19617 | whole record redhat | stated at publication 5.7, now states 5.5CVSS v3.1 · base scoreMediumMedium | Time to revision 0 days |
| Wed 12 Aug 2026· 3 changes | ||||
| 2026-08-12 | CVE-2026-10090 | whole record redhat | stated at publication 9.9, now states 9.0CVSS v3.1 · base scoreCriticalCritical | Time to revision 7 days |
| 2026-08-12 | CVE-2026-73434 | whole record redhat | stated at publication 7.1, now states 6.1CVSS v3.1 · base scoreHighMedium | Time to revision 0 days |
| 2026-08-12 | CVE-2026-73433 | whole record redhat | stated at publication 7.6, now states 6.6CVSS v3.1 · base scoreHighMedium | Time to revision 0 days |
| Tue 11 Aug 2026· 3 changes | ||||
| 2026-08-11 | CVE-2025-61848 | whole record fortinet | stated at publication 6.8, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 119 days |
| 2026-08-11 | CVE-2026-18635 | whole record rapid7 | stated at publication 6.2, now states 7.2CVSS v3.1 · base scoreMediumHigh | Time to revision 0 days |
| 2026-08-11 | CVE-2026-18772 | whole record samsung.tv_appliance | stated at publication 5.5, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 7 days |
| Mon 10 Aug 2026· 1 change | ||||
| 2026-08-10 | 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· 3 changes | ||||
| 2026-08-06 | CVE-2026-47991 | whole record adobe | stated at publication 4.3, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 58 days |
| 2026-08-06 | CVE-2026-48000 | whole record adobe | stated at publication 4.3, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 23 days |
| 2026-08-06 | CVE-2026-19023 | whole record HDFG | stated at publication 0.0, now states 6.8CVSS v4.0 · base scoreNoneMedium | Time to revision 1 days |
| Wed 5 Aug 2026· 14 changes | ||||
| 2026-08-05 | CVE-2026-55747 | whole record TuranSec | stated at publication 7.1, now states 6.8CVSS v3.1 · base scoreHighMedium | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71205 | whole record TuranSec | stated at publication 5.3, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71210 | whole record TuranSec | stated at publication 6.5, now states 5.3CVSS v3.1 · base scoreMediumMedium | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71211 | whole record TuranSec | stated at publication 7.7, now states 7.1CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71213 | whole record TuranSec | stated at publication 8.1, now states 9.1CVSS v3.1 · base scoreHighCritical | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71235 | whole record TuranSec | stated at publication 9.9, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71236 | whole record TuranSec | stated at publication 8.0, now states 8.7CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71239 | whole record TuranSec | stated at publication 8.8, now states 8.1CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71240 | whole record TuranSec | stated at publication 5.4, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71244 | whole record TuranSec | stated at publication 7.1, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71246 | whole record TuranSec | stated at publication 5.7, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71254 | whole record TuranSec | stated at publication 9.1, now states 9.8CVSS v3.1 · base scoreCriticalCritical | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71255 | whole record TuranSec | stated at publication 8.2, now states 8.6CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| 2026-08-05 | CVE-2026-71256 | whole record TuranSec | stated at publication 8.1, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 0 days |
| Tue 4 Aug 2026· 3 changes | ||||
| 2026-08-04 | CVE-2025-61813 | whole record adobe | stated at publication 8.2, now states 7.4CVSS v3.1 · base scoreHighHigh | Time to revision 238 days |
| 2026-08-04 | CVE-2026-47996 | whole record adobe | stated at publication 7.6, now states 6.8CVSS v3.1 · base scoreHighMedium | Time to revision 21 days |
| 2026-08-04 | CVE-2026-48322 | whole record adobe | stated at publication 9.6, now states 9.9CVSS v3.1 · base scoreCriticalCritical | Time to revision 21 days |
| Mon 3 Aug 2026· 2 changes | ||||
| 2026-08-03 | CVE-2026-47296 | whole record microsoft | stated at publication 7.8, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 20 days |
| 2026-08-03 | CVE-2026-55002 | whole record microsoft | stated at publication 7.8, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 20 days |
| Wed 29 Jul 2026· 1 change | ||||
| 2026-07-29 | CVE-2025-4318 | whole record AMZN | stated at publication 9.5, now states 9.0CVSS v4.0 · base scoreCriticalCritical | Time to revision 450 days |
| Tue 28 Jul 2026· 1 change | ||||
| 2026-07-28 | CVE-2026-12495 | whole record INCIBE | stated at publication 9.2, now states 5.3CVSS v4.0 · base scoreCriticalMedium | Time to revision 1 days |
| Fri 24 Jul 2026· 1 change | ||||
| 2026-07-24 | CVE-2026-15786 | whole record Wordfence | stated at publication 4.9, now states 4.4CVSS v3.1 · base scoreMediumMedium | Time to revision 2 days |
| Thu 23 Jul 2026· 1 change | ||||
| 2026-07-23 | CVE-2026-63764 | whole record VulnCheck | stated at publication 9.3, now states 8.6CVSS v3.1 · base scoreCriticalHigh | Time to revision 2 days |
| Wed 22 Jul 2026· 1 change | ||||
| 2026-07-22 | CVE-2026-7253 | whole record ibm | stated at publication 5.3, now states 6.0CVSS v3.1 · base scoreMediumMedium | Time to revision 30 days |
| Tue 21 Jul 2026· 1 change | ||||
| 2026-07-21 | CVE-2026-48356 | whole record adobe | stated at publication 9.6, now states 9.3CVSS v3.1 · base scoreCriticalCritical | Time to revision 7 days |
| Mon 20 Jul 2026· 1 change | ||||
| 2026-07-20 | CVE-2026-34632 | whole record adobe | stated at publication 8.2, now states 8.6CVSS v3.1 · base scoreHighHigh | Time to revision 96 days |
| Sat 18 Jul 2026· 1 change | ||||
| 2026-07-18 | CVE-2026-57857 | whole record VulnCheck | stated at publication 7.2, now states 5.1CVSS v4.0 · base scoreHighMedium | Time to revision 0 days |
| Fri 17 Jul 2026· 1 change | ||||
| 2026-07-17 | CVE-2026-7189 | whole record TR-CERT | stated at publication 8.2, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| Tue 14 Jul 2026· 1 change | ||||
| 2026-07-14 | CVE-2026-10642 | whole record zephyr | stated at publication 6.5, now states 4.6CVSS v3.1 · base scoreMediumMedium | Time to revision 20 days |
| Mon 13 Jul 2026· 1 change | ||||
| 2026-07-13 | CVE-2026-12257 | whole record INCIBE | stated at publication 5.1, now states 9.3CVSS v4.0 · base scoreMediumCritical | Time to revision 0 days |
| Thu 9 Jul 2026· 1 change | ||||
| 2026-07-09 | CVE-2026-15308 | whole record PSF | stated at publication 10.0, now states 8.7CVSS v4.0 · base scoreCriticalHigh | Time to revision 0 days |
| Wed 8 Jul 2026· 2 changes | ||||
| 2026-07-08 | CVE-2026-60104 | whole record VulnCheck | stated at publication 8.5, now states 9.3CVSS v4.0 · base scoreHighCritical | Time to revision 0 days |
| 2026-07-08 | CVE-2026-9182 | whole record Esri | stated at publication 5.3, now states 9.8CVSS v3.1 · base scoreMediumCritical | Time to revision 2 days |
| Tue 7 Jul 2026· 1 change | ||||
| 2026-07-07 | CVE-2026-55255 | whole record GitHub_M | stated at publication 9.9, now states 8.4CVSS v3.1 · base scoreCriticalHigh | Time to revision 14 days |
| Thu 2 Jul 2026· 4 changes | ||||
| 2026-07-02 | CVE-2026-56004 | whole record suse | stated at publication 8.8, now states 10.0CVSS v3.1 · base scoreHighCritical | Time to revision 0 days |
| 2026-07-02 | CVE-2026-44832 | whole record GitHub_M | stated at publication 7.1, now states 8.7CVSS v4.0 · base scoreHighHigh | Time to revision 37 days |
| 2026-07-02 | 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 | 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· 5 changes | ||||
| 2026-06-30 | CVE-2026-12539 | whole record Docker | stated at publication 5.7, now states 5.1CVSS v4.0 · base scoreMediumMedium | Time to revision 12 days |
| 2026-06-30 | CVE-2026-24716 | whole record qnap | stated at publication 5.1, now states 1.2CVSS v4.0 · base scoreMediumLow | Time to revision 20 days |
| 2026-06-30 | CVE-2026-24717 | whole record qnap | stated at publication 5.1, now states 1.2CVSS v4.0 · base scoreMediumLow | Time to revision 20 days |
| 2026-06-30 | CVE-2026-24719 | whole record qnap | stated at publication 8.6, now states 6.1CVSS v4.0 · base scoreHighMedium | Time to revision 20 days |
| 2026-06-30 | CVE-2026-41539 | whole record qnap | stated at publication 8.7, now states 6.3CVSS v4.0 · base scoreHighMedium | Time to revision 21 days |
This kind is counted once per CVE record, so changes and records are the same number here.
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 →