Faktory is a language-agnostic background job server. In versions prior to 1.10.0, the embedded Redis bootstrapper is vulnerable to an insecure temporary file flaw that lets a local unprivileged user hijack the Redis configuration and escalate to root. It writes its startup configuration to a fixed, predictable, world-writable path, /tmp/redis.conf, only creating the file if it does not already exist and never validating it on later boots. Because /tmp is world-writable, a local unprivileged user can pre-create /tmp/redis.conf with attacker-chosen Redis directives before Faktory starts, and Faktory will use the planted file verbatim. Faktory only overrides the unixsocket, dir, and logfile options, leaving directives such as bind, protected-mode, requirepass, and loadmodule attacker-controlled. This lets an attacker silently expose the entire job queue over an unauthenticated network port with no visible error to the administrator. Because the official systemd unit runs Faktory, and the redis-server child it spawns, as root, an attacker can also supply a loadmodule directive to execute arbitrary native code in the root-owned Redis process, escalating from a local unprivileged user to root. This issue is fixed in version 1.10.0.
CVE-2026-63404
This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(low)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity73% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
Advisory Details (3)
Auto-updated Aug 25, 2026Insecure predictable /tmp/redis.conf enables local Redis config hijack (network exposure / root RCE primitive) · Advisory · contribsys/faktory · GitHub
https://github.com/contribsys/faktory/security/advisories/GHSA-j2vx-rpwf-w77v1.10.0
Patch available: contribsys/faktory v1.10.0
https://github.com/contribsys/faktory/releases/tag/v1.10.0commit 0fb44c0a2b3c (contribsys/faktory)
Fix landed in contribsys/faktory commit 0fb44c0a2b3c — awaiting tagged release
https://github.com/contribsys/faktory/commit/0fb44c0a2b3c554857b53563ad0cf61295cd0c41Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 22:29 UTCEG score recompute
- 2026-08-25 22:10 UTCEG score recompute
- 2026-08-25 22:09 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-63404?
When was CVE-2026-63404 disclosed?
What is the CVSS score of CVE-2026-63404?
How do I remediate CVE-2026-63404?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63404
Is Your Infrastructure Affected by CVE-2026-63404?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.