CVE-2026-63404

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (4th percentile of EPSS-scored CVEs). 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/100CISA SSVC

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 computed
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 25, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 25, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
githubMentions a patch (unverified)🟡 PoC Available

Insecure 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-w77v
github_release Patch Available

1.10.0

Patch available: contribsys/faktory v1.10.0

https://github.com/contribsys/faktory/releases/tag/v1.10.0
github_commit

commit 0fb44c0a2b3c (contribsys/faktory)

Fix landed in contribsys/faktory commit 0fb44c0a2b3c — awaiting tagged release

https://github.com/contribsys/faktory/commit/0fb44c0a2b3c554857b53563ad0cf61295cd0c41

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 44× 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.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 02:17 UTCEG score recompute
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 20:45 UTCEG score recompute
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-06 07:38 UTCEG score recompute
  7. 2026-10-05 17:43 UTCEPSS rescore
  8. 2026-10-05 05:02 UTCEG score recompute
  9. 2026-10-04 23:22 UTCEPSS rescore
  10. 2026-10-03 16:16 UTCEG score recompute
  11. 2026-10-03 14:26 UTCEPSS rescore
  12. 2026-10-02 21:32 UTCEG score recompute
  13. 2026-10-02 17:56 UTCEPSS rescore
  14. 2026-10-01 20:57 UTCEG score recompute
  15. 2026-10-01 19:50 UTCEPSS rescore
  16. 2026-09-30 20:09 UTCEG score recompute
  17. 2026-09-30 15:03 UTCEPSS rescore
  18. 2026-09-30 06:21 UTCEG score recompute
  19. 2026-09-28 23:14 UTCEG score recompute
  20. 2026-09-28 13:51 UTCEPSS rescore
  21. 2026-09-27 22:17 UTCEG score recompute
  22. 2026-09-26 21:32 UTCEG score recompute
  23. 2026-09-26 15:59 UTCEPSS rescore
  24. 2026-09-24 20:25 UTCEG score recompute
  25. 2026-09-23 19:56 UTCEG score recompute
Show 47 more
  1. 2026-09-23 17:54 UTCEPSS rescore
  2. 2026-09-22 18:52 UTCEG score recompute
  3. 2026-09-22 06:08 UTCEG score recompute
  4. 2026-09-21 05:38 UTCEG score recompute
  5. 2026-09-20 20:16 UTCEPSS rescore
  6. 2026-09-19 16:52 UTCEG score recompute
  7. 2026-09-19 04:37 UTCEG score recompute
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-18 03:47 UTCEG score recompute
  10. 2026-09-16 14:12 UTCEG score recompute
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 13:12 UTCEG score recompute
  14. 2026-09-14 00:21 UTCEG score recompute
  15. 2026-09-11 23:22 UTCEG score recompute
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-11 10:04 UTCEG score recompute
  18. 2026-09-11 09:37 UTCEPSS rescore
  19. 2026-09-10 21:47 UTCEG score recompute
  20. 2026-09-09 00:56 UTCEG score recompute
  21. 2026-09-08 22:01 UTCEPSS rescore
  22. 2026-09-07 16:44 UTCEG score recompute
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-06 16:10 UTCEG score recompute
  25. 2026-09-06 13:47 UTCEPSS rescore
  26. 2026-09-05 15:36 UTCEG score recompute
  27. 2026-09-05 15:31 UTCEPSS rescore
  28. 2026-09-04 15:08 UTCEG score recompute
  29. 2026-09-04 05:07 UTCEPSS rescore
  30. 2026-09-03 02:13 UTCEG score recompute
  31. 2026-09-02 14:12 UTCEPSS rescore
  32. 2026-09-02 01:39 UTCEG score recompute
  33. 2026-09-01 13:54 UTCEPSS rescore
  34. 2026-08-31 00:29 UTCEG score recompute
  35. 2026-08-30 19:17 UTCEPSS rescore
  36. 2026-08-30 12:14 UTCEG score recompute
  37. 2026-08-30 01:22 UTCEPSS rescore
  38. 2026-08-28 23:28 UTCEG score recompute
  39. 2026-08-28 22:50 UTCEG score recompute
  40. 2026-08-28 21:42 UTCEPSS rescore
  41. 2026-08-27 23:36 UTCEG score recompute
  42. 2026-08-27 14:25 UTCEPSS rescore
  43. 2026-08-26 22:59 UTCEG score recompute
  44. 2026-08-26 14:46 UTCEPSS rescore
  45. 2026-08-25 22:29 UTCEG score recompute
  46. 2026-08-25 22:10 UTCEG score recompute
  47. 2026-08-25 22:09 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-63404?
CVE-2026-63404 is a high vulnerability published on August 25, 2026. 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…
When was CVE-2026-63404 disclosed?
CVE-2026-63404 was first published on August 25, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63404 actively exploited?
CVE-2026-63404 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63404?
CVE-2026-63404 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63404?
A fix for CVE-2026-63404 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63404

Explore →

Is Your Infrastructure Affected by CVE-2026-63404?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.