CVE-2026-43624
Received Received - Intake
Path Traversal in F5-TTS via Unsanitized Project Names

Publication date: 2026-06-01

Last updated on: 2026-06-01

Assigner: VulnCheck

Description
F5-TTS through version 1.1.20 contains a path traversal vulnerability in the finetune Gradio handlers that allows unauthenticated attackers to write arbitrary files by passing unsanitized user-supplied project names directly to os.path.join() without validating the resulting path stays within the intended base directory. Attackers can supply absolute path arguments such as /tmp/EVIL to override the base directory entirely and create arbitrary directories with attacker-controlled JSON content at any filesystem path writable by the server process.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-01
Last Modified
2026-06-01
Generated
2026-06-02
AI Q&A
2026-06-01
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
f5 tts to 1.1.20 (exc)
f5 tts 1.1.20
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.


Can you explain this vulnerability to me?

CVE-2026-43624 is a path traversal vulnerability in the F5-TTS software, specifically in the finetune Gradio handlers. It occurs because user-supplied project names are passed directly to os.path.join() without proper validation, allowing attackers to supply absolute paths or path traversal sequences.

This flaw enables unauthenticated attackers to create arbitrary directories and write files outside the intended base directories anywhere on the filesystem writable by the server process. For example, an attacker can use a project name like "/tmp/EVIL" to override the base directory and write attacker-controlled JSON content in arbitrary locations.

The vulnerability affects functions such as create_data_project and save_settings, which accept unsanitized project names, leading to directory creation and file writes outside the intended application boundaries. Although it does not allow direct code execution, it enables unauthorized file system modifications.


How can this vulnerability impact me? :

This vulnerability can impact you by allowing unauthenticated attackers to write arbitrary files and create directories anywhere on the filesystem where the server process has write permissions.

  • Attackers can bypass directory restrictions and place attacker-controlled JSON files outside the intended application directories.
  • This can lead to unauthorized modification or addition of files, potentially affecting application behavior or data integrity.
  • While it does not allow direct code execution, the ability to write files arbitrarily can be leveraged in further attacks or to disrupt normal operations.

How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by checking for the presence of unexpected directories or files created outside the intended F5-TTS data or checkpoint directories, especially directories or files with attacker-controlled names such as those starting with /tmp/F5TTS_PWND or similar path traversal patterns.

On the system running the vulnerable F5-TTS version, you can look for suspicious directories or files created by the server process in locations like /tmp or other writable filesystem paths.

  • Use commands like `find /tmp -name 'F5TTS_PWND*'` to locate suspicious directories or files created by exploitation attempts.
  • Check for the presence of unexpected `setting.json` files outside the normal F5-TTS directories, for example: `find /tmp -name 'setting.json'`.

Additionally, monitoring logs for unusual or unauthenticated requests to the finetune Gradio handlers that include project names with absolute paths or path traversal sequences can help detect exploitation attempts.


What immediate steps should I take to mitigate this vulnerability?

The immediate mitigation step is to upgrade F5-TTS to a version that includes the patch fixing this vulnerability. The fix was introduced in commit `2f53ded` which adds proper validation and sanitization of project names to prevent path traversal.

If upgrading immediately is not possible, restrict access to the finetune Gradio handlers to trusted users only, as the vulnerability allows unauthenticated attackers to exploit it.

Implement filesystem permissions to limit the write access of the F5-TTS server process, preventing it from writing outside intended directories.

Monitor and audit filesystem locations for suspicious files or directories created by exploitation attempts and remove them.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart