All vulnerabilities

Servers and applications

CVE-2026-44883

JWT accepted in URL query leaks tokens to logs and referers

Severity
High 7.7
Published
10 May 2026
Last changed
21 Jul 2026
Added to UpHeron
1 Nov 2026
Fixed in
2.33.8, 2.39.2, 2.41.0
Exploit chance
0.3% in the next 30 daysHigher than 22% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
CWE-598
Attack
Over the network · Only under certain conditions · No login needed · Needs someone to view a page or file
Attacker can
Read data · Change data · Take it down
CVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-jvp4-q659-95mj
Sources
NVD, Project advisories (GitHub)

Description

Portainer's authentication middleware accepts JWT bearer tokens passed as the ?token= URL query parameter on any authenticated API endpoint, in addition to the standard Authorization: Bearer header. URLs are recorded in reverse-proxy access logs, browser history, and HTTP Referer headers on outbound navigation, so any JWT passed this way can be harvested by anyone with access to those logs or by an external site the user subsequently visits. A leaked token grants the full privileges of the user it was issued to, until the token expires (default 8 hours, configurable).

The ?token= parameter was used by Portainer's browser-based container attach, exec, and pod shell features, so any user with exec or attach rights on a container was exposed — not only administrators.

Attack complexity is High because exploitation depends on the attacker obtaining a leaked token from a log, referer, or shared URL.

From portainer/portainer's security advisory. Shortened; the full text is there.

Workarounds

Administrators who cannot immediately upgrade can reduce exposure by:

  • Stripping ?token= at the reverse proxy. A rewrite rule in nginx, Traefik, or equivalent that removes the token query parameter before the request reaches Portainer blocks the query-parameter auth path entirely. Container exec and interactive shells rely on the query-parameter token for WebSocket upgrade and will stop working until the patched release is deployed.
  • Auditing existing logs. Search reverse-proxy access logs and application logs for ?token= or &token= occurrences and treat any captured JWT as compromised.
Workarounds as given by portainer/portainer's security advisory.

Affected software

SoftwareAffected versions
PortainerServers and applications · cpe:a:portainer:portainer
  • From 2.33.0 before 2.33.8
  • From 2.34.0 before 2.39.2
  • From 2.40.0 before 2.41.0
PortainerServers and applications · github:portainer/portainer
  • From 2.33.0 before 2.33.8
  • From 2.39.0 before 2.39.2
  • From 2.40.0 before 2.41.0

About Portainer

Open source software to manage Docker, docker swarm and Kubernetes

From Wikidata, CC0 1.0.
Docker Hub pulls
1,590,442,292Docker Hub, 15 Nov 2026
GitHub stars
38,831GitHub, 15 Nov 2026
Forks
2,940GitHub, 15 Nov 2026
Latest release
2.45.3GitHub, 15 Nov 2026
Released
21 Oct 2026GitHub
License
ZlibGitHub
First published on GitHub
19 May 2016GitHub

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-44883
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-44883
  • GitHub Advisory Database https://github.com/advisories/GHSA-jvp4-q659-95mj
  • github.com https://github.com/portainer/portainer/security/advisories/GHSA-jvp4-q659-95mj