[Aikido] Fix 9 security issues in lodash, uuid, @octokit/endpoint and 3 more - #15
Closed
aikido-autofix[bot] wants to merge 1 commit into
Closed
[Aikido] Fix 9 security issues in lodash, uuid, @octokit/endpoint and 3 more#15aikido-autofix[bot] wants to merge 1 commit into
aikido-autofix[bot] wants to merge 1 commit into
Conversation
Author
|
Closed by Aikido: a new AutoFix has been created → #16 |
aikido-autofix
Bot
deleted the
fix/aikido-security-update-packages-39512577-irv8
branch
May 28, 2026 23:31
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.
Upgrade dependencies to fix critical RCE vulnerability in lodash template injection via options.imports and high-severity buffer overflow in uuid.
✅ No breaking changes from the package upgrades affect this codebase.
lodash (4.17.21 => 4.18.1):
The codebase only uses
_.filter()(line 12 insrc/gh.js) and_.merge()(line 44 insrc/gh.js)The breaking changes in lodash 4.18.0 only affect
_.unset(),_.omit(), and_.template(), which are not used in this codebaseuuid (8.3.2 => 11.1.1):
uuidpackage is not used anywhere in the source code@octokit packages:
These packages are consumed indirectly through
@actions/githubv6.0.1, which already bundles the upgraded versions (@octokit/endpoint9.0.6,@octokit/plugin-paginate-rest9.2.2,@octokit/request8.4.1,@octokit/request-error5.1.1)The action uses Node.js 24 runtime (
node24inaction.yml), which satisfies all Node.js version requirementsNo custom HTTP agents or custom request options are passed to octokit - only standard parameters like
method,headers, andbodyare usedThe breaking changes related to Node.js http(s) Agents and custom request options do not affect this codebase
All breaking changes by upgrading lodash from version 4.17.21 to 4.18.1 (CHANGELOG)
_.unset/_.omitnow blockconstructorandprototypeas non-terminal path keys unconditionally. Calls that previously returnedtrueand deleted the property now returnfalseand leave the target untouched._.templatenow throws"Invalid imports option passed into _.template"whenimportskeys contain forbidden identifier characters, which were previously allowed.All breaking changes by upgrading uuid from version 8.3.2 to 11.1.1 (CHANGELOG)
✅ 9 CVEs resolved by this upgrade, including 1 critical 🚨 CVE
This PR will resolve the following CVEs:
linkheaders, allowing attackers to cause denial of service through specially crafted requests.🤖 Remediation details
Fix security vulnerabilities in
lodash,uuid,@octokit/endpoint,@octokit/plugin-paginate-rest,@octokit/request, and@octokit/request-error; remediate newly introducedundicivulnerabilities as a result of parent-chain bumps. Changes touch the rootpackage.json(four direct-dependency spec updates and oneoverridesentry) andpackage-lock.json(lockfile refreshed to reflect all resolved version changes).lodash
lodashis a direct dependency declared in the rootpackage.json. Its spec was widened from^4.17.21to^4.18.1so that npm resolves it to4.18.1, the minimum patched release covering all three lodash advisories. No parent bump was required.uuid
uuidappeared as two transitive instances: one pulled by@actions/core@1.10.0(spec^8.3.2) and one nested underaws-sdk(exact-pinned at8.0.0). The@actions/coreinstance was eliminated by bumping that direct dependency to^1.11.0(the first release that dropsuuidentirely). Theaws-sdk-nested instance has no fixing parent version across any published release ofaws-sdk, so a targetedoverridesentry ("uuid@<11.1.1": "11.1.1") was added to the rootpackage.jsonas a last resort, resolving both instances to a singleuuid@11.1.1copy.@octokit/endpoint
@octokit/endpointis a transitive dependency pulled through@octokit/request. Fixing it required bumping@actions/githubfrom^4.0.0to^6.0.0(and later to^8.0.1), which brought in@octokit/core@^5and@octokit/request@^8;@octokit/request@8.xdeclares@octokit/endpoint@^9.0.0, allowing npm to resolve it to9.0.6(the minimum patched version). The intermediate@octokit/requestparent bump was the necessary vehicle for this fix.@octokit/plugin-paginate-rest
@octokit/plugin-paginate-restis a transitive dependency pulled by@actions/github. Bumping@actions/githubfrom^4.0.0to^6.0.0was the first fixing parent version, as@actions/github@6.xdeclares@octokit/plugin-paginate-rest@^9.0.0, which npm resolves to9.2.2(the minimum patched version). The subsequent bump to^8.0.1(forundici) resolved it further to14.0.0, which also satisfies the patched requirement.@octokit/request
@octokit/requestis a transitive dependency pulled by@octokit/coreand@octokit/graphql, both of which are themselves pulled by@actions/github. Bumping@actions/githubto^6.0.0brought@octokit/core@^5, whose^8.0.2range for@octokit/requestallows npm to resolve it to8.4.1(the minimum patched version). The@actions/githubparent bump was the necessary vehicle; no direct manifest entry for@octokit/requestwas needed.@octokit/request-error
@octokit/request-erroris a transitive dependency pulled by@octokit/coreand@octokit/request. Bumping@actions/githubto^6.0.0brought@octokit/core@^5, which declares@octokit/request-error@^5.0.0; npm resolves this to5.1.1(the minimum patched version). As with@octokit/request, the@actions/githubparent bump was the necessary and sufficient vehicle.undici
undiciwas not in the original task but was introduced as a new vulnerable transitive dependency by the@actions/githuband@actions/coreparent bumps performed to fix the octokit and uuid advisories. Two instances appeared at5.29.0: one via@actions/github@6.0.1and one via@actions/core@1.11.1→@actions/http-client@2.2.3. Fixing both required further parent bumps:@actions/githubwas raised to^8.0.1(the first version declaringundici@^6.23.0directly) and@actions/corewas raised to^2.0.0(the first version declaring@actions/http-client@^3.0.0, which in turn declaresundici@^6.23.0). Both changes are manifest edits in the rootpackage.json; npm resolves the single consolidatedundiciinstance to6.25.0, satisfying the≥6.24.0patched floor for all five undici advisories.Version changes
lodash^4.17.21/4.17.21^4.18.1/4.18.1uuid8.3.2+8.0.0(nested)11.1.1(single instance)@actions/core^1.10.0/1.10.0^2.0.0/2.0.3undicivia@actions/http-client@3.x@actions/github^4.0.0/4.0.0^8.0.1/8.0.1@octokit/plugin-paginate-rest,@octokit/request,@octokit/request-error,@octokit/endpoint, andundici@actions/http-client2.2.33.0.2@actions/core@2.x); bringsundici@^6.23.0undici5.29.06.25.0@actions/github@8.x,@actions/core@2.x)@octokit/endpoint6.0.1211.0.3@actions/github@8.x→@octokit/request@10.x)@octokit/plugin-paginate-rest2.21.314.0.0@actions/github@8.x)@octokit/request5.6.310.0.9@actions/github@8.x→@octokit/core@7.x)@octokit/request-error2.1.07.1.0@actions/github@8.x→@octokit/core@7.x)@octokit/core3.6.07.0.6@actions/github@8.x)@octokit/graphql4.8.09.0.3@actions/github@8.x)@octokit/plugin-rest-endpoint-methods17.0.0@actions/github@8.x)@octokit/types13.x@actions/github@8.x)