Every change, newest first
Showing changes seen on 2026-07-28. 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 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 28 Jul 2026· 39 changes | |||||
| 2026-07-28 | Fix version moved | CVE-2026-45500 | microsoftmicrosoft exchange server 2016 cumulative update 23 | stated at publication 15.01.2507.069, now states 15.01.2507.071Release branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45500 | microsoftmicrosoft exchange server 2019 cumulative update 14 | stated at publication 15.02.1544.041, now states 15.02.1544.043Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45500 | microsoftmicrosoft exchange server 2019 cumulative update 15 | stated at publication 15.02.1748.046, now states 15.02.1748.048Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45500 | microsoftmicrosoft exchange server subscription edition rtm | stated at publication 15.02.2562.043, now states 15.02.2562.045Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45501 | microsoftmicrosoft exchange server 2016 cumulative update 23 | stated at publication 15.01.2507.069, now states 15.01.2507.071Release branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45501 | microsoftmicrosoft exchange server 2019 cumulative update 14 | stated at publication 15.02.1544.041, now states 15.02.1544.043Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45501 | microsoftmicrosoft exchange server 2019 cumulative update 15 | stated at publication 15.02.1748.046, now states 15.02.1748.048Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45501 | microsoftmicrosoft exchange server subscription edition rtm | stated at publication 15.02.2562.043, now states 15.02.2562.045Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45502 | microsoftmicrosoft exchange server 2016 cumulative update 23 | stated at publication 15.01.2507.069, now states 15.01.2507.071Release branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45502 | microsoftmicrosoft exchange server 2019 cumulative update 14 | stated at publication 15.02.1544.041, now states 15.02.1544.043Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45502 | microsoftmicrosoft exchange server 2019 cumulative update 15 | stated at publication 15.02.1748.046, now states 15.02.1748.048Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45502 | microsoftmicrosoft exchange server subscription edition rtm | stated at publication 15.02.2562.043, now states 15.02.2562.045Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45503 | microsoftmicrosoft exchange server 2016 cumulative update 23 | stated at publication 15.01.2507.069, now states 15.01.2507.071Release branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45503 | microsoftmicrosoft exchange server 2019 cumulative update 14 | stated at publication 15.02.1544.041, now states 15.02.1544.043Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45503 | microsoftmicrosoft exchange server 2019 cumulative update 15 | stated at publication 15.02.1748.046, now states 15.02.1748.048Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45503 | microsoftmicrosoft exchange server subscription edition rtm | stated at publication 15.02.2562.043, now states 15.02.2562.045Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45504 | microsoftmicrosoft exchange server 2016 cumulative update 23 | stated at publication 15.01.2507.069, now states 15.01.2507.071Release branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45504 | microsoftmicrosoft exchange server 2019 cumulative update 14 | stated at publication 15.02.1544.041, now states 15.02.1544.043Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45504 | microsoftmicrosoft exchange server 2019 cumulative update 15 | stated at publication 15.02.1748.046, now states 15.02.1748.048Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45504 | microsoftmicrosoft exchange server subscription edition rtm | stated at publication 15.02.2562.043, now states 15.02.2562.045Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45583 | microsoftmicrosoft exchange server 2016 cumulative update 23 | stated at publication 15.01.2507.069, now states 15.01.2507.071Release branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45583 | microsoftmicrosoft exchange server 2019 cumulative update 14 | stated at publication 15.02.1544.041, now states 15.02.1544.043Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45583 | microsoftmicrosoft exchange server 2019 cumulative update 15 | stated at publication 15.02.1748.046, now states 15.02.1748.048Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-45583 | microsoftmicrosoft exchange server subscription edition rtm | stated at publication 15.02.2562.043, now states 15.02.2562.045Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-47631 | microsoftmicrosoft exchange server 2016 cumulative update 23 | stated at publication 15.01.2507.069, now states 15.01.2507.071Release branch starts at 15.01.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-47631 | microsoftmicrosoft exchange server 2019 cumulative update 14 | stated at publication 15.02.1544.041, now states 15.02.1544.043Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-47631 | microsoftmicrosoft exchange server 2019 cumulative update 15 | stated at publication 15.02.1748.046, now states 15.02.1748.048Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Fix version moved | CVE-2026-47631 | microsoftmicrosoft exchange server subscription edition rtm | stated at publication 15.02.2562.043, now states 15.02.2562.045Release branch starts at 15.02.0.0. | Time to revision 49 days |
| 2026-07-28 | Affected range extended | CVE-2026-49779 | addifytax exempt for woocommerce Patchstack | stated at publication 1.9.3, now states 1.9.5Release branch starts at 0. | Time to revision 26 days |
| 2026-07-28 | Product added | CVE-2026-16313 | not named as affected at publication, now names red hat openshift container platform 4 | Time to revision 0 days | |
| 2026-07-28 | Product added | CVE-2026-12505 | not named as affected at publication, now names red hat openshift container platform 4.22 | Time to revision 41 days | |
| 2026-07-28 | Product added | CVE-2026-52720 | not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support | Time to revision 43 days | |
| 2026-07-28 | Product added | CVE-2026-52722 | not named as affected at publication, now names red hat enterprise linux 8.6 advanced mission critical update support | Time to revision 43 days | |
| 2026-07-28 | Product added | CVE-2026-4258 | vendor not named snyk | not named as affected at publication, now names org.webjars.npm:sjcl | Time to revision 134 days |
| 2026-07-28 | Product added | CVE-2026-52720 | not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support | Time to revision 43 days | |
| 2026-07-28 | Product added | CVE-2026-52722 | not named as affected at publication, now names red hat enterprise linux 8.4 advanced mission critical update support | Time to revision 43 days | |
| 2026-07-28 | Product added | CVE-2026-40000 | not named as affected at publication, now names blade a75 5g | Time to revision 1 days | |
| 2026-07-28 | CVSS base score changed | CVE-2026-12495 | whole record INCIBE | stated at publication 9.2, now states 5.3CVSS v4.0 · base scoreCriticalMedium | Time to revision 1 days |
| 2026-07-28published 2025-08-27 | Advisory withdrawn | GHSA-cxm3-wv7p-598cCVE-2025-10894 | whole advisorycritical | withdrawn 2026-07-28 | Time to revision 335 days |
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.
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 →