Every change, newest first
| 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. |
|---|---|---|---|---|---|
| Fri 13 Feb 2026· 16 changes | |||||
| 2026-02-133 commits | Product added | GitHub_M | not named as affected at publication, now names endpointman and 8 moreBranches and original-value intervals are stated on each row. | Time to revision 60 to 500 days | |
| 2026-02-13 | same kind of change as the line above | CVE-2025-61678 | same vendor as the line above | not named as affected at publication, now names endpointman | Time to revision 122 days |
| 2026-02-13 | same kind of change as the line above | CVE-2025-62173 | same vendor as the line above | not named as affected at publication, now names restapps | Time to revision 72 days |
| 2026-02-13 | same kind of change as the line above | CVE-2025-64328 | same vendor as the line above | not named as affected at publication, now names filestore | Time to revision 99 days |
| 2026-02-13 | same kind of change as the line above | CVE-2025-66039 | same vendor as the line above | not named as affected at publication, now names framework | Time to revision 66 days |
| 2026-02-13 | same kind of change as the line above | CVE-2025-67513 | same vendor as the line above | not named as affected at publication, now names endpoint | Time to revision 65 days |
| 2026-02-13 | same kind of change as the line above | CVE-2025-67722 | same vendor as the line above | not named as affected at publication, now names framework | Time to revision 60 days |
| 2026-02-13 | same kind of change as the line above | CVE-2025-67736 | same vendor as the line above | not named as affected at publication, now names tts | Time to revision 60 days |
| 2026-02-13 | same kind of change as the line above | CVE-2025-55209 | same vendor as the line above | not named as affected at publication, now names contactmanager | Time to revision 162 days |
| 8 more rows in this change are not listed here. Open all 16 rows → | |||||
Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
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 →