Every change, newest first
These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.
| 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. |
|---|---|---|---|---|---|
| Sat 5 Sep 2026· 3 record changes | |||||
| 2026-09-05 | Product added | CVE-2026-85599 | VulnCheck | not named as affected at publication, now names grav-plugin-shortcode-coreNot counted: Product relabelled. probable relabelling of getgrav/grav, not a newly affected product | Days to revision 1 |
| 2026-09-05 | Product added | CVE-2026-85600 | VulnCheck | not named as affected at publication, now names grav-plugin-admin2Not counted: Product relabelled. probable relabelling of getgrav/grav, not a newly affected product | Days to revision 1 |
| 2026-09-05 | Product added | CVE-2026-85602 | VulnCheck | not named as affected at publication, now names grav-plugin-formNot counted: Product relabelled. probable relabelling of getgrav/grav, not a newly affected product | Days to revision 1 |
| Wed 2 Sep 2026· 1 record change | |||||
| 2026-09-02 | Affected range extended | CVE-2026-82641 | keploykeploy VulnCheck | stated at publication 3.6.25, now states 3.6.26Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 3.6.25 still holds | not dated |
| Tue 1 Sep 2026· 8 record changes | |||||
| 2026-09-01 | Product added | CVE-2026-75121 | VulnCheck | not named as affected at publication, now names planet gs-4210-16p2s v3Not counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Days to revision 4 |
| 2026-09-01 | Product added | CVE-2026-75122 | VulnCheck | not named as affected at publication, now names planet gs-4210-16p2s v3Not counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Days to revision 4 |
| 2026-09-01 | Product added | CVE-2026-75123 | VulnCheck | not named as affected at publication, now names planet gs-4210-16p2s v3Not counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Days to revision 4 |
| 2026-09-01 | Product added | CVE-2026-75124 | VulnCheck | not named as affected at publication, now names planet gs-4210-16p2s v3Not counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Days to revision 4 |
| 2026-09-01 | Product added | CVE-2026-75125 | VulnCheck | not named as affected at publication, now names planet gs-4210-16p2s v3Not counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Days to revision 4 |
| 2026-09-01 | Product added | CVE-2026-75126 | VulnCheck | not named as affected at publication, now names planet gs-4210-16p2s v3Not counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Days to revision 4 |
| 2026-09-01 | Product added | CVE-2026-77217 | VulnCheck | not named as affected at publication, now names planet gs-4210-16p2s v3Not counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Days to revision 4 |
| 2026-09-01 | Product added | CVE-2026-77218 | VulnCheck | not named as affected at publication, now names planet gs-4210-16p2s v3Not counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Days to revision 4 |
| Sat 29 Aug 2026· 1 record change | |||||
| 2026-08-29 | Product added | CVE-2026-72699 | VulnCheck | not named as affected at publication, now names grav-plugin-loginNot counted: Product relabelled. probable relabelling of getgrav/grav, not a newly affected product | Days to revision 4 |
| Wed 26 Aug 2026· 1 record change | |||||
| 2026-08-26 | Affected range extended | CVE-2026-5917 | libgit2libgit2 VulnCheck | stated at publication 1.9.0, now states 1.9.7Release branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | not dated |
| Tue 25 Aug 2026· 1 record change | |||||
| 2026-08-25 | Affected range extended | CVE-2026-73325 | fujitsu researchonecompression VulnCheck | stated at publication 1.2.0, now states 1.2.1Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Days to revision 12 |
| Mon 24 Aug 2026· 1 record change | |||||
| 2026-08-24 | CVSS base score changed | CVE-2026-67340 | whole record VulnCheck | stated at publication 9.8, now states 8.6Assessments not comparable · base scoreCriticalHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 23 |
| Fri 21 Aug 2026· 1 record change | |||||
| 2026-08-21 | Fix version moved | CVE-2026-63722 | icecodericecoder VulnCheck | stated at publication 8.1, now states 8.1Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 2 |
| Mon 3 Aug 2026· 1 record change | |||||
| 2026-08-03 | Affected range extended | CVE-2026-65321 | laughingman7743pyathena VulnCheck | stated at publication 3.35.3, now states 3.35.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 3.35.3 still holds | not dated |
| Sun 2 Aug 2026· 1 record change | |||||
| 2026-08-02 | CVSS base score changed | CVE-2026-67308 | whole record VulnCheck | stated at publication 10.0, now states 9.3Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 1 |
| Fri 31 Jul 2026· 4 record changes | |||||
| 2026-07-31 | Fix version moved | CVE-2026-10031 | drakkansftpgo VulnCheck | stated at publication 2.7.4, now states 2.7.4Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 1 |
| 2026-07-31 | Fix version moved | CVE-2026-66414 | leantimeleantime VulnCheck | stated at publication 3.6.2, now states 3.6.2Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 1 |
| 2026-07-31 | Fix version moved | CVE-2026-66415 | leantimeleantime VulnCheck | stated at publication 3.6.2, now states 3.6.2Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 1 |
| 2026-07-31 | Fix version moved | CVE-2026-66416 | leantimeleantime VulnCheck | stated at publication 3.6.2, now states 3.6.2Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 1 |
| Tue 28 Jul 2026· 2 record changes | |||||
| 2026-07-28 | CVSS base score changed | CVE-2026-66752 | whole record VulnCheck | stated at publication 7.2, now states 6.3Assessments not comparable · base scoreHighMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| 2026-07-28 | CVSS base score changed | CVE-2026-67181 | whole record VulnCheck | stated at publication 7.2, now states 6.3Assessments not comparable · base scoreHighMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| Mon 27 Jul 2026· 1 record change | |||||
| 2026-07-27 | Affected range extended | CVE-2026-63094 | signozsignoz VulnCheck | stated at publication 0.133.0, now states 0.134.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Days to revision 10 |
| Fri 24 Jul 2026· 1 record change | |||||
| 2026-07-24 | Affected range extended | CVE-2026-29009 | u-bootu-boot VulnCheck | stated at publication 2026.04-rc3, now states 2026.07-rc2Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch to | Days to revision 16 |
| Mon 20 Jul 2026· 1 record change | |||||
| 2026-07-20 | Fix version moved | CVE-2024-58362 | surrealdbsurrealdb VulnCheck | stated at publication 1.5.2, now states 2.0.0-beta.3Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 1.5.2 still holds | not dated |
| Thu 25 Jun 2026· 1 record change | |||||
| 2026-06-25 | CVSS base score changed | CVE-2026-56115 | whole record VulnCheck | stated at publication 6.0, now states 8.8Assessments not comparable · base scoreMediumHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 2 |
| Tue 23 Jun 2026· 2 record changes | |||||
| 2026-06-23 | Affected range extended | CVE-2026-54390 | jtl softwarejtl shop VulnCheck | stated at publication 5.3.x, now states 5.4.0Release branch starts at 5.2.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Days to revision 5 |
| 2026-06-23 | CVSS base score changed | CVE-2026-56784 | whole record VulnCheck | stated at publication 8.3, now states 8.6Assessments not comparable · base scoreHighHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| Wed 10 Jun 2026· 4 record changes | |||||
| 2026-06-10 | Fix version moved | CVE-2025-71319 | image-sizeimage-size VulnCheck | stated at publication 1.2.1, now states 1.2.1Release branch starts at 1.1.0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 1 |
| 2026-06-10 | Fix version moved | CVE-2025-71319 | image-sizeimage-size VulnCheck | stated at publication 2.0.2, now states 2.0.2Release branch starts at 2.0.0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 1 |
| 2026-06-10 | Affected range extended | CVE-2026-50635 | limesurveylimesurvey VulnCheck | stated at publication 7.0, now states 7.0.1Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0 still holds | not dated |
| 2026-06-10 | Affected range extended | CVE-2026-50636 | limesurveylimesurvey VulnCheck | stated at publication 7.0, now states 7.0.1Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0 still holds | not dated |
| Wed 3 Jun 2026· 2 record changes | |||||
| 2026-06-03 | Fix version moved | CVE-2024-14036 | drägercore VulnCheck | stated at publication 1.0.5, now states 1.0.5Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 1 |
| 2026-06-03 | Fix version moved | CVE-2024-14036 | drägerm540 converter service VulnCheck | stated at publication 1.0.9, now states 1.0.9Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 1 |
| Thu 28 May 2026· 9 record changes | |||||
| 2026-05-28 | CVSS base score changed | CVE-2026-45007 | whole record VulnCheck | stated at publication 4.3, now states 5.3Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 13 |
| 2026-05-28 | CVSS base score changed | CVE-2026-45008 | whole record VulnCheck | stated at publication 6.5, now states 7.0Assessments not comparable · base scoreMediumHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 13 |
| 2026-05-28 | CVSS base score changed | CVE-2026-45009 | whole record VulnCheck | stated at publication 4.3, now states 5.3Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 13 |
| 2026-05-28 | CVSS base score changed | CVE-2026-45010 | whole record VulnCheck | stated at publication 9.1, now states 9.3Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 13 |
| 2026-05-28 | CVSS base score changed | CVE-2026-46359 | whole record VulnCheck | stated at publication 7.5, now states 7.7Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 13 |
| 2026-05-28 | CVSS base score changed | CVE-2026-46361 | whole record VulnCheck | stated at publication 6.9, now states 8.2Assessments not comparable · base scoreMediumHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 13 |
| 2026-05-28 | CVSS base score changed | CVE-2026-46362 | whole record VulnCheck | stated at publication 6.5, now states 7.1Assessments not comparable · base scoreMediumHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 13 |
| 2026-05-28 | CVSS base score changed | CVE-2026-46366 | whole record VulnCheck | stated at publication 7.5, now states 8.7Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 13 |
| 2026-05-28 | CVSS base score changed | CVE-2026-46367 | whole record VulnCheck | stated at publication 7.6, now states 8.3Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 13 |
| Tue 26 May 2026· 3 record changes | |||||
| 2026-05-26 | Affected range extended | CVE-2026-41947 | langgeniusdify VulnCheck | stated at publication 1.14.1, now states 1.14.2Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Days to revision 8 |
| 2026-05-26 | Affected range extended | CVE-2026-41949 | langgeniusdify VulnCheck | stated at publication 1.14.1, now states 1.14.2Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Days to revision 8 |
| 2026-05-26 | CVSS base score changed | CVE-2026-41948 | whole record VulnCheck | stated at publication 9.2, now states 9.4Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 8 |
| Mon 25 May 2026· 11 record changes | |||||
| 2026-05-25 | Fix version moved | CVE-2025-34254 | d-linknuclias connect VulnCheck | stated at publication 1.3.1.4, now states 1.3.1.4Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 221 |
| 2026-05-25 | Fix version moved | CVE-2025-34255 | d-linknuclias connect VulnCheck | stated at publication 1.3.1.4, now states 1.3.1.4Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 221 |
| 2026-05-25 | Fix version moved | CVE-2026-25068 | alsa projectalsa-lib VulnCheck | stated at publication 1.2.15.2, now states 1.2.15.2Release branch starts at 1.2.2.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 116 |
| 2026-05-25 | Fix version moved | CVE-2026-44400 | mailenablemailenable enterprise premium VulnCheck | stated at publication 10.55, now states 10.55Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 17 |
| 2026-05-25 | Affected range extended | CVE-2026-26352 | smoothwallexpress VulnCheck | stated at publication 3.1 Update 13, now states 3.1 Update 13Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Days to revision 56 |
| 2026-05-25 | Affected range extended | CVE-2026-27508 | smoothwallexpress VulnCheck | stated at publication 3.1 Update 13, now states 3.1 Update 13Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Days to revision 56 |
| 2026-05-25 | Affected range extended | CVE-2026-27510 | unitreeroboticsunitree go2 VulnCheck | stated at publication 1.1.9, now states 1.1.11Release branch starts at 1.1.7.Not counted: Description already named the later value. the record's own description at publication already named 1.1.11 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 88 |
| 2026-05-25 | Affected range extended | CVE-2026-28481 | openclawopenclaw VulnCheck | stated at publication 2026.1.30, now states 2026.2.1Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 2026.1.30 still holds | not dated |
| 2026-05-25 | Affected range extended | CVE-2026-28532 | frroutingfrr VulnCheck | stated at publication 10.5.3, now states 10.5.3Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Days to revision 25 |
| 2026-05-25 | Affected range extended | CVE-2026-34963 | bareboxbarebox VulnCheck | stated at publication 2026.04.0, now states 2026.04.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Days to revision 14 |
| 2026-05-25 | Affected range extended | CVE-2026-40032 | tclahruac VulnCheck | stated at publication 3.2.0, now states 3.3.0-rc1Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Days to revision 47 |
| Wed 20 May 2026· 1 record change | |||||
| 2026-05-20 | CVSS base score changed | CVE-2026-47107 | whole record VulnCheck | stated at publication 9.6, now states 8.6Assessments not comparable · base scoreCriticalHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 1 |
| Wed 13 May 2026· 3 record changes | |||||
| 2026-05-13 | Affected range extended | CVE-2026-32834 | scott patersoneasy-paypal-events-tickets VulnCheck | stated at publication 1.3, now states 1.4.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Days to revision 9 |
| 2026-05-13 | Affected range extended | CVE-2026-41471 | scott patersoneasy-paypal-events-tickets VulnCheck | stated at publication 1.3, now states 1.4.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Days to revision 9 |
| 2026-05-13 | CVSS base score changed | CVE-2026-44112 | whole record VulnCheck | stated at publication 6.0, now states 9.6Assessments not comparable · base scoreMediumCriticalNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 7 |
| Tue 12 May 2026· 2 record changes | |||||
| 2026-05-12 | CVSS base score changed | CVE-2025-15617 | whole record VulnCheck | stated at publication 6.5, now states 8.3Assessments not comparable · base scoreMediumHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 46 |
| 2026-05-12 | CVSS base score changed | CVE-2025-15620 | whole record VulnCheck | stated at publication 9.3, now states 9.2Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 40 |
| Wed 29 Apr 2026· 1 record change | |||||
| 2026-04-29 | CVSS base score changed | CVE-2026-41446 | whole record VulnCheck | stated at publication 9.2, now states 9.8Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 1 |
| Thu 23 Apr 2026· 2 record changes | |||||
| 2026-04-23 | CVSS base score changed | CVE-2026-41461 | whole record VulnCheck | stated at publication 6.3, now states 8.5Assessments not comparable · base scoreMediumHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 0 |
| 2026-04-23 | CVSS base score changed | CVE-2026-41460 | whole record VulnCheck | stated at publication 9.3, now states 9.8Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 0 |
| Wed 22 Apr 2026· 4 record changes | |||||
| 2026-04-22 | CVSS base score changed | CVE-2026-22191 | whole record VulnCheck | stated at publication 6.9, now states 5.2Assessments not comparable · base scoreMediumMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 41 |
| 2026-04-22 | CVSS base score changed | CVE-2026-22192 | whole record VulnCheck | stated at publication 6.3, now states 9.9Assessments not comparable · base scoreMediumCriticalNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 41 |
| 2026-04-22 | CVSS base score changed | CVE-2026-41469 | whole record VulnCheck | stated at publication 5.1, now states 5.2Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 0 |
| 2026-04-22 | CVSS base score changed | CVE-2026-22199 | whole record VulnCheck | stated at publication 6.9, now states 8.7Assessments not comparable · base scoreMediumHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 41 |
| Tue 21 Apr 2026· 1 record change | |||||
| 2026-04-21 | Affected range extended | CVE-2026-40525 | volcengineopenviking VulnCheck | stated at publication 0.3.8, now states 0.3.9Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Days to revision 4 |
| Mon 20 Apr 2026· 1 record change | |||||
| 2026-04-20 | CVSS base score changed | CVE-2026-23758 | whole record VulnCheck | stated at publication 5.1, now states 6.4Assessments not comparable · base scoreMediumMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| Thu 16 Apr 2026· 2 record changes | |||||
| 2026-04-16 | Fix version moved | CVE-2026-39922 | geonodegeonode VulnCheck | stated at publication 4.4.5, now states 4.4.5Release branch starts at 4.0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 5 |
| 2026-04-16 | Fix version moved | CVE-2026-39922 | geonodegeonode VulnCheck | stated at publication 5.0.2, now states 5.0.2Release branch starts at 5.0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Days to revision 5 |
| Mon 13 Apr 2026· 1 record change | |||||
| 2026-04-13 | CVSS base score changed | CVE-2026-26221 | whole record VulnCheck | stated at publication 10.0, now states 9.8Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 59 |
| Wed 8 Apr 2026· 1 record change | |||||
| 2026-04-08 | CVSS base score changed | CVE-2026-40035 | whole record VulnCheck | stated at publication 9.8, now states 9.3Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| Mon 6 Apr 2026· 1 record change | |||||
| 2026-04-06 | CVSS base score changed | CVE-2026-33579 | whole record VulnCheck | stated at publication 9.8, now states 9.9Assessments not comparable · base scoreCriticalCriticalOriginal value first replaced 2026-03-31; this value first seen 2026-04-06.Not counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| Fri 3 Apr 2026· 1 record change | |||||
| 2026-04-03 | CVSS base score changed | CVE-2026-22664 | whole record VulnCheck | stated at publication 7.1, now states 7.7Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 0 |
| Thu 2 Apr 2026· 1 record change | |||||
| 2026-04-02 | CVSS base score changed | CVE-2023-53908 | whole record VulnCheck | stated at publication 8.7, now states 8.8Assessments not comparable · base scoreHighHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 106 |
| Wed 1 Apr 2026· 6 record changes | |||||
| 2026-04-01 | CVSS base score changed | CVE-2026-29014 | whole record VulnCheck | stated at publication 9.3, now states 9.8Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 0 |
| 2026-04-01 | CVSS base score changed | CVE-2026-34430 | whole record VulnCheck | stated at publication 8.6, now states 8.8Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 0 |
| 2026-04-01 | CVSS base score changed | CVE-2026-27748 | whole record VulnCheck | stated at publication 8.5, now states 7.8Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 27 |
| 2026-04-01 | CVSS base score changed | CVE-2026-27749 | whole record VulnCheck | stated at publication 8.5, now states 7.8Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 27 |
| 2026-04-01 | CVSS base score changed | CVE-2026-27750 | whole record VulnCheck | stated at publication 8.5, now states 7.8Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 27 |
| 2026-04-01 | CVSS base score changed | CVE-2026-35056 | whole record VulnCheck | stated at publication 8.8, now states 8.6Assessments not comparable · base scoreHighHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 1 |
| Tue 31 Mar 2026· 9 record changes | |||||
| 2026-03-31 | CVSS base score changed | CVE-2026-32916 | whole record VulnCheck | stated at publication 9.2, now states 9.4Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| 2026-03-31 | CVSS base score changed | CVE-2026-32920 | whole record VulnCheck | stated at publication 9.8, now states 8.6Assessments not comparable · base scoreCriticalHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| 2026-03-31 | CVSS base score changed | CVE-2026-34505 | whole record VulnCheck | stated at publication 9.8, now states 6.9Assessments not comparable · base scoreCriticalMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| 2026-03-31 | CVSS base score changed | CVE-2026-34506 | whole record VulnCheck | stated at publication 7.5, now states 4.3Assessments not comparable · base scoreHighMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| 2026-03-31 | CVSS base score changed | CVE-2026-33576 | whole record VulnCheck | stated at publication 9.8, now states 6.9Assessments not comparable · base scoreCriticalMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| 2026-03-31 | CVSS base score changed | CVE-2026-33577 | whole record VulnCheck | stated at publication 9.8, now states 8.6Assessments not comparable · base scoreCriticalHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| 2026-03-31 | CVSS base score changed | CVE-2026-33578 | whole record VulnCheck | stated at publication 9.8, now states 5.3Assessments not comparable · base scoreCriticalMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| 2026-03-31 | CVSS base score changed | CVE-2026-33580 | whole record VulnCheck | stated at publication 9.8, now states 6.5Assessments not comparable · base scoreCriticalMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| 2026-03-31 | CVSS base score changed | CVE-2026-34504 | whole record VulnCheck | stated at publication 6.9, now states 8.3Assessments not comparable · base scoreMediumHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| Fri 27 Mar 2026· 2 record changes | |||||
| 2026-03-27 | CVSS base score changed | CVE-2026-32857 | whole record VulnCheck | stated at publication 7.8, now states 8.6Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 1 |
| 2026-03-27 | CVSS base score changed | CVE-2026-32859 | whole record VulnCheck | stated at publication 5.1, now states 5.4Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 0 |
| Wed 25 Mar 2026· 1 record change | |||||
| 2026-03-25 | CVSS base score changed | CVE-2026-22170 | whole record VulnCheck | stated at publication 6.3, now states 6.5Assessments not comparable · base scoreMediumMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 8 |
Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none.
Data sources and quality
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 →