CVE-2026-3682
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 vulnerability has been detected in welovemedia FFmate up to 2.0.15. This vulnerability affects the function Execute of the file /internal/service/ffmpeg/ffmpeg.go. The manipulation leads to argument injection. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceArgument injection vulnerability in welovemedia FFmate up to v2.0.15 allows remote attackers to inject arbitrary arguments into ffmpeg command execution via the Execute function in /internal/service/ffmpeg/ffmpeg.go. The vulnerability stems from insufficient sanitization of user-controlled input passed to ffmpeg command-line arguments.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 FFmate versionRun 'ffmate --version' or check the binary metadata; if source code, inspect version tag or go.mod fileAffected if Version is 2.0.15 or earlier (including any version up to v2.0.15)
-
Locate the vulnerable Execute functionInspect /internal/service/ffmpeg/ffmpeg.go in the installed codebase or binary; verify the Execute function exists and handles ffmpeg command constructionAffected if The Execute function is present and processes input into ffmpeg command arguments
-
Determine if ffmpeg execution accepts external inputReview application configuration, API endpoints, or CLI interfaces that feed user data to FFmate; check if any input paths lead to the Execute functionAffected if User-supplied data (files, parameters, or arguments) can reach the ffmpeg command execution without strict allowlist filtering
-
Verify current input sanitizationExamine the codebase for argument validation logic before the Execute function call; look for allowlist or input validation routinesAffected if No strict allowlist-based filtering exists on arguments passed to ffmpeg, or sanitization is missing entirely
You are affected if FFmate version is 2.0.15 or earlier AND user-controlled input can reach the Execute function without strict allowlist filtering on ffmpeg arguments.
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 and use allowlist-based argument filtering before passing parameters to ffmpeg execution. Consider refactoring to use ffmpeg libraries instead of shell command execution where possible.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3682 — 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-3682 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