🛡️ openSUSE-SU-2026:20949-1 — wicked (CVE-2026-44932)
Description
Security update for wicked
This update for wicked fixes the following issues:
Changes in wicked:
- Update to version 0.6.79
- Fix an indirect remote shell command injection via unsanitized
dhcp strings and leaseinfo dump (bsc#1265221,CVE-2026-44932):
- Fix to escape single-quotes in leaseinfo dump output used by the
wicked test dhcp4 and wicked test dhcp6 and written to the
/run/wicked/leaseinfo.* files, e.g. to pass them to netconfig.
A netconfig modify filtered for strict key='value' lines without
any escaped quotes and discarded these lines already before.
- Fix posix-tz-dbname and tz-string option processing checks to
permit only valid characters according to RFC4833.
- Discard string values containing single-quotes in other options.
- Trigger to regenerate initrd that may contain wicked binaries on
updates from wicked versions <= 0.6.78.
Affected software
openSUSE-SU-2026:20949-1 is recorded against 1 package.
- wicked (fixed in 0.6.79-bp160.1.1)
Timeline and source
Published on 12 June 2026 and last revised on 13 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| wicked | — | 0.6.79-bp160.1.1 |
References
Similar Threats
- Unknown openSUSE-SU-2026:11018-1
- Unknown SUSE-SU-2026:2349-1
- Unknown SUSE-SU-2026:2350-1
- Unknown SUSE-SU-2026:2353-1
- Unknown SUSE-SU-2026:2354-1
Free Vulnerability Check
Is your site affected by openSUSE-SU-2026:20949-1?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against openSUSE-SU-2026:20949-1 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.