Every change, newest first
One change, in full: Product added: 13 products named as affected from red hat. The same change in 11 CVE records, across 13 products: 19 rows in all. Drawn here as 5 lines, one per product. Back to the ledger
| 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-08-252 commits | Product added | CVE-2026-16313 | not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support and 6 moreBranches and original-value intervals are stated on each row. | Time to revision 28 days | |
| 2026-08-25 | same kind of change as the line above | CVE-2026-16313 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support | Time to revision 28 days |
| 2026-08-25 | same kind of change as the line above | CVE-2026-16313 | 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-on | Time to revision 28 days |
| 2026-08-25 | same kind of change as the line above | CVE-2026-16313 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support | Time to revision 28 days |
| 2026-08-25 | same kind of change as the line above | CVE-2026-16313 | 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-on | Time to revision 28 days |
| 2026-08-25 | same kind of change as the line above | CVE-2026-16313 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 8.8 telecommunications update service | Time to revision 28 days |
| 2026-08-25 | same kind of change as the line above | CVE-2026-16313 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 8.8 update services for sap solutions | Time to revision 28 days |
| 2026-08-25 | same kind of change as the line above | CVE-2026-16313 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 9.6 extended update support | Time to revision 28 days |
| 2026-08-25 | Product added | CVE-2025-57847 | not named as affected at publication, now names red hat ansible automation platform ansible core 2 | Time to revision 139 days | |
| 2026-08-25 | Product added | CVE-2026-15809 | not named as affected at publication, now names red hat openshift container platform 4.22 | Time to revision 41 days | |
| 2026-08-25 | Product added | not named as affected at publication, now names red hat update infrastructure 5 | Time to revision 36 to 56 days | ||
| 2026-08-25 | same kind of change as the line above | CVE-2026-15588 | same vendor as the line above | same change as the line above | Time to revision 36 days |
| 2026-08-25 | 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 56 days |
| 2026-08-25 | 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 56 days |
| 2026-08-25 | 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 56 days |
| 2026-08-25 | 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 56 days |
| 2026-08-25 | 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 56 days |
| 2026-08-25 | 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 56 days |
| 2026-08-25 | Product added | CVE-2026-17527 | not named as affected at publication, now names red hat container native virtualization 4.19 and 2 more | Time to revision 29 days | |
| 2026-08-25 | same kind of change as the line above | CVE-2026-17527 | same vendor as the line above | not named as affected at publication, now names red hat container native virtualization 4.19 | Time to revision 29 days |
| 2026-08-25 | same kind of change as the line above | CVE-2026-17527 | same vendor as the line above | not named as affected at publication, now names red hat container native virtualization 4.20 | Time to revision 29 days |
| 2026-08-25 | same kind of change as the line above | CVE-2026-17527 | same vendor as the line above | not named as affected at publication, now names red hat container native virtualization 4.21 | Time to revision 29 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 →