Quick answers
- Is CVE-2026-44884 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44884 being exploited in the wild.
- How severe is CVE-2026-44884?
- Medium severity, with a CVSS score of 6.5, published 28 May 2026.
- Which products and versions are affected?
- github.com/portainer/portainer (Go) SEMVER:introduced=0, SEMVER:introduced=2.33.0,fixed=2.33.8; Portainer >= 2.33.0, < 2.33.8; >= 2.39.0, < 2.39.1; Portainer Community Edition 2.33.0 to 2.33.7, 2.39.0.
- Is there a fix for CVE-2026-44884?
- Yes. github.com/portainer/portainer (Go): upgrade to 2.33.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44884 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44884?
- Check whether you run github.com/portainer/portainer (Go), Portainer or Portainer Community Edition at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/portainer/portainer (Go): upgrade to 2.33.8 or later
go get github.com/portainer/portainer@v2.33.8
Technical details
A missing authorization check in the `customTemplateFile` handler within `api/http/handler/customtemplates/customtemplate_file.go` allows any authenticated user to access the `GET /api/custom_templates/{id}/file` endpoint. By enumerating sequential integer IDs, an attacker can bypass Resource Control restrictions to retrieve the verbatim file content of any custom template. These templates frequently contain Docker Compose configurations with embedded environment-specific secrets such as connection strings and registry credentials. The vulnerability has been addressed in versions 2.33.8, 2.39.1, and 2.40.0.
Affected products
- Portainer Portainer >= 2.33.0, < 2.33.8; >= 2.39.0, < 2.39.1
Identifiers
- CVE-2026-44884
- GHSA-cqpq-2fgr-8mvc
- GO-2026-5333
Timeline
- 2026-02-11: disclosed: Reported via GitHub Security Advisory
- 2026-03-19: patched: Version 2.39.1 released with fix
- 2026-03-25: patched: Version 2.40.0 released with fix
- 2026-05-07: patched: Version 2.33.8 released with fix
- 2026-05-14: advisory: GHSA-cqpq-2fgr-8mvc published