Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Code Injection in js-yaml

GHSA-8j8c-7jfh-h6hx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (js-yaml 3.13.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm js-yaml

    Affected
    < 3.13.1
    Fixed in
    3.13.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-8j8c-7jfh-h6hx

  2. Revision 1 · created ·

    Published from osv record GHSA-8j8c-7jfh-h6hx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-8j8c-7jfh-h6hx

Advisory: Code Injection in js-yaml
IDs: GHSA-8j8c-7jfh-h6hx
Record: https://patchnext.com/advisories/ghsa-8j8c-7jfh-h6hx (revision 2, source checked 26 Oct 2026, 12:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: js-yaml 3.13.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm js-yaml: affected < 3.13.1; fixed in 3.13.1

## Suggested inspection (read-only)
- `npm ls js-yaml --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on js-yaml.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8j8c-7jfh-h6hx (OSV record GHSA-8j8c-7jfh-h6hx lists affected ranges: npm js-yaml >=0 <3.13.1 (fixed))
- Verified: https://github.com/advisories/GHSA-8j8c-7jfh-h6hx (GitHub-reviewed advisory GHSA-8j8c-7jfh-h6hx lists affected ranges: npm js-yaml >=0 <3.13.1)

Commands are suggestions: review each one before running it.

Loading voting…