Multiple Locks of a Critical Resource Affecting container-tools:rhel8/podman-gvproxy package, versions <3:4.4.1-27.module+el8.8.0+24545+b713e821.8


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.62% (46th 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 IDSNYK-RHEL8-CONTAINERTOOLS-18535982
  • published5 Aug 2026
  • disclosed8 Apr 2026

Introduced: 8 Apr 2026

CVE-2026-32283  (opens in a new tab)
CWE-764  (opens in a new tab)

How to fix?

Upgrade RHEL:8 container-tools:rhel8/podman-gvproxy to version 3:4.4.1-27.module+el8.8.0+24545+b713e821.8 or higher.
This issue was patched in RHSA-2026:49944.

NVD Description

Note: Versions mentioned in the description apply only to the upstream container-tools:rhel8/podman-gvproxy package and not the container-tools:rhel8/podman-gvproxy package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.

CVSS Base Scores

version 3.1