GHSA-fhwm-pc6r-4h2f
MEDIUMGHSA-fhwm-pc6r-4h2f is a medium-severity (CVSS 6.1) CWE-706 vulnerability in commandkit. O3 Security confirms whether GHSA-fhwm-pc6r-4h2f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
CommandKit has incorrect command name exposure in context object for message command aliases
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
commandkitnpmDescription
Impact
A logic flaw exists in the message command handler of CommandKit that affects how the commandName property is exposed to both middleware functions and command execution contexts when handling command aliases. When a message command is invoked using an alias, the ctx.commandName value reflects the alias rather than the canonical command name. This occurs in both middleware functions and within the command’s own run function.
Although not explicitly documented, CommandKit’s examples and guidance around middleware usage implicitly convey that ctx.commandName represents the canonical command identifier. Middleware examples in the documentation consistently use ctx.commandName to reference the command being executed, and the documentation describes middleware as suitable for “logging, authentication, permission checks, or any other cross-cutting concerns.” As a result, developers reasonably expect ctx.commandName to return the canonical command name and may rely on it for security-sensitive logic.
Developers who assume ctx.commandName is canonical may introduce unintended behavior when relying on it for logic such as permission checks, rate limiting, or audit logging. This could allow unauthorized command execution or inaccurate access control decisions. Slash commands and context menu commands are not affected.
Patches
Fixed in v1.2.0-rc.12.
ctx.commandName now consistently returns the actual canonical command name, regardless of the alias used to invoke it.
Workaround
If upgrading isn't immediately possible:
- Use
ctx.command.data.command.namefor permission validations, or - Include all command aliases in your permission logic.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | commandkit | ≥ 1.2.0-rc.1&&< 1.2.0-rc.12 | 1.2.0-rc.12 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for commandkit. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update commandkit to 1.2.0-rc.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fhwm-pc6r-4h2f is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-fhwm-pc6r-4h2f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-fhwm-pc6r-4h2f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-fhwm-pc6r-4h2f in your dependencies?
O3 detects GHSA-fhwm-pc6r-4h2f across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.