Product added

What a record said when it was published, what it says now, and the commit that changed it.

16 changes behind one line · newest firstCSV JSON RSS

One change, in full: Product added: 9 products named as affected from freepbx. Products named as affected in 16 CVE records, across 9 products. Drawn here as 9 lines, one per product. Back to the ledger

Counted changes of "Product added", newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
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-02-132 commits	Show all 2 CVE records in this change: Product added: endpointman named as affected from freepbxHide the 2 CVE records in this change: Product added: endpointman named as affected from freepbx	freepbx GitHub_M	not named as affected at publication, now names endpointmanBranches and original-value intervals are stated on each row.	Days to revision 122 to 500
2026-02-13	CVE-2025-61678	same vendor as the line above	same change as the line above	Days to revision 122
2026-02-13	CVE-2024-47071	same vendor as the line above	same change as the line above	Days to revision 500
2026-02-13	CVE-2025-62173	freepbx GitHub_M	not named as affected at publication, now names restapps	Days to revision 72
2026-02-13	CVE-2025-64328	freepbx GitHub_M	not named as affected at publication, now names filestore	Days to revision 99
2026-02-132 commits	Show all 4 CVE records in this change: Product added: framework named as affected from freepbxHide the 4 CVE records in this change: Product added: framework named as affected from freepbx	freepbx GitHub_M	not named as affected at publication, now names frameworkBranches and original-value intervals are stated on each row.	Days to revision 60 to 151
2026-02-13	CVE-2025-66039	same vendor as the line above	same change as the line above	Days to revision 66
2026-02-13	CVE-2025-67722	same vendor as the line above	same change as the line above	Days to revision 60
2026-02-13	CVE-2025-55211	same vendor as the line above	same change as the line above	Days to revision 151
2026-02-13	CVE-2025-59056	same vendor as the line above	same change as the line above	Days to revision 151
2026-02-132 commits	Show all 4 CVE records in this change: Product added: endpoint named as affected from freepbxHide the 4 CVE records in this change: Product added: endpoint named as affected from freepbx	freepbx GitHub_M	not named as affected at publication, now names endpointBranches and original-value intervals are stated on each row.	Days to revision 65 to 169
2026-02-13	CVE-2025-67513	same vendor as the line above	same change as the line above	Days to revision 65
2026-02-13	CVE-2025-57819	same vendor as the line above	same change as the line above	Days to revision 169
2026-02-13	CVE-2025-59051	same vendor as the line above	same change as the line above	Days to revision 122
2026-02-13	CVE-2025-61675	same vendor as the line above	same change as the line above	Days to revision 122
2026-02-13	CVE-2025-67736	freepbx GitHub_M	not named as affected at publication, now names tts	Days to revision 60
2026-02-13	CVE-2025-55209	freepbx GitHub_M	not named as affected at publication, now names contactmanager	Days to revision 162
2026-02-13	CVE-2025-55739	freepbx GitHub_M	not named as affected at publication, now names api	Days to revision 162
2026-02-13	CVE-2025-59429	freepbx GitHub_M	not named as affected at publication, now names core	Days to revision 122

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. 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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

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 →

Check my CVEs against these changes →