# CVE-2026-59680: yast2-users: OS command injection via LDAP-supplied shadowLastChange/shadowExpire attribute

> Administrators viewing user password settings in YaST can trigger root command execution via malicious LDAP attributes.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-qvch-9vjh-pr6p, SUSE-SU-2026:3945-1, SUSE-SU-2026:3946-1, SUSE-SU-2026:3947-1, SUSE-SU-2026:3948-1, SUSE-SU-2026:3949-1, openSUSE-SU-2026:11978-1

## What is CVE-2026-59680?

CVE-2026-59680 is a high-severity command injection vulnerability in SUSE yast2-users, published on 1 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An OS command injection vulnerability was found in yast2-users. When displaying the "Password Settings" tab of a user, get_password_term() in src/include/users/dialogs.rb read the shadowLastChange and shadowExpire fields with GetString(), which performs no numeric validation, and passed the resulting string to format_days_after_epoch(). That helper interpolated the value into a shell command executed via Ruby backticks without quoting or escaping.

Impact: an administrator who manages users against an external/federated LDAP directory via `yast2 users` triggers root command execution the moment they view or edit that particular user's "Password Settings" tab. No "join domain" or trust setup is required, just browsing/editing one user entry.

This issue affects yast2-users through 5.0.8.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-1287 (Improper Validation of Specified Type of Input)

## Which versions are affected by CVE-2026-59680?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `yast2-users` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 4.4.17-150400.3.21.1 |
| `yast2-users` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 4.4.17-150400.3.21.1 |
| `yast2-users` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 4.5.8-150500.3.11.1 |
| `yast2-users` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 4.5.8-150500.3.11.1 |
| `yast2-users` | SUSE:Linux Enterprise Installer Updates 15 SP4 | All versions | 4.4.17-150400.3.21.1 |
| `yast2-users` | SUSE:Linux Enterprise Installer Updates 15 SP7 | All versions | 4.7.2-150700.3.8.1 |
| `yast2-users` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 4.7.2-150700.3.8.1 |
| `yast2-users` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 3.2.20-3.3.1 |
| `yast2-users` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 4.4.17-150400.3.21.1 |
| `yast2-users` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 4.5.8-150500.3.11.1 |
| `yast2-users` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 4.6.7-150600.3.6.1 |
| `yast2-users` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 3.2.20-3.3.1 |
| `yast2-users` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 4.5.8-150500.3.11.1 |
| `yast2-users` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 4.6.7-150600.3.6.1 |
| `yast2-users` | openSUSE:Tumbleweed | All versions | 5.0.9-1.1 |

## How do I fix CVE-2026-59680?

Apply the vendor's patch.

## Is CVE-2026-59680 being exploited?

There is no known exploitation of CVE-2026-59680 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59680 and fix it if it is affected.

What it is: CVE-2026-59680 is a high-severity command injection vulnerability in SUSE yast2-users, published on 1 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-59680 in the wild and no public exploit code.

Affected product: SUSE yast2-users. 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-59680/ (Markdown: https://insights.sbomify.com/CVE-2026-59680/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59680
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59680
- OSV: https://osv.dev/vulnerability/CVE-2026-59680

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59680/
Summaries are generated and may contain mistakes; the official description above is the record.