# SUSE-SU-2026:23592-1: Security update for wicked2nm


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 1 Sep 2026

## What is SUSE-SU-2026:23592-1?

SUSE-SU-2026:23592-1 is a vulnerability in wicked2nm, published on 1 Sep 2026. 

### Official description

This update for wicked2nm fixes the following issue:

Update to v1.5.2.

Security issues fixed:

- `serde_with`: `KeyValueMap` serialization panics on empty sequence or map entries (bsc#1271848).

Other updates and bugfixes:

* Build(deps): bump `serde_with` from 3.18.0 to 3.21.0.
* Fix flaky tests.
* Fix `team_lacp_ethtool` test by setting `lacp active` explicitly.

## Which versions are affected by SUSE-SU-2026:23592-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wicked2nm` | SUSE:Linux Enterprise Server 16.0 | All versions | 1.5.2-160000.1.1 |
| `wicked2nm` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 1.5.2-160000.1.1 |

## How do I fix SUSE-SU-2026:23592-1?

Upgrade to a fixed version.

## Is SUSE-SU-2026:23592-1 being exploited?

There is no known exploitation of SUSE-SU-2026:23592-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2026:23592-1 and fix it if it is affected.

What it is: SUSE-SU-2026:23592-1 is a vulnerability in wicked2nm, published on 1 Sep 2026. 
Exploitation: There is no known exploitation of SUSE-SU-2026:23592-1 in the wild and no public exploit code.

Affected product: wicked2nm. 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/SUSE-SU-2026-23592-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-23592-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2026:23592-1

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