Skip to main content
VulnerabilityPublished

CVE-2026-134756: portainer · Server-Side Request Forgery (SSRF)

Affects portainerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.45.1 when convenient.

Data as of 22 Nov 2026, 14:25 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.05.3
CNA (VulnCheck)CVSS 3.15.0
Patch
Available – fixed in 2.45.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade portainer to 2.45.1.

Affected software

ProductAffectedFixed in
portainerportainerAffected
  • >=2.39.0 <2.45.1
Fixed in
  • 2.45.1
Goportainerpkg:golang/portainerOther threatsAffected
  • >=2.39.0 <2.45.1
Fixed in
  • 2.45.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Portainer to version 2.45.1 or later, where this SSRF vulnerability is fixed. No other mitigation or temporary workaround is indicated by the vendor advisory.

Description

Portainer Community Edition and Business Edition versions from 2.39.0 up to but not including 2.45.1 contain a server-side request forgery (SSRF) vulnerability. This flaw arises because user-supplied URLs are only checked for syntax without validating the resolved addresses. Authenticated users can exploit this to make the server send requests to internal, loopback, or cloud metadata addresses, potentially probing ports and reading responses. The issue is fixed in version 2.45.1.

References

Community reviews

Loading reviews…