Medium, CVSS 6.1npmAmendedPublished
CommandKit has incorrect command name exposure in context object for message command aliases
CVE-2025-62378 · GHSA-fhwm-pc6r-4h2f
- Affected
- npm commandkit >= 1.2.0-rc.1, <= 1.2.0-rc.11
- Fixed in
- 1.2.0-rc.12· Vendor fix available
- Issue
- 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…
Recommended action: Upgrade to 1.2.0-rc.12 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.