CVE-2013-4660

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 17%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
—
EG Score
0.0(none)
EPSS
96.7%
KEV
Not listed

Published

June 28, 2013

Last Modified

April 29, 2026

References (4)

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
js-yaml—2.0.5—

Data Freshness Timeline

(refreshed 5× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 13:41 UTCEPSS rescore
  2. 2026-07-05 02:26 UTCEPSS rescore
  3. 2026-07-02 15:21 UTCEPSS rescore
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-06-30 23:19 UTCEPSS rescore
  6. 2026-06-29 14:02 UTCEPSS rescore
  7. 2026-06-28 14:03 UTCEPSS rescore
  8. 2026-06-28 04:53 UTCEPSS rescore
  9. 2026-06-28 04:53 UTCEPSS rescore
  10. 2026-06-27 03:05 UTCEPSS rescore
  11. 2026-06-25 13:47 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-24 14:02 UTCEPSS rescore
  14. 2026-06-24 14:02 UTCEPSS rescore
  15. 2026-06-23 21:30 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-21 14:53 UTCEPSS rescore
  18. 2026-06-21 01:57 UTCEPSS rescore
  19. 2026-06-21 01:57 UTCEPSS rescore
  20. 2026-06-19 19:23 UTCEPSS rescore
  21. 2026-06-18 17:49 UTCEPSS rescore
  22. 2026-06-18 17:49 UTCEPSS rescore
  23. 2026-06-17 17:49 UTCEPSS rescore
  24. 2026-06-17 17:49 UTCEPSS rescore
  25. 2026-06-16 17:49 UTCEPSS rescore
Show 35 more
  1. 2026-06-16 17:49 UTCEPSS rescore
  2. 2026-06-16 17:49 UTCEPSS rescore
  3. 2026-06-15 17:44 UTCEPSS rescore
  4. 2026-06-14 23:14 UTCEPSS rescore
  5. 2026-06-13 22:57 UTCEPSS rescore
  6. 2026-06-12 23:08 UTCEPSS rescore
  7. 2026-06-11 13:56 UTCEPSS rescore
  8. 2026-06-10 22:15 UTCEPSS rescore
  9. 2026-06-10 13:18 UTCEPSS rescore
  10. 2026-06-07 15:22 UTCEPSS rescore
  11. 2026-06-06 13:45 UTCEPSS rescore
  12. 2026-06-06 13:45 UTCEPSS rescore
  13. 2026-06-05 22:44 UTCEPSS rescore
  14. 2026-06-05 22:44 UTCEPSS rescore
  15. 2026-06-05 06:08 UTCEPSS rescore
  16. 2026-06-05 06:08 UTCEPSS rescore
  17. 2026-06-04 13:09 UTCEPSS rescore
  18. 2026-06-04 13:09 UTCEPSS rescore
  19. 2026-06-02 20:10 UTCEPSS rescore
  20. 2026-06-02 20:10 UTCEPSS rescore
  21. 2026-06-01 13:49 UTCEPSS rescore
  22. 2026-06-01 13:49 UTCEPSS rescore
  23. 2026-05-29 13:41 UTCEPSS rescore
  24. 2026-05-29 13:41 UTCEPSS rescore
  25. 2026-05-28 23:29 UTCEG score recompute
  26. 2026-05-27 13:38 UTCEPSS rescore
  27. 2026-05-27 13:38 UTCEPSS rescore
  28. 2026-05-22 21:15 UTCEPSS rescore
  29. 2026-05-22 21:15 UTCEPSS rescore
  30. 2026-05-22 21:15 UTCEPSS rescore
  31. 2026-05-21 22:39 UTCEPSS rescore
  32. 2026-05-20 22:37 UTCEPSS rescore
  33. 2026-05-20 22:37 UTCEPSS rescore
  34. 2026-05-18 21:29 UTCEPSS rescore
  35. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-28655✓ verified
    First seen Sep 30, 2013

    Nodejs - 'js-yaml load()' Code Exec (Metasploit)

    Open source ↗
  • Metasploitexploit/multi/fileformat/nodejs_js_yaml_load_code_exec✓ verified
    First seen Jun 28, 2013

    Nodejs js-yaml load() Code Execution

    Open source ↗

Frequently asked(4)

What is CVE-2013-4660?
CVE-2013-4660 is a none vulnerability published on June 28, 2013. 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.
When was CVE-2013-4660 disclosed?
CVE-2013-4660 was first published in the National Vulnerability Database on June 28, 2013, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-4660 actively exploited?
CVE-2013-4660 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2013-4660?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-4660, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-4660

Explore →

Is Your Infrastructure Affected by CVE-2013-4660?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs