Vendor advisory review — 2026-09

[github-actions]

Monthly check that the compatibility list still matches what the
vendors are publishing. Nothing here is automated on purpose:
deciding whether an advisory changed in a way that matters is the
part that needs reading.

data/devices.json was last marked updated 2026-08-27 — 5 days ago.

Currently tracking 23 entries across
22 vendors.

Re-check each advisory

• Brother — currently check-advisory — advisory (unverified (403) from CI — check by hand)
• Canon — currently unsupported — advisory
• Cerberus — currently check-advisory — advisory (unverified (403) from CI — check by hand)
• Cisco — currently check-advisory — advisory
• Faxination — currently check-advisory — advisory
• HP — currently partial — advisory (unverified (no response) from CI — check by hand)
• Konica Minolta / DEVELOP — currently none-planned — advisory
• Kyocera — currently check-advisory — advisory
• Laserfiche — currently check-advisory — advisory
• Lexmark — currently check-advisory — advisory
• ManageEngine — currently check-advisory — advisory
• Microsoft — currently available, partial — advisory · advisory
• QNAP — currently unsupported — advisory
• Ricoh — currently check-advisory — advisory
• Sharp — currently partial — advisory
• Sophos — currently available — advisory
• Synology — currently check-advisory — advisory
• Toshiba — currently check-advisory — advisory
• TrueNAS — currently partial — advisory
• Veeam — currently partial — advisory
• Xerox — currently partial — advisory
• Zabbix — currently partial — advisory

What to look for

• A model moving off the "no OAuth firmware" list — that is the
  single most valuable change to catch, because
  NO-OAUTH-FIRMWARE.md
  tells people their hardware is a write-off.
• New models added to an existing advisory.
• A vendor publishing an advisory for the first time — those are
  new rows, and the reason to keep doing this.
• A dead link. An entry whose evidence URL 404s cannot be checked
  by a reader and should be replaced or removed.

When something changed

1. Edit data/devices.json and
   bump its updated field.
2. Run python tools/build-device-table.py to regenerate the
   docs table. CI fails if you skip it.

Close this issue when the pass is done, even if nothing changed —
that is a useful signal too.