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.

62 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes from red hat, published by redhat, from the last 7 days, 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.
Fri 4 Sep 2026· 3 changes
2026-09-04Product addedCVE-2025-9784not named as affected at publication, now names red hat jboss enterprise application platform 8.1.6Time to revision 367 days
2026-09-04Product addedCVE-2026-11332not named as affected at publication, now names red hat satellite 6.18 for rhel 9 and 1 moreTime to revision 91 days
2026-09-04same kind of change as the line aboveCVE-2026-11332same vendor as the line abovenot named as affected at publication, now names red hat satellite 6.18 for rhel 9Time to revision 91 days
2026-09-04same kind of change as the line aboveCVE-2026-11332same vendor as the line abovenot named as affected at publication, now names red hat satellite 6.19 for rhel 9Time to revision 91 days
Thu 3 Sep 2026· 40 changes
2026-09-037 commitsProduct added40 rows, one per record and productnot 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-03same kind of change as the line aboveCVE-2026-11332same vendor as the line abovenot named as affected at publication, now names red hat satellite 6.17 for rhel 9Time to revision 91 days
2026-09-03same kind of change as the line aboveCVE-2026-15563same vendor as the line abovenot named as affected at publication, now names red hat single sign-on 7Time to revision 24 days
2026-09-03same kind of change as the line aboveCVE-2026-18255same vendor as the line abovenot named as affected at publication, now names red hat quay 3.15Time to revision 36 days
2026-09-03same kind of change as the line aboveCVE-2025-5222same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.17Time to revision 464 days
2026-09-03same kind of change as the line aboveCVE-2026-14476same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.17Time to revision 58 days
2026-09-03same kind of change as the line aboveCVE-2026-2340same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.17Time to revision 99 days
2026-09-03same kind of change as the line aboveCVE-2026-3833same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.17Time to revision 126 days
2026-09-03same kind of change as the line aboveCVE-2026-42011same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.17Time to revision 119 days
32 more rows in this change are not listed here. Open all 40 rows
Wed 2 Sep 2026· 6 changes
2026-09-02Product addedCVE-2026-15809not named as affected at publication, now names red hat openshift container platform 4.19Time to revision 49 days
2026-09-02Product addedCVE-2026-17527not named as affected at publication, now names red hat container native virtualization 4.14Time to revision 37 days
2026-09-02Product addedCVE-2026-84218not named as affected at publication, now names red hat amq broker 7Time to revision 1 days
2026-09-022 commitsProduct addednot 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-02same kind of change as the line aboveCVE-2026-72693same vendor as the line abovesame change as the line aboveTime to revision 22 days
2026-09-02same kind of change as the line aboveCVE-2026-15816same vendor as the line abovesame change as the line aboveTime to revision 26 days
2026-09-02Product addedCVE-2026-15816not named as affected at publication, now names red hat openshift container platform 4.20Time to revision 26 days
Tue 1 Sep 2026· 13 changes
2026-09-012 commitsProduct addedCVE-2026-15809not 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-01same kind of change as the line aboveCVE-2026-15809same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.21Time to revision 48 days
2026-09-01same kind of change as the line aboveCVE-2026-15809same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.20Time to revision 48 days
2026-09-01Product addedCVE-2026-11873not named as affected at publication, now names red hat certificate system 9Time to revision 0 days
2026-09-01Product addednot named as affected at publication, now names red hat discovery 2Time to revision 29 to 148 days
2026-09-01same kind of change as the line aboveCVE-2026-15588same vendor as the line abovesame change as the line aboveTime to revision 43 days
2026-09-01same kind of change as the line aboveCVE-2026-18477same vendor as the line abovesame change as the line aboveTime to revision 29 days
2026-09-01same kind of change as the line aboveCVE-2026-18508same vendor as the line abovesame change as the line aboveTime to revision 29 days
2026-09-01same kind of change as the line aboveCVE-2026-58010same vendor as the line abovesame change as the line aboveTime to revision 63 days
2026-09-01same kind of change as the line aboveCVE-2026-58011same vendor as the line abovesame change as the line aboveTime to revision 63 days
2026-09-01same kind of change as the line aboveCVE-2026-58012same vendor as the line abovesame change as the line aboveTime to revision 63 days
2026-09-01same kind of change as the line aboveCVE-2026-58013same vendor as the line abovesame change as the line aboveTime to revision 63 days
2026-09-01same kind of change as the line aboveCVE-2026-58014same vendor as the line abovesame change as the line aboveTime to revision 63 days
2 more rows in this change are not listed here. Open all 10 rows

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.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

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 →