validator vulnerabilities
String validation and sanitization
- Registry
- npm
- Latest
- 13.15.35
- License
- MIT
10 known advisories
The latest version, 13.15.35, is not affected by any of them. Projects on older versions may be.
npm install validator@13.15.35Security advisories for validator
Validator is Vulnerable to Incomplete Filtering of One or More Instances of Special Elements
- Affected
- <13.15.22
- Fixed in
- 13.15.22
validator.js has a URL validation bypass vulnerability in its isURL function
- Affected
- <13.15.20
- Fixed in
- 13.15.20
Inefficient Regular Expression Complexity in Validator.js
- Affected
- >=11.1.0 <13.7.0
- Fixed in
- 13.7.0
Inefficient Regular Expression Complexity in validator.js
- Affected
- <13.7.0
- Fixed in
- 13.7.0
Regular Expression Denial of Service in validator
- Affected
- <3.22.1
- Fixed in
- 3.22.1
XSS Filter Bypass via Encoded URL in validator
- Affected
- <2.0.0
- Fixed in
- 2.0.0
Moderate severity vulnerability that affects validator
- Affected
- <1.1.0
- Fixed in
- 1.1.0
Multiple XSS Filter Bypasses in validator
- Affected
- <1.1.0
- Fixed in
- 1.1.0
Moderate severity vulnerability that affects validator
- Affected
- <1.1.0
- Fixed in
- 1.1.0
Moderate severity vulnerability that affects validator
- Affected
- <1.1.0
- Fixed in
- 1.1.0
Which of your client projects still run an old validator?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.