Server-Side Request Forgery (SSRF) Affecting podman-docker package, versions *


Severity

Recommended
0.0
medium
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
0.01% (3rd 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 Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CENTOS10-PODMANDOCKER-15123097
  • published28 Jan 2026
  • disclosed22 Jan 2026

Introduced: 22 Jan 2026

CVE-2026-24117  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

There is no fixed version for Centos:10 podman-docker.

NVD Description

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

Rekor is a software supply chain transparency log. In versions 1.4.3 and below, attackers can trigger SSRF to arbitrary internal services because /api/v1/index/retrieve supports retrieving a public key via user-provided URL. Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF. The issue has been fixed in version 1.5.0. To workaround this issue, disable the search endpoint with --enable_retrieve_api=false.

CVSS Base Scores

version 3.1