CVE-2026-37281
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 · uneditedAn OS command injection vulnerability in the /stream-to-vlc Express route in hitarth-gg Zenshin before 2.7.0 allows remote attackers to execute arbitrary commands via the url parameter.
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 · high confidenceThe /stream-to-vlc Express route in hitarth-gg Zenshin versions before 2.7.0 contains an OS command injection vulnerability in the 'url' parameter, allowing remote attackers to execute arbitrary operating system commands on the host.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm Zenshin is installedIdentify if the hitarth-gg Zenshin application is running in your environment by checking running processes, installed packages, or application directories. Look for the application name 'Zenshin' or related files.Affected if Zenshin software is present on the system
-
Check installed Zenshin versionRetrieve the version of Zenshin currently installed. This may be in a package.json file, package-lock.json, a version file, or obtainable via a version command if the application exposes one. Compare the version number to the affected range (versions prior to 2.7.0).Affected if The installed version is less than 2.7.0 (e.g., 2.6.x, 2.5.x, etc.)
-
Verify /stream-to-vlc endpoint existsInspect the application source code, routing configuration, or API documentation to confirm the /stream-to-vlc route is defined in the Express application. Alternatively, attempt an HTTP request to this endpoint if it may be externally accessible.Affected if The /stream-to-vlc endpoint is defined and accessible in the application
-
Confirm url parameter handlingReview the source code implementation of the /stream-to-vlc route handler. Look for code that takes a 'url' query parameter and passes it to system command execution functions (such as exec, execSync, spawn, or shell execution) without sanitization.Affected if The url parameter is passed directly to system command functions without input validation
You are affected if Zenshin version is less than 2.7.0 AND the /stream-to-vlc endpoint exists with unsanitized url parameter handling in your deployment.
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.
dbcve · scopedUpgrade to Zenshin version 2.7.0 or later. If immediate patching is not possible, disable the /stream-to-vlc endpoint and implement strict input validation on the 'url' parameter to prevent shell metacharacter injection.
Upgrade to Zenshin version 2.7.0 or later
- 1. Identify the current version of Zenshin being used (check package.json or package-lock.json)
- 2. Upgrade to version 2.7.0 or later using: npm install zenshin@latest or npm install zenshin@^2.7.0
- 3. Verify the upgrade was successful by checking the installed version: npm list zenshin
- 4. Restart the application to load the patched version
- 5. Test that the /stream-to-vlc route no longer accepts arbitrary command injection via the url parameter
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-37281 — 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-37281 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