Every change, newest first
Showing changes seen on 2026-08-24. Every day
| 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. |
|---|---|---|---|---|---|
| Mon 24 Aug 2026· 25 changes | |||||
| 2026-08-24 | Product added | CVE-2026-52902 | not named as affected at publication, now names red hat ansible automation platform 2.5 for rhel 8 | Time to revision 77 days | |
| 2026-08-24 | Product added | CVE-2026-52902 | not named as affected at publication, now names red hat ansible automation platform 2.5 for rhel 9 | Time to revision 77 days | |
| 2026-08-24 | Product added | CVE-2026-52902 | not named as affected at publication, now names red hat ansible automation platform 2.6 for rhel 9 | Time to revision 77 days | |
| 2026-08-24 | Product added | CVE-2026-52902 | not named as affected at publication, now names red hat ansible automation platform 2.7 for rhel 10 | Time to revision 76 days | |
| 2026-08-24 | Product added | CVE-2026-52902 | not named as affected at publication, now names red hat ansible automation platform 2.7 for rhel 9 | Time to revision 76 days | |
| 2026-08-24 | Product added | CVE-2026-11841 | not named as affected at publication, now names icr890-4 | Time to revision 27 days | |
| 2026-08-24 | Product added | CVE-2026-14164 | not named as affected at publication, now names red hat enterprise linux 9.6 extended update support | Time to revision 55 days | |
| 2026-08-24 | Product added | CVE-2026-14164 | not named as affected at publication, now names red hat enterprise linux 9.2 update services for sap solutions | Time to revision 55 days | |
| 2026-08-24 | Product added | CVE-2026-14164 | not named as affected at publication, now names red hat enterprise linux 9.4 update services for sap solutions | Time to revision 55 days | |
| 2026-08-24 | CVSS base score changed | CVE-2026-78555 | whole record CIRCL | stated at publication 10.0, now states 9.4CVSS v4.0 · base scoreCriticalCritical | Time to revision 0 days |
| 2026-08-24 | CVSS base score changed | CVE-2023-50176 | whole record fortinet | stated at publication 7.1, now states 4.0CVSS v3.1 · base scoreHighMedium | Time to revision 650 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-26369 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 190 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-34100 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-34101 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-34102 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-34103 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-34104 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-34105 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 54 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-39910 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 77 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-72822 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-72824 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-72826 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-72829 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-72830 | whole record VulnCheck | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 10 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-18652 | whole record rapid7 | stated at publication 4.9, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 12 days |
Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or 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 →