Root code execution via predictable Redis configuration
Published Aug 25, 2026 · Updated Aug 25, 2026
Insecure temporary-file handling in Contributed Systems Faktory before 1.10.0 allows local users to execute arbitrary code as root. On startup, the embedded Redis bootstrapper trusts an existing /tmp/redis.conf and preserves attacker-selected directives, including loadmodule. Exploitation requires a local user to plant the file before a root-run Faktory service starts; the configuration can also expose job data over an unauthenticated Redis port.
Summary
What happened
Insecure temporary-file handling in Contributed Systems Faktory before 1.10.0 allows local users to execute arbitrary code as root. On startup, the embedded Redis bootstrapper trusts an existing /tmp/redis.conf and preserves attacker-selected directives, including loadmodule. Exploitation requires a local user to plant the file before a root-run Faktory service starts; the configuration can also expose job data over an unauthenticated Redis port.
The record
- CVE
- CVE-2026-63404
- Published
- Aug 25, 2026
- Updated
- Aug 25, 2026
- Vendor
- Contributed Systems
- Product
- Faktory
- Classifications
- CWE-377, T1574.010
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.10.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo