Every change, newest first
Showing changes seen on 2026-06-23. 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. |
|---|---|---|---|---|---|
| Tue 23 Jun 2026· 26 record changes | |||||
| 2026-06-23 | Fix version moved | CVE-2026-56784 | openremoteopenremote VulnCheck | stated at publication 1.24.2, now states 1.25.0Release branch starts at 0.same day | Days to revision 0 |
| 2026-06-23 | Fix version moved | CVE-2026-41715 | springreactor netty vmware | stated at publication 1.3.6, now states 1.3.15.1Release branch starts at 1.3.0. | Days to revision 15 |
| 2026-06-23 | Affected range extended | CVE-2025-25250 | fortinetfortios | stated at publication 7.2.11, now states 7.2.13Release branch starts at 7.2.0. | Days to revision 378 |
| 2026-06-23 | Affected range extended | CVE-2025-25250 | fortinetfortios | stated at publication 7.0.17, now states 7.0.19Release branch starts at 7.0.0. | Days to revision 378 |
| 2026-06-23 | Affected range extended | CVE-2025-54821 | fortinetfortios | stated at publication 7.2.12, now states 7.2.13Release branch starts at 7.2.0. | Days to revision 217 |
| 2026-06-23 | Affected range extended | CVE-2025-54821 | fortinetfortios | stated at publication 7.4.9, now states 7.4.11Release branch starts at 7.4.0. | Days to revision 217 |
| 2026-06-23 | Affected range extended | CVE-2025-54821 | fortinetfortios | stated at publication 7.0.18, now states 7.0.19Release branch starts at 7.0.0. | Days to revision 217 |
| 2026-06-23 | Product added | CVE-2026-45170 | palo_alto | not named as affected at publication, now names vendor pam | Days to revision 12 |
| 2026-06-23 | Product added | CVE-2026-49494 | VulnCheck | not named as affected at publication, now names xcitium client security (xcs) | Days to revision 16 |
| 2026-06-23 | Product added | CVE-2025-25250 | not named as affected at publication, now names fortisase | Days to revision 378 | |
| 2026-06-23 | Product added | CVE-2025-54821 | not named as affected at publication, now names fortisase | Days to revision 217 | |
| 2026-06-23 | Product added | CVE-2026-1933 | not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support | Days to revision 27 | |
| 2026-06-23 | Product added | CVE-2026-2340 | not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support | Days to revision 27 | |
| 2026-06-23 | Product added | CVE-2026-3012 | not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support | Days to revision 27 | |
| 2026-06-23 | Product added | CVE-2026-4408 | not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support | Days to revision 26 | |
| 2026-06-23 | Product added | CVE-2026-4408 | not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support | Days to revision 26 | |
| 2026-06-23 | Product added | CVE-2026-4480 | not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support | Days to revision 28 | |
| 2026-06-23 | Product added | CVE-2026-4480 | not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support | Days to revision 28 | |
| 2026-06-23 | CVSS base score changed | CVE-2026-12164 | whole record Fortra | stated at publication 4.9, now states 4.4CVSS v3.1 · base scoreMediumMedium | Days to revision 0 |
| 2026-06-23 | CVSS base score changed | CVE-2026-47907 | whole record adobe | stated at publication 8.2, now states 8.6CVSS v3.1 · base scoreHighHigh | Days to revision 14 |
| 2026-06-23 | CVSS base score changed | CVE-2026-47937 | whole record adobe | stated at publication 7.4, now states 7.7CVSS v3.1 · base scoreHighHigh | Days to revision 14 |
| 2026-06-23 | CVSS base score changed | CVE-2025-64898 | whole record adobe | stated at publication 4.3, now states 5.3CVSS v3.1 · base scoreMediumMedium | Days to revision 196 |
| 2026-06-23 | CVSS base score changed | CVE-2026-34694 | whole record adobe | stated at publication 5.9, now states 4.8CVSS v3.1 · base scoreMediumMedium | Days to revision 14 |
| 2026-06-23 | CVSS base score changed | CVE-2026-12628 | whole record ibm | stated at publication 8.1, now states 9.1CVSS v3.1 · base scoreHighCritical | Days to revision 1 |
| 2026-06-23 | CVSS base score changed | CVE-2026-56104 | whole record VulnCheck | stated at publication 9.1, now states 8.8CVSS v4.0 · base scoreCriticalHigh | Days to revision 1 |
| 2026-06-23 | Record state changed | CVE-2026-56120 | whole record VulnCheck | stated at publication PUBLISHED, now states REJECTED | Days to revision 0 |
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.
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 →