Every change, newest first

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

21 refused changes behind one line · newest firstCSV JSON RSS

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.

One change, in full: Product added: red hat build of keycloak 26.4.13 named as affected from red hat. Products named as affected in 21 CVE records. Back to the ledger

Rows we checked and refused, counted nowhere from red hat, 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.	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.
2026-06-26	Product added	CVE-2026-37977	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 81
2026-06-26	Product added	CVE-2026-4874	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 92
2026-06-26	Product added	CVE-2026-7500	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 57
2026-06-26	Product added	CVE-2026-8830	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 38
2026-06-26	Product added	CVE-2026-8922	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 38
2026-06-26	Product added	CVE-2026-9083	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 1
2026-06-26	Product added	CVE-2026-9086	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 1
2026-06-26	Product added	CVE-2026-9087	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 37
2026-06-26	Product added	CVE-2026-9088	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 21
2026-06-26	Product added	CVE-2026-9099	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 1
2026-06-26	Product added	CVE-2026-9704	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 30
2026-06-26	Product added	CVE-2026-9705	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 1
2026-06-26	Product added	CVE-2026-9791	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 29
2026-06-26	Product added	CVE-2026-9792	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 29
2026-06-26	Product added	CVE-2026-9794	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 29
2026-06-26	Product added	CVE-2026-9795	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 29
2026-06-26	Product added	CVE-2026-9799	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 1
2026-06-26	Product added	CVE-2026-9800	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 1
2026-06-26	Product added	CVE-2026-9801	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 29
2026-06-26	Product added	CVE-2026-9802	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 29
2026-06-26	Product added	CVE-2026-9803	red hat	not named as affected at publication, now names red hat build of keycloak 26.4.13Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposure	Days to revision 29

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.

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

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 →