[Aikido] Fix 9 security issues in lodash, uuid, @octokit/endpoint and 3 more - #22
Closed
aikido-autofix[bot] wants to merge 1 commit into
Closed
[Aikido] Fix 9 security issues in lodash, uuid, @octokit/endpoint and 3 more#22aikido-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 → #23 |
aikido-autofix
Bot
deleted the
fix/aikido-security-update-packages-82165193-3vqa
branch
August 7, 2026 02:15
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 any of the package upgrades affect this codebase:
lodash (4.17.21 => 4.18.1): The codebase only uses
_.filter()and_.merge()methods (insrc/gh.js). The breaking changes to_.unset(),_.omit(), and_.template()do not affect this code.uuid (8.3.2 => 11.1.1): The
uuidpackage is not used anywhere in the source code.@octokit packages: These are transitive dependencies through
@actions/githubv6.0.1, which already uses compatible versions (@octokit/core v5+, @octokit/plugin-paginate-rest v9+). The codebase:Does not configure custom HTTP agents
Does not pass custom request options beyond standard parameters (
method,headers,body)Runs on Node.js 24, which is fully supported by all upgraded package versions
All Node.js version requirements are satisfied as the action runs on Node.js 24 (specified in
action.yml).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, undici, and @octokit/* transitive chain
Short summary
This PR remediates security vulnerabilities in six packages identified in the initial task:
lodash,uuid,@octokit/endpoint,@octokit/plugin-paginate-rest,@octokit/request, and@octokit/request-error. A seventh vulnerable package,undici, was introduced as a new transitive dependency by the parent bumps required to fix the@octokit/*chain and was also remediated in the same pass. Changes touch the rootpackage.json(declared version specs for@actions/core,@actions/github, andlodash, plus one targetedoverridesentry) and the rootpackage-lock.json(all resolved transitive versions).lodash
lodashis a direct dependency declared in the rootpackage.json. Its spec was widened from^4.17.21to^4.18.1, causing npm to resolve the lockfile to4.18.1, which is the patched release. No parent chain traversal was needed.uuid
uuidappeared in two lockfile instances: one hoisted tonode_modules/uuid(pulled in by@actions/core@1.xat8.3.2) and one nested atnode_modules/aws-sdk/node_modules/uuid(pinned byaws-sdkat exactly8.0.0). The@actions/coreinstance was eliminated entirely by bumping@actions/coreto^2.0.0(see below), which drops theuuiddependency altogether. Theaws-sdkinstance has no fixing parent release across the entireaws-sdk@2.xpublished history—aws-sdkhard-pinsuuid@8.0.0in every release—so a targeted override"uuid@<11.1.1": "11.1.1"was added to the rootpackage.jsonas the only viable path for that instance.@octokit/endpoint
@octokit/endpointis a transitive dependency pulled in through the chain@actions/github→@octokit/core→@octokit/request→@octokit/endpoint. The installed version6.0.12is only reachable via@octokit/request@5.x; the patched floor is9.0.6. Bumping@actions/githubto^8.0.1in the rootpackage.jsonbrought in@octokit/core@7.xand@octokit/request@10.x, which resolves@octokit/endpointto11.0.4—well above the patched minimum.@octokit/plugin-paginate-rest
@octokit/plugin-paginate-restis a transitive dependency of@actions/github. The installed version2.21.3is below the patched floor of9.2.2. Bumping@actions/githubto^8.0.1in the rootpackage.jsonresolves@octokit/plugin-paginate-restto14.0.0, satisfying the patched requirement. The same parent bump that fixed the@octokit/endpointchain covers this package.@octokit/request
@octokit/requestis a transitive dependency reachable via@actions/github→@octokit/core/@octokit/graphql. The installed version5.6.3is below the patched floor of8.4.1. Bumping@actions/githubto^8.0.1pulls in@octokit/core@7.xand@octokit/graphql@9.x, both of which declare@octokit/request@^10.x, resolving to10.0.13in the lockfile.@octokit/request-error
@octokit/request-erroris a transitive dependency pulled in by@octokit/coreand@octokit/request. The installed version2.1.0is below the patched floor of5.1.1. The same@actions/githubbump to^8.0.1that fixed the broader@octokit/*chain resolves@octokit/request-errorto7.1.1via@octokit/core@7.xand@octokit/request@10.x.undici
undiciwas not in the original task but was introduced as a new transitive vulnerability when@actions/githubwas bumped from^4.0.0to^6.0.0(required for the@octokit/*fixes):@actions/github@6.xpulls in@actions/http-client@2.x→undici@5.29.0, which is below the patched floor of6.28.0for all twelve reported CVEs. Fixing this required walking the full parent chain:@actions/http-client@2.xhas no fixing release below3.0.2(a major bump), and@actions/core@1.xpins@actions/http-client@^2.x. Bumping@actions/coreto^2.0.0in the rootpackage.jsonwas therefore necessary—@actions/core@2.xdeclares@actions/http-client@^3.0.0, which in turn declaresundici@^6.23.0, resolving to6.28.0in the lockfile and covering all reported CVEs.Version changes
lodash^4.17.21→4.17.21^4.18.1→4.18.1@actions/core^1.10.0→1.10.0^2.0.0→2.0.3undici(dropsuuid, upgrades@actions/http-clientto v3)@actions/github^4.0.0→4.0.0^8.0.1→8.0.1@octokit/endpoint,@octokit/plugin-paginate-rest,@octokit/request,@octokit/request-erroruuid8.3.2(hoisted) /8.0.0(nested inaws-sdk)11.1.1(single instance, override)aws-sdkpath); hoisted instance eliminated by@actions/corebumpundici5.29.06.28.0@actions/core→@actions/http-client@3.x)@actions/http-client2.2.33.0.2@actions/corebump; required to resolveundici@^6.23.0@octokit/core3.6.07.0.7@actions/githubbump@octokit/endpoint6.0.1211.0.4@actions/githubbump@octokit/graphql4.8.09.0.4@actions/githubbump@octokit/plugin-paginate-rest2.21.314.0.0@actions/githubbump@octokit/plugin-rest-endpoint-methods4.15.110.4.1@actions/githubbump@octokit/request5.6.310.0.13@actions/githubbump@octokit/request-error2.1.07.1.1@actions/githubbump