Home/CVE/js-yaml is a JavaScript YAML parser and dumper. In js-yaml before 4.1.1 and 3.14.2, it's possible for an attacker to mod
CVE
CVE-2025-64718
js-yaml is a JavaScript YAML parser and dumper. In js-yaml before 4.1.1 and 3.14.2, it's possible for an attacker to mod
js-yaml is a JavaScript YAML parser and dumper. In js-yaml before 4.1.1 and 3.14.2, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution (__proto__). All users who parse untrusted yaml documents may be impacted.
The problem is patched in js-yaml 4.1.1 and 3.14.2. Users can protect against this kind of attack on the server by using node --disable-proto=delete or deno (in Deno, pollution protection is on by default).
MEDIUM · CVSS 5.3
EPSS 0.00025
Schedule remediation
- SSVC automatable: yes - attacks can be scripted at scale
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2025-64718, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
1Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
3Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
⬡
Weakness Classification
▤
Affected Products & Versions
2nodeca js-yaml< 3.14.2
nodeca js-yaml>= 4.0.0 and < 4.1.1
▤
Affected Packages
1Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
npm
js-yaml
MODERATE
fixed in 4.1.1
📦
Fixed versions by distribution
38The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
suse sle15golang-github-prometheus-prometheus open
suse sle15nodejs10 open
suse sle15nodejs10-devel open
suse sle15nodejs10-docs open
suse sle15nodejs12 open
suse sle15nodejs12-devel open
suse sle15nodejs12-docs open
suse sle15nodejs14 open
suse sle15nodejs14-devel open
suse sle15nodejs14-docs open
suse sle15nodejs16 open
suse sle15nodejs16-devel open
suse sle15nodejs16-docs open
suse sle15nodejs18 open
suse sle15nodejs18-devel open
suse sle15nodejs18-docs open
suse sle15nodejs20 open
suse sle15nodejs20-devel open
suse sle15nodejs20-docs open
suse sle15nodejs22 open
suse sle15nodejs22-devel open
suse sle15nodejs22-docs open
suse sle15nodejs24 open
suse sle15nodejs24-devel open
suse sle15nodejs24-docs open
suse sle15nodejs8 open
suse sle15nodejs8-devel open
suse sle15nodejs8-docs open
suse sle15npm10 open
suse sle15npm12 open
suse sle15npm14 open
suse sle15npm16 open
suse sle15npm18 open
suse sle15npm20 open
suse sle15npm22 open
suse sle15npm24 open
suse sle15npm8 open
suse sle15trento-web open
▣
Scoring & Timeline
5.3
MEDIUM · CVSS v3.1 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Technical impact
partial
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
⚑
Vendor Advisories
11siemens-csafSSA-485750
suse-csafopenSUSE-SU-2026:20251-1
suse-csafSUSE-SU-2026:20540-1
suse-csafSUSE-SU-2026:20580-1
🔗
References & Sources
5Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
https://github.com/advisories/GHSA-mh29-5h37-fv8mVendor Advisory