[Aikido] Fix 8 security issues in lodash, uuid, @octokit/endpoint and 3 more - #12
Closed
aikido-autofix[bot] wants to merge 1 commit into
Closed
[Aikido] Fix 8 security issues in lodash, uuid, @octokit/endpoint and 3 more#12aikido-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 → #13 |
aikido-autofix
Bot
deleted the
fix/aikido-security-update-packages-37940236-owt4
branch
May 22, 2026 23:46
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 and prototype pollution attacks in Octokit packages.
✅ No breaking changes from any of the package upgrades affect this codebase.
lodash: The codebase only uses
_.filter()and_.merge()methods. The breaking changes in lodash 4.18.x affect_.unset(),_.omit(), and_.template(), which are not used in this project.uuid: This package is not directly imported or used in the source code; it only appears as a transitive dependency.
@octokit packages: The action runs on Node.js 24 (specified in
action.yml), which satisfies all Node.js version requirements. The code uses the high-level@actions/githubwrapper and doesn't pass custom HTTP agents or non-standard request options. The removed OAuth Authorizations APIs and required workflow endpoints are not used in 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)
✅ 8 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, @octokit/request-error, and undici
Short summary
This PR remediates security vulnerabilities in seven npm packages: lodash, uuid, @octokit/endpoint, @octokit/plugin-paginate-rest, @octokit/request, @octokit/request-error, and undici (introduced transitively by the parent bumps required to fix the other packages). All fixes are applied via direct dependency version spec changes in the root
package.json, one targetedoverridesentry for a case where no parent bump was possible, and a correspondingpackage-lock.jsonrefresh.lodash
lodashis a direct dependency declared in the rootpackage.json. Its spec was raised from^4.17.21to^4.18.1, resolving to4.18.1in the lockfile. Version 4.18.1 is the minimum patched release that satisfies all three lodash advisories; no parent chain was involved.uuid
uuidappears as a transitive dependency in two places. The instance under@actions/corewas eliminated by bumping@actions/coreto^2.0.0(that major release dropped theuuiddependency entirely). The instance nested underaws-sdkcannot be fixed via a parent bump because no published version ofaws-sdkupgrades pastuuid@8.x; a targeted override"uuid@<11.1.1": "11.1.1"was added to the rootpackage.jsonto force that nested copy to the patched version.@octokit/endpoint
@octokit/endpointis a transitive dependency pulled in through the@actions/github→@octokit/requestchain. Bumping@actions/githubto^8.0.0brought in@octokit/request@^10.x, which depends on@octokit/endpoint@^11.x, resolving to11.0.3—well above the required minimum of9.0.6.@octokit/plugin-paginate-rest
@octokit/plugin-paginate-restis a transitive dependency of@actions/github. Bumping@actions/githubto^8.0.0resolved@octokit/plugin-paginate-restto14.0.0, which exceeds the required minimum of9.2.2.@octokit/request
@octokit/requestis a transitive dependency pulled in by@actions/github,@octokit/core, and@octokit/graphql. Bumping@actions/githubto^8.0.0caused all three importers to resolve@octokit/requestto10.0.9, which exceeds the required minimum of8.4.1.@octokit/request-error
@octokit/request-erroris a transitive dependency pulled in by@actions/github,@octokit/core, and@octokit/request. Bumping@actions/githubto^8.0.0resolved@octokit/request-errorto7.1.0across all importers, exceeding the required minimum of5.1.1.undici
undiciwas not in the original advisory list but was introduced as a vulnerable transitive dependency (5.29.0) when@actions/githubwas first bumped to^6.0.0, because that version's@actions/http-client@2.xdepends onundici@^5.x. Fixing this required two further major parent bumps:@actions/githubraised to^8.0.0(which directly depends onundici@^6.23.0) and@actions/coreraised to^2.0.0(which brings@actions/http-client@^3.0.2, also depending onundici@^6.23.0). Both bumps were necessary to eliminate the single remainingundici@5.29.0instance; the lockfile now resolves a singleundici@6.25.0.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.3uuidand fixundicivia@actions/http-client@3.x@actions/github^4.0.0→4.0.0^8.0.0→8.0.1@octokit/endpoint,@octokit/plugin-paginate-rest,@octokit/request,@octokit/request-error, andundiciuuid8.0.0/8.3.211.1.1aws-sdkinstance via override;@actions/coreinstance dropped by parent bump@octokit/endpoint6.0.1211.0.3@actions/githubparent bump@octokit/plugin-paginate-rest2.21.314.0.0@actions/githubparent bump@octokit/request5.6.310.0.9@actions/githubparent bump@octokit/request-error2.1.07.1.0@actions/githubparent bumpundici5.29.06.25.0@actions/githuband@actions/coreparent bumps@actions/http-client2.2.33.0.2@actions/coreand@actions/githubparent bumps (carries fixedundici@^6.23.0)@octokit/core3.6.07.0.6@actions/githubparent bump@octokit/graphql4.8.09.0.3@actions/githubparent bump@octokit/plugin-rest-endpoint-methods5.x17.x@actions/githubparent bump