CVE-2026-134756

Portainer 2.39.0 before 2.45.1 SSRF via Multiple Outbound-Request Features

Published Nov 22, 2026 CVSS 4.0 · 5.3 Medium EPSS n/a KEV · Not listed
Description
Portainer Community Edition and Business Edition 2.39.0 before 2.45.1 contain a server-side request forgery vulnerability because user-supplied URLs are only syntax-checked by validate.IsURL without resolved address validation. Authenticated users can abuse Git cloning, Helm retrieval, registry ping, or the GitLab proxy to reach loopback, internal, and cloud metadata addresses, probing ports and reading responses.

Analysis

AI-generated

Technical impact

Portainer Community and Business Editions between 2.39.0 and 2.44.x allow authenticated users to supply URLs that are only syntax‑checked, enabling the server to reach arbitrary internal or cloud‑metadata endpoints. The resulting SSRF lets an attacker probe ports, read responses, and potentially extract sensitive data or interact with other services from within the host. This flaw aligns with CWE‑918 and poses a moderate risk to confidentiality and integrity when exploited.

Affected Systems

Portainer Community Edition and Business Edition versions 2.39.0 through 2.44.x are affected. The vulnerability exists in all releases that precede 2.45.1, which introduced the fix.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity, and the EPSS score is not provided, so the exploitation probability is unknown. The flaw is not listed in CISA KEV. The likely attack vector requires an authenticated session to one of multiple endpoints that accept a user‑supplied URL (e.g., Git clone, Helm chart retrieval, registry ping, or GitLab proxy). Once authenticated, an attacker can craft a request that forces the server to resolve and connect to internal addresses, loopback or cloud‑metadata services, and capture the returned data.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Portainer to version 2.45.1 or later, which removes the vulnerability by properly validating URL target addresses.
  • If immediate update is not possible, disable the features that accept external URLs (Git repositories, Helm charts, registry ping, GitLab proxy) or restrict them to trusted users through role‑based access controls.
  • Configure outbound network filtering or firewall rules to block the Portainer process from connecting to internal network ranges or cloud‑metadata endpoints, thereby mitigating the impact of any remaining SSRF exposure.

Generated by OpenCVE AI on November 22, 2026 at 15:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description Portainer Community Edition and Business Edition 2.39.0 before 2.45.1 contain a server-side request forgery vulnerability because user-supplied URLs are only syntax-checked by validate.IsURL without resolved address validation. Authenticated users can abuse Git cloning, Helm retrieval, registry ping, or the GitLab proxy to reach loopback, internal, and cloud metadata addresses, probing ports and reading responses.
Title Portainer 2.39.0 before 2.45.1 SSRF via Multiple Outbound-Request Features
First Time appeared Portainer
Portainer portainer
Weaknesses CWE-918
CPEs cpe:2.3:a:portainer:portainer:*:*:*:*:*:*:*:*
Vendors & Products Portainer
Portainer portainer
References
Metrics cvssV3_1

{'score': 5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N'}

cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 22, 2026, 2:16 PM
Reserved
Nov 22, 2026, 1:48 PM
Status
Received
Published
Nov 22, 2026, 3:17 PM
Modified
Nov 22, 2026, 3:17 PM