Every change, newest first
Showing changes seen on 2026-07-02. 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. |
|---|---|---|---|---|---|
| Thu 2 Jul 2026· 18 changes | |||||
| 2026-07-022 commits | Product added | 10 rows, one per record and product | not named as affected at publication, now names red hat openshift container platform 4.19 and 2 moreBranches and original-value intervals are stated on each row. | Time to revision 0 to 36 days | |
| 2026-07-02 | same kind of change as the line above | CVE-2026-1933 | same vendor as the line above | not named as affected at publication, now names red hat openshift container platform 4.19 | Time to revision 36 days |
| 2026-07-02 | 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.19 | Time to revision 36 days |
| 2026-07-02 | same kind of change as the line above | CVE-2026-3012 | same vendor as the line above | not named as affected at publication, now names red hat openshift container platform 4.19 | Time to revision 36 days |
| 2026-07-02 | same kind of change as the line above | CVE-2026-4408 | same vendor as the line above | not named as affected at publication, now names red hat openshift container platform 4.19 | Time to revision 36 days |
| 2026-07-02 | same kind of change as the line above | CVE-2026-5135 | 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 0 days |
| 2026-07-02 | same kind of change as the line above | CVE-2026-5135 | 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 0 days |
| 2026-07-02 | same kind of change as the line above | CVE-2026-5138 | 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 0 days |
| 2026-07-02 | same kind of change as the line above | CVE-2026-5138 | 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 0 days |
| 2 more rows in this change are not listed here. Open all 10 rows → | |||||
| 2026-07-02 | CVSS base score changed | CVE-2026-56004 | whole record suse | stated at publication 8.8, now states 10.0CVSS v3.1 · base scoreHighCritical | Time to revision 0 days |
| 2026-07-02 | CVSS base score changed | CVE-2026-44832 | whole record GitHub_M | stated at publication 7.1, now states 8.7CVSS v4.0 · base scoreHighHigh | Time to revision 37 days |
| 2026-07-02 | CVSS base score changed | CVE-2026-56371 | whole record VulnCheck | stated at publication 0.0, now states 6.9CVSS v4.0 · base scoreNoneMedium | Time to revision 9 days |
| 2026-07-02 | CVSS base score changed | CVE-2026-56379 | whole record VulnCheck | stated at publication 0.0, now states 9.2CVSS v4.0 · base scoreNoneCritical | Time to revision 9 days |
| 2026-07-02published 2026-06-19 | Advisory fix version moved | GHSA-h3m5-97jq-qjrfCVE-2026-57168 | mavenio.openremote:openremote-manager critical | stated at publication 1.24.2, now states 1.25.0 | Time to revision 13 days |
| 2026-07-02published 2026-04-29 | Advisory severity changed | GHSA-5843-p793-ghmmCVE-2026-22740 | 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 64 days |
| 2026-07-02published 2026-05-27 | Advisory severity changed | GHSA-6439-2f28-8p8qCVE-2026-45075 | 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 36 days |
| 2026-07-02published 2026-03-18 | Advisory withdrawn | GHSA-wmxr-6j5f-838p | whole advisoryhigh | withdrawn 2026-07-02 | Time to revision 107 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 →