Skip to content

chore(deps): update dependency js-yaml to v4.1.1 [security]#42

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-js-yaml-vulnerability
Open

chore(deps): update dependency js-yaml to v4.1.1 [security]#42
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-js-yaml-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Nov 14, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
js-yaml 4.1.04.1.1 age confidence

js-yaml has prototype pollution in merge (<<)

CVE-2025-64718 / GHSA-mh29-5h37-fv8m

More information

Details

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

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

nodeca/js-yaml (js-yaml)

v4.1.1

Compare Source

Security
  • Fix prototype pollution issue in yaml merge (<<) operator.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@changeset-bot

changeset-bot Bot commented Nov 14, 2025

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: f749904

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Nov 14, 2025

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review

Comment @coderabbitai help to get the list of available commands and usage tips.

@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 7756991 to ce6774b Compare November 18, 2025 12:05
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from ce6774b to 3b87187 Compare December 3, 2025 19:29
@socket-security

socket-security Bot commented Dec 3, 2025

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Protestware or unwanted behavior: npm es5-ext

Note: The script attempts to run a local post-install script, which could potentially contain malicious code. The error handling suggests that it is designed to fail silently, which is a common tactic in malicious scripts.

From: pnpm-lock.yamlnpm/@1stg/app-config@4.1.3npm/es5-ext@0.10.64

ℹ Read more on: This package | This alert | What is protestware?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Consider that consuming this package may come along with functionality unrelated to its primary purpose.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es5-ext@0.10.64. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch 2 times, most recently from 7b2728d to 23c963f Compare December 31, 2025 19:09
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 23c963f to 6dd28ea Compare January 8, 2026 17:36
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch 2 times, most recently from c4b5c72 to 7dcfc5a Compare January 23, 2026 19:50
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 7dcfc5a to d81c3a8 Compare February 2, 2026 17:41
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch 2 times, most recently from e87d062 to da84d19 Compare February 17, 2026 16:10
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from da84d19 to bf78331 Compare March 5, 2026 15:46
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from bf78331 to 34c38a2 Compare March 13, 2026 11:13
@renovate renovate Bot changed the title chore(deps): update dependency js-yaml to v4.1.1 [security] chore(deps): update dependency js-yaml to v4.1.1 [security] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-js-yaml-vulnerability branch March 27, 2026 00:47
@renovate renovate Bot changed the title chore(deps): update dependency js-yaml to v4.1.1 [security] - autoclosed chore(deps): update dependency js-yaml to v4.1.1 [security] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch 3 times, most recently from 68cd39f to 65cfb02 Compare April 1, 2026 20:06
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 65cfb02 to 57753bc Compare April 8, 2026 20:59
@renovate renovate Bot changed the title chore(deps): update dependency js-yaml to v4.1.1 [security] chore(deps): update dependency js-yaml to v4.1.1 [security] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title chore(deps): update dependency js-yaml to v4.1.1 [security] - autoclosed chore(deps): update dependency js-yaml to v4.1.1 [security] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch 2 times, most recently from 57753bc to a1e1905 Compare April 27, 2026 23:06
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from a1e1905 to a474ad4 Compare April 29, 2026 12:56
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch 2 times, most recently from 7960d95 to 75fbaff Compare May 18, 2026 09:39
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch 2 times, most recently from c09e033 to 46e1b84 Compare June 1, 2026 19:06
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 46e1b84 to 2bce3ba Compare June 13, 2026 15:49
@socket-security

socket-security Bot commented Jun 13, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedjs-yaml@​4.1.0 ⏵ 4.1.1100 +183 +2100 +192100

View full report

@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 2bce3ba to 5c69572 Compare June 16, 2026 23:04
@renovate renovate Bot changed the title chore(deps): update dependency js-yaml to v4.1.1 [security] chore(deps): update dependency js-yaml to v4.2.0 [security] Jun 16, 2026
@renovate renovate Bot changed the title chore(deps): update dependency js-yaml to v4.2.0 [security] chore(deps): update dependency js-yaml to v4.1.1 [security] Jun 29, 2026
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from 5c69572 to fa930c0 Compare June 29, 2026 19:44
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch 2 times, most recently from 8656eda to a5df0a1 Compare July 16, 2026 16:15
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from a5df0a1 to c4c4e21 Compare July 20, 2026 22:35
@renovate
renovate Bot force-pushed the renovate/npm-js-yaml-vulnerability branch from c4c4e21 to f749904 Compare July 24, 2026 19:37
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.

0 participants