Record state changed
One change, in full: Record state changed: PUBLISHED → REJECTED. The same change in 32 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. | 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-07-31 | CVE-2026-51235 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 5 |
| 2026-07-31 | CVE-2026-51244 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 5 |
| 2026-07-31 | CVE-2026-51251 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51252 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51254 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51259 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51260 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51261 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51263 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51266 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51267 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51268 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51269 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51270 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51271 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51272 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 2 |
| 2026-07-31 | CVE-2026-51273 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51274 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51275 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 4 |
| 2026-07-31 | CVE-2026-51290 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 2 |
| 2026-07-31 | CVE-2026-51291 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 2 |
| 2026-07-31 | CVE-2026-51292 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 2 |
| 2026-07-31 | CVE-2026-51293 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 2 |
| 2026-07-31 | CVE-2026-51294 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 2 |
| 2026-07-31 | CVE-2026-51295 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 2 |
| 2026-07-31 | CVE-2026-51296 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 5 |
| 2026-07-31 | CVE-2026-51297 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 5 |
| 2026-07-31 | CVE-2026-51298 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 5 |
| 2026-07-31 | CVE-2026-51300 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 5 |
| 2026-07-31 | CVE-2026-51302 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 5 |
| 2026-07-31 | CVE-2026-51303 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 5 |
| 2026-07-31 | CVE-2026-51304 | whole record mitre | stated at publication PUBLISHED, now states REJECTED | Days to revision 5 |
This kind is counted once per CVE record, so changes and records are the same number here. 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 →