[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 affect this codebase.

The lodash upgrade's breaking changes to _.unset, _.omit, and _.template do not impact the code, which only uses _.filter() and _.merge(). The uuid package is not used in the source code. The @octokit packages are transitive dependencies accessed only through @actions/github's getOctokit() method, and the codebase does not use any of the deprecated features (HTTP agents, custom request options, or removed API endpoints). The action runs on Node.js 24, which satisfies all 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, @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). Changes touch the root package.json (four declared dependency version specs updated, one overrides entry added) and package-lock.json (lockfile refreshed to reflect all resolved version changes).

---

lodash

lodash is a direct dependency declared in the root package.json. Its declared spec was widened from ^4.17.21 to ^4.18.1, and the lockfile resolves it to 4.18.1. The bump was necessary because all three lodash CVEs require a minimum of 4.18.1 to be patched.

uuid

uuid appears as a transitive dependency pulled in by two parents: @actions/core (resolved away entirely after its parent bump) and aws-sdk (which exact-pins uuid@8.0.0 and has no upstream release that upgrades it). For the aws-sdk path, no parent bump was possible across the entire aws-sdk@2.x line, so a targeted overrides entry ("uuid@<11.1.1": "11.1.1") was added to the root package.json as a last resort, forcing the nested copy to the patched 11.1.1.

@octokit/endpoint

@octokit/endpoint is a transitive dependency; its immediate parent in the lockfile is @octokit/request. Fixing it required bumping @actions/github (a direct dependency) from ^4.0.0 to ^8.0.1, which pulls in a new major of @octokit/request (^10.x) that in turn depends on @octokit/endpoint@^11.x — well above the patched floor of 9.0.6. No direct manifest entry for @octokit/endpoint exists or was needed.

@octokit/plugin-paginate-rest

@octokit/plugin-paginate-rest is a transitive dependency whose immediate parent is @actions/github. Bumping @actions/github from ^4.0.0 to ^8.0.1 in the root package.json was required because @actions/github@4.x–7.x all resolve @octokit/plugin-paginate-rest below the patched floor of 9.2.2; @actions/github@8.0.1 resolves it to 14.0.0.

@octokit/request

@octokit/request is a transitive dependency pulled in through @actions/github → @octokit/core and @octokit/graphql. Bumping @actions/github to ^8.0.1 was necessary because that version brings in @octokit/core@^7.x and @octokit/graphql@^9.x, both of which depend on @octokit/request@^10.x — above the patched floor of 8.4.1. The lockfile resolves to 10.0.11.

@octokit/request-error

@octokit/request-error is a transitive dependency whose parents are @octokit/core and @octokit/request. Both of those packages were themselves upgraded as a consequence of bumping @actions/github to ^8.0.1; the new versions of @octokit/core (^7.x) and @octokit/request (^10.x) depend on @octokit/request-error@^7.x, which is above the patched floor of 5.1.1. The lockfile resolves to 7.1.0.

undici

undici was not in the original task but was introduced as a new vulnerable transitive at 5.29.0 by the @actions/github bump to ^6.0.0 (round 1). It is pulled in via two paths: @actions/github → undici directly, and @actions/core → @actions/http-client → undici. Fixing the first path required bumping @actions/github further to ^8.0.1 (the first version that depends on undici@^6.23.0, resolving to 6.28.0 ≥ the patched floor of 6.24.0). Fixing the second path required bumping @actions/core from ^1.11.0 to ^2.0.0 in the root package.json, because @actions/core@2.x is the first major that depends on @actions/http-client@^3.x, which in turn depends on undici@^6.23.0. After both bumps, the two previously separate undici instances collapsed into a single shared copy at 6.28.0.

---

Version changes

Package	From	To	Why updated
lodash	^4.17.21 (resolved 4.17.21)	^4.18.1 (resolved 4.18.1)	Direct CVE fix
@actions/core	^1.10.0 (resolved 1.10.0)	^2.0.0 (resolved 2.0.3)	Parent bump required to fix undici via @actions/http-client
@actions/github	^4.0.0 (resolved 4.0.0)	^8.0.1 (resolved 8.0.1)	Parent bump required to fix @octokit/plugin-paginate-rest, @octokit/request, @octokit/request-error, @octokit/endpoint, and undici
uuid	8.3.2 + nested 8.0.0	11.1.1	Override (uuid@<11.1.1) — aws-sdk@2.x exact-pins 8.0.0 with no fixing parent
@octokit/endpoint	6.0.12	11.0.3	Transitive CVE fix after @actions/github parent bump
@octokit/plugin-paginate-rest	2.21.3	14.0.0	Transitive CVE fix after @actions/github parent bump
@octokit/request	5.6.3	10.0.11	Transitive CVE fix after @actions/github parent bump
@octokit/request-error	2.1.0	7.1.0	Transitive CVE fix after @actions/github parent bump
undici	5.29.0	6.28.0	Transitive CVE fix after @actions/github and @actions/core parent bumps
@actions/http-client	2.2.3	3.0.2	Transitive after @actions/core parent bump (required to reach undici@^6.x)
@octokit/core	3.6.0	7.0.6	Transitive after @actions/github parent bump
@octokit/graphql	4.8.0	9.0.3	Transitive after @actions/github parent bump