Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented May 28, 2023

This PR contains the following updates:

Package Change Age Confidence
js-yaml 3.10.03.14.2 age confidence

GitHub Vulnerability Alerts

GHSA-8j8c-7jfh-h6hx

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.

GHSA-2pr6-76vf-7546

Versions of js-yaml prior to 3.13.0 are vulnerable to Denial of Service. By parsing a carefully-crafted YAML file, the node process stalls and may exhaust system resources leading to a Denial of Service.

Recommendation

Upgrade to version 3.13.0.

CVE-2025-64718

Impact

In js-yaml 4.1.0, 4.0.0, and 3.14.1 and below, 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.

Patches

Problem is patched in js-yaml 4.1.1 and 3.14.2.

Workarounds

You 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).

References

https://cheatsheetseries.owasp.org/cheatsheets/Prototype_Pollution_Prevention_Cheat_Sheet.html


Release Notes

nodeca/js-yaml (js-yaml)

v3.14.2

Compare Source

Security
  • Backported v4.1.1 fix to v3

v3.14.1

Compare Source

Security
  • Fix possible code execution in (already unsafe) .load() (in &anchor).

v3.14.0

Compare Source

Changed
  • Support safe/loadAll(input, options) variant of call.
  • CI: drop outdated nodejs versions.
  • Dev deps bump.
Fixed
  • Quote = in plain scalars #​519.
  • Check the node type for !<?> tag in case user manually specifies it.
  • Verify that there are no null-bytes in input.
  • Fix wrong quote position when writing condensed flow, #​526.

v3.13.1

Compare Source

Security
  • Fix possible code execution in (already unsafe) .load(), #​480.

v3.13.0

Compare Source

Security
  • Security fix: safeLoad() can hang when arrays with nested refs
    used as key. Now throws exception for nested arrays. #​475.

v3.12.2

Compare Source

Fixed
  • Fix noArrayIndent option for root level, #​468.

v3.12.1

Compare Source

Added
  • Added noArrayIndent option, #​432.

v3.12.0

Compare Source

Changed
  • Support arrow functions without a block statement, #​421.

v3.11.0

Compare Source

Added
  • Add arrow functions suport for !!js/function.
Fixed
  • Fix dump in bin/octal/hex formats for negative integers, #​399.

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update dependency js-yaml to v3.13.1 [SECURITY] Update dependency js-yaml to v3.13.1 [SECURITY] - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/npm-js-yaml-vulnerability branch December 8, 2024 18:52
@renovate renovate bot changed the title Update dependency js-yaml to v3.13.1 [SECURITY] - autoclosed Update dependency js-yaml to v3.13.1 [SECURITY] Dec 8, 2024
@renovate renovate bot reopened this Dec 8, 2024
@renovate renovate bot force-pushed the renovate/npm-js-yaml-vulnerability branch from bec5dd0 to 7b096f7 Compare December 8, 2024 21:23
@renovate renovate bot changed the title Update dependency js-yaml to v3.13.1 [SECURITY] Update dependency js-yaml to v4 [SECURITY] Nov 16, 2025
@renovate renovate bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 7b096f7 to 5ab97ac Compare November 16, 2025 20:41
@renovate renovate bot changed the title Update dependency js-yaml to v4 [SECURITY] Update dependency js-yaml to v3.13.1 [SECURITY] Nov 18, 2025
@renovate renovate bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 5ab97ac to 2dda72d Compare November 18, 2025 03:35
@renovate renovate bot changed the title Update dependency js-yaml to v3.13.1 [SECURITY] Update dependency js-yaml to v3.14.2 [SECURITY] Nov 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant