Every change, newest first
| 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. |
|---|---|---|---|---|---|
| Wed 2 Sep 2026· 4 changes | |||||
| 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 |
| Mon 31 Aug 2026· 4 changes | |||||
| 2026-08-31 | Product added | redhat | not named as affected at publication, now names gimp | Time to revision 3 days | |
| 2026-08-31 | same kind of change as the line above | CVE-2026-82324 | same vendor as the line above | same change as the line above | Time to revision 3 days |
| 2026-08-31 | same kind of change as the line above | CVE-2026-82328 | same vendor as the line above | same change as the line above | Time to revision 3 days |
| 2026-08-31 | same kind of change as the line above | CVE-2026-82330 | same vendor as the line above | same change as the line above | Time to revision 3 days |
| 2026-08-31 | same kind of change as the line above | CVE-2026-82343 | same vendor as the line above | same change as the line above | Time to revision 3 days |
| Wed 26 Aug 2026· 1 change | |||||
| 2026-08-26 | Product added | CVE-2026-80101 | redhat | not named as affected at publication, now names gimp | Time to revision 1 days |
| Tue 25 Aug 2026· 2 changes | |||||
| 2026-08-25 | Product added | redhat | not named as affected at publication, now names gimp | Time to revision 1 days | |
| 2026-08-25 | same kind of change as the line above | CVE-2026-78465 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2026-08-25 | same kind of change as the line above | CVE-2026-78475 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| Fri 31 Jul 2026· 3 changes | |||||
| 2026-07-312 commits | Product added | redhat | not named as affected at publication, now names gimpBranches and original-value intervals are stated on each row. | Time to revision 4 days | |
| 2026-07-31 | same kind of change as the line above | CVE-2026-66757 | same vendor as the line above | same change as the line above | Time to revision 4 days |
| 2026-07-31 | same kind of change as the line above | CVE-2026-66758 | same vendor as the line above | same change as the line above | Time to revision 4 days |
| 2026-07-31 | same kind of change as the line above | CVE-2026-66759 | same vendor as the line above | same change as the line above | Time to revision 4 days |
| Fri 24 Jul 2026· 1 change | |||||
| 2026-07-24 | Product added | CVE-2026-16768 | redhat | not named as affected at publication, now names gdk-pixbuf | Time to revision 1 days |
| Thu 23 Jul 2026· 1 change | |||||
| 2026-07-23 | Product added | CVE-2026-16615 | redhat | not named as affected at publication, now names librest | Time to revision 1 days |
| Tue 7 Jul 2026· 1 change | |||||
| 2026-07-07 | Product added | CVE-2025-49795 | redhat | not named as affected at publication, now names libxml2 | Time to revision 386 days |
| Tue 30 Jun 2026· 7 changes | |||||
| 2026-06-30 | Product added | redhat | not named as affected at publication, now names glib | Time to revision 0 days | |
| 2026-06-30 | 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 0 days |
| 2026-06-30 | 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 0 days |
| 2026-06-30 | 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 0 days |
| 2026-06-30 | 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 0 days |
| 2026-06-30 | 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 0 days |
| 2026-06-30 | same kind of change as the line above | CVE-2026-58015 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2026-06-30 | same kind of change as the line above | CVE-2026-58016 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| Tue 16 Jun 2026· 1 change | |||||
| 2026-06-16 | Product added | CVE-2026-2604 | redhat | not named as affected at publication, now names evolution data server | Time to revision 0 days |
| Wed 24 Dec 2025· 2 changes | |||||
| 2025-12-24 | Product added | CVE-2025-7425 | redhat | not named as affected at publication, now names libxml2 | Time to revision 167 days |
| 2025-12-24 | Product added | CVE-2025-7424 | redhat | not named as affected at publication, now names libxslt | Time to revision 167 days |
| Mon 22 Dec 2025· 2 changes | |||||
| 2025-12-22 | Product added | redhat | not named as affected at publication, now names glib | Time to revision 12 to 13 days | |
| 2025-12-22 | same kind of change as the line above | CVE-2025-14087 | same vendor as the line above | same change as the line above | Time to revision 13 days |
| 2025-12-22 | same kind of change as the line above | CVE-2025-14512 | same vendor as the line above | same change as the line above | Time to revision 12 days |
| Fri 19 Dec 2025· 1 change | |||||
| 2025-12-19 | Product added | CVE-2025-12105 | redhat | not named as affected at publication, now names libsoup | Time to revision 58 days |
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 →