Raw vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:HSummary
CVE-2026-7246 is a high-severity Command Injection (CWE-77) vulnerability in Palletsprojects Click. Its CVSS base score is 7.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-7246 is a command injection vulnerability (CWE-77) affecting Pallets Click versions 8.3.2 and below, specifically in the click.edit() function. This flaw enables attackers to execute arbitrary operating system commands. The vulnerability carries a CVSS v3.1 base score of 7.2 (AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H) and was published on 2026-04-30.
Exploitation requires local access (AV:L), high attack complexity (AC:H), elevated privileges (PR:H), and user interaction (UI:R). Despite the description noting execution from an unprivileged account, the CVSS metrics indicate high privileges are needed. Successful attacks can achieve high confidentiality, integrity, and availability impacts (C:I:A:H) with changed scope (S:C), potentially leading to full system compromise via arbitrary command execution.
Mitigation is addressed in the release of Click version 8.3.3, available at https://github.com/pallets/click/releases/tag/8.3.3. Additional details are provided in GitHub Security Advisories GHSA-47fr-3ffg-hgmw at https://github.com/tsigouris007/security-advisories/security/advisories/GHSA-47fr-3ffg-hgmw. Security practitioners should upgrade to the patched version and review the advisories for further guidance.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-26375
Vulnerability Data
Pallets Click, versions 8.3.2 and below, contain a command injection vulnerability in the click.edit() function, allowing attackers to pass arbitrary OS commands from an unprivileged account.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.3V1.2.5V1.2.8V1.2.9
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover command-construction flaws before deployment.
Input validation directly stops construction of commands from untrusted data containing special elements.
Least privilege reduces the permissions available to any process that could be subverted by injected commands.
Least functionality restricts available OS commands and interpreters, limiting the blast radius of injection.
Secure engineering principles include proper neutralization and safe command construction practices.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and neutralization that prevent command injection.
Runtime monitoring of software and data can detect anomalous command execution resulting from injection.
Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.
Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.
Security testing in development catches command-injection vulnerabilities before release.
Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.
Application security requirements explicitly call for controls against injection flaws including command injection.
Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.
Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.