/

CVE-2026-84702

Severity:

HIGH RISK

(7.5)

Path Traversal (CWE-22) in FaceFusion Job File Handling

CVE-2026-84702

Deferred

Vulnerability type

Category:

Path Traversal

CWE:

CWE-22

Impact:

Arbitrary File Creation and Potential File Overwrite

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

FaceFusion does not properly normalize job identifiers before constructing job file paths, allowing path traversal through its unauthenticated HTTP API. An attacker may use this flaw to create or overwrite files outside the intended jobs directory when the API processes a malicious job identifier.

Affected context

The vulnerability may affect FaceFusion deployments that expose the HTTP API and use attacker-controlled job identifiers when generating job file names. Risk is higher when the service runs with write access to sensitive directories or when API requests are reachable without authentication.

Exploit preconditions

  • Attack surface: FaceFusion's HTTP API
  • Required access: Ability to send requests to the unauthenticated API
  • Trigger point: Processing a job identifier by get_job_file_name
  • Why exploitation is possible: The identifier is incorporated into a filesystem path without sufficient normalization or confinement to the intended jobs directory

Why this happens

The underlying bug is improper neutralization of path elements used in a dynamically constructed filesystem path. When user-controlled job identifiers are treated as trusted path components without canonicalization and directory-boundary enforcement, traversal sequences can cause file operations to resolve outside the intended directory. This behavior maps to CWE-22: Improper Limitation of a Pathname to a Restricted Directory, commonly known as path traversal.

Potential impact

  • An attacker may create files outside the designated jobs directory
  • Existing files may be overwritten if the process has suitable permissions
  • Application behavior or configuration may be disrupted
  • Sensitive files could be modified, depending on filesystem permissions and path resolution
  • The service may be used as a stepping stone for broader compromise if written content is later executed or loaded

General mitigation guidance

Mitigation generally focuses on treating job identifiers as untrusted data and enforcing filesystem confinement.

Common defensive patterns include:

  • Allowing only a narrowly defined identifier format, such as opaque server-generated values
  • Resolving candidate paths canonically and verifying that they remain beneath the intended jobs directory
  • Rejecting path separators, traversal components, absolute paths, and other filesystem-specific special forms
  • Using safe file-creation APIs that do not follow unexpected links where appropriate
  • Reducing service filesystem permissions and separating writable job storage from sensitive application paths
  • Requiring authentication and authorization for API operations that create or modify files

How teams detect issues like this

Organizations commonly identify path traversal risks through:

  • Static analysis rules for concatenating request-derived values with filesystem paths
  • Code review checks for missing canonicalization and directory-boundary validation
  • Tests using encoded, platform-specific, and separator-based path variants
  • Runtime monitoring for file creation outside approved application directories
  • Policy enforcement that restricts API access and service write permissions to required locations

Automated application-security review tools may help flag filesystem operations that consume unsanitized request parameters.

Sources

SourceLink
github.comgithub.com/facefusion/facefusion
github.comgithub.com/facefusion/facefusion/blob/3.6.1/facefusion/jobs/job_manager.py
github.comgithub.com/facefusion/facefusion/commit/a2cbfd73b10191e51ed2eb1e83c19121153e0a22
github.comgithub.com/facefusion/facefusion/releases/tag/3.7.0
github.comgithub.com/geo-chen/oss/blob/main/facefusion.md
vulncheck.comvulncheck.com/advisories/facefusion-before-3.7.0-path-traversal-via-job-identifier

Frequently asked

questions

Yes, deployments that expose the affected unauthenticated HTTP API may be remotely exploitable because the job identifier is supplied through an API request.

The attacker generally needs network access to the API endpoint. Authentication is not necessarily required when the endpoint is exposed without access controls.

Treat job identifiers as untrusted, restrict them to an allowlisted format, and verify that every resolved path remains inside the intended jobs directory before performing file operations.

Combine strict identifier validation, canonical path checks, least-privilege filesystem permissions, authenticated API access, and testing for traversal variants in code review and continuous security testing.

Find out what's already
exploitable in your codebase.