CVE-2026-29955: n/a
The `/registercrd` endpoint in KubePlus 4.14 in the kubeconfiggenerator component is vulnerable to command injection. The component uses `subprocess.Popen()` with `shell=True` parameter to execute shell commands, and the user-supplied `chartName` parameter is directly concatenated into the command string without any sanitization or validation. An attacker can inject arbitrary shell commands by crafting a malicious `chartName` parameter value.
AI Analysis
Technical Summary
The /registercrd endpoint in KubePlus version 4.14, specifically within the kubeconfiggenerator component, is vulnerable to command injection (CWE-94). This occurs because the component executes shell commands using subprocess.Popen() with the shell=True parameter, and it directly concatenates the user-controlled chartName parameter into the command string without any input validation or sanitization. An attacker with low privileges can exploit this to inject and execute arbitrary shell commands on the underlying system. The vulnerability has a CVSS 3.1 base score of 8.8, indicating high severity with network attack vector, low attack complexity, no user interaction, and high impact on confidentiality, integrity, and availability. There is no information on affected versions beyond 4.14, no known exploits in the wild, and no vendor advisory or patch currently available.
Potential Impact
Successful exploitation allows an attacker with low privileges to execute arbitrary shell commands on the system hosting the vulnerable KubePlus component. This can lead to full compromise of confidentiality, integrity, and availability of the affected system. Given the high CVSS score (8.8), the impact is severe, potentially allowing remote code execution and system takeover.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid exposing the /registercrd endpoint to untrusted users and restrict access to trusted administrators only. Consider implementing input validation or filtering on the chartName parameter as a temporary mitigation if possible.
CVE-2026-29955: n/a
Description
The `/registercrd` endpoint in KubePlus 4.14 in the kubeconfiggenerator component is vulnerable to command injection. The component uses `subprocess.Popen()` with `shell=True` parameter to execute shell commands, and the user-supplied `chartName` parameter is directly concatenated into the command string without any sanitization or validation. An attacker can inject arbitrary shell commands by crafting a malicious `chartName` parameter value.
CVSS v3.1
Score 8.8high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The /registercrd endpoint in KubePlus version 4.14, specifically within the kubeconfiggenerator component, is vulnerable to command injection (CWE-94). This occurs because the component executes shell commands using subprocess.Popen() with the shell=True parameter, and it directly concatenates the user-controlled chartName parameter into the command string without any input validation or sanitization. An attacker with low privileges can exploit this to inject and execute arbitrary shell commands on the underlying system. The vulnerability has a CVSS 3.1 base score of 8.8, indicating high severity with network attack vector, low attack complexity, no user interaction, and high impact on confidentiality, integrity, and availability. There is no information on affected versions beyond 4.14, no known exploits in the wild, and no vendor advisory or patch currently available.
Potential Impact
Successful exploitation allows an attacker with low privileges to execute arbitrary shell commands on the system hosting the vulnerable KubePlus component. This can lead to full compromise of confidentiality, integrity, and availability of the affected system. Given the high CVSS score (8.8), the impact is severe, potentially allowing remote code execution and system takeover.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid exposing the /registercrd endpoint to untrusted users and restrict access to trusted administrators only. Consider implementing input validation or filtering on the chartName parameter as a temporary mitigation if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-03-04T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69dd369b82d89c981f37505e
Added to database: 4/13/2026, 6:31:55 PM
Last enriched: 4/21/2026, 6:04:38 AM
Last updated: 5/27/2026, 10:42:51 AM
Views: 57
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.