GHSA-xxvw-45rp-3mj2 · Severity: critical · Ecosystem: npm — Deserialization Code Execution in js-yaml
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, which allows remote attackers to execute arbitrary code via a crafted string that triggers an eval operation.
Conclusion & alert: CVE-2013-4660 is rated High Exploit Risk (75.5/100): CVSS Medium severity, with high exploitation likelihood (EPSS 64.51%, 98th percentile). Core evidence: 2 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
| EDB-ID | Source | Kind | Published | Link |
|---|---|---|---|---|
| 28655 | exploit_db | edb | 2013-09-30 | Exploit-DB ↗ |
| — | nvd_ref | exploit_tag | Exploit-DB ↗ |
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
| # | Date | Old EPSS score | New EPSS score | Delta (New - Old) |
|---|---|---|---|---|
| 1 | 2025-08-18 | 65.61% | 64.51% | -1.10% |
| 2 | 2025-03-30 | 65.66% | 65.61% | -0.05% |
| 3 | 2025-03-29 | — | 65.66% | — |
Full EPSS history (17 records total)
CVSS metrics for this CVE.
| Base score | Version | Severity | Vector | Exploitability | Impact | Score source |
|---|---|---|---|---|---|---|
| 6.8 | 2.0 | MEDIUM |
|
8.6 | 6.4 | [email protected] |
GHSA-xxvw-45rp-3mj2 · Severity: critical · Ecosystem: npm — Deserialization Code Execution in js-yaml
| Vendor | Product | Version | Raw CPE |
|---|---|---|---|
| nodeca | js-yaml | <= 2.0.4 | cpe:2.3:a:nodeca:js-yaml:*:*:*:*:*:*:*:* |
| nodeca | js-yaml | 0.2.0 | cpe:2.3:a:nodeca:js-yaml:0.2.0:*:*:*:*:*:*:* |
| nodeca | js-yaml | 0.2.1 | cpe:2.3:a:nodeca:js-yaml:0.2.1:*:*:*:*:*:*:* |
| nodeca | js-yaml | 0.2.2 | cpe:2.3:a:nodeca:js-yaml:0.2.2:*:*:*:*:*:*:* |
| nodeca | js-yaml | 0.3.0 | cpe:2.3:a:nodeca:js-yaml:0.3.0:*:*:*:*:*:*:* |
| nodeca | js-yaml | 0.3.1 | cpe:2.3:a:nodeca:js-yaml:0.3.1:*:*:*:*:*:*:* |
| nodeca | js-yaml | 0.3.2 | cpe:2.3:a:nodeca:js-yaml:0.3.2:*:*:*:*:*:*:* |
| nodeca | js-yaml | 0.3.3 | cpe:2.3:a:nodeca:js-yaml:0.3.3:*:*:*:*:*:*:* |
| nodeca | js-yaml | 0.3.4 | cpe:2.3:a:nodeca:js-yaml:0.3.4:*:*:*:*:*:*:* |
| nodeca | js-yaml | 0.3.5 | cpe:2.3:a:nodeca:js-yaml:0.3.5:*:*:*:*:*:*:* |
| nodeca | js-yaml | 0.3.6 | cpe:2.3:a:nodeca:js-yaml:0.3.6:*:*:*:*:*:*:* |
| nodeca | js-yaml | 0.3.7 | cpe:2.3:a:nodeca:js-yaml:0.3.7:*:*:*:*:*:*:* |
| nodeca | js-yaml | 1.0.0 | cpe:2.3:a:nodeca:js-yaml:1.0.0:*:*:*:*:*:*:* |
| nodeca | js-yaml | 1.0.1 | cpe:2.3:a:nodeca:js-yaml:1.0.1:*:*:*:*:*:*:* |
| nodeca | js-yaml | 1.0.2 | cpe:2.3:a:nodeca:js-yaml:1.0.2:*:*:*:*:*:*:* |
| nodeca | js-yaml | 1.0.3 | cpe:2.3:a:nodeca:js-yaml:1.0.3:*:*:*:*:*:*:* |
| nodeca | js-yaml | 2.0.0 | cpe:2.3:a:nodeca:js-yaml:2.0.0:*:*:*:*:*:*:* |
| nodeca | js-yaml | 2.0.1 | cpe:2.3:a:nodeca:js-yaml:2.0.1:*:*:*:*:*:*:* |
| nodeca | js-yaml | 2.0.2 | cpe:2.3:a:nodeca:js-yaml:2.0.2:*:*:*:*:*:*:* |
| nodeca | js-yaml | 2.0.3 | cpe:2.3:a:nodeca:js-yaml:2.0.3:*:*:*:*:*:*:* |
| URL | Tags |
|---|---|
| http://portal.nodesecurity.io/advisories/js-yaml | Vendor Advisory |
| https://nealpoole.com/blog/2013/06/code-execution-via-yaml-in-js-yaml-nodejs-module/ | Exploit Vendor Advisory |