dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2026-5986

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
A weakness has been identified in Zod jsVideoUrlParser up to 0.5.1. The impacted element is the function getTime in the library lib/util.js. This manipulation of the argument timestamp causes inefficient regular expression complexity. It is possible to initiate the attack remotely. The exploit has been made available to the public and could 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 confidence

A Regular Expression Denial of Service (ReDoS) vulnerability exists in the getTime function in lib/util.js of jsVideoUrlParser up to version 0.5.1. The function contains an inefficient regular expression that can be exploited remotely by providing a specially crafted timestamp argument, causing excessive computational complexity and potential denial of service.

MitigationUpgrade to a patched version of jsVideoUrlParser once available. If no patch is available, implement input validation and length constraints on the timestamp parameter to limit the regex attack surface, or replace the inefficient regex with an optimized pattern.

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
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if jsVideoUrlParser is installed
    Check your project dependencies (e.g., look in package.json for jsVideoUrlParser, or run 'npm list jsVideoUrlParser' if using npm)
    Affected if jsVideoUrlParser is listed as a dependency with a version at or below 0.5.1
  2. Confirm the installed version
    Run a command to retrieve the installed version, such as 'npm list jsVideoUrlParser --depth=0' or check the installed package.json in node_modules/jsVideoUrlParser/package.json
    Affected if The version returned is 0.5.1 or any version lower than 0.5.1
  3. Locate usage of the getTime function
    Search your codebase for imports or requires of the getTime function from lib/util.js, for example by searching for 'getTime' or the pattern 'require("jsVideoUrlParser").util.getTime'
    Affected if Code calls the getTime function from jsVideoUrlParser lib/util.js module
  4. Check if input validation exists on timestamp parameter
    Review the code that calls getTime to see if the timestamp argument is validated before being passed, or check if any middleware/input sanitization exists for timestamp inputs
    Affected if No input validation or length constraints are applied to the timestamp argument before it is passed to getTime
  5. Verify the vulnerable regex exists in the library
    If accessible, inspect the lib/util.js file within the installed jsVideoUrlParser package and locate the getTime function to confirm it contains the inefficient regular expression
    Affected if The getTime function in lib/util.js contains an unoptimized regex pattern that processes timestamp input

You are affected if jsVideoUrlParser version 0.5.1 or lower is installed AND your code calls the getTime function from lib/util.js without validating the timestamp input first.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of jsVideoUrlParser once available. If no patch is available, implement input validation and length constraints on the timestamp parameter to limit the regex attack surface, or replace the inefficient regex with an optimized pattern.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5986 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5986 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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