Quick answers
- Is CVE-2026-59681 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59681 being exploited in the wild.
- How severe is CVE-2026-59681?
- High severity, with a CVSS score of 8.8, published 1 September 2026.
- Which products and versions are affected?
- Suse YaST2 auth-client <UNKNOWN>.
- Is there a fix for CVE-2026-59681?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-59681 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-59681?
- Check whether you run Suse YaST2 auth-client at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an OS command injection flaw in the Auth::AuthConf component (src/lib/auth/authconf.rb) in yast2-auth-client. The code assembles Samba net ads join, net ads lookup, and net ads testjoin commands by directly interpolating unvalidated and unquoted user-controlled configuration values (organizational unit, DNS hostname, AD username, AD domain name) into a shell command string, then passes it to Ruby's Open3.popen2 or Open3.capture2 functions which execute it through /bin/sh. An attacker controlling these Active Directory configuration values can inject shell metacharacters to break out of the intended command and execute arbitrary code. No input validation or shell escaping is performed on the interpolated values. The attack requires ability to modify Active Directory configuration, and successful exploitation results in arbitrary command execution as root.
Affected products
- SUSE YaST2 auth-client <UNKNOWN>
Timeline
- 2026-09-01: disclosed