Skip to content

Every change, newest first

What a record said when it was published, what it says now, and the commit that changed it.

30 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes from gnome, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
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.KindRecord, 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 changedDays 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 record changes
2026-09-02Product addedCVE-2026-84268redhatnot named as affected at publication, now names gvfsDays to revision 1
2026-09-02Product addedCVE-2026-84269redhatnot named as affected at publication, now names gvfsDays to revision 1
2026-09-02Product addedCVE-2026-84270redhatnot named as affected at publication, now names gvfsDays to revision 1
2026-09-02Product addedCVE-2026-84267redhatnot named as affected at publication, now names gvfsDays to revision 1
Mon 31 Aug 2026· 4 record changes
2026-08-31Product addedCVE-2026-82324redhatnot named as affected at publication, now names gimpDays to revision 3
2026-08-31Product addedCVE-2026-82328redhatnot named as affected at publication, now names gimpDays to revision 3
2026-08-31Product addedCVE-2026-82330redhatnot named as affected at publication, now names gimpDays to revision 3
2026-08-31Product addedCVE-2026-82343redhatnot named as affected at publication, now names gimpDays to revision 3
Wed 26 Aug 2026· 1 record change
2026-08-26Product addedCVE-2026-80101redhatnot named as affected at publication, now names gimpDays to revision 1
Tue 25 Aug 2026· 2 record changes
2026-08-25Product addedCVE-2026-78465redhatnot named as affected at publication, now names gimpDays to revision 1
2026-08-25Product addedCVE-2026-78475redhatnot named as affected at publication, now names gimpDays to revision 1
Fri 31 Jul 2026· 3 record changes
2026-07-31Product addedCVE-2026-66757redhatnot named as affected at publication, now names gimpDays to revision 4
2026-07-31Product addedCVE-2026-66758redhatnot named as affected at publication, now names gimpDays to revision 4
2026-07-31Product addedCVE-2026-66759redhatnot named as affected at publication, now names gimpDays to revision 4
Fri 24 Jul 2026· 1 record change
2026-07-24Product addedCVE-2026-16768redhatnot named as affected at publication, now names gdk-pixbufDays to revision 1
Thu 23 Jul 2026· 1 record change
2026-07-23Product addedCVE-2026-16615redhatnot named as affected at publication, now names librestDays to revision 1
Tue 7 Jul 2026· 1 record change
2026-07-07Product addedCVE-2025-49795redhatnot named as affected at publication, now names libxml2Days to revision 386
Tue 30 Jun 2026· 7 record changes
2026-06-30Product addedCVE-2026-58010redhatnot named as affected at publication, now names glibDays to revision 0
2026-06-30Product addedCVE-2026-58011redhatnot named as affected at publication, now names glibDays to revision 0
2026-06-30Product addedCVE-2026-58012redhatnot named as affected at publication, now names glibDays to revision 0
2026-06-30Product addedCVE-2026-58013redhatnot named as affected at publication, now names glibDays to revision 0
2026-06-30Product addedCVE-2026-58014redhatnot named as affected at publication, now names glibDays to revision 0
2026-06-30Product addedCVE-2026-58015redhatnot named as affected at publication, now names glibDays to revision 0
2026-06-30Product addedCVE-2026-58016redhatnot named as affected at publication, now names glibDays to revision 0
Tue 16 Jun 2026· 1 record change
2026-06-16Product addedCVE-2026-2604redhatnot named as affected at publication, now names evolution data serverDays to revision 0
Wed 24 Dec 2025· 2 record changes
2025-12-24Product addedCVE-2025-7425redhatnot named as affected at publication, now names libxml2Days to revision 167
2025-12-24Product addedCVE-2025-7424redhatnot named as affected at publication, now names libxsltDays to revision 167
Mon 22 Dec 2025· 2 record changes
2025-12-22Product addedCVE-2025-14087redhatnot named as affected at publication, now names glibDays to revision 13
2025-12-22Product addedCVE-2025-14512redhatnot named as affected at publication, now names glibDays to revision 12
Fri 19 Dec 2025· 1 record change
2025-12-19Product addedCVE-2025-12105redhatnot named as affected at publication, now names libsoupDays to revision 58

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.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 12:43 UTC · scroll for earlierfewermore

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 →

Check my CVEs against these changes →