Every change, newest first

Compare earlier and later source statements, with the dates and evidence behind each measured change.

27 record edits refused · 13 advisory changes · newest first · grouped by dayCSV JSON RSS

Showing changes seen on 2026-07-07. Every day

These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.

Rows we checked and refused, counted nowhere changed on 2026-07-07, newest first, one line per change to a CVE record or a GHSA advisory, 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.	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.
Tue 7 Jul 2026· 40 changes
2026-07-074 commits	Product added	Show all 10 CVE records in this change: Product added: 9 products named as affected from red hatHide the 10 CVE records in this change: Product added: 9 products named as affected from red hat26 rows, one per record and product	red hat	not named as affected at publication, now names red hat jboss enterprise application platform 8.1 for rhel 10 and 8 moreBranches and original-value intervals are stated on each row.not counted: A variant beneath an already affected parent	Time to revision 0 to 32 days
2026-07-07	same kind of change as the line above	CVE-2025-12799	same vendor as the line above	not named as affected at publication, now names red hat jboss enterprise application platform 8.1 for rhel 10Not counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat jboss enterprise application platform 8; the record does not establish whether this newly names affected scope or refines the existing product listing	Time to revision 0 days
2026-07-07	same kind of change as the line above	CVE-2025-12799	same vendor as the line above	not named as affected at publication, now names red hat jboss enterprise application platform 8.1 for rhel 8Not counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat jboss enterprise application platform 8; the record does not establish whether this newly names affected scope or refines the existing product listing	Time to revision 0 days
2026-07-07	same kind of change as the line above	CVE-2025-12799	same vendor as the line above	not named as affected at publication, now names red hat jboss enterprise application platform 8.1 for rhel 9Not counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat jboss enterprise application platform 8; the record does not establish whether this newly names affected scope or refines the existing product listing	Time to revision 0 days
2026-07-07	same kind of change as the line above	CVE-2026-11610	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 extended update support long-life add-onNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 8; the record does not establish whether this newly names affected scope or refines the existing product listing	Time to revision 0 days
2026-07-07	same kind of change as the line above	CVE-2026-11610	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.6 extended update support long-life add-onNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 8; the record does not establish whether this newly names affected scope or refines the existing product listing	Time to revision 0 days
2026-07-07	same kind of change as the line above	CVE-2026-11774	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.4 extended update support long-life add-onNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 8; the record does not establish whether this newly names affected scope or refines the existing product listing	Time to revision 26 days
2026-07-07	same kind of change as the line above	CVE-2026-11774	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.6 extended update support long-life add-onNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 8; the record does not establish whether this newly names affected scope or refines the existing product listing	Time to revision 26 days
2026-07-07	same kind of change as the line above	CVE-2026-11610	same vendor as the line above	not named as affected at publication, now names red hat enterprise linux 8.8 telecommunications update serviceNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 8; the record does not establish whether this newly names affected scope or refines the existing product listing	Time to revision 0 days
18 more rows in this change are not listed here. Open all 26 rows →
2026-07-07	CVSS base score changed	CVE-2026-3823	whole record twcert	stated at publication 9.3, now states 9.8Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable	Time to revision 120 days
2026-07-07published 2026-06-25	Package added to advisory	Show all 13 advisories in this change: Package added to advisory: golang.org/x/crypto named as affected in goHide the 13 advisories in this change: Package added to advisory: golang.org/x/crypto named as affected in go	go 3 bands	not named as affected when the advisory was published, now names golang.org/x/crypto	Time to revision 12 days
2026-07-07published 2026-06-25	same kind of change as the line above	GHSA-x527-x647-q7ggCVE-2026-46595	same package registry as the line abovecritical	same change as the line above	Time to revision 12 days
2026-07-07published 2026-06-25	same kind of change as the line above	GHSA-5cgq-3rg8-m6cvCVE-2026-42508	same package registry as the line abovecritical	same change as the line above	Time to revision 12 days
2026-07-07published 2026-06-25	same kind of change as the line above	GHSA-rm3j-f69w-wqmqCVE-2026-39834	same package registry as the line abovecritical	same change as the line above	Time to revision 12 days
2026-07-07published 2026-06-25	same kind of change as the line above	GHSA-89gr-r52h-f8rxCVE-2026-39831	same package registry as the line abovecritical	same change as the line above	Time to revision 12 days
2026-07-07published 2026-06-25	same kind of change as the line above	GHSA-w879-237q-wc7rCVE-2026-39829	same package registry as the line abovehigh	same change as the line above	Time to revision 12 days
2026-07-07published 2026-06-25	same kind of change as the line above	GHSA-vgwf-h737-ff37CVE-2026-39830	same package registry as the line abovecritical	same change as the line above	Time to revision 12 days
2026-07-07published 2026-06-25	same kind of change as the line above	GHSA-f5wc-c3c7-36mcCVE-2026-39832	same package registry as the line abovecritical	same change as the line above	Time to revision 12 days
2026-07-07published 2026-06-25	same kind of change as the line above	GHSA-jppx-rxg9-jmrxCVE-2026-39833	same package registry as the line abovecritical	same change as the line above	Time to revision 12 days
5 more rows in this change are not listed here. Open all 13 rows →

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.

4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

Every kind of change

Each bar filters the ledger to that kind, and counts what it would show under the filters already on. Two units, one length scale, never a total.

To a CVE record or a KEV entry

To a GitHub advisory

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 →