All changesCanonas of 2026-09-07
CVE-2025-1268
canon inc.pdf drivercve.org →this looks wrong →
Record history
4 dated edit eventsPublished
- 4 products named later, not at publication
18 days between eventsProduct addedSource d68314d — commit d68314d2f230 in the CVE catalog
- not namedgeneric fax printer driver
21 days between eventsProducts addedSource 143005c — commit 143005ccde01 in the CVE catalog
- not namedcarps2 printer driver, ufrii lt printer driver
38 days between eventsProduct addedSource 5adeff0 — commit 5adeff0747da in the CVE catalog
- not namedpdf driver
272 days between eventsExcluded comparisonnot countedSource e206583 — commit e20658379241 in the CVE catalog
- not namedlips4 printer driver
- not namedlipslx printer driver
- not namedpcl6 printer driver
- and 2 more products in this commit, listed under Where you stand
Filtered, not counted: already named at publication inside canon inc./generic plus lips4 printer driver — the record spelled this product out all along.
176 days to snapshotSnapshot
Source record: View on CVE.org ↗
Check your tickets
Add your patched version to compare it with the recorded boundary.
Change cards link to the source commit. Compare CVE values with the first mirrored record and KEV values with the preceding catalog snapshot. The full recipe →
Data coverage & methodology
CVE values compare the first mirrored record with later source states. Initial records may have been backfilled after publication. KEV events compare consecutive catalog snapshots. Dates identify the reported value’s first observed appearance; earlier intermediate revisions may exist. Only counted rows contribute to totals. as of the 2026-09-07 snapshot.
5 rows marked filtered, not counted are on the rail and counted nowhere. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site.
Not checked: a record published before 2023 cannot have its state at publication recovered, so the CVE-record checks never compared it. For such a record, silence on this page means it was not looked at, not that it held.
Not checked: a CISA KEV listing added before 2025-01-27 was never seen changing, so a record that has been in KEV for years carries no listing node here. A missing KEV node is not evidence that CISA has not listed it.
The GitHub Advisory Database was read and carries no changed advisory naming CVE-2025-1268. An advisory is an entry in the GitHub Advisory Database, the GHSA page a Dependabot alert links to. It is reached from a CVE id only when the advisory names that CVE id itself, and many advisories name none. So no advisory here means none was found among the advisories that name one of these ids. It does not mean there is nothing to find.
How every one of these figures is measured, in full →
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.
Shipped snapshot computed 2026-09-07 from catalog commit ed5547afbae2. Real findings, not live ones: records amended since are not reflected. A later fix version is evidence that the record changed, not evidence that the first fix was incomplete.