Non-destructive checker for CVE-2026-44848: Portainer missing authorization on Docker plugin endpoints
Non-destructive checker for CVE-2026-44848 / GHSA-rrmm-9v76-h3p4: missing authorization on Portainer's Docker plugin proxy endpoints.
The tool answers two questions:
/plugins/* operation?It deliberately does not pull, enable, disable, or modify any plugin. The live
probe calls POST /plugins/<nonexistent>/disable; a vulnerable instance proxies
that request to Docker, which replies 404 plugin not found, while a fixed
instance rejects it at the Portainer authorization layer with 403.
From the GitHub advisory / NVD:
| Affected | Fixed |
|---|---|
>= 2.33.0, < 2.33.8 | 2.33.8 |
>= 2.39.0, < 2.39.2 | 2.39.2 |
>= 2.40.0, < 2.41.0 | 2.41.0 |
A Portainer administrator cannot be used for the live probe: plugin management is allowed for administrators even on patched builds, so the response would be identical on both. The checker detects this and reports the result as inconclusive.
# Recommended: non-admin user with endpoint access
python3 check_portainer_cve_2026_44848.py \
--url https://portainer.example.com \
--username readonly-user \
--password 'secret'
# Self-signed TLS lab
python3 check_portainer_cve_2026_44848.py \
--url https://localhost:9444 --insecure \
--username readonly-user --password 'secret'
# Existing JWT / API credentials via environment (avoids shell history)
PORTAINER_TOKEN='...' python3 check_portainer_cve_2026_44848.py --url https://portainer.example.com
PORTAINER_PASSWORD='...' python3 check_portainer_cve_2026_44848.py --url https://portainer.example.com --username readonly-user
# Version check only (no credentials, no probe)
python3 check_portainer_cve_2026_44848.py --url https://portainer.example.com --version-only
# Machine-readable output
python3 check_portainer_cve_2026_44848.py ... --json
| Option | Description |
|---|---|
--url | Portainer base URL (default https://localhost:9444) |
--username / --password | Non-admin credentials (or PORTAINER_PASSWORD) |
--token | Existing JWT (or PORTAINER_TOKEN) |
--endpoint-id | Probe only one endpoint ID |
--version-only | Skip authentication and the live probe |
--insecure | Disable TLS certificate verification |
--timeout | HTTP timeout in seconds (default 15) |
--json | Emit a JSON report |
| Code | Meaning |
|---|---|
0 | Not vulnerable |
1 | Vulnerable (authorization bypass confirmed) |
2 | Inconclusive / error (for example version match without a usable probe) |
GET /plugins returning 200 is not enoughGET /plugins is intentionally allowed for every endpoint role, including
read-only, on both vulnerable and patched releases. A checker that only tests
the list endpoint will report a false positive on fixed versions.
The actual bug is that mutating plugin routes were not registered with an
authorization handler. In 2.33.8 the fix adds adminOnlyRoutes for:
POST /plugins/pullPOST /plugins/{name}/enablePOST /plugins/{name}/disablePOST /plugins/{name}/pushPOST /plugins/{name}/upgradePOST /plugins/{name}/setPOST /plugins/createDELETE /plugins/{name}This checker uses one of those routes (disable) with a plugin name that does
not exist, so it can distinguish 403 (blocked by Portainer) from 404
(proxied to Docker) without side effects.
Vulnerable 2.33.6, read-only endpoint user:
[*] Target: https://localhost:9444
[*] Portainer version: 2.33.6
[!] Version is in an affected range: >= 2.33.0, < 2.33.8
[*] Authenticated as: u_readonly (role 2)
[*] Probing endpoint 1 (primary)...
GET /plugins -> HTTP 200
POST /plugins/<probe>/disable -> HTTP 404
Result: bypass - Docker answered HTTP 404 for the probe plugin
[RESULT] VULNERABLE
A non-admin account reached a privileged Docker plugin operation.
Fixed release: 2.33.8
Fixed 2.33.8, same user:
[*] Portainer version: 2.33.8
[+] Version is not in a known affected range.
POST /plugins/<probe>/disable -> HTTP 403
Result: blocked - Portainer denied the plugin operation
[RESULT] NOT VULNERABLE
2), because a vendor backport could block the route without changing the
version string. The live probe is the stronger signal.adminOnlyRoutes in
api/http/proxy/factory/docker/transport.goUse only against systems you own or are authorized to test.