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. |
|---|---|---|---|---|---|
| Thu 16 May 2024· 29 record changes | |||||
| 2024-05-166 commits | CVSS base score changed | whole record juniper | stated at publication 7.5, now states 8.7Assessments not comparable · base scoreHighHighBranches and original-value intervals are stated on each row.not counted: CVSS version set changed | Days to revision 34 | |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30405 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30397 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30398 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30392 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30394 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30395 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-21598 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30382 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-162 commits | CVSS base score changed | whole record juniper | stated at publication 5.9, now states 8.2Assessments not comparable · base scoreMediumHighBranches and original-value intervals are stated on each row.not counted: CVSS version set changed | Days to revision 34 | |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30402 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30401 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-164 commits | CVSS base score changed | whole record juniper | stated at publication 6.5, now states 7.1Assessments not comparable · base scoreMediumHighBranches and original-value intervals are stated on each row.not counted: CVSS version set changed | Days to revision 30 to 34 | |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30403 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-21618 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30387 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30388 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-21593 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-21605 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-21609 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30380 | same vendor as the line above | same change as the line aboveNot 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 30 |
| 2024-05-16 | CVSS base score changed | CVE-2024-30391 | whole record juniper | stated at publication 4.8, now states 6.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 34 |
| 2024-05-16 | CVSS base score changed | CVE-2024-30384 | whole record juniper | stated at publication 5.5, now states 6.8Assessments 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 34 |
| 2024-05-162 commits | CVSS base score changed | whole record juniper | stated at publication 5.3, now states 7.1Assessments not comparable · base scoreMediumHighBranches and original-value intervals are stated on each row.not counted: CVSS version set changed | Days to revision 34 | |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30386 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-21590 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-162 commits | CVSS base score changed | whole record juniper | stated at publication 5.3, now states 6.9Assessments not comparable · base scoreMediumMediumBranches and original-value intervals are stated on each row.not counted: CVSS version set changed | Days to revision 34 | |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30390 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | same kind of change as the line above | CVE-2024-30409 | same vendor as the line above | same change as the line aboveNot 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 34 |
| 2024-05-16 | CVSS base score changed | CVE-2024-21615 | whole record juniper | stated at publication 5.0, now states 5.1Assessments 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 34 |
| 2024-05-16 | CVSS base score changed | CVE-2024-5023 | whole record netflix | stated at publication 9.6, 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 0 |
| 2024-05-16 | CVSS base score changed | CVE-2024-30378 | whole record juniper | stated at publication 5.5, now states 6.9Assessments 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 30 |
| 2024-05-16 | CVSS base score changed | CVE-2024-4966 | whole record VulDB | stated at publication 6.5, now states 7.5Assessments 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 |
| 2024-05-16 | CVSS base score changed | CVE-2024-4826 | whole record INCIBE | 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 |
| Mon 13 May 2024· 1 record change | |||||
| 2024-05-13 | Fix version moved | CVE-2024-26817 | linuxlinux | stated at publication 6.8.6, now states 6.9Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.8.6 still holds | not dated |
| Thu 9 May 2024· 2 record changes | |||||
| 2024-05-09 | Affected range extended | CVE-2024-34383 | the seo guys at seopressseopress Patchstack | stated at publication 7.6.1, now states 7.7.1Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 3 |
| 2024-05-09 | CVSS base score changed | CVE-2024-4645 | whole record VulDB | stated at publication 4.0, 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 1 |
| Wed 8 May 2024· 1 record change | |||||
| 2024-05-08 | Fix version moved | CVE-2024-29059 | microsoftmicrosoft .net framework 3.5 | stated at publication 3.0.50727.8975, now states 3.0.50727.8976Release branch starts at 3.5.0.Not counted: Boundary below its own start. the boundary stated at publication was below the range's own start — a malformed range, not a fix anyone patched to | Days to revision 47 |
| Mon 6 May 2024· 1 record change | |||||
| 2024-05-06 | CVSS base score changed | CVE-2024-4349 | whole record VulDB | stated at publication 6.5, now states 7.5Assessments 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 6 |
| Thu 25 Apr 2024· 1 record change | |||||
| 2024-04-25 | Affected range extended | CVE-2024-32677 | loginpressloginpress pro Patchstack | stated at publication 2.5.3, now states 3.0.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 1 |
| Thu 18 Apr 2024· 1 record change | |||||
| 2024-04-18 | CVSS base score changed | CVE-2024-1309 | whole record Honeywell | stated at publication 6.4, now states 6.5Assessments 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 65 |
| Mon 15 Apr 2024· 2 record changes | |||||
| 2024-04-15 | Fix version moved | CVE-2024-1655 | asusexpertwifi ebm68 twcert | stated at publication 3.0.0.6.102_31933, now states 3.0.0.6.102_44384Release branch starts at earlier .Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 0 |
| 2024-04-15 | CVSS base score changed | CVE-2024-3764 | whole record VulDB | stated at publication 5.3, now states 3.3Assessments not comparable · base scoreMediumLowNot 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 Apr 2024· 1 record change | |||||
| 2024-04-10 | Fix version moved | CVE-2024-29946 | splunksplunk cloud platform | stated at publication 9.1.2312.100, now states 9.1.2312.104Release branch starts at 0.Original value first replaced 2024-04-04; this value first seen 2024-04-10.Not counted: Build number corrected to the one that shipped. only the build revision moved, 13.4 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 8 |
| Thu 14 Mar 2024· 2 record changes | |||||
| 2024-03-14 | Fix version moved | CVE-2024-26167 | microsoftmicrosoft edge for android | stated at publication 122.0.2365.80, now states 122.0.2365.92Release branch starts at 1.0.0.Original value first replaced 2024-03-08; this value first seen 2024-03-14.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 0 |
| 2024-03-14 | Fix version moved | CVE-2024-2247 | jfrogartifactory | stated at publication 7.77.7, now states 7.82.1Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.77.7 still holds | not dated |
| Mon 11 Mar 2024· 1 record change | |||||
| 2024-03-11 | Fix version moved | CVE-2024-26602 | linuxlinux | stated at publication 6.7.6, now states 6.8Release 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 |
| Fri 1 Mar 2024· 12 record changes | |||||
| 2024-03-01 | Affected range extended | CVE-2023-48674 | dellcpg bios | stated at publication 1.9.0, now states 1.9.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 0 |
| 2024-03-01 | Affected range extended | CVE-2023-48674 | dellcpg bios | stated at publication 1.11.0, now states 1.11.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 0 |
| 2024-03-01 | Affected range extended | CVE-2023-48674 | dellcpg bios | stated at publication 1.12.0, now states 1.12.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 0 |
| 2024-03-01 | Affected range extended | CVE-2023-48674 | dellcpg bios | stated at publication 1.17.0, now states 1.17.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 0 |
| 2024-03-01 | Affected range extended | CVE-2023-48674 | dellcpg bios | stated at publication 1.20.0, now states 1.20.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 0 |
| 2024-03-01 | Affected range extended | CVE-2023-48674 | dellcpg bios | stated at publication 1.24.0, now states 1.24.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 0 |
| 2024-03-01 | Affected range extended | CVE-2023-48674 | dellcpg bios | stated at publication 1.26.0, now states 1.26.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 0 |
| 2024-03-01 | Affected range extended | CVE-2023-48674 | dellcpg bios | stated at publication 1.27.0, now states 1.27.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 0 |
| 2024-03-01 | Affected range extended | CVE-2023-48674 | dellcpg bios | stated at publication 1.27.1, now states 1.27.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 0 |
| 2024-03-01 | Affected range extended | CVE-2023-48674 | dellcpg bios | stated at publication 1.28.0, now states 1.28.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 0 |
| 2024-03-01 | Affected range extended | CVE-2023-48674 | dellcpg bios | stated at publication 1.32.0, now states 1.32.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 0 |
| 2024-03-01 | Affected range extended | CVE-2023-48674 | dellcpg bios | stated at publication 3.20.0, now states 3.20.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 0 |
| Wed 14 Feb 2024· 2 record changes | |||||
| 2024-02-14 | Fix version moved | red hatrhel-8 based middleware containers | stated at publication 7.6-38, now states 7.6-41Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2024-02-14 | same kind of change as the line above | CVE-2023-6134 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.6-38 still holds | not dated |
| 2024-02-14 | same kind of change as the line above | CVE-2023-6291 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.6-38 still holds | not dated |
| Tue 13 Feb 2024· 1 record change | |||||
| 2024-02-13 | Affected range extended | CVE-2023-0076 | unknowndownload attachments WPScan | stated at publication 1.2.24, now states 1.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 344 |
| Mon 29 Jan 2024· 1 record change | |||||
| 2024-01-29 | Affected range extended | CVE-2023-49657 | apache software foundationapache superset apache | stated at publication 3.0.3, now states 3.0.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 6 |
| Sun 28 Jan 2024· 3 record changes | |||||
| 2024-01-28 | CVSS base score changed | whole record VulDB | stated at publication 5.8, now states 8.3Assessments not comparable · base scoreMediumHighnot counted: CVSS assessments are not comparable | Days to revision 2 | |
| 2024-01-28 | same kind of change as the line above | CVE-2024-0918 | same vendor as the line above | same change as the line aboveNot 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 |
| 2024-01-28 | same kind of change as the line above | CVE-2024-0920 | same vendor as the line above | same change as the line aboveNot 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 |
| 2024-01-28 | CVSS base score changed | CVE-2024-0919 | whole record VulDB | stated at publication 6.5, now states 9.0Assessments 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 2 |
| Thu 25 Jan 2024· 2 record changes | |||||
| 2024-01-25 | Product added | not named as affected at publication, now names cisco secure endpointnot counted: Already named at publication | Days to revision 162 to 343 | ||
| 2024-01-25 | same kind of change as the line above | CVE-2023-20032 | same vendor as the line above | same change as the line aboveNot counted: Already named at publication. already named at publication inside cisco/cisco secure endpoint private cloud administration portal — the record spelled this product out all along | Days to revision 343 |
| 2024-01-25 | same kind of change as the line above | CVE-2023-20197 | same vendor as the line above | same change as the line aboveNot counted: Already named at publication. already named at publication inside cisco/cisco secure endpoint private cloud console — the record spelled this product out all along | Days to revision 162 |
| Fri 29 Dec 2023· 1 record change | |||||
| 2023-12-29 | CVSS base score changed | CVE-2023-27990 | whole record Zyxel | stated at publication 3.5, now states 4.8Assessments not comparable · base scoreLowMediumNot 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 249 |
| Fri 15 Dec 2023· 2 record changes | |||||
| 2023-12-15 | Fix version moved | CVE-2023-35632 | microsoftwindows 10 version 21h2 | stated at publication 10.0.19041.3803, now states 10.0.19044.3803Release branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-12-15 | Affected range extended | CVE-2023-3226 | unknownpopup builder WPScan | stated at publication 4.1.15, now states 4.2.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 81 |
| Thu 14 Dec 2023· 1 record change | |||||
| 2023-12-14 | Product added | CVE-2023-6134 | not named as affected at publication, now names red hat build of keycloak 22Not counted: Already named at publication. already named at publication inside red hat/red hat build of keycloak 22.0.7 — the record spelled this product out all along | Days to revision 0 | |
| Wed 13 Dec 2023· 6 record changes | |||||
| 2023-12-13 | Fix version moved | CVE-2023-5869 | red hatred hat enterprise linux 8 | stated at publication 8090020231114113712.a75119d5, now states 8090020231201202407.a75119d5Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8090020231114113712.a75119d5 still holds | not dated |
| 2023-12-13 | Fix version moved | CVE-2023-5869 | red hat3 products | stated at publication 8020020231128165246.4cda2c84, now states 8020020231201202149.4cda2c84Release branch starts at *.not counted: Another branch advanced | not dated |
| 2023-12-13 | same kind of change as the line above | CVE-2023-5869 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8020020231128165246.4cda2c84 still holds | not dated |
| 2023-12-13 | same kind of change as the line above | CVE-2023-5869 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8020020231128165246.4cda2c84 still holds | not dated |
| 2023-12-13 | same kind of change as the line above | CVE-2023-5869 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8020020231128165246.4cda2c84 still holds | not dated |
| 2023-12-13 | Fix version moved | CVE-2023-5869 | red hatred hat enterprise linux 8.6 extended update support | stated at publication 8060020231128165328.ad008a3a, now states 8060020231201202249.ad008a3aRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8060020231128165328.ad008a3a still holds | not dated |
| 2023-12-13 | Fix version moved | CVE-2023-5869 | red hatred hat enterprise linux 8.8 extended update support | stated at publication 8080020231128165335.63b34585, now states 8080020231201202316.63b34585Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8080020231128165335.63b34585 still holds | not dated |
| Mon 11 Dec 2023· 2 record changes | |||||
| 2023-12-11 | Fix version moved | red hatred hat enterprise linux 8 | stated at publication 8090020231114113712.a75119d5, now states 8090020231128173330.a75119d5Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2023-12-11 | same kind of change as the line above | CVE-2023-5868 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8090020231114113712.a75119d5 still holds | not dated |
| 2023-12-11 | same kind of change as the line above | CVE-2023-5870 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8090020231114113712.a75119d5 still holds | not dated |
| Wed 6 Dec 2023· 1 record change | |||||
| 2023-12-06 | Fix version moved | CVE-2023-45283 | go standard librarypath/filepath Go | stated at publication 1.21.4, now states 1.21.5Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 1.21.4 still holds | not dated |
| Thu 30 Nov 2023· 1 record change | |||||
| 2023-11-30 | CVSS base score changed | CVE-2023-6019 | whole record @huntr_ai | stated at publication 10.0, now states 9.8Assessments not comparable · base scoreCriticalCriticalOriginal value first replaced 2023-11-29; this value first seen 2023-11-30.Not 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 |
| Wed 29 Nov 2023· 1 record change | |||||
| 2023-11-29 | CVSS base score changed | CVE-2023-6021 | whole record @huntr_ai | stated at publication 9.3, now states 7.5Assessments not comparable · base scoreCriticalHighNot 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 |
| Wed 22 Nov 2023· 55 record changes | |||||
| 2023-11-22 | Fix version moved | microsoftwindows 11 version 22h3 | stated at publication 10.0.22621.2715, now states 10.0.22631.2715Release branch starts at *.not counted: Product line renumbered | not dated | |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36017 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36025 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36028 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36033 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36036 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36046 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36047 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36393 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 16 more rows in this change are not listed here. Open all 24 rows → | |||||
| 2023-11-22 | Fix version moved | microsoftwindows 11 version 23h2 | stated at publication 10.0.22621.2715, now states 10.0.22631.2715Release branch starts at *.not counted: Product line renumbered | not dated | |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36017 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36025 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36028 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36033 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36036 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36046 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36047 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 2023-11-22 | same kind of change as the line above | CVE-2023-36393 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | not dated |
| 15 more rows in this change are not listed here. Open all 23 rows → | |||||
| 2023-11-22 | Fix version moved | mozillafirefox | stated at publication 115.5, now states 120Release branch starts at 0.not counted: Description already named the later value | Days to revision 1 | |
| 2023-11-22 | same kind of change as the line above | CVE-2023-6204 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 1 |
| 2023-11-22 | same kind of change as the line above | CVE-2023-6205 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 1 |
| 2023-11-22 | same kind of change as the line above | CVE-2023-6206 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 1 |
| 2023-11-22 | same kind of change as the line above | CVE-2023-6207 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 1 |
| 2023-11-22 | same kind of change as the line above | CVE-2023-6208 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 1 |
| 2023-11-22 | same kind of change as the line above | CVE-2023-6209 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 1 |
| 2023-11-22 | same kind of change as the line above | CVE-2023-6212 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 120 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 1 |
| 2023-11-22 | CVSS base score changed | CVE-2023-1162 | whole record VulDB | 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 265 |
| Tue 14 Nov 2023· 2 record changes | |||||
| 2023-11-14 | Fix version moved | red hatred hat enterprise linux 8 | stated at publication 8080020231030214932.63b34585, now states 8090020231030224841.a75119d5Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2023-11-14 | same kind of change as the line above | CVE-2023-46846 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8080020231030214932.63b34585 still holds | not dated |
| 2023-11-14 | same kind of change as the line above | CVE-2023-46847 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 8080020231030214932.63b34585 still holds | not dated |
| Mon 6 Nov 2023· 1 record change | |||||
| 2023-11-06 | Product added | CVE-2023-36805 | not named as affected at publication, now names windows server 2012Not counted: Already named at publication. already named at publication inside microsoft/windows server 2012 r2 — the record spelled this product out all along | Days to revision 55 | |
| Thu 2 Nov 2023· 1 record change | |||||
| 2023-11-02 | CVSS base score changed | CVE-2023-1177 | whole record @huntrdev | stated at publication 10.0, 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 224 |
| Tue 24 Oct 2023· 1 record change | |||||
| 2023-10-24 | Product added | CVE-2023-5732 | not named as affected at publication, now names firefoxNot counted: Already named at publication. already named at publication inside mozilla/firefox esr — the record spelled this product out all along | Days to revision 0 | |
| Mon 23 Oct 2023· 1 record change | |||||
| 2023-10-23 | Affected range extended | CVE-2023-2995 | unknownleyka WPScan | stated at publication 3.30.3, now states 3.30.4Release 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 34 |
| Wed 4 Oct 2023· 2 record changes | |||||
| 2023-10-04 | Fix version moved | CVE-2023-4571 | splunksplunk itsi | stated at publication 4.15.3, now states 4.17.1Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 4.15.3 still holds | not dated |
| 2023-10-04 | CVSS base score changed | CVE-2023-22374 | whole record f5 | stated at publication 7.5, now states 8.5Assessments 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 244 |
| Tue 26 Sep 2023· 1 record change | |||||
| 2023-09-26 | Affected range extended | CVE-2023-1995 | hitachihirdb server with addtional function | stated at publication 09-66-*, now states 09-66-/QRelease branch starts at 09-66.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 28 |
| Fri 8 Sep 2023· 1 record change | |||||
| 2023-09-08 | Fix version moved | CVE-2023-4369 | googlechrome Chrome | stated at publication 116.0.5845.96, now states 116.0.5845.120Release 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 |
| Wed 23 Aug 2023· 33 record changes | |||||
| 2023-08-23 | Fix version moved | microsoftwindows 11 version 21h2 | stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.not counted: Product line renumbered | Days to revision 189 | |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21684 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21685 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21686 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21687 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21688 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21689 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21690 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 2023-08-23 | same kind of change as the line above | CVE-2023-21691 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Days to revision 189 |
| 25 more rows in this change are not listed here. Open all 33 rows → | |||||
| Wed 16 Aug 2023· 13 record changes | |||||
| 2023-08-16 | Fix version moved | microsoftmicrosoft exchange server 2016 cumulative update 23 | stated at publication 15.01.2507.031, now states 15.01.2507.032Release branch starts at 15.01.0.not counted: Build number corrected to the one that shipped | Days to revision 7 | |
| 2023-08-16 | same kind of change as the line above | CVE-2023-21709 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-35368 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-35388 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-38181 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-38182 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-38185 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.01.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | Fix version moved | microsoftmicrosoft exchange server 2019 cumulative update 12 | stated at publication 15.02.1118.036, now states 15.02.1118.037Release branch starts at 15.02.0.not counted: Build number corrected to the one that shipped | Days to revision 7 | |
| 2023-08-16 | same kind of change as the line above | CVE-2023-21709 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-35368 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-35388 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-38181 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-38182 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | same kind of change as the line above | CVE-2023-38185 | same vendor as the line above | same change as the line aboveRelease branch starts at 15.02.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 7.3 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Days to revision 7 |
| 2023-08-16 | Affected range extended | CVE-2023-2330 | unknowncaldera forms google sheets connector WPScan | stated at publication 1.2, now states 1.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 30 |
| Mon 14 Aug 2023· 1 record change | |||||
| 2023-08-14 | Affected range extended | CVE-2023-1119 | unknownsrbtranslatin WPScan | stated at publication 2.4, now states 2.4.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 35 |
| Fri 4 Aug 2023· 3 record changes | |||||
| 2023-08-04 | Fix version moved | googlechrome Chrome | stated at publication 115.0.5790.98, now states 115.0.5790.131Release branch starts at *.not counted: Release branches rewritten | not dated | |
| 2023-08-04 | same kind of change as the line above | CVE-2023-3729 | same vendor as the line above | same change as the line aboveRelease 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 |
| 2023-08-04 | same kind of change as the line above | CVE-2023-3731 | same vendor as the line above | same change as the line aboveRelease 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 |
| 2023-08-04 | same kind of change as the line above | CVE-2023-3739 | same vendor as the line above | same change as the line aboveRelease 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 |
| Thu 3 Aug 2023· 4 record changes | |||||
| 2023-08-03 | CVSS base score changed | CVE-2023-23837 | whole record SolarWinds | stated at publication 4.3, now states 7.5Assessments 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 101 |
| 2023-08-03 | CVSS base score changed | CVE-2023-23838 | whole record SolarWinds | stated at publication 4.0, 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 101 |
| 2023-08-03 | CVSS base score changed | CVE-2023-23839 | whole record SolarWinds | stated at publication 6.8, 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 101 |
| 2023-08-03 | CVSS base score changed | CVE-2023-23836 | whole record SolarWinds | stated at publication 8.8, now states 7.2Assessments 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 170 |
| Wed 2 Aug 2023· 1 record change | |||||
| 2023-08-02 | CVSS base score changed | CVE-2023-3568 | whole record @huntrdev | stated at publication 4.8, now states 6.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 23 |
| Tue 1 Aug 2023· 1 record change | |||||
| 2023-08-01 | Fix version moved | CVE-2023-28304 | microsoftmicrosoft ole db driver 18 for sql server | stated at publication 18.2.1.1, now states 18.6.5Release branch starts at 18.0.0.Original value first replaced 2023-06-17; this value first seen 2023-08-01.Not counted: Two products' boundaries swapped. 18.6.5 was the boundary of `microsoft odbc driver 18 for sql server` in the same record at publication and that entry now states 18.2.1.1 — the two values were swapped between two product entries, the same builds relabelled | Days to revision 66 |
| Thu 27 Jul 2023· 18 record changes | |||||
| 2023-07-272 commits | Fix version moved | appletvos | stated at publication 13.2, now states 16.3Branches and original-value intervals are stated on each row.not counted: Description already named the later value | Days to revision 150 | |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23496 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23500 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23503 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23511 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23517 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23519 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23502 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23518 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | Fix version moved | appletvos | stated at publication 15.7, now states 16.3Release branch starts at 0.not counted: Description already named the later value | Days to revision 150 | |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23500 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23503 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-272 commits | Fix version moved | appletvos | stated at publication 12.6, now states 16.3Branches and original-value intervals are stated on each row.not counted: Description already named the later value | Days to revision 150 | |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23511 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23517 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23502 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23518 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-272 commits | Fix version moved | appletvos | stated at publication 11.7, now states 16.3Branches and original-value intervals are stated on each row.not counted: Description already named the later value | Days to revision 150 | |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23517 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | same kind of change as the line above | CVE-2023-23518 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-27 | Fix version moved | CVE-2023-28206 | appleios and ipados | stated at publication 15.7, now states 16.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 15.7 still holds | not dated |
| 2023-07-27 | Fix version moved | CVE-2023-23514 | applemacos | stated at publication 13.2, now states 13.3Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 13.2 still holds | not dated |
| Wed 26 Jul 2023· 9 record changes | |||||
| 2023-07-26 | Fix version moved | CVE-2023-23499 | appletvos | stated at publication 11.7, now states 16.3Release branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-26 | Fix version moved | appletvos | stated at publication 12.6, now states 16.3Release branch starts at 0.not counted: Description already named the later value | Days to revision 150 | |
| 2023-07-26 | same kind of change as the line above | CVE-2023-23499 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-26 | same kind of change as the line above | CVE-2023-23504 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-26 | Fix version moved | appletvos | stated at publication 13.2, now states 16.3Release branch starts at 0.not counted: Description already named the later value | Days to revision 150 | |
| 2023-07-26 | same kind of change as the line above | CVE-2023-23499 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-26 | same kind of change as the line above | CVE-2023-23504 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-26 | same kind of change as the line above | CVE-2023-23512 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-26 | Fix version moved | CVE-2023-23504 | appletvos | stated at publication 15.7, now states 16.3Release branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 16.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 150 |
| 2023-07-26 | Fix version moved | CVE-2023-37450 | applemacos | stated at publication 13.4, now states 13.5Release branch starts at 0.Not counted: Description already named the later value. the record's own description at publication already named 13.5 — the structured field was corrected to the value the prose stated, not a fix that moved | Days to revision 0 |
| 2023-07-26 | Fix version moved | CVE-2023-28205 | appleios and ipados | stated at publication 15.7, now states 16.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 15.7 still holds | not dated |
| Wed 12 Jul 2023· 1 record change | |||||
| 2023-07-12 | CVSS base score changed | CVE-2023-20119 | whole record cisco | stated at publication 5.4, now states 6.1Assessments 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 15 |
| Thu 15 Jun 2023· 1 record change | |||||
| 2023-06-15 | Fix version moved | CVE-2023-0009 | palo alto networksglobalprotect app palo_alto | stated at publication 6.1.1, now states 6.2Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.1.1 still holds | not dated |
| Tue 13 Jun 2023· 2 record changes | |||||
| 2023-06-13 | Affected range extended | unknowneasy forms for mailchimp WPScan | stated at publication 6.8.8, now states 6.8.9Release branch starts at 0.not counted: Same claim, other operator | Days to revision 1 to 14 | |
| 2023-06-13 | same kind of change as the line above | CVE-2023-1323 | same vendor as the line above | same change as the line aboveRelease 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 1 |
| 2023-06-13 | same kind of change as the line above | CVE-2023-2518 | same vendor as the line above | same change as the line aboveRelease 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 |
| Tue 30 May 2023· 1 record change | |||||
| 2023-05-30 | Affected range extended | CVE-2023-0779 | zephyrproject-rtoszephyr zephyr | stated at publication v3.3, now states v3.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 1 |
| Wed 24 May 2023· 1 record change | |||||
| 2023-05-24 | Fix version moved | CVE-2023-2597 | eclipse foundationeclipse openj9 eclipse | stated at publication 0.37.0, now states 0.37.0Release 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 |
| Wed 10 May 2023· 4 record changes | |||||
| 2023-05-10 | Affected range extended | CVE-2023-22813 | sandiskibi mobile app WDC PSIRT | stated at publication 4.21.0, now states 4.21.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 2 |
| 2023-05-10 | Affected range extended | CVE-2023-22813 | sandiskibi web app WDC PSIRT | stated at publication 4.26.0-6126, now states 4.26.0-6126Release 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 2 |
| 2023-05-10 | Affected range extended | CVE-2023-22813 | western digital2 products WDC PSIRT | stated at publication 4.21.0, now states 4.21.0Release branch starts at 0.not counted: Same claim, other operator | Days to revision 2 |
| 2023-05-10 | same kind of change as the line above | CVE-2023-22813 | same vendor as the line above | same change as the line aboveRelease 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 2 |
| 2023-05-10 | same kind of change as the line above | CVE-2023-22813 | same vendor as the line above | same change as the line aboveRelease 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 2 |
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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
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 →