What changed this week
| 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. |
|---|---|---|---|---|---|
| Fri 4 Sep 2026· 16 changes | |||||
| 2026-09-04 | Added to CISA KEV | CVE-2026-85046 | GoogleChromium V8 CISA KEV | fix due 2026-09-18 | Duration unknown |
| 2026-09-04 | Ransomware use confirmed | CVE-2022-37969 | MicrosoftWindows CISA KEV | stated at publication Unknown, now states Known | Duration unknown |
| 2026-09-04 | Ransomware use confirmed | CVE-2016-4117 | AdobeFlash Player CISA KEV | stated at publication Unknown, now states Known | Duration unknown |
| 2026-09-04 | Product added | CVE-2025-9784 | not named as affected at publication, now names red hat jboss enterprise application platform 8.1.6 | Time to revision 367 days | |
| 2026-09-04 | Product added | VulnCheck | not named as affected at publication, now names gfi clearview | Time to revision 0 days | |
| 2026-09-04 | same kind of change as the line above | CVE-2026-74235 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-09-04 | same kind of change as the line above | CVE-2026-74236 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-09-04 | same kind of change as the line above | CVE-2026-74237 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-09-04 | Product added | CVE-2026-56152 | not named as affected at publication, now names kibana | Time to revision 65 days | |
| 2026-09-04 | Product added | CVE-2026-12894 | redhat | not named as affected at publication, now names quarkus-qute | Time to revision 4 days |
| 2026-09-04 | Product added | CVE-2026-49509 | samsung.tv_appliance | not named as affected at publication, now names rlottie | Time to revision 0 days |
| 2026-09-04 | Product added | CVE-2026-11332 | not named as affected at publication, now names red hat satellite 6.18 for rhel 9 and 1 more | Time to revision 91 days | |
| 2026-09-04 | same kind of change as the line above | CVE-2026-11332 | same vendor as the line above | not named as affected at publication, now names red hat satellite 6.18 for rhel 9 | Time to revision 91 days |
| 2026-09-04 | same kind of change as the line above | CVE-2026-11332 | same vendor as the line above | not named as affected at publication, now names red hat satellite 6.19 for rhel 9 | Time to revision 91 days |
| 2026-09-04 | CVSS base score changed | CVE-2026-13732 | whole record redhat | stated at publication 7.8, now states 7.0CVSS v3.1 · base scoreHighHigh | Time to revision 4 days |
| 2026-09-04 | Record state changed | CVE-2026-18745 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 0 days |
| 2026-09-04 | Record state changed | CVE-2026-61485 | whole record apache | stated at publication PUBLISHED, now states REJECTED | Time to revision 30 days |
| 2026-09-04 | Record state changed | CVE-2026-19582 | whole record redhat | stated at publication PUBLISHED, now states REJECTED | Time to revision 15 days |
| Thu 3 Sep 2026· 42 changes | |||||
| 2026-09-037 commits | Product added | 40 rows, one per record and product | not named as affected at publication, now names red hat satellite 6.17 for rhel 9 and 5 moreBranches and original-value intervals are stated on each row. | Time to revision 1 to 464 days | |
| 2026-09-03 | same kind of change as the line above | CVE-2026-11332 | same vendor as the line above | not named as affected at publication, now names red hat satellite 6.17 for rhel 9 | Time to revision 91 days |
| 2026-09-03 | same kind of change as the line above | CVE-2026-15563 | same vendor as the line above | not named as affected at publication, now names red hat single sign-on 7 | Time to revision 24 days |
| 2026-09-03 | same kind of change as the line above | CVE-2026-18255 | same vendor as the line above | not named as affected at publication, now names red hat quay 3.15 | Time to revision 36 days |
| 2026-09-03 | same kind of change as the line above | CVE-2025-5222 | same vendor as the line above | not named as affected at publication, now names red hat openshift container platform 4.17 | Time to revision 464 days |
| 2026-09-03 | same kind of change as the line above | CVE-2026-14476 | same vendor as the line above | not named as affected at publication, now names red hat openshift container platform 4.17 | Time to revision 58 days |
| 2026-09-03 | same kind of change as the line above | CVE-2026-2340 | same vendor as the line above | not named as affected at publication, now names red hat openshift container platform 4.17 | Time to revision 99 days |
| 2026-09-03 | same kind of change as the line above | CVE-2026-3833 | same vendor as the line above | not named as affected at publication, now names red hat openshift container platform 4.17 | Time to revision 126 days |
| 2026-09-03 | same kind of change as the line above | CVE-2026-42011 | same vendor as the line above | not named as affected at publication, now names red hat openshift container platform 4.17 | Time to revision 119 days |
| 32 more rows in this change are not listed here. Open all 40 rows → | |||||
| 2026-09-03 | Product added | CVE-2026-58641 | not named as affected at publication, now names skiasharp | Time to revision 23 days | |
| 2026-09-03 | Record state changed | CVE-2026-76848 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 10 days |
| Wed 2 Sep 2026· 59 changes | |||||
| 2026-09-02 | Added to CISA KEV | CVE-2026-59822 | BerriAILiteLLM CISA KEV | fix due 2026-09-16 | Duration unknown |
| 2026-09-02 | Added to CISA KEV | CVE-2026-48710 | KludexStarlette CISA KEV | fix due 2026-09-16 | Duration unknown |
| 2026-09-02 | Added to CISA KEV | CVE-2026-49869 | KestraKestra OSS CISA KEV | fix due 2026-09-05 | Duration unknown |
| 2026-09-02 | Added to CISA KEV | CVE-2026-82329 | JFrogArtifactory CISA KEV | fix due 2026-09-05 | Duration unknown |
| 2026-09-02 | Added to CISA KEV | CVE-2026-9586 | SangomaSwitchvox CISA KEV | fix due 2026-09-05 | Duration unknown |
| 2026-09-02 | Added to CISA KEV | SonicWallSMA1000 Appliances | fix due 2026-09-05 | Duration unknown | |
| 2026-09-02 | same kind of change as the line above | CVE-2026-83548 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-09-02 | same kind of change as the line above | CVE-2026-83549 | same vendor as the line above | same change as the line above | Duration unknown |
| 2026-09-02 | Fix version moved | CVE-2026-65675 | microsoftmicrosoft visual studio code copilot chat extension | stated at publication 1.132.1, now states 1.135Release branch starts at 0.27.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | Fix version moved | microsoftvisual studio code | stated at publication 1.132.1, now states 1.135Release branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days | |
| 2026-09-02 | same kind of change as the line above | CVE-2026-58650 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-59113 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-47285 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-69320 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-69278 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-69306 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-70335 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-70336 | same vendor as the line above | same change as the line aboveRelease branch starts at 1.0.0.Original value first replaced 2026-08-28; this value first seen 2026-09-02. | Time to revision 17 days |
| 2026-09-02 | Product added | CVE-2026-15809 | not named as affected at publication, now names red hat openshift container platform 4.19 | Time to revision 49 days | |
| 2026-09-02 | Product added | CVE-2023-50224 | zdi | not named as affected at publication, now names archer c5 and 20 more | Time to revision 853 days |
| 2026-09-02 | same kind of change as the line above | CVE-2023-50224 | same vendor as the line above | not named as affected at publication, now names archer c5 | Time to revision 853 days |
| 2026-09-02 | same kind of change as the line above | CVE-2023-50224 | same vendor as the line above | not named as affected at publication, now names archer c7 | Time to revision 853 days |
| 2026-09-02 | same kind of change as the line above | CVE-2023-50224 | same vendor as the line above | not named as affected at publication, now names tl-mr3420 | Time to revision 853 days |
| 2026-09-02 | same kind of change as the line above | CVE-2023-50224 | same vendor as the line above | not named as affected at publication, now names tl-mr6400 | Time to revision 853 days |
| 2026-09-02 | same kind of change as the line above | CVE-2023-50224 | same vendor as the line above | not named as affected at publication, now names tl-wa801nd | Time to revision 853 days |
| 2026-09-02 | same kind of change as the line above | CVE-2023-50224 | same vendor as the line above | not named as affected at publication, now names tl-wa901nd | Time to revision 853 days |
| 2026-09-02 | same kind of change as the line above | CVE-2023-50224 | same vendor as the line above | not named as affected at publication, now names tl-wdr3500 | Time to revision 853 days |
| 2026-09-02 | same kind of change as the line above | CVE-2023-50224 | same vendor as the line above | not named as affected at publication, now names tl-wdr3600 | Time to revision 853 days |
| 13 more rows in this change are not listed here. Open all 21 rows → | |||||
| 2026-09-022 commits | Product added | redhat | not named as affected at publication, now names gvfsBranches and original-value intervals are stated on each row. | Time to revision 1 days | |
| 2026-09-02 | same kind of change as the line above | CVE-2026-84268 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-84269 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-84270 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-84267 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2026-09-02 | Product added | CVE-2026-17527 | not named as affected at publication, now names red hat container native virtualization 4.14 | Time to revision 37 days | |
| 2026-09-02 | Product added | CVE-2026-84218 | not named as affected at publication, now names red hat amq broker 7 | Time to revision 1 days | |
| 2026-09-022 commits | Product added | not named as affected at publication, now names red hat openshift container platform 4.22Branches and original-value intervals are stated on each row. | Time to revision 22 to 26 days | ||
| 2026-09-02 | same kind of change as the line above | CVE-2026-72693 | same vendor as the line above | same change as the line above | Time to revision 22 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-15816 | same vendor as the line above | same change as the line above | Time to revision 26 days |
| 2026-09-02 | Product added | CVE-2026-15816 | not named as affected at publication, now names red hat openshift container platform 4.20 | Time to revision 26 days | |
| 2026-09-02 | CVSS base score changed | CVE-2026-71474 | whole record redhat | stated at publication 6.3, now states 7.1CVSS v3.1 · base scoreMediumHigh | Time to revision 22 days |
| 2026-09-02 | CVSS base score changed | CVE-2026-71475 | whole record redhat | stated at publication 5.0, now states 6.8CVSS v3.1 · base scoreMediumMedium | Time to revision 22 days |
| 2026-09-02 | Record state changed | CVE-2026-39909 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 12 days |
| 2026-09-023 commits | Record state changed | whole record zdi | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 223 days | |
| 2026-09-02 | same kind of change as the line above | CVE-2026-0766 | same vendor as the line above | same change as the line above | Time to revision 223 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-0765 | same vendor as the line above | same change as the line above | Time to revision 223 days |
| 2026-09-02 | same kind of change as the line above | CVE-2026-0767 | same vendor as the line above | same change as the line above | Time to revision 223 days |
| 2026-09-02published 2026-05-06 | Advisory fix version moved | GHSA-248h-974q-xrc2 | mavencom.getaxonflow:axonflow-sdk moderate | stated at publication 6.0.0, now states 7.0.0 | Time to revision 119 days |
| 2026-09-02published 2024-10-09 to 2025-03-20 | Advisory withdrawn | whole advisory3 bands | withdrawn 2026-09-02 | Time to revision 531 to 693 days | |
| 2026-09-02published 2025-03-20 | same kind of change as the line above | GHSA-x757-hv69-jr45CVE-2024-7959 | same package and registry as the line abovehigh | withdrawn 2026-09-02 | Time to revision 531 days |
| 2026-09-02published 2025-03-20 | same kind of change as the line above | GHSA-pqwr-phvv-v49fCVE-2024-7039 | same package and registry as the line abovehigh | withdrawn 2026-09-02 | Time to revision 531 days |
| 2026-09-02published 2025-03-20 | same kind of change as the line above | GHSA-crh6-pj8c-xrhcCVE-2024-7034 | same package and registry as the line abovemoderate | withdrawn 2026-09-02 | Time to revision 531 days |
| 2026-09-02published 2025-03-20 | same kind of change as the line above | GHSA-3p9q-7w63-3f8qCVE-2024-7033 | same package and registry as the line abovemoderate | withdrawn 2026-09-02 | Time to revision 531 days |
| 2026-09-02published 2024-10-09 | same kind of change as the line above | GHSA-mq92-jr35-ffpcCVE-2024-7038 | same package and registry as the line abovelow | withdrawn 2026-09-02 | Time to revision 693 days |
| Tue 1 Sep 2026· 40 changes | |||||
| 2026-09-012 commits | Product added | CVE-2026-15809 | not named as affected at publication, now names red hat openshift container platform 4.21 and 1 moreBranches and original-value intervals are stated on each row. | Time to revision 48 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-15809 | same vendor as the line above | not named as affected at publication, now names red hat openshift container platform 4.21 | Time to revision 48 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-15809 | same vendor as the line above | not named as affected at publication, now names red hat openshift container platform 4.20 | Time to revision 48 days |
| 2026-09-01 | Product added | CVE-2026-83596 | redhat | not named as affected at publication, now names webkit | Time to revision 1 days |
| 2026-09-01 | Product added | CVE-2026-83596 | redhat | not named as affected at publication, now names webkitgtk | Time to revision 1 days |
| 2026-09-01 | Product added | CVE-2026-11873 | not named as affected at publication, now names red hat certificate system 9 | Time to revision 0 days | |
| 2026-09-01 | Product added | not named as affected at publication, now names red hat discovery 2 | Time to revision 29 to 148 days | ||
| 2026-09-01 | same kind of change as the line above | CVE-2026-15588 | same vendor as the line above | same change as the line above | Time to revision 43 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-18477 | same vendor as the line above | same change as the line above | Time to revision 29 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-18508 | same vendor as the line above | same change as the line above | Time to revision 29 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-58010 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-58011 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-58012 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-58013 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-58014 | same vendor as the line above | same change as the line above | Time to revision 63 days |
| 2 more rows in this change are not listed here. Open all 10 rows → | |||||
| 2026-09-01 | CVSS base score changed | CVE-2026-66795 | whole record redhat | stated at publication 9.1, now states 9.9CVSS v3.1 · base scoreCriticalCritical | Time to revision 15 days |
| 2026-09-01 | CVSS base score changed | CVE-2026-66783 | whole record redhat | stated at publication 8.2, now states 4.4CVSS v3.1 · base scoreHighMedium | Time to revision 14 days |
| 2026-09-01 | CVSS base score changed | CVE-2026-66785 | whole record redhat | stated at publication 9.9, now states 2.5CVSS v3.1 · base scoreCriticalLow | Time to revision 12 days |
| 2026-09-01 | CVSS base score changed | CVE-2026-66787 | whole record redhat | stated at publication 8.7, now states 5.4CVSS v3.1 · base scoreHighMedium | Time to revision 12 days |
| 2026-09-01 | CVSS base score changed | CVE-2026-66788 | whole record redhat | stated at publication 9.9, now states 3.7CVSS v3.1 · base scoreCriticalLow | Time to revision 12 days |
| 2026-09-01 | CVSS base score changed | CVE-2026-66781 | whole record redhat | stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 14 days |
| 2026-09-01 | CVSS base score changed | CVE-2026-66782 | whole record redhat | stated at publication 7.8, now states 5.8CVSS v3.1 · base scoreHighMedium | Time to revision 14 days |
| 2026-09-01 | CVSS base score changed | CVE-2026-66780 | whole record redhat | stated at publication 9.9, now states 6.5CVSS v3.1 · base scoreCriticalMedium | Time to revision 14 days |
| 2026-09-01 | CVSS base score changed | CVE-2026-6876 | whole record SN | stated at publication 8.7, now states 10.0CVSS v4.0 · base scoreHighCritical | Time to revision 5 days |
| 2026-09-01 | Record state changed | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Time to revision 7 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2024-58377 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2024-58378 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2025-71346 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2025-71406 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2025-71407 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | Record state changed | whole record Wordfence | stated at publication PUBLISHED, now states REJECTED | Time to revision 7 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-78477 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-78562 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-78563 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-78566 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-78568 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-78570 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-78572 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-78576 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-09-01published 2026-06-16 | Package added to advisory | GHSA-5r4w-85f3-pw66 | high | not named as affected when the advisory was published, now names github.com/traefik/traefik/v2 and 1 more | Time to revision 77 days |
| 2026-09-01published 2026-06-16 | same kind of change as the line above | GHSA-5r4w-85f3-pw66CVE-2026-48491 | same package registry as the line abovehigh | not named as affected when the advisory was published, now names github.com/traefik/traefik/v2 | Time to revision 77 days |
| 2026-09-01published 2026-06-16 | same kind of change as the line above | GHSA-5r4w-85f3-pw66CVE-2026-48491 | same package registry as the line abovehigh | not named as affected when the advisory was published, now names github.com/traefik/traefik/v3 | Time to revision 77 days |
| 2026-09-01published 2025-12-01 | Advisory severity changed | GHSA-569q-mpph-wgwwCVE-2025-71401 | whole advisoryhigh | stated at publication LOW, now states HIGHA vector changed on a shared CVSS version. The band and vector edits may have occurred separately. | Time to revision 274 days |
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 and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
What this page cannot see
Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.
A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.
The units, the refusals, the cut-offs and every source, in full →
Paste your closed CVE tickets and see which of these changes hit them →