Every change, newest first
One change, in full: Fix version moved: 10.0.6 → 10.0.10 from microsoft. The same change in 11 CVE records. 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 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. |
|---|---|---|---|---|---|
| 2026-07-22 | Fix version moved | CVE-2026-50524 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | Fix version moved | CVE-2026-50525 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | Fix version moved | CVE-2026-50526 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | Fix version moved | CVE-2026-50527 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | Fix version moved | CVE-2026-50528 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | Fix version moved | CVE-2026-50648 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | Fix version moved | CVE-2026-50651 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | Fix version moved | CVE-2026-50659 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | Fix version moved | CVE-2026-47300 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | Fix version moved | CVE-2026-47302 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Time to revision 8 days |
| 2026-07-22 | Fix version moved | CVE-2026-47303 | microsoft.net 10.0 | stated at publication 10.0.6, now states 10.0.10Release branch starts at 10.0.0. | Time to revision 8 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 →