Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-84702 – Unauthenticated Arbitrary File Write via Path Traversal – FaceFusion < 3.7.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-84702 is a path traversal vulnerability (CWE-22) in FaceFusion, an open-source face-swapping/deepfake toolkit, affecting all versions prior to 3.7.0. The flaw resides in the job management code’s handling of job identifiers, allowing an unauthenticated remote attacker to write arbitrary files to the filesystem through FaceFusion’s HTTP-exposed Gradio API. The issue has a CVSS v4.0 base score of 8.7 (High) and a CVSS v3.1 base score of 7.5 (High).

Technical details

  • Root cause: The get_job_file_name and suggest_job_path functions in facefusion/jobs/job_manager.py construct on-disk job file paths by concatenating an attacker-controlled job_id value with the jobs directory using os.path.join, without normalizing or rejecting directory traversal sequences (e.g., ../). A sanitize_job_id function exists and is applied in the CLI path, but the Gradio-based HTTP API does not invoke this sanitizer.
  • Trigger conditions: An attacker submits a create_job request (via the /gradio_api/run/ endpoint exposed by FaceFusion’s web UI) containing a crafted job_id, such as ../../../../tmp/attacker_owned.
  • Attack vector: Network-based, no authentication and no user interaction required (per both CVSS v3.1 and v4.0 vectors).
  • Impact: The unsanitized path is passed through create_job_file/write_json (facefusion/json.py), allowing the application to write a JSON file to an arbitrary filesystem location writable by the FaceFusion process. This can be used to overwrite or plant configuration files or otherwise corrupt data outside the intended jobs directory. Public analysis characterizes the primary impact as integrity loss (arbitrary file write), without confirmed impact to confidentiality or availability.

Affected software

  • FaceFusion versions 0 up to (but not including) 3.7.0
  • Vulnerable code confirmed present in the 3.6.1 release of facefusion/jobs/job_manager.py

Severity

  • CVSS v3.1 Base Score: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
  • CVSS v4.0 Base Score: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade FaceFusion to version 3.7.0 or later, which fixes the job identifier normalization issue (patch commit a2cbfd73b10191e51ed2eb1e83c19121153e0a22).
  • If unable to patch immediately:
    • Do not expose the FaceFusion Gradio web UI/API directly to the internet or untrusted networks; restrict access behind authentication and network-level controls (firewall/VPN/allow-listing).
    • Run FaceFusion under a low-privilege service account with write access limited to the intended jobs directory to reduce the blast radius of any arbitrary file write.
    • Monitor for unexpected file creation/modification outside the configured jobs directory as an indicator of exploitation attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge