CVE-2026-41526
Shell Injection Vulnerability in KDE KCoreAddons KShell::quoteArgs
Publication date: 2026-04-28
Last updated on: 2026-05-05
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| kde | kcoreaddons | to 6.25.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-150 | The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as escape, meta, or control character sequences when they are sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in KDE KCoreAddons before version 6.25 involves the function KShell::quoteArgs, which is designed to safely quote arguments for shell commands. However, it does not properly handle certain metacharacters, allowing an attacker to escape the intended quoting.
Specifically, when applications use sendInput() to send strings to a terminal, control characters like \x01 can be injected. This breaks out of the single-quoted context that KShell::quoteArgs assumes is safe, enabling an attacker to inject additional shell commands.
This means that any KDE application relying on this method in security-critical paths to handle user input, such as Dolphin and Kate with embedded terminals, can be exploited to execute arbitrary commands.
How can this vulnerability impact me? :
This vulnerability can lead to command injection attacks where an attacker crafts input that, when processed by affected KDE applications, executes arbitrary shell commands with the privileges of the user running the application.
If a user pastes or opens manipulated content in applications like Dolphin or Kate that use the vulnerable functions, the attacker can run unintended commands, potentially compromising the user's system.
There is no available workaround, so the only mitigation is to update KCoreAddons to version 6.25 or later or apply the provided patch.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability affects KDE applications that use the function sendInput() combined with KShell::quoteArg() to pass user input to shell commands, especially in embedded terminals such as those in Dolphin and Kate.
Detection involves monitoring for suspicious input containing control characters like \x01 that could break out of single-quoted contexts and inject shell metacharacters.
Since the vulnerability arises when user input is passed to the terminal via sendInput(), you can look for unusual or unexpected control characters in terminal input or logs.
No specific detection commands are provided in the resources, but you might consider using tools or scripts to scan for control characters in input streams or logs related to KDE applications using embedded terminals.
What immediate steps should I take to mitigate this vulnerability?
There is no workaround available for this vulnerability.
The immediate mitigation step is to update KCoreAddons to version 6.25 or later, where the issue is fixed.
Alternatively, you can apply the patch available at https://invent.kde.org/frameworks/kcoreaddons/-/commit/6153c9ae025fa570174bb4a143df38fa2f46606b.
Until the update or patch is applied, avoid using KDE applications that rely on sendInput() with untrusted user input in embedded terminals.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in KDE KCoreAddons allows attackers to inject arbitrary shell commands by exploiting inadequate handling of shell metacharacters in user input. This can lead to unauthorized command execution with the user's privileges.
Such unauthorized command execution could potentially lead to unauthorized access, data breaches, or manipulation of sensitive information, which may violate compliance requirements under standards like GDPR or HIPAA that mandate protection of personal and sensitive data.
However, the provided information does not explicitly discuss or analyze the impact of this vulnerability on compliance with specific regulations such as GDPR or HIPAA.