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 or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together. | Vendor or package, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry. | What changed | Days to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong. |
|---|---|---|---|---|---|
| Wed 16 Aug 2023· 13 record changes | |||||
| 2023-08-16 | Fix version moved | CVE-2023-21709 | 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. 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 | CVE-2023-21709 | 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. 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 | CVE-2023-35368 | 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. 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 | CVE-2023-35368 | 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. 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 | CVE-2023-35388 | 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. 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 | CVE-2023-35388 | 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. 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 | CVE-2023-38181 | 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. 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 | CVE-2023-38181 | 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. 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 | CVE-2023-38182 | 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. 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 | CVE-2023-38182 | 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. 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 | CVE-2023-38185 | 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. 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 | CVE-2023-38185 | 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. 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 | CVE-2023-3729 | googlechrome Chrome | stated at publication 115.0.5790.98, now states 115.0.5790.131Release 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 | Fix version moved | CVE-2023-3731 | googlechrome Chrome | stated at publication 115.0.5790.98, now states 115.0.5790.131Release 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 | Fix version moved | CVE-2023-3739 | googlechrome Chrome | stated at publication 115.0.5790.98, now states 115.0.5790.131Release 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 · 1 advisory change | |||||
| 2023-07-27 | Fix version moved | CVE-2023-23496 | appletvos | stated at publication 13.2, 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-27 | Fix version moved | CVE-2023-23500 | appletvos | stated at publication 13.2, 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-27 | Fix version moved | CVE-2023-23500 | 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-27 | Fix version moved | CVE-2023-23503 | appletvos | stated at publication 13.2, 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-27 | Fix version moved | CVE-2023-23503 | 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-27 | Fix version moved | CVE-2023-23511 | appletvos | stated at publication 12.6, 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-27 | Fix version moved | CVE-2023-23511 | appletvos | stated at publication 13.2, 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-27 | Fix version moved | CVE-2023-23517 | 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-27 | Fix version moved | CVE-2023-23517 | appletvos | stated at publication 12.6, 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-27 | Fix version moved | CVE-2023-23517 | appletvos | stated at publication 13.2, 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-27 | Fix version moved | CVE-2023-23519 | appletvos | stated at publication 13.2, 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-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-23502 | appletvos | stated at publication 12.6, 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-27 | Fix version moved | CVE-2023-23502 | appletvos | stated at publication 13.2, 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-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 |
| 2023-07-27 | Fix version moved | CVE-2023-23518 | 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-27 | Fix version moved | CVE-2023-23518 | appletvos | stated at publication 12.6, 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-27 | Fix version moved | CVE-2023-23518 | appletvos | stated at publication 13.2, 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-27published 2023-07-17 | Package added to advisory | GHSA-9x44-9pgq-cf45CVE-2023-37475 | high | not named as affected when the advisory was published, now names github.com/hamba/avro/v2 | Days to revision 10 |
| 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 | CVE-2023-23499 | appletvos | stated at publication 12.6, 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-23499 | appletvos | stated at publication 13.2, 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-23504 | appletvos | stated at publication 12.6, 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-23504 | appletvos | stated at publication 13.2, 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-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-23512 | appletvos | stated at publication 13.2, 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 | CVE-2023-1323 | 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. `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 | Affected range extended | CVE-2023-2518 | 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. `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· 6 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 digitalmy cloud home 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 | western digitalmy cloud home 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 digitalmy cloud os 5 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 | western digitalmy cloud os 5 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 |
| Tue 9 May 2023· 1 record change | |||||
| 2023-05-09 | CVSS base score changed | CVE-2023-21738 | whole record microsoft | stated at publication 7.1, now states 7.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 120 |
| Thu 27 Apr 2023· 2 record changes | |||||
| 2023-04-27 | CVSS base score changed | CVE-2023-21561 | whole record microsoft | stated at publication 8.8, now states 7.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 108 |
| 2023-04-27 | CVSS base score changed | CVE-2023-21779 | whole record microsoft | stated at publication 7.3, now states 7.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 108 |
| Mon 17 Apr 2023· 1 advisory change | |||||
| 2023-04-17published 2022-02-15 | Package added to advisory | GHSA-6hv3-7c34-4hx8CVE-2019-14802 | moderate | not named as affected when the advisory was published, now names github.com/hashicorp/nomad | not dated |
| Fri 7 Apr 2023· 1 advisory change | |||||
| 2023-04-07published 2023-03-31 | Package added to advisory | GHSA-63f2-6959-2pxjCVE-2023-1776 | moderate | not named as affected when the advisory was published, now names github.com/mattermost/mattermost-server/v5 | Days to revision 7 |
| Thu 6 Apr 2023· 1 advisory change | |||||
| 2023-04-06published 2023-03-30 | Package added to advisory | GHSA-2wcr-87wf-cf9jCVE-2023-27489 | high | not named as affected when the advisory was published, now names kiwitcms | Days to revision 7 |
| Thu 30 Mar 2023· 1 advisory change | |||||
| 2023-03-30published 2021-08-25 | Package added to advisory | GHSA-p9gf-gmfv-398mCVE-2021-29938 | high | not named as affected when the advisory was published, now names slice-deque | not dated |
| Wed 29 Mar 2023· 1 record change | |||||
| 2023-03-29 | Affected range extended | CVE-2023-0149 | unknownwordprezi WPScan | stated at publication 0.8.2, now states 0.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 51 |
| Thu 23 Mar 2023· 1 advisory change | |||||
| 2023-03-23published 2023-03-16 | Package added to advisory | GHSA-5g39-ppwg-6xx8CVE-2023-28105 | high | not named as affected when the advisory was published, now names github.com/dablelv/go-huge-util | Days to revision 7 |
| Wed 8 Mar 2023· 1 advisory change | |||||
| 2023-03-08published 2022-08-31 | Package added to advisory | GHSA-5229-94p3-7wwqCVE-2022-36745 | moderate | not named as affected when the advisory was published, now names librenms/librenms | not dated |
| Sat 25 Feb 2023· 7 advisory changes | |||||
| 2023-02-25published 2022-02-11 | Package added to advisory | GHSA-76wf-9vgp-pj7w | moderate | not named as affected when the advisory was published, now names github.com/aws/aws-sdk-go | not dated |
| 2023-02-25published 2022-05-13 | Package added to advisory | GHSA-fcf9-6fv2-fc5vCVE-2018-17143 | high | not named as affected when the advisory was published, now names golang.org/x/net | Days to revision 288 |
| 2023-02-25published 2022-05-13 | Package added to advisory | GHSA-h62f-wm92-2cmwCVE-2017-11468 | high | not named as affected when the advisory was published, now names github.com/docker/distribution | Days to revision 288 |
| 2023-02-25published 2022-06-24 | Package added to advisory | GHSA-p782-xgp4-8hr8CVE-2022-29526 | moderate | not named as affected when the advisory was published, now names golang.org/x/sys | Days to revision 246 |
| 2023-02-25published 2022-05-14 | Package added to advisory | GHSA-p5gc-957x-gfw9CVE-2018-12018 | high | not named as affected when the advisory was published, now names github.com/ethereum/go-ethereum | Days to revision 287 |
| 2023-02-25published 2023-01-14 | Package added to advisory | GHSA-fxg5-wq6x-vr4wCVE-2022-41721 | high | not named as affected when the advisory was published, now names golang.org/x/net | Days to revision 42 |
| 2023-02-25published 2022-05-14 | Package added to advisory | GHSA-w4xh-w33p-4v29CVE-2017-17831 | high | not named as affected when the advisory was published, now names github.com/git-lfs/git-lfs | Days to revision 287 |
| Fri 24 Feb 2023· 17 advisory changes | |||||
| 2023-02-24published 2023-02-08 | Package added to advisory | GHSA-74fp-r6jw-h4mp | high | not named as affected when the advisory was published, now names k8s.io/apimachinery | Days to revision 17 |
| 2023-02-24published 2023-02-06 | Package added to advisory | GHSA-w55j-f7vx-6q37CVE-2018-1103 | moderate | not named as affected when the advisory was published, now names github.com/openshift/source-to-image | Days to revision 18 |
| 2023-02-24published 2022-12-26 | Package added to advisory | GHSA-ppp9-7jff-5vj2CVE-2021-38561 | high | not named as affected when the advisory was published, now names golang.org/x/text | Days to revision 61 |
| 2023-02-24published 2022-05-24 | Package added to advisory | GHSA-vfxc-r2gx-v2vqCVE-2019-12496 | high | not named as affected when the advisory was published, now names github.com/hybridgroup/gobot | Days to revision 276 |
| 2023-02-24published 2022-05-13 | Package added to advisory | GHSA-5p4h-3377-7w67CVE-2018-17075 | high | not named as affected when the advisory was published, now names golang.org/x/net | Days to revision 288 |
| 2023-02-24published 2022-05-13 | Package added to advisory | GHSA-mv93-wvcp-7m7rCVE-2018-17848 | high | not named as affected when the advisory was published, now names golang.org/x/net | Days to revision 288 |
| 2023-02-24published 2022-05-13 | Package added to advisory | GHSA-2wp2-chmh-r934CVE-2018-17142 | high | not named as affected when the advisory was published, now names golang.org/x/net | Days to revision 288 |
| 2023-02-24published 2022-05-24 | Package added to advisory | GHSA-8mpq-fmr3-6jxvCVE-2015-1340 | high | not named as affected when the advisory was published, now names github.com/lxc/lxd | Days to revision 276 |
| 2023-02-24published 2022-05-24 | Package added to advisory | GHSA-3vm4-22fp-5rfmCVE-2020-29652 | high | not named as affected when the advisory was published, now names golang.org/x/crypto | Days to revision 276 |
| 2023-02-24published 2022-05-24 | Package added to advisory | GHSA-83g2-8m93-v3w7CVE-2021-33194 | high | not named as affected when the advisory was published, now names golang.org/x/net | Days to revision 276 |
| 2023-02-24published 2022-05-24 | Package added to advisory | GHSA-h86h-8ppg-mxmhCVE-2021-31525 | moderate | not named as affected when the advisory was published, now names golang.org/x/net | Days to revision 276 |
| 2023-02-24published 2023-02-07 | Package added to advisory | GHSA-xhjq-w7xm-p8qjCVE-2017-3204 | high | not named as affected when the advisory was published, now names golang.org/x/crypto | Days to revision 17 |
| 2023-02-24published 2022-05-24 | Package added to advisory | GHSA-hgr8-6h9x-f7q9CVE-2019-9512 | high | not named as affected when the advisory was published, now names golang.org/x/net | Days to revision 276 |
| 2023-02-24published 2022-05-24 | Package added to advisory | GHSA-r5c5-pr8j-pfp7CVE-2019-11840 | moderate | not named as affected when the advisory was published, now names golang.org/x/crypto | Days to revision 276 |
| 2023-02-24published 2022-05-24 | Package added to advisory | GHSA-jmrx-5g74-6v2fCVE-2019-11250 | moderate | not named as affected when the advisory was published, now names k8s.io/client-go | Days to revision 276 |
| 2023-02-24published 2022-05-24 | Package added to advisory | GHSA-jmrx-5g74-6v2fCVE-2019-11250 | moderate | not named as affected when the advisory was published, now names k8s.io/kubernetes | Days to revision 276 |
| 2023-02-24published 2022-05-24 | Package added to advisory | GHSA-39qc-96h7-956fCVE-2019-9514 | high | not named as affected when the advisory was published, now names golang.org/x/net | Days to revision 276 |
| Thu 23 Feb 2023· 1 advisory change | |||||
| 2023-02-23published 2022-05-13 | Package added to advisory | GHSA-4r78-hx75-jjj2CVE-2018-17847 | high | not named as affected when the advisory was published, now names golang.org/x/net | Days to revision 287 |
| Wed 22 Feb 2023· 1 advisory change | |||||
| 2023-02-22published 2022-10-14 | Package added to advisory | GHSA-69ch-w2m2-3vjpCVE-2022-32149 | high | not named as affected when the advisory was published, now names golang.org/x/text | not dated |
| Sat 18 Feb 2023· 1 advisory change | |||||
| 2023-02-18published 2022-09-07 | Package added to advisory | GHSA-gwc9-m7rh-j2wwCVE-2021-43565 | high | not named as affected when the advisory was published, now names golang.org/x/crypto | not dated |
Two units, never added: changes to a CVE record or KEV entry, and changes to a GitHub advisory. 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 →