CVE-2020-7608: yargs-parser could be tricked into adding or modifying properties of Object.prototype using a "__proto__" payload.
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.51% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: nodejs-nodemon (AlmaLinux:8) 1.18.3-1.module_el8.3.0+2023+d2377ea3, 1.18.3-1.module_el8.3.0+2047+b07ac28e; nodejs-packaging (AlmaLinux:8) 17-3.module_el8.3.0+2023+d2377ea3, 17-3.module_el8.4.0+2521+c668cc9f, 17-3.module_el8.4.0+2224+b07ac28e; node-yargs-parser (Debian:12) 18.1.1-1.
Low priority for now. Upgrade to nodejs-nodemon (AlmaLinux:8) 1.18.3-1.module_el8.3.0+2023+d2377ea3, 1.18.3-1.module_el8.3.0+2047+b07ac28e; nodejs-packaging (AlmaLinux:8) 17-3.module_el8.3.0+2023+d2377ea3, 17-3.module_el8.4.0+2521+c668cc9f, 17-3.module_el8.4.0+2224+b07ac28e; node-yargs-parser (Debian:12) 18.1.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- Mar 16, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 43th percentile
- CWE
- CWE-1321
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| yargs | yargs-parser | cpe:2.3:a:yargs:yargs-parser |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- yargs yargs-parserbefore 5.0.1
- yargs yargs-parser6.0.0 and later · before 13.1.2
- yargs yargs-parser14.0.0 and later · before 15.0.1
- yargs yargs-parser16.0.0 and later · before 18.1.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (snyk). Independent of NVD's CPE analysis and usually ahead of it.
n/a yargs-parser
- All versions prior to version 18.1.1 and patches at 13.1.2 and 15.0.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | nodejs-nodemon | before 1.18.3-1.module_el8.3.0+2023+d2377ea3 | 1.18.3-1.module_el8.3.0+2023+d2377ea3 |
| AlmaLinux:8 | nodejs-nodemon | before 1.18.3-1.module_el8.3.0+2047+b07ac28e | 1.18.3-1.module_el8.3.0+2047+b07ac28e |
| AlmaLinux:8 | nodejs-packaging | before 17-3.module_el8.3.0+2023+d2377ea3 | 17-3.module_el8.3.0+2023+d2377ea3 |
| AlmaLinux:8 | nodejs-packaging | before 17-3.module_el8.4.0+2521+c668cc9f | 17-3.module_el8.4.0+2521+c668cc9f |
| AlmaLinux:8 | nodejs-packaging | before 17-3.module_el8.4.0+2224+b07ac28e | 17-3.module_el8.4.0+2224+b07ac28e |
| Debian:12 | node-yargs-parser | before 18.1.1-1 | 18.1.1-1 |
| npm | yargs-parser | from 14.0.0 · before 15.0.1 | 15.0.1 |
| npm | yargs-parser | from 16.0.0 · before 18.1.1 | 18.1.1 |
| npm | yargs-parser | from 6.0.0 · before 13.1.2 | 13.1.2 |
| npm | yargs-parser | before 5.0.1 | 5.0.1 |
| Red Hat:enterprise_linux:8::appstream | nodejs | before 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 | 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 |
| Red Hat:enterprise_linux:8::appstream | nodejs | before 1:10.23.1-1.module+el8.3.0+9502+012d8a97 | 1:10.23.1-1.module+el8.3.0+9502+012d8a97 |
| Red Hat:enterprise_linux:8::appstream | nodejs-debuginfo | before 1:10.23.1-1.module+el8.3.0+9502+012d8a97 | 1:10.23.1-1.module+el8.3.0+9502+012d8a97 |
| Red Hat:enterprise_linux:8::appstream | nodejs-debuginfo | before 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 | 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 |
| Red Hat:enterprise_linux:8::appstream | nodejs-debugsource | before 1:10.23.1-1.module+el8.3.0+9502+012d8a97 | 1:10.23.1-1.module+el8.3.0+9502+012d8a97 |
| Red Hat:enterprise_linux:8::appstream | nodejs-debugsource | before 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 | 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 |
| Red Hat:enterprise_linux:8::appstream | nodejs-devel | before 1:10.23.1-1.module+el8.3.0+9502+012d8a97 | 1:10.23.1-1.module+el8.3.0+9502+012d8a97 |
| Red Hat:enterprise_linux:8::appstream | nodejs-devel | before 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 | 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 |
| Red Hat:enterprise_linux:8::appstream | nodejs-docs | before 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 | 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 |
| Red Hat:enterprise_linux:8::appstream | nodejs-docs | before 1:10.23.1-1.module+el8.3.0+9502+012d8a97 | 1:10.23.1-1.module+el8.3.0+9502+012d8a97 |
| Red Hat:enterprise_linux:8::appstream | nodejs-full-i18n | before 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 | 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 |
| Red Hat:enterprise_linux:8::appstream | nodejs-full-i18n | before 1:10.23.1-1.module+el8.3.0+9502+012d8a97 | 1:10.23.1-1.module+el8.3.0+9502+012d8a97 |
| Red Hat:enterprise_linux:8::appstream | nodejs-nodemon | before 0:1.18.3-1.module+el8+2632+6c5111ed | 0:1.18.3-1.module+el8+2632+6c5111ed |
| Red Hat:enterprise_linux:8::appstream | nodejs-nodemon | before 0:1.18.3-1.module+el8.1.0+3369+37ae6a45 | 0:1.18.3-1.module+el8.1.0+3369+37ae6a45 |
+16
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:nodejs-nodemon | 1.18.3-1.module_el8.3.0+2023+d2377ea3 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging | 17-3.module_el8.4.0+2224+b07ac28e · AlmaLinux:8 | Package registry (OSV) |
| debian:node-yargs-parser | 18.1.1-1 · Debian:12 | Package registry (OSV) |
| npm:yargs-parser | 13.1.2 | Package registry (OSV) |
| npm:yargs-parser | 15.0.1 | Package registry (OSV) |
| npm:yargs-parser | 18.1.1 | Package registry (OSV) |
| npm:yargs-parser | 5.0.1 | Package registry (OSV) |
| red hat:nodejs | 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-debuginfo | 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-debugsource | 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-devel | 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-docs | 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-full-i18n | 1:12.19.1-1.module+el8.3.0+8851+b7b41ca0 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-nodemon | 0:1.18.3-1.module+el8.1.0+3369+37ae6a45 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:rh-nodejs12-nodejs | 0:12.19.1-2.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs12-nodejs-debuginfo | 0:12.19.1-2.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs12-nodejs-devel | 0:12.19.1-2.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs12-nodejs-docs | 0:12.19.1-2.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-nodejs12-npm | 0:6.14.8-12.19.1.2.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| rocky linux:nodejs-nodemon | 0:1.18.3-1.module+el8.3.0+101+f84c7154 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:nodejs-packaging | 0:17-3.module+el8.3.0+101+f84c7154 · Rocky Linux:8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-1321 · Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →