Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
portainer-cve-2026-44848-checker — Non-destructive checker for CVE-2026-44848: Portainer missing authorization on Docker plugin endpoints | Kitploit
Tools/GitHubGitHub/mnk-works/portainer-cve-2026-44848-checker
Authentication & AuthorizationDefensive ToolsVulnerability ScannersContainer SecurityVulnerability AnalysisWeb SecurityPenetration Testing
GitHub
Share
mnk-works/portainer-cve-2026-44848-checker

portainer-cve-2026-44848-checker

Non-destructive checker for CVE-2026-44848: Portainer missing authorization on Docker plugin endpoints

View Repository
125 days agoNot yet reviewed

Portainer CVE-2026-44848 checker

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:

  1. Is the Portainer version in a published affected range?
  2. Can a non-admin account with Docker endpoint access reach a privileged /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.

Affected versions

From the GitHub advisory / NVD:

AffectedFixed
>= 2.33.0, < 2.33.82.33.8
>= 2.39.0, < 2.39.22.39.2
>= 2.40.0, < 2.41.02.41.0

Requirements

  • Python 3.9+ (standard library only)
  • A non-admin Portainer account that has been granted access to a Docker endpoint. The read-only endpoint role is ideal.

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.

Usage

# 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

Options

OptionDescription
--urlPortainer base URL (default https://localhost:9444)
--username / --passwordNon-admin credentials (or PORTAINER_PASSWORD)
--tokenExisting JWT (or PORTAINER_TOKEN)
--endpoint-idProbe only one endpoint ID
--version-onlySkip authentication and the live probe
--insecureDisable TLS certificate verification
--timeoutHTTP timeout in seconds (default 15)
--jsonEmit a JSON report

Exit codes

CodeMeaning
0Not vulnerable
1Vulnerable (authorization bypass confirmed)
2Inconclusive / error (for example version match without a usable probe)

Why GET /plugins returning 200 is not enough

GET /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/pull
  • POST /plugins/{name}/enable
  • POST /plugins/{name}/disable
  • POST /plugins/{name}/push
  • POST /plugins/{name}/upgrade
  • POST /plugins/{name}/set
  • POST /plugins/create
  • DELETE /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.

Example output

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

Limitations

  • The probe needs an account with endpoint access. Without one, only the version check is possible.
  • A version match alone is reported as likely vulnerable / inconclusive (2), because a vendor backport could block the route without changing the version string. The live probe is the stronger signal.
  • The checker demonstrates the authorization bypass, not host RCE. Docker runs enabled plugins as root, which is the documented impact of the CVE.
  • Permissions and endpoint visibility can vary with custom roles, endpoint groups, and reverse proxies. A bypass on any tested Docker endpoint is sufficient to report vulnerable.

References

  • GitHub Advisory: https://github.com/advisories/GHSA-rrmm-9v76-h3p4
  • NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44848
  • Portainer 2.33.8 fix: adminOnlyRoutes in api/http/proxy/factory/docker/transport.go

Disclaimer

Use only against systems you own or are authorized to test.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    544
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    385
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    360
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    302
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    279

Explore all tools

Browse our collection of tools

View all tools →