chore(security): patch 13 Dependabot alerts#1568
Merged
Conversation
- Bump axios direct dep in forest-cloud to ^1.15.0 (GHSA 329) - Add yarn resolutions to cover transitive vulns: - axios ^1.15.0 (329, also pins nx's copy) - follow-redirects ^1.16.0 (328) - hono ^4.12.12 (318-322) - @hono/node-server ^1.19.13 (317) - langsmith ^0.5.18 (326) - lodash ^4.18.0 (323, 324) - lodash-es ^4.18.0 (312, 313) - Remove stale lerna/js-yaml and @lerna/create/js-yaml resolutions (pin 4.1.1 was incompatible with lockfile and ignored by yarn)
|
Coverage Impact This PR will not change total coverage. 🚦 See full report on Qlty Cloud »🛟 Help
|
arnaud-moncel
approved these changes
Apr 23, 2026
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
13 fixed, 0 ignored, 9 deferred, 7 resolutions added, 2 resolutions removed.
Fixed
axiosinpackages/forest-cloud/package.json^1.13.5→^1.15.0; plus rootaxiosresolution to also pin nx's transitive copyfollow-redirects^1.16.0(axios 1.15.2 still declaresfollow-redirects ^1.15.11, so resolution is still needed)langsmith^0.5.18(transitive via@langchain/coreand@langchain/classic)lodash^4.18.0(many parents — unconditional narrow-enough)hono^4.12.12(transitive via@modelcontextprotocol/sdk)@hono/node-server^1.19.13(transitive via@modelcontextprotocol/sdk)lodash-es^4.18.0(transitive via@qiwi/multi-semantic-release)Ignored
None. All eligible alerts were actionable.
Deferred
Nine alerts opened less than 7 days ago; deferred to the next run:
@fastify/express(critical) — created 2026-04-16hono(medium) — created 2026-04-16 (likely already closed by the hono bump here:4.12.14 >= 4.12.14; Dependabot will confirm on merge)@fastify/middie(high, critical) — created 2026-04-16langsmith(medium) — created 2026-04-16 (likely already closed:0.5.21 >= 0.5.19)axios(medium) — created 2026-04-17 (likely already closed:1.15.2 >= 1.15.0)Resolutions added
package.jsonaxios^1.15.0packages/forest-cloudappliedlerna > nx > axios@1.13.5is still vulnerablepackage.jsonfollow-redirects^1.16.0axiosbumped to 1.15.2; still declaresfollow-redirects ^1.15.11package.jsonlangsmith^0.5.18@langchain/core/langsmith+@langchain/classic/langsmith, but two parentspackage.jsonlodash^4.18.0package.jsonhono^4.12.12@modelcontextprotocol/sdk/honofirst — yarn 1 silently ignored the deeply-scoped key (hono stayed at 4.12.9 after install)package.json@hono/node-server^1.19.13package.jsonlodash-es^4.18.0@qiwi/multi-semantic-releasechain@qiwi/multi-semantic-release/**/lodash-esbut there's no other lodash-es anywhere, so scope is effectively the samepackage.jsonResolutions removed
package.jsonlerna/js-yaml:4.1.1Resolution field "js-yaml@4.1.1" is incompatible with requested version "js-yaml@4.1.0"and ignored the pin. Removing it leaves the lerna chain atjs-yaml@4.1.0(unchanged).package.json@lerna/create/js-yaml:4.1.1yarn install:js-yaml@4.1.0still resolves for the lerna chain, no change.Kept after audit (verified still active):
tar,lerna/**/glob,micromatch,semantic-release,qs. Removing any one of these caused a downgrade of some transitive copy below the pinned floor, or an install failure (semantic-release).Risks
forest-cloudfor HTTP calls to the Forest Admin API; those calls use a fixed base URL, so the header-injection vector is not exploitable here anyway — this is a defensive bump.toSSG(), repeated-slash middleware bypass inserveStatic. We don't usetoSSG(),serveStatic,getCookie,setCookie, oripRestriction()directly — hono is only pulled in by@modelcontextprotocol/sdkas an HTTP adapter. No behavior change expected for our usage.serveStaticbypass; not a code path we hit.__proto__guard in a lodashset()call. No public-API breakage. Used only inside@langchain/coretracing._.templatecode-injection and_.unset/_.omitprototype-pollution fixes. No API surface change.@qiwi/multi-semantic-release(dev-only tooling).None of the bumps touch peer-dep ranges that would ripple into neighbor packages.
Manual testing
Covered by CI.
Validation
✅ CI green — 24 checks passed, 3 skipped (release/publish gated on merge), 0 failures.