Deserialization of Untrusted Data Affecting podman-fips package, versions <5.8.2-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.07% (22nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Deserialization of Untrusted Data vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-PODMANFIPS-16965384
  • published28 May 2026
  • disclosed22 May 2026

Introduced: 22 May 2026

NewCVE-2026-39832  (opens in a new tab)
CWE-502  (opens in a new tab)

How to fix?

Upgrade Chainguard podman-fips to version 5.8.2-r3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream podman-fips package and not the podman-fips package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

When adding a key to a remote agent constraint extensions such as restrict-destination-v00@openssh.com were not serialized in the request. Destination restrictions were silently stripped when forwarding keys, allowing unrestricted use of the key on the remote host. The client now serializes all constraint extensions. Additionally, the in-memory keyring returned by NewKeyring() now rejects keys with unsupported constraint extensions instead of silently ignoring them.