fix(sec-auto): aikido Fix 13 security issues in undici, @fastify/busboy - #146
Closed
aikido-autofix[bot] wants to merge 1 commit into
Closed
fix(sec-auto): aikido Fix 13 security issues in undici, @fastify/busboy#146aikido-autofix[bot] wants to merge 1 commit into
aikido-autofix[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Closed by Aikido: a new AutoFix has been created → #147 |
aikido-autofix
Bot
deleted the
fix/SEC-AUTOFIX-update-packages-64822542-4ri2
branch
July 15, 2026 01:26
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.
AI AutoFix
These PRs will require human vetting and potentially some fixes to fully integrate with the codebase.
Upgrade undici and @fastify/busboy to fix HTTP request smuggling, WebSocket decompression DoS, and header parsing vulnerabilities.
✅ Code not affected by breaking changes.
✅ No breaking changes from the undici upgrade affect this codebase.
The codebase does not directly import or use undici. The package is only used as a transitive dependency through
@actions/github(version 8.0.1), which internally uses undici 6.27.0 (not the version being upgraded).Key findings:
No direct imports of undici in the source code (
src/directory)No usage of
throwOnErroroption in the codebaseNo usage of interceptors (searched for
interceptor,createRedirectInterceptor,kInterceptors)No usage of the deduplicate interceptor
The codebase requires Node.js >=24, which is well above the dropped Node.js v18 support in undici 7.0.0
The only "deduplicate" reference found is in application logic for deduplicating GitHub check runs by name, which is unrelated to undici's deduplicate interceptor
The undici upgrade would only affect this codebase if
@actions/githubor@actions/http-clientupgrade their undici dependency to version 7.x, which is a separate concern.All breaking changes by upgrading undici from version 5.29.0 to 6.27.0 (CHANGELOG)
✅ 13 CVEs resolved by this upgrade, including 1 critical 🚨 CVE
This PR will resolve the following CVEs:
undicilibrary are vulnerable to memory leaks. By making multiple fetch requests with the sameAbortSignal, undici adds event listeners without removing them, leading to excessive memory consumption.__proto__orconstructor, potentially influencing application behavior or enabling further attacks.__proto__,constructor, orprototypeinto internal objects, potentially modifying the prototype chain and influencing application behavior or enabling further attacks.🤖 Remediation details
Fix transitive
undiciand@fastify/busboyvulnerabilities via parent dependency bumpsShort summary
This PR remediates multiple critical, high, medium, and low severity vulnerabilities in the transitive dependencies
undiciand@fastify/busboy. Both packages entered the tree through the@actions/coreand@actions/githubdependency chains. Fixes are applied by bumping the two direct dependencies in the rootpackage.json, with the updated resolutions reflected inpackage-lock.json.undici
undiciwas resolved at5.29.0as a transitive dependency pulled in by two parent chains:@actions/github→@actions/http-client→undici, and@actions/core→@actions/http-client→undici. Version5.29.0is below the patched floor of6.27.0required to address all listed advisories. Becauseundiciis not a direct dependency, the fix required bumping both owning parents:@actions/githubwas raised from^6.0.0to^8.0.1(the first release declaringundici@^6.23.0, which resolves to≥6.27.0), and@actions/corewas raised from^1.10.1to^2.0.0(the first release declaring@actions/http-client@^3.0.0, which in turn declaresundici@^6.23.0). After both manifest edits and a lockfile refresh,undiciconsolidates to a single hoisted instance at6.27.0.@fastify/busboy
@fastify/busboywas resolved at2.1.1as a transitive dependency ofundici@5.29.0, which declared it as^2.0.0. Version2.1.1falls within the vulnerable range[1.0.0, 3.1.1]requiring a patched version of≥3.2.0. Because@fastify/busboyis not a direct dependency and its presence was entirely a consequence of the oldundici@5.xrequiring it, bumpingundicito6.27.0(via the parent bumps described above) removes@fastify/busboyfrom the dependency tree entirely —undici@6.xno longer depends on it.Version changes
@actions/core^1.10.1→1.11.1resolved^2.0.0→2.0.3resolved@actions/http-client@^3.0.0and transitively fixundici@actions/github^6.0.0→6.0.1resolved^8.0.1→8.0.1resolved@actions/http-client@^3.0.2and transitively fixundici@actions/http-client2.2.33.0.2@actions/coreand@actions/github); declaresundici@^6.23.0undici5.29.06.27.0@actions/coreand@actions/github@fastify/busboy2.1.1undici@6.xafter parent bumps