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. |
|---|---|---|---|---|
| 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 23 Jun 2026· 1 change | ||||
| 2026-06-23 | CVE-2026-12628 | whole record ibm | stated at publication 8.1, now states 9.1CVSS v3.1 · base scoreHighCritical | Time to revision 1 days |
| Wed 25 Mar 2026· 1 change | ||||
| 2026-03-25 | CVE-2026-2484 | whole record ibm | stated at publication 5.4, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 0 days |
| Thu 5 Feb 2026· 1 change | ||||
| 2026-02-05 | CVE-2025-33081 | whole record ibm | stated at publication 4.3, now states 3.3CVSS v3.1 · base scoreMediumLow | Time to revision 2 days |
| Tue 4 Nov 2025· 1 change | ||||
| 2025-11-04 | CVE-2025-36248 | whole record ibm | stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium | Time to revision 46 days |
| Sat 28 Jun 2025· 1 change | ||||
| 2025-06-28 | CVE-2024-39730 | whole record ibm | stated at publication 6.1, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 0 days |
| Mon 5 May 2025· 1 change | ||||
| 2025-05-05 | CVE-2025-1992 | whole record ibm | stated at publication 5.9, now states 5.3CVSS v3.1 · base scoreMediumMedium | Time to revision 0 days |
| Sat 21 Sep 2024· 4 changes | ||||
| 2024-09-212 commits | whole record ibm | stated at publication 6.2, now states 5.5CVSS v3.1 · base scoreMediumMediumBranches and original-value intervals are stated on each row. | Time to revision 37 to 73 days | |
| 2024-09-21 | CVE-2024-39733 | same vendor as the line above | same change as the line above | Time to revision 69 days |
| 2024-09-21 | CVE-2024-25023 | same vendor as the line above | same change as the line above | Time to revision 73 days |
| 2024-09-21 | CVE-2024-25024 | same vendor as the line above | same change as the line above | Time to revision 37 days |
| 2024-09-21 | CVE-2023-47728 | whole record ibm | stated at publication 4.9, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 36 days |
| Sat 24 Aug 2024· 7 changes | ||||
| 2024-08-24 | whole record ibm | stated at publication 4.0, now states 3.3CVSS v3.1 · base scoreMediumLow | Time to revision 55 to 72 days | |
| 2024-08-24 | CVE-2023-35022 | same vendor as the line above | same change as the line above | Time to revision 55 days |
| 2024-08-24 | CVE-2024-22333 | same vendor as the line above | same change as the line above | Time to revision 72 days |
| 2024-08-242 commits | whole record ibm | stated at publication 6.2, now states 5.5CVSS v3.1 · base scoreMediumMediumBranches and original-value intervals are stated on each row. | Time to revision 58 days | |
| 2024-08-24 | CVE-2023-38368 | same vendor as the line above | same change as the line above | Time to revision 58 days |
| 2024-08-24 | CVE-2023-30430 | same vendor as the line above | same change as the line above | Time to revision 58 days |
| 2024-08-24 | CVE-2024-41774 | whole record ibm | stated at publication 5.5, now states 4.8CVSS v3.1 · base scoreMediumMedium | Time to revision 11 days |
| 2024-08-24 | whole record ibm | stated at publication 8.4, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 58 days | |
| 2024-08-24 | CVE-2023-30997 | same vendor as the line above | same change as the line above | Time to revision 58 days |
| 2024-08-24 | CVE-2023-30998 | same vendor as the line above | same change as the line above | Time to revision 58 days |
| Sat 4 May 2024· 1 change | ||||
| 2024-05-04 | CVE-2023-27283 | whole record ibm | stated at publication 5.9, now states 5.3CVSS v3.1 · base scoreMediumMedium | Time to revision 0 days |
| Fri 19 Jan 2024· 1 change | ||||
| 2024-01-19 | CVE-2023-38738 | whole record ibm | stated at publication 8.8, now states 6.8CVSS v3.1 · base scoreHighMedium | Time to revision 0 days |
| Thu 14 Dec 2023· 1 change | ||||
| 2023-12-14 | CVE-2023-45182 | whole record ibm | stated at publication 7.1, now states 7.4CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| Fri 14 Jul 2023· 1 change | ||||
| 2023-07-14 | CVE-2023-30990 | whole record ibm | stated at publication 5.6, now states 8.6CVSS v3.1 · base scoreMediumHigh | Time to revision 11 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 →