fix(deps): [release-2.8] bump yaml to ^2.8.3 (SNYK-JS-YAML-15765520)#2416
Merged
malinskibeniamin merged 1 commit intorelease-2.8from Apr 22, 2026
Merged
Conversation
yaml is reachable in frontend/src (rp-connect pipeline parsing, MCP
config, yaml-label-sync — 5+ direct imports), so this is a direct-dep
fix rather than a .snyk dismissal.
Before:
- yaml@2.7.0 (direct — vulnerable)
- yaml@2.6.1 (via vitest/ast-v8-to-istanbul chain — vulnerable)
- yaml@1.10.2 ×3 (via @emotion/css > babel-plugin-macros > cosmiconfig
— vulnerable even though dev/build-only)
After: all 5 resolve to yaml@2.8.3 via the single overrides/resolutions
entry. Snyk scan confirms 0 yaml findings post-fix.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Follow-up to PRs #2413 and #2414. Fixes
SNYK-JS-YAML-15765520(yaml Uncontrolled Recursion, medium) onrelease-2.8.Why direct-bump, not
.snykdismissal: unlike the undici / remix-run / hono / lodash findings already dismissed on this branch,yamlis reachable —frontend/srchas 5+ directimport ... from 'yaml'statements (rp-connect pipeline parsing, MCP server config, yaml label sync). The vulnerable parser is exercised, so the advisory is actionable.Before → After
Changes
Verification
Master
Master already resolves yaml to 2.8.3 (override present + lockfile aggregates all semver ranges to that version), so no master PR is required.
cc @redpanda-data/ux-console