[Aikido] Fix 9 security issues in lodash, uuid, @octokit/endpoint and 3 more

[aikido-autofix]

Upgrade dependencies to fix critical RCE vulnerability in lodash template injection via options.imports and high-severity buffer overflow in uuid.

⚠️ Incomplete breaking changes analysis (2/6 analyzed)

⚠️ Breaking changes analysis not available for: @octokit/endpoint, @octokit/plugin-paginate-rest, @octokit/request, @octokit/request-error

✅ No breaking changes from the package upgrades affect this codebase.

lodash (4.17.21 => 4.18.1): The codebase only uses _.filter() and _.merge() methods (in src/gh.js). The breaking changes to _.unset(), _.omit(), and _.template() do not affect this code.

uuid (8.3.2 => 11.1.1): The uuid package is not used anywhere in the source code.

@octokit packages: The codebase uses @actions/github v6.0.1, which abstracts the Octokit packages. The code only uses standard octokit.request() and octokit.paginate() calls without passing custom agents or advanced request options. The breaking changes related to Node.js http(s) Agents and custom request options do not affect this usage pattern. Additionally, the action runs on Node.js 24 (as specified in action.yml), which satisfies all Node.js version requirements.

All breaking changes by upgrading lodash from version 4.17.21 to 4.18.1 (CHANGELOG)

Version	Description
4.18.0	_.unset / _.omit now block constructor and prototype as non-terminal path keys unconditionally. Calls that previously returned true and deleted the property now return false and leave the target untouched.
4.18.0	_.template now throws "Invalid imports option passed into _.template" when imports keys contain forbidden identifier characters, which were previously allowed.

All breaking changes by upgrading uuid from version 8.3.2 to 11.1.1 (CHANGELOG)

Version	Description
9.0.0	Drop Node.js 10.x support
9.0.0	Remove the minified UMD build from the package
9.0.0	Drop IE 11 and Safari 10 support, remove msCrypto fallback, and no longer transpile browser build to ES2015
10.0.0	Drop Node.js 12 and 14 support, add Node.js 20 (update node support matrix to only support node 16-20)
11.0.0	Refactor v1 internal state and options logic
11.0.0	Refactor v7 internal state and options logic
11.0.0	Port to TypeScript
11.0.0	Update node support matrix (only support node 16-20)

✅ 9 CVEs resolved by this upgrade, including 1 critical 🚨 CVE

This PR will resolve the following CVEs:

Issue	Severity	Description
CVE-2026-4800	🚨 CRITICAL	[lodash] A vulnerability in _.template allows arbitrary code execution through untrusted key names in options.imports or prototype pollution, as validation was incomplete after a prior CVE fix. An attacker can inject malicious code that executes during template compilation.
CVE-2025-13465	MEDIUM	[lodash] A prototype pollution vulnerability in _.unset and _.omit functions allows attackers to delete methods from global prototypes via crafted paths. While this prevents property overwriting, it can cause denial of service by removing critical functionality.
CVE-2026-2950	MEDIUM	[lodash] Prototype pollution vulnerability in _.unset and _.omit functions allows attackers to bypass previous fixes using array-wrapped path segments, enabling deletion of properties from built-in prototypes. While this doesn't allow overwriting prototype behavior, it can cause denial of service or unexpected application behavior.
CVE-2026-41907	HIGH	[uuid] A buffer overflow vulnerability allows v3, v5, and v6 UUID functions to write beyond caller-provided buffer boundaries when given small buffers or large offsets, causing silent data corruption. This can lead to memory corruption and potential code execution or information disclosure.
AIKIDO-2026-10892	MEDIUM	[uuid] UUID functions v3(), v5(), and v6() can write past the end of a caller-provided buffer due to missing offset validation, enabling buffer overflow attacks. The fix adds bounds checks to prevent out-of-range writes.
AIKIDO-2025-10094	LOW	[@octokit/endpoint] Improper header parsing for GraphQL endpoints allows attackers to craft malicious inputs triggering ReDoS through excessive regex backtracking, causing denial of service and performance degradation.
CVE-2025-25288	LOW	[@octokit/plugin-paginate-rest] A ReDoS (Regular Expression Denial of Service) vulnerability exists in the pagination iterator when processing malicious link headers, allowing attackers to cause denial of service through specially crafted requests.
CVE-2025-25290	LOW	[@octokit/request] A ReDoS vulnerability in the link header parsing regex allows attackers to cause excessive CPU usage and service unavailability through specially crafted HTTP responses. The unbounded regex pattern is susceptible to catastrophic backtracking when processing malicious input.
CVE-2025-25289	LOW	[@octokit/request-error] A Regular Expression Denial of Service (ReDoS) vulnerability in HTTP header processing allows attackers to cause excessive resource consumption and DoS by sending malformed authorization headers with long space sequences. This can significantly degrade performance or crash services.

🤖 Remediation details

Fix security vulnerabilities in lodash, uuid, undici, and @octokit/* transitive dependencies

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 as a new transitive by the parent bumps required to fix the octokit chain). All fixes are applied via direct dependency version spec changes in the root package.json, one targeted overrides entry for a pinned transitive that cannot be reached by any parent bump, and a refreshed package-lock.json.

---

lodash

lodash is a direct dependency declared in the root package.json. Its version spec was raised from ^4.17.21 to ^4.18.1, resolving to 4.18.1 in the lockfile. This was necessary to satisfy the patched-version floor required by three separate advisories affecting the 4.17.x line.

uuid

uuid appears as a transitive dependency pulled in by two parents: @actions/core (which dropped uuid entirely in 1.11.0) and aws-sdk (which exact-pins uuid@8.0.0 and has no published release that upgrades or drops it). The @actions/core path was resolved by bumping that direct dependency; the aws-sdk path required an overrides entry ("uuid@<11.1.1": "11.1.1") because no version of aws-sdk on the registry ever resolves uuid to a patched release, making a parent bump impossible for that edge.

@octokit/endpoint

@octokit/endpoint is a transitive dependency pulled through @octokit/request. Bumping the direct dependency @actions/github to ^8.0.0 caused the entire octokit stack to resolve at a new major generation (@octokit/request@10.x), which in turn resolves @octokit/endpoint to 11.0.3—well above the 9.0.6 patched floor. No direct manifest entry for @octokit/endpoint was needed.

@octokit/plugin-paginate-rest

@octokit/plugin-paginate-rest is a transitive dependency pulled by @actions/github. The installed 4.0.0 release of @actions/github resolved it to 2.21.3, far below the 9.2.2 patched floor. Bumping @actions/github to ^8.0.0 resolves @octokit/plugin-paginate-rest to 14.0.0, satisfying the requirement.

@octokit/request

@octokit/request is a transitive dependency pulled by @octokit/core and @octokit/graphql, both of which are themselves pulled by @actions/github. The 4.0.0 generation of @actions/github pinned the entire octokit stack at major versions that resolved @octokit/request to 5.6.3, below the 8.4.1 patched floor. Bumping @actions/github to ^8.0.0 moves the whole stack to a new major generation, resolving @octokit/request to 10.0.10.

@octokit/request-error

@octokit/request-error is a transitive dependency pulled by @octokit/core and @octokit/request. The same root cause as @octokit/request applies: the old @actions/github@4.x generation pinned the octokit stack such that @octokit/request-error resolved to 2.1.0, below the 5.1.1 patched floor. Bumping @actions/github to ^8.0.0 resolves it to 7.1.0.

undici

undici was not present in the original lockfile but was introduced as a transitive dependency when @actions/github was moved to 6.x (required to fix the octokit chain). Both @actions/github@6.x and its nested @actions/http-client@2.x resolved undici to 5.29.0, which carries five advisories. Two parent bumps were required: @actions/github was raised further to ^8.0.0 (which carries undici ^6.23.0 directly and nests @actions/http-client@3.x), and @actions/core was raised to ^2.0.0 (the first release that depends on @actions/http-client@^3.0.0, which in turn carries undici ^6.23.0), eliminating the vulnerable 5.x instance entirely and resolving undici to 6.26.0.

---

Version changes

Package	From	To	Why updated
lodash	^4.17.21 / 4.17.21	^4.18.1 / 4.18.1	Direct CVE fix
@actions/core	^1.10.0 / 1.10.0	^2.0.0 / 2.0.3	Parent bump required to fix undici via @actions/http-client@3.x
@actions/github	^4.0.0 / 4.0.0	^8.0.0 / 8.0.1	Parent bump required to fix @octokit/* chain and undici
uuid	8.3.2 / 8.0.0 (two instances)	11.1.1 (one instance)	Override (uuid@<11.1.1) for aws-sdk-pinned instance; @actions/core bump dropped the other
undici	5.29.0 (introduced by @actions/github@6.x)	6.26.0	Transitive CVE fix after parent bumps (@actions/github@8.x, @actions/core@2.x)
@actions/http-client	2.2.3	3.0.2	Transitive after @actions/core@2.x parent bump; carries patched undici ^6.23.0
@octokit/endpoint	6.0.12	11.0.3	Transitive CVE fix after @actions/github@8.x parent bump
@octokit/plugin-paginate-rest	2.21.3	14.0.0	Transitive CVE fix after @actions/github@8.x parent bump
@octokit/request	5.6.3	10.0.10	Transitive CVE fix after @actions/github@8.x parent bump
@octokit/request-error	2.1.0	7.1.0	Transitive CVE fix after @actions/github@8.x parent bump
@octokit/core	3.6.0	7.0.6	Transitive after @actions/github@8.x parent bump
@octokit/graphql	4.8.0	9.0.3	Transitive after @actions/github@8.x parent bump
@octokit/plugin-rest-endpoint-methods	5.16.2	17.0.0	Transitive after @actions/github@8.x parent bump
@octokit/types	6.41.0	13.10.0	Transitive after @actions/github@8.x parent bump

[aikido-autofix]

Closed by Aikido: a new AutoFix has been created → #18