Every change, newest first
Showing changes seen on 2026-03-30. Every day
| 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. |
|---|---|---|---|---|---|
| Mon 30 Mar 2026· 163 changes | |||||
| 2026-03-30 | Added to CISA KEV | CVE-2026-3055 | CitrixNetScaler CISA KEV | fix due 2026-04-02 | Duration unknown |
| 2026-03-30 | Fix version moved | CVE-2025-13611 | gitlabgitlab | stated at publication 18.6.1, now states 18.6.3Release branch starts at 18.6. | Time to revision 124 days |
| 2026-03-302 commits | Affected range extended | brother industries, ltdpj-883 rapid7 | stated at publication 1.07, now states 1.08Branches and original-value intervals are stated on each row. | Time to revision 278 to 279 days | |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 278 days |
| 2026-03-302 commits | Affected range extended | brother industries, ltdpt-p750w rapid7 | stated at publication 1.18, now states 1.22Branches and original-value intervals are stated on each row. | Time to revision 278 to 279 days | |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 278 days |
| 2026-03-302 commits | Affected range extended | 4 rows, one per record and product | brother industries, ltd2 products rapid7 | stated at publication 1.31, now states 1.33Branches and original-value intervals are stated on each row. | Time to revision 278 to 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 278 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 278 days |
| 2026-03-30 | Affected range extended | CVE-2024-51978 | brother industries, ltdql-820nwbc rapid7 | stated at publication 2.04, now states 2.11Release branch starts at 0. | Time to revision 279 days |
| 2026-03-302 commits | Affected range extended | brother industries, ltdrj-4250wb rapid7 | stated at publication 1.41, now states 1.44Branches and original-value intervals are stated on each row. | Time to revision 278 to 279 days | |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 278 days |
| 2026-03-302 commits | Affected range extended | brother industries, ltdtd-2130n rapid7 | stated at publication 1.13, now states 1.25Branches and original-value intervals are stated on each row. | Time to revision 278 to 279 days | |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | same change as the line aboveRelease branch starts at 0. | Time to revision 278 days |
| 2026-03-30 | Affected range extended | CVE-2026-23813 | hpe | stated at publication 10.13.1101, now states 10.13.1160Release branch starts at 10.13.0000. | Time to revision 20 days |
| 2026-03-30 | Product added | CVE-2024-51978 | rapid7 | not named as affected at publication, now names dcp-b7520dw (china) and 29 more | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | not named as affected at publication, now names dcp-b7520dw (china) | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | not named as affected at publication, now names dcp-b7535dw (china) | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | not named as affected at publication, now names dcp-b7640dw (asia) | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | not named as affected at publication, now names dcp-l2535dw (china) | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | not named as affected at publication, now names dcp-l2540dw (japan) | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | not named as affected at publication, now names dcp-l2550dw (china) | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | not named as affected at publication, now names dcp-l2550dw (japan) | Time to revision 279 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51978 | same vendor as the line above | not named as affected at publication, now names dcp-l2550dw (taiwan) | Time to revision 279 days |
| 22 more rows in this change are not listed here. Open all 30 rows → | |||||
| 2026-03-30 | Product added | CVE-2024-51977 | rapid7 | not named as affected at publication, now names dcp-b7520dw (china) and 23 more | Time to revision 278 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | not named as affected at publication, now names dcp-b7520dw (china) | Time to revision 278 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | not named as affected at publication, now names dcp-b7535dw (china) | Time to revision 278 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | not named as affected at publication, now names dcp-j973n w/b | Time to revision 278 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | not named as affected at publication, now names dcp-j978n w/b | Time to revision 278 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | not named as affected at publication, now names dcp-j982n w/b | Time to revision 278 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | not named as affected at publication, now names dcp-l2535dw (china) | Time to revision 278 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | not named as affected at publication, now names dcp-l2540dw (japan) | Time to revision 278 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-51977 | same vendor as the line above | not named as affected at publication, now names dcp-l2550dw (china) | Time to revision 278 days |
| 16 more rows in this change are not listed here. Open all 24 rows → | |||||
| 2026-03-30 | Product added | CVE-2026-33634 | GitHub_M | not named as affected at publication, now names telnyx | Time to revision 7 days |
| 2026-03-302 commits | Product added | MediaTek | not named as affected at publication, now names mediatek chipsetBranches and original-value intervals are stated on each row. | Time to revision 28 to 84 days | |
| 2026-03-30 | same kind of change as the line above | CVE-2025-20760 | same vendor as the line above | same change as the line above | Time to revision 84 days |
| 2026-03-30 | same kind of change as the line above | CVE-2025-20761 | same vendor as the line above | same change as the line above | Time to revision 84 days |
| 2026-03-30 | same kind of change as the line above | CVE-2025-20762 | same vendor as the line above | same change as the line above | Time to revision 84 days |
| 2026-03-30 | same kind of change as the line above | CVE-2025-20778 | same vendor as the line above | same change as the line above | Time to revision 84 days |
| 2026-03-30 | same kind of change as the line above | CVE-2025-20779 | same vendor as the line above | same change as the line above | Time to revision 84 days |
| 2026-03-30 | same kind of change as the line above | CVE-2025-20780 | same vendor as the line above | same change as the line above | Time to revision 84 days |
| 2026-03-30 | same kind of change as the line above | CVE-2025-20781 | same vendor as the line above | same change as the line above | Time to revision 84 days |
| 2026-03-30 | same kind of change as the line above | CVE-2025-20782 | same vendor as the line above | same change as the line above | Time to revision 84 days |
| 62 more rows in this change are not listed here. Open all 70 rows → | |||||
| 2026-03-30 | Product added | 4 rows, one per record and product | not named as affected at publication, now names red hat jboss enterprise application platform 7.1 eus for rhel 7 and 1 more | Time to revision 66 to 117 days | |
| 2026-03-30 | same kind of change as the line above | CVE-2024-3884 | same vendor as the line above | not named as affected at publication, now names red hat jboss enterprise application platform 7.1 eus for rhel 7 | Time to revision 117 days |
| 2026-03-30 | same kind of change as the line above | CVE-2024-3884 | same vendor as the line above | not named as affected at publication, now names red hat jboss enterprise application platform 7.3 eus for rhel 7 | Time to revision 117 days |
| 2026-03-30 | same kind of change as the line above | CVE-2026-0603 | same vendor as the line above | not named as affected at publication, now names red hat jboss enterprise application platform 7.1 eus for rhel 7 | Time to revision 66 days |
| 2026-03-30 | same kind of change as the line above | CVE-2026-0603 | same vendor as the line above | not named as affected at publication, now names red hat jboss enterprise application platform 7.3 eus for rhel 7 | Time to revision 66 days |
| 2026-03-30 | Record state changed | whole record redhat | stated at publication PUBLISHED, now states REJECTED | Time to revision 7 to 11 days | |
| 2026-03-30 | same kind of change as the line above | CVE-2026-4427 | same vendor as the line above | same change as the line above | Time to revision 11 days |
| 2026-03-30 | same kind of change as the line above | CVE-2026-4645 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-03-30published 2025-06-28 | Advisory severity changed | GHSA-m964-fjrh-xxq2CVE-2025-32897 | whole advisorylow | stated at publication CRITICAL, now states LOWCVSS versions were removed or replaced; no shared version's vector was rescored. | Time to revision 275 days |
| 2026-03-30published 2026-03-03 | Advisory severity changed | whole advisoryhigh | stated at publication MODERATE, now states HIGHA CVSS version was added; the existing vectors stayed the same. | Time to revision 27 to 28 days | |
| 2026-03-30published 2026-03-03 | same kind of change as the line above | GHSA-h9xm-j4qg-fvpgCVE-2026-32007 | same package and registry as the line abovehigh | same change as the line above | Time to revision 27 days |
| 2026-03-30published 2026-03-03 | same kind of change as the line above | GHSA-2fgq-7j6h-9rm4CVE-2026-32003 | same package and registry as the line abovehigh | same change as the line above | Time to revision 28 days |
| 2026-03-30published 2026-03-02 to 2026-03-03 | Advisory severity changed | whole advisoryhigh | stated at publication MODERATE, now states HIGHA vector changed on a shared CVSS version. The band and vector edits may have occurred separately. | Time to revision 27 to 28 days | |
| 2026-03-30published 2026-03-03 | same kind of change as the line above | GHSA-25gx-x37c-7pphCVE-2026-32064 | same package and registry as the line abovehigh | same change as the line above | Time to revision 27 days |
| 2026-03-30published 2026-03-02 | same kind of change as the line above | GHSA-rxxp-482v-7mrhCVE-2026-32049 | same package and registry as the line abovehigh | same change as the line above | Time to revision 28 days |
| 2026-03-30published 2026-03-03 | same kind of change as the line above | GHSA-v865-p3gq-hw6mCVE-2026-32004 | same package and registry as the line abovehigh | same change as the line above | Time to revision 27 days |
| 2026-03-30published 2026-03-02 | same kind of change as the line above | GHSA-vpj2-69hf-rppwCVE-2026-32041 | same package and registry as the line abovehigh | same change as the line above | Time to revision 28 days |
| 2026-03-30published 2026-03-02 to 2026-03-03 | Advisory severity changed | whole advisorymoderate | stated at publication HIGH, now states MODERATEA vector changed on a shared CVSS version. The band and vector edits may have occurred separately. | Time to revision 27 to 28 days | |
| 2026-03-30published 2026-03-02 | same kind of change as the line above | GHSA-hwpq-rrpf-pgcqCVE-2026-32065 | same package and registry as the line abovemoderate | same change as the line above | Time to revision 28 days |
| 2026-03-30published 2026-03-03 | same kind of change as the line above | GHSA-6rcp-vxwf-3mfpCVE-2026-32052 | same package and registry as the line abovemoderate | same change as the line above | Time to revision 27 days |
| 2026-03-30published 2026-03-03 | same kind of change as the line above | GHSA-mwcg-wfq3-4gjcCVE-2026-32043 | same package and registry as the line abovemoderate | same change as the line above | Time to revision 27 days |
| 2026-03-30published 2026-03-03 | same kind of change as the line above | GHSA-4gc7-qcvf-38wgCVE-2026-32010 | same package and registry as the line abovemoderate | same change as the line above | Time to revision 27 days |
| 2026-03-30published 2026-03-03 | Advisory severity changed | GHSA-vvgp-4c28-m3jmCVE-2026-32057 | whole advisorymoderate | stated at publication LOW, now states MODERATEA vector changed on a shared CVSS version. The band and vector edits may have occurred separately. | Time to revision 27 days |
| 2026-03-30published 2026-03-02 to 2026-03-09 | Advisory severity changed | whole advisorylow | stated at publication MODERATE, now states LOWA vector changed on a shared CVSS version. The band and vector edits may have occurred separately. | Time to revision 21 to 28 days | |
| 2026-03-30published 2026-03-02 | same kind of change as the line above | GHSA-hjvp-qhm6-wrh2CVE-2026-32058 | same package and registry as the line abovelow | same change as the line above | Time to revision 28 days |
| 2026-03-30published 2026-03-09 | same kind of change as the line above | GHSA-r6qf-8968-wj9qCVE-2026-27183 | same package and registry as the line abovelow | same change as the line above | Time to revision 21 days |
| 2026-03-30published 2026-03-03 | same kind of change as the line above | GHSA-2ww6-868g-2c56CVE-2026-32040 | same package and registry as the line abovelow | same change as the line above | Time to revision 27 days |
| 2026-03-30published 2026-03-19 | Advisory withdrawn | GHSA-x6gf-mpr2-68h6CVE-2026-4427 | whole advisoryhigh | withdrawn 2026-03-30 | Time to revision 11 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 →