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

> A panic in serde_with serialization can cause denial of service in wicked2nm, requiring a patch update.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Sep 2026

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

SUSE-SU-2026:4405-1 is a denial of service vulnerability in wicked2nm, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for wicked2nm fixes the following issue:

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

Changes for wicked2nm:

- Update v1.5.2.

- Update v1.5.1:
 * Update agama to fix default vlan flags (bsc#1271079).

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wicked2nm` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 1.5.2-150500.11.6.1 |
| `wicked2nm` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 1.5.2-150500.11.6.1 |
| `wicked2nm` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 1.5.2-150500.11.6.1 |
| `wicked2nm` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 1.5.2-150500.11.6.1 |

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2026:4405-1 is a denial of service vulnerability in wicked2nm, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2026:4405-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-4405-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-4405-1/index.md)
```

## Sources

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

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