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 | 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 | CVE-2026-26369 | same vendor as the line above | same change as the line above | Time to revision 190 days |
| 2026-08-24 | CVE-2026-34100 | same vendor as the line above | same change as the line above | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34101 | same vendor as the line above | same change as the line above | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34102 | same vendor as the line above | same change as the line above | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34103 | same vendor as the line above | same change as the line above | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34104 | same vendor as the line above | same change as the line above | Time to revision 54 days |
| 2026-08-24 | CVE-2026-34105 | same vendor as the line above | same change as the line above | Time to revision 54 days |
| 2026-08-24 | 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 → | ||||
| 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 | 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-54117 | same vendor as the line above | same change as the line above | Time to revision 37 days |
| 2026-08-20 | CVE-2026-54118 | same vendor as the line above | same change as the line above | 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 |
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 →