Product added
Showing changes seen on 2026-02-13. 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. | 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· 20 changes | ||||
| 2026-02-13 | CVE-2025-61678 | GitHub_M | not named as affected at publication, now names endpointman | Time to revision 122 days |
| 2026-02-13 | CVE-2025-62173 | GitHub_M | not named as affected at publication, now names restapps | Time to revision 72 days |
| 2026-02-13 | CVE-2025-64328 | GitHub_M | not named as affected at publication, now names filestore | Time to revision 99 days |
| 2026-02-13 | CVE-2025-66039 | GitHub_M | not named as affected at publication, now names framework | Time to revision 66 days |
| 2026-02-13 | CVE-2025-67513 | GitHub_M | not named as affected at publication, now names endpoint | Time to revision 65 days |
| 2026-02-13 | CVE-2025-67722 | GitHub_M | not named as affected at publication, now names framework | Time to revision 60 days |
| 2026-02-13 | CVE-2025-67736 | GitHub_M | not named as affected at publication, now names tts | Time to revision 60 days |
| 2026-02-13 | CVE-2025-55209 | GitHub_M | not named as affected at publication, now names contactmanager | Time to revision 162 days |
| 2026-02-13 | CVE-2025-55211 | GitHub_M | not named as affected at publication, now names framework | Time to revision 151 days |
| 2026-02-13 | CVE-2025-55739 | GitHub_M | not named as affected at publication, now names api | Time to revision 162 days |
| 2026-02-13 | CVE-2025-57819 | GitHub_M | not named as affected at publication, now names endpoint | Time to revision 169 days |
| 2026-02-13 | CVE-2025-59051 | GitHub_M | not named as affected at publication, now names endpoint | Time to revision 122 days |
| 2026-02-13 | CVE-2025-59056 | GitHub_M | not named as affected at publication, now names framework | Time to revision 151 days |
| 2026-02-13 | CVE-2025-59429 | GitHub_M | not named as affected at publication, now names core | Time to revision 122 days |
| 2026-02-13 | CVE-2025-61675 | GitHub_M | not named as affected at publication, now names endpoint | Time to revision 122 days |
| 2026-02-13 | CVE-2024-47071 | GitHub_M | not named as affected at publication, now names endpointman | Time to revision 500 days |
| 2026-02-13 | CVE-2025-21264 | not named as affected at publication, now names microsoft visual studio code copilot chat extension | Time to revision 276 days | |
| 2026-02-13 | CVE-2025-27488 | not named as affected at publication, now names windows hlk, version 1809 | Time to revision 276 days | |
| 2026-02-13 | CVE-2025-47733 | not named as affected at publication, now names microsoft power pages | Time to revision 281 days | |
| 2026-02-13 | CVE-2025-13601 | not named as affected at publication, now names red hat openshift container platform 4.12 | Time to revision 79 days | |
This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller.
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 →