CVE-2026-8115
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security flaw has been discovered in gyoridavid short-video-maker up to 1.3.4. This affects an unknown part of the file src/server/routers/rest.ts of the component REST API. The manipulation of the argument req.params.tmpFile results in path traversal. The attack can be launched remotely. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePath traversal vulnerability in the REST API of gyoridavid short-video-maker allows remote attackers to access arbitrary files on the server by manipulating the tmpFile parameter in src/server/routers/rest.ts with directory traversal sequences (e.g., ../../../).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of short-video-makerCheck the package.json file in the project root for the version field, or run 'npm list short-video-maker' if installed as a dependencyAffected if The installed version falls within the vulnerable range (prior to the patch that addresses the path traversal in tmpFile parameter)
-
Locate the vulnerable REST API router fileInspect the file at src/server/routers/rest.ts in the application directoryAffected if The file exists and contains code handling the tmpFile parameter without proper path traversal validation
-
Verify the tmpFile parameter handling in the REST endpointSearch the src/server/routers/rest.ts file for 'tmpFile' and examine how it is processed - look for direct file system access without path.basename() or allowlist validationAffected if The tmpFile parameter is used in file operations without sanitizing directory traversal sequences like ../
-
Confirm the REST API is exposedCheck the server configuration or main entry point (such as src/server/index.ts) to verify the REST API router is mounted and accessibleAffected if The REST API endpoint handling tmpFile is reachable from the network
-
Check for presence of path traversal protectionReview the code around tmpFile usage for input validation functions - look for path.basename(), allowlist validation, or regex patterns rejecting ../ sequencesAffected if No such validation is present and the tmpFile parameter accepts raw user input for file operations
You are affected if you are running any version of gyoridavid short-video-maker with the REST API enabled and the vulnerable tmpFile parameter code exists without path traversal validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation on the tmpFile parameter to reject path traversal sequences; use path.basename() or allowlist validation to ensure only intended files within the allowed directory can be accessed.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8115 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8115 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data