CVE-2026-63403
Unauthenticated malformed commands crash Faktory server, causing full service outage.
Is CVE-2026-63403 being exploited?
Not confirmed. CVE-2026-63403 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-63403?
CVE-2026-63403 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-63403?
Yes. A fix has been recorded for CVE-2026-63403. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63403 affect?
CVE-2026-63403 affects Faktory server < 1.10.0, Deployments exposing Faktory command port (workers/clients impacted). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63403?
Upgrade to Faktory 1.10.0; restrict command-port access and require authentication.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote DoS: a malformed command triggers a Go panic that terminates the process, disconnecting all clients and halting jobs; repeatable to sustain outage.
Immediate action required
- affected< 1.10.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.