Skip to main content

ai-fusion-video CVE-2026-110212

| EUVDEUVD-2026-99253 MEDIUM
Path Traversal (CWE-22)
2026-10-13 disclosure@vulncheck.com GHSA-56g6-3cr7-7xx2
5.3
CVSS 4.0 · Vendor: vulncheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege user
  2. Delivery
    POST crafted upload with ../ in subDir
  3. Exploit
    LocalStorageStrategy.storeBytes skips normalization
  4. Execution
    Write attacker file outside media dir
  5. Impact
    Potential code execution or config tampering

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a valid authenticated account (PR:L) able to reach POST /api/storage/upload, and the instance must use the local filesystem storage backend (LocalStorageStrategy) rather than a remote/object store, since the flaw is the missing normalization in LocalStorageStrategy.storeBytes. The attacker controls the subDir parameter and supplies parent-directory (../) sequences plus a chosen filename and extension. Exploitation is limited to directories the service account has write permission to, and impact scales with where that account can write (e.g., a web-served or configuration directory); it does not grant read/confidentiality access by itself. Limiting factors: authentication is mandatory, and no confidentiality or availability impact is produced by the write primitive alone.

Impact

This is a moderate, not top-tier, priority. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) and the 5.3 base score agree with the description: network-reachable, low attack complexity, no user interaction, but requiring authentication (PR:L) and yielding only limited integrity impact (VI:L) with no confidentiality or availability impact. No EPSS score, CISA KEV listing, or explicit POC/exploit-code flag is present in the input, so there is no signal of active or widespread exploitation - the exploitation status is 'no public exploit identified at time of analysis.' Two of the four NVD references are human-written analyses (a hackmd write-up and a VulnCheck advisory) that describe the flaw in detail, which lowers the barrier to weaponization even though no packaged exploit is indicated. One tension worth flagging: the vendor rates integrity as Low (VI:L), but the description states an attacker can write attacker-controlled files with chosen extensions anywhere the service account can write - depending on deployment that could enable webshell drop or config overwrite and a higher real integrity impact, so the Low rating may understate worst-case risk. Overall, the authentication requirement and the niche nature of the affected product keep real-world risk contained, making this a 'patch in normal cycle' item rather than an emergency.

Exploit ScenarioDerived

An authenticated low-privilege user of an ai-fusion-video instance sends a POST to /api/storage/upload with a subDir value containing ../ sequences, causing LocalStorageStrategy.storeBytes to write the uploaded file outside the intended media directory. By choosing the filename, extension, and traversal target, the attacker plants attacker-controlled content (e.g., into a web-served or config directory) anywhere the service account can write. No packaged public exploit is indicated, but detailed technical write-ups of the flaw are publicly referenced.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Authenticated file-write path traversal in ai-fusion-video through 1.2.0 lets a logged-in user escape the intended media directory by supplying parent-directory sequences in the subDir parameter of POST /api/storage/upload, writing attacker-chosen filenames and extensions anywhere the service account can write. Only deployments using the local filesystem backend (LocalStorageStrategy) are affected, and the write primitive produces no confidentiality or availability impact by itself, so the real severity depends on where the service account can write; authentication is mandatory (CVSS 4.0 vector shows PR:L) and no public exploit identified at time of analysis. This is a moderate, not top-tier, priority finding - the risk rises sharply if the account can write into a web-served, startup, or configuration directory, which would turn an integrity-only write into a potential code-execution or configuration-tampering stepping stone.

RemediationAI

No vendor-released patch identified at time of analysis: neither the vendor advisory nor any reference supplied names a fixed ai-fusion-video version, so upgrade guidance cannot be given with a version number and operators should track https://www.vulncheck.com/advisories/ai-fusion-video-through-1.2.0-path-traversal-in-media-upload-subdir-parameter for the first patched release. Because the root cause is the missing canonicalization in LocalStorageStrategy.storeBytes, the definitive code fix is to resolve the requested destination with Path.normalize/toRealPath and reject or clamp any result that does not start with the configured media root, and to refuse any subDir value containing .. segments or absolute paths; until that ships, the most effective compensating control is to reject uploads whose subDir is anything other than a short allowlisted token (for example a date or category slug), accepting the trade-off that some legitimate nested-directory workflows will break. Switch instances to a remote/object storage backend if one is supported, which removes the vulnerable code path entirely at the cost of relying on external storage credentials and network availability. Run the service under a dedicated least-privilege account whose write permissions are confined to a single media directory that is not web-served, not on the executable path, and not adjacent to configuration or template files; mount that directory noexec and nosuid, and ensure it is not reachable by the application server's classpath or plugin loader. Applying an extension allowlist to uploaded files adds defense in depth but is not a substitute, since the traversal itself is in the path and not the type. Where the upload endpoint is not needed by all users, disable or network-restrict POST /api/storage/upload to trusted accounts and monitor file-creation events outside the media root, since an alert on writes outside that boundary is a reliable indicator of exploitation attempts.

Affected VersionsENISA

ai-fusion-video 0 ≤1.2.0

Affected Packages

euvd ai_fusion_video no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected code is a Java web application whose upload pipeline splits responsibilities between the Spring-style controller in FileUploadController.java (lines 72-99 of the v1.2.0 tree) and the local storage backend LocalStorageStrategy.storeBytes (lines 77-92). The controller passes the client-supplied subDir value straight into the storage layer, and storeBytes concatenates it onto the configured media root without ever canonicalizing the resulting path, so the CWE-22 path traversal class applies directly: sequences such as ../ are preserved, directory creation follows the attacker-controlled path, and the uploaded bytes land with the attacker-selected filename and extension. Because the flaw is architectural to the local strategy rather than to a specific parser or codec, it affects any deployment configured with the filesystem backend, while deployments backed by an object/remote store do not exercise the vulnerable code path. The primitive is a write-only, authenticated primitive limited by the OS permissions of the service account; the code path itself never grants read access to files outside the media directory, and it does not itself cause denial of service. Cross-referencing the two source references shows the missing normalization exists in storeBytes rather than in the controller, which is why input filtering at the controller boundary alone is not sufficient remediation.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vulncheck) PRIMARY 5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.3 MEDIUM

Network endpoint with low complexity but mandatory low-privilege authentication (PR:L); arbitrary file write gives integrity impact (I:L), with no confidentiality or availability loss and no scope change.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (vulncheck).

CVSS VectorVendor: vulncheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Stonewuu ai-fusion-video through 1.2.0 contains a path traversal vulnerability that allows authenticated users to write uploaded files outside the media directory via the subDir parameter of POST /api/storage/upload. Attackers can supply parent-directory sequences that LocalStorageStrategy.storeBytes never normalizes, creating directories and writing attacker-controlled files with chosen extensions anywhere the service account can write.

Threat Intelligence Overview

EPSS Score
0.4%
Top 69% exploitable
Prevalence
Rare
obscure single-author open-source Java project, no enterprise footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy