# CVE-2026-25706: yast2-samba-client: OS command injection via attacker-controlled Organizational Unit (Active Directory-supplied) > An attacker controlling Active Directory data can execute arbitrary commands as root on machines joining the domain via the SUSE YaST Samba client. - **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 1 Sep 2026 - **Updated:** 2 Sep 2026 - **Also known as:** GHSA-rjwh-46cm-g6mv, SUSE-SU-2026:3886-1, SUSE-SU-2026:3887-1, SUSE-SU-2026:3888-1, SUSE-SU-2026:3889-1, SUSE-SU-2026:3890-1, openSUSE-SU-2026:11762-1 ## What is CVE-2026-25706? CVE-2026-25706 is a high-severity command injection vulnerability in SUSE yast2-samba-client, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Improper neutralization of special elements used in an OS command in yast2-samba-client allows an attacker who controls the content of an Active Directory directory tree - a rogue domain controller, or a directory user delegated the right to create objects - to execute arbitrary commands as root on a machine being joined to that domain. This issue affects yast2-samba-client through 5.0.4. Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command) ## Which versions are affected by CVE-2026-25706? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `yast2-samba-client` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 4.4.5-150400.3.6.1 | | `yast2-samba-client` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 4.4.5-150400.3.6.1 | | `yast2-samba-client` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 4.5.4-150500.3.3.1 | | `yast2-samba-client` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 4.5.4-150500.3.3.1 | | `yast2-samba-client` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 4.7.2-150700.3.3.1 | | `yast2-samba-client` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 3.1.25-3.9.1 | | `yast2-samba-client` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 4.4.5-150400.3.6.1 | | `yast2-samba-client` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 4.5.4-150500.3.3.1 | | `yast2-samba-client` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 4.6.2-150600.3.3.1 | | `yast2-samba-client` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 3.1.25-3.9.1 | | `yast2-samba-client` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 4.4.5-150400.3.6.1 | | `yast2-samba-client` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 4.5.4-150500.3.3.1 | | `yast2-samba-client` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 4.6.2-150600.3.3.1 | | `yast2-samba-client` | openSUSE:Tumbleweed | All versions | 5.0.5-1.1 | ## How do I fix CVE-2026-25706? Apply the vendor's patch. ## Is CVE-2026-25706 being exploited? There is no known exploitation of CVE-2026-25706 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-25706 and fix it if it is affected. What it is: CVE-2026-25706 is a high-severity command injection vulnerability in SUSE yast2-samba-client, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-25706 in the wild and no public exploit code. Affected product: SUSE yast2-samba-client. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-25706/ (Markdown: https://insights.sbomify.com/CVE-2026-25706/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25706 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25706 - OSV: https://osv.dev/vulnerability/CVE-2026-25706 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-25706/ Summaries are generated and may contain mistakes; the official description above is the record.