CVE-2025-65122
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 · uneditedRegex Denial of Service in youtube-regex npm package through version 1.0.5.
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 confidenceThis is a Regular Expression Denial of Service (ReDoS) vulnerability in the youtube-regex npm package. The vulnerable regex pattern can be triggered to cause excessive CPU consumption and service disruption through specially crafted input strings.
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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Check installed youtube-regex versionRun 'npm list youtube-regex' in your project directory, or inspect package.json dependenciesAffected if The installed version is 1.0.5 or earlier
-
Identify all code paths using youtube-regexSearch your codebase for imports or requires of 'youtube-regex' and review where the returned regex is applied to inputAffected if The package is imported and its regex is used to validate or parse user-supplied strings
-
Verify if untrusted input reaches the regexAudit the data flow from external sources (HTTP requests, user uploads, API calls) to the youtube-regex functionAffected if External or untrusted strings are passed to the youtube-regex validation function without length limits
-
Confirm the vulnerable regex is in useInspect node_modules/youtube-regex/index.js or the installed package source to confirm the regex pattern exists (the flaw is in the package's regex itself, present in versions <=1.0.5)Affected if The package version is 1.0.5 or earlier and the regex module is loaded
You are affected if youtube-regex version 1.0.5 or earlier is installed and your application processes untrusted input through the package's regex pattern.
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 · scopedUpdate youtube-regex to a version newer than 1.0.5, or if no fixed version exists, consider alternatives or implement input length/validation limits as a workaround.
youtube-regex version greater than 1.0.5 (e.g., latest stable release)
- Run `npm list youtube-regex` to identify the current installed version in your project
- Run `npm install youtube-regex@latest` or `npm install youtube-regex@>1.0.5` to upgrade to a fixed version
- Run `npm audit` to verify the vulnerability is resolved
- Commit the updated package-lock.json file
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65122 — 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-2025-65122 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