[Deps] fix js-yaml prototype pollution vulnerability (CVE-2024-6869) #358
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automated Security Fix
This PR updates js-yaml from 3.14.1 to 3.14.2 to address a moderate severity prototype pollution vulnerability.
Security Advisory
CVE: GHSA-mh29-5h37-fv8m
Severity: Moderate
CVSS Score: 5.3
Package: js-yaml (transitive dependency via @istanbuljs/load-nyc-config)
Affected Versions: < 3.14.2
Fixed Version: 3.14.2
Vulnerability Details
The vulnerability involves prototype pollution through the
mergefunction when using the<<merge operator in YAML files. While js-yaml is only used as a dev dependency for test coverage reporting in this project, patching this vulnerability follows security best practices.Changes
Files Changed:
package-lock.json(transitive dependency update)Verification
npm run build)npm test)Testing
Impact
✅ Low risk change: This is a patch-level update to a transitive dev dependency used only for test coverage reporting. The vulnerability does not affect production code or runtime behavior.
Generated by: Dependency Security Monitor Workflow
Detection Time: 2026-01-19T13:36:36Z
Source: npm audit