CVE-2024-33662: portainer · Inadequate Encryption Strength
Affects portainerSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 2.20.2 soon.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.20.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade portainer/portainer to 2.20.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubportainer/portainerpkg:github/portainer/portainerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should immediately upgrade Portainer to version 2.20.2 or later, where the encryption algorithm misuse has been corrected. If you cannot patch yet, restrict network access to Portainer management interfaces using firewalls or VPNs to limit exposure. Implement strict access controls and monitor for unusual activity related to Portainer services. Review and rotate any sensitive credentials or secrets managed through Portainer to mitigate potential compromise. Employ network segmentation to isolate container management systems from critical production environments. Conduct regular security audits and vulnerability scans focusing on container orchestration platforms. Additionally, consider deploying runtime security tools that can detect anomalous container behavior indicative of exploitation attempts. Stay informed through official Portainer security advisories and subscribe to vulnerability databases for updates on exploit developments or patches.
Description
Portainer before 2.20.2 improperly uses an encryption algorithm in the AesEncrypt function.