← Back
CVE-2026-44883
high
CVSS 7.5
Vulnerability in github.com/portainer/portainer (CVE-2026-44883)
Summary
vulnerability in github.com/portainer/portainer (CVE-2026-44883). Successful exploitation can lead to full system takeover. Exploitable via ``Referer``. Mitigation: upgrade to `2.41.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44883** has been found in github.com/portainer/portainer.
Attackers can target a specific entry point like ``Referer`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade github.com/portainer/portainer to **2.41.0** or later.
If unsure, ask your IT team or search "github.com/portainer/portainer CVE-2026-44883" on the vendor's site.
CVE-2026-44883 (github.com/portainer/portainer) — CWE-598 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `Referer` / `token` / `extractBearerToken` / `Authorization`
Patched: `2.41.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-598) exists in github.com/portainer/portainer. Attackers reach the vulnerable code path via ``Referer`` without authentication.
📍 Affected scope
github.com/portainer/portainer — . Attack surface: `Referer` / `token` / `extractBearerToken` / `Authorization`.
🔥 Severity
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.41.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/portainer/portainer' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/portainer/portainer' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/portainer/portainer` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/portainer/portainer to 2.41.0ステージング環境で 2.41.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/portainer/portainer
[{"type":"SEMVER","events":[{"introduced":"2.40.0"},{"fixed":"2.41.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-44883
- package https://github.com/portainer/portainer
- web https://github.com/portainer/portainer/security/advisories/GHSA-jvp4-q659-95mj
- web https://github.com/portainer/portainer/releases/tag/2.33.8
- web https://github.com/portainer/portainer/releases/tag/2.39.2
- web https://github.com/portainer/portainer/releases/tag/2.41.0
- web https://github.com/advisories/GHSA-jvp4-q659-95mj