Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege user
-
ExploitCall Media Generation API saveGeneratedImages
-
ExecutionManipulate output_path argument
-
ImpactWrite/include file outside managed storage
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File name/path control
|
| Exploitation Conditions | Exploitation requires an authenticated low-privilege account on an ekko-studio instance (≤1.0.6) and the ability to reach the Media Generation API endpoint backed by the saveGeneratedImages function (packages/server/src/modules/studio/controllers/media.ts). The specific trigger is supplying an attacker-controlled output_path argument to that image-generation request; the patch evidence shows this 'request custom image/video output path' capability was available to ordinary users and is removed by the fix. Limiting factors: valid authentication is required (PR:L, so not exploitable by fully anonymous attackers), the instance must expose the Media Generation API, and impact is bounded to limited file integrity/availability effects with no confidentiality disclosure per the authoritative vector. |
| Impact | This is a medium-severity (CVSS 4.0 base 5.3) path-control flaw (CWE-73, External Control of File Name or Path) that is a low-to-moderate priority, not a top-tier emergency. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L) indicates network-reachable, low-complexity exploitation but requires authenticated low-privilege access (PR:L) and yields only limited integrity and availability impact with NO confidentiality impact (VC:N). There is no EPSS score provided, no CISA KEV listing, and no public exploit identified at time of analysis - so there is no evidence of active exploitation; the requirement for prior authentication plus the low technical impact meaningfully constrains real-world risk. One signal conflicts with the data: the 'Information Disclosure' tag implies confidentiality exposure, yet the authoritative CVSS vector explicitly sets VC:N, so the issue is better characterized as unauthorized file write/inclusion affecting integrity and availability rather than data leakage - verify the actual impact against the patch behavior. The GitHub source evidence corroborates the authentication requirement: the fix prevents ordinary users from requesting custom image/video output paths, consistent with PR:L. |
| Exploit ScenarioDerived | An authenticated low-privilege user of ekko-studio invokes the Media Generation API's saveGeneratedImages function and supplies a crafted output_path argument, causing a file to be written to or included from a location outside the intended managed image storage directory. No public exploit code exists; exploitation requires a valid (even low-privilege) account on the target instance. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
EKKOLearnAI ekko-studio through 1.0.6 lets an authenticated low-privilege user supply an attacker-controlled output_path to the Media Generation API, which the saveGeneratedImages handler in packages/server/src/modules/studio/controllers/media.ts passes into a file operation without adequate path validation. Successful abuse gives limited file integrity and availability impact (CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L) with no confidentiality disclosure per the authoritative assessment, and requires a valid account plus network reachability to the media-generation endpoint - anonymous attackers cannot trigger it. No public exploit code was identified at time of analysis, exploitation has not been confirmed in the wild, and an upstream fix exists as commit 1d42459c292f89e412f7f6243829e7fed2e85bf5 (PR #3404) that removes the ordinary-user ability to request custom image/video output paths.
RemediationAI
Apply the upstream fix identified by commit 1d42459c292f89e412f7f6243829e7fed2e85bf5 (pull request https://github.com/EKKOLearnAI/ekko-studio/pull/3404, referenced from the advisory at https://vuldb.com/vuln/424736); note that the input confirms an upstream fix via PR/commit and vendor-available patch data, but a released patched version number is not independently confirmed, so verify the tag or build you deploy actually contains that commit - upstream fix available (PR/commit); released patched version not independently confirmed. The fix changes behavior so ordinary users can no longer request custom image/video output paths while managed image storage continues to function, so re-test media generation workflows for users who previously relied on a custom output_path. If immediate upgrade is not possible, compensating controls are: restrict network access to the Media Generation API endpoints to trusted users or internal networks only (reduces exposure window but does not fix the flaw, and breaks remote/team use of those endpoints); run the ekko-studio service account with write permission confined to the managed media storage directory and no write access elsewhere on the host filesystem (limits where an attacker-controlled output_path can land, at the cost of requiring a deliberate filesystem permission audit and possibly breaking auxiliary exports); and audit existing accounts for low-privileged users who should not be generating media at all, removing that access. Additional detail is available in the VulDB CTI entry https://vuldb.com/vuln/424736/cti.
Affected VersionsENISA
Affected Packages
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
ekko-studio is a Node/TypeScript application whose server component exposes a Studio media-generation controller at packages/server/src/modules/studio/controllers/media.ts; saveGeneratedImages persists generated media to a caller-influenced destination path. The root cause is CWE-73 (External Control of File Name or Path): the output_path argument is trusted and used to construct a filesystem destination without canonicalization or confinement to the managed media storage directory, so a user able to reach the endpoint can redirect writes outside the intended location. The upstream acceptance record for PR #3404 explicitly lists the behavioral change that 'ordinary users cannot ... request custom image/video output paths; managed image storage remains functional,' which confirms the vulnerable capability was exposed to non-privileged accounts and that the fix removes user-supplied paths while keeping server-controlled storage intact. Both the CVSS 4.0 vector supplied with the CVE (AV:N/AC:L/AT:N/PR:L/UI:N) and the independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:U) agree the attack is network-reachable but requires a low-privileged authenticated session, and both bound impact to integrity/availability only. CPE coverage is the single wildcard entry cpe:2.3:a:ekkolearnai:ekko-studio:*:*:*:*:*:*:*:*, i.e. all versions up to and including 1.0.6.
Know when Ekko Studio gets its next vulnerability
- 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
Network-reachable API with low complexity but requires an authenticated low-privilege account (PR:L); attacker-controlled output_path yields limited file write/inclusion affecting integrity and availability, no confidentiality impact.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
DescriptionCVE.org
A flaw has been found in EKKOLearnAI ekko-studio up to 1.0.6. This vulnerability affects the function saveGeneratedImages of the file packages/server/src/modules/studio/controllers/media.ts of the component Media Generation API. This manipulation of the argument output_path causes file inclusion. Remote exploitation of the attack is possible. Patch name: 1d42459c292f89e412f7f6243829e7fed2e85bf5. It is recommended to apply a patch to fix this issue.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-107558
GHSA-622g-c849-p3ww
NVD
CVE.org
EPSS
VulDB
Exploit-DB