How severe is GHSA-8j8c-7jfh-h6hx?

No CVSS score has been assigned to GHSA-8j8c-7jfh-h6hx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8j8c-7jfh-h6hx?

GHSA-8j8c-7jfh-h6hx affects the following packages: js-yaml (npm). Ecosystems affected: npm.

How do I fix GHSA-8j8c-7jfh-h6hx?

Update js-yaml to 3.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8j8c-7jfh-h6hx is resolved across your whole dependency graph.

How do I detect GHSA-8j8c-7jfh-h6hx in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for js-yaml. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-8j8c-7jfh-h6hx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-8j8c-7jfh-h6hx?

O3 pinpoints whether GHSA-8j8c-7jfh-h6hx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-8j8c-7jfh-h6hx actively exploited in the wild?

No public exploit code has been indexed for GHSA-8j8c-7jfh-h6hx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-8j8c-7jfh-h6hx published, and has it been updated?

GHSA-8j8c-7jfh-h6hx was published on June 4, 2019 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-8j8c-7jfh-h6hx

GHSA-8j8c-7jfh-h6hx is a remote code execution vulnerability in js-yaml. O3 Security confirms whether GHSA-8j8c-7jfh-h6hx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Code Injection in js-yaml

Published

Jun 4, 2019

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

js-yamlnpm

279.1Mdownloads / week

Description

Versions of js-yaml prior to 3.13.1 are vulnerable to Code Injection. The load() function may execute arbitrary code injected through a malicious YAML file. Objects that have toString as key, JavaScript code as value and are used as explicit mapping keys allow attackers to execute the supplied code through the load() function. The safeLoad() function is unaffected.

An example payload is { toString: !<tag:yaml.org,2002:js/function> 'function (){return Date.now()}' } : 1 which returns the object { "1553107949161": 1 }

Recommendation

Upgrade to version 3.13.1.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`js-yaml`	all versions	3.13.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for js-yaml. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update js-yaml to 3.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8j8c-7jfh-h6hx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8j8c-7jfh-h6hx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8j8c-7jfh-h6hx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `js-yaml` prior to 3.13.1 are vulnerable to Code Injection. The `load()` function may execute arbitrary code injected through a malicious YAML file. Objects that have `toString` as key, JavaScript code as value and are used as explicit mapping keys allow attackers to execute the supplied code through the `load()` function. The `safeLoad()` function is unaffected. An example payload is `{ toString: !<tag:yaml.org,2002:js/function> 'function (){return Date.now()}' } : 1` which returns the object { "1553107949161": 1 } ## Recommendation Upgrade to version 3.13.1.

O3 Security · Impact-Aware SCA

Is GHSA-8j8c-7jfh-h6hx in your dependencies?

O3 detects GHSA-8j8c-7jfh-h6hx across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works