NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Portainer improperly uses an encryption algorithm in the AesEncrypt functionGHSA-9mjw-79r6-c9m8

HIGH

GHSA-9mjw-79r6-c9m8 is a high-severity (CVSS 7.5) CWE-326 vulnerability in github.com/portainer/portainer. A fix is available for github.com/portainer/portainer — see the affected versions and patch details below.

Also known asCVE-2024-33662GO-2024-3172
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9mjw-79r6-c9m8.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs21th percentile — riskier than 21% of all scored CVEsHighest risk
0.00%0.26%0.52%0.78%0.1%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/portainer/portainer

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Portainer before 2.20.2 improperly uses an encryption algorithm in the AesEncrypt function.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/portainer/portainerall versions2.20.2go get github.com/portainer/portainer@v2.20.2

Affected Products

1 product · 1 configurations
Application
portainerportainer
< 2.20.2
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/portainer/portainer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/portainer/portainer to 2.20.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9mjw-79r6-c9m8 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Portainer before 2.20.2 improperly uses an encryption algorithm in the `AesEncrypt` function.
O3 Security · Impact-Aware SCA

Is GHSA-9mjw-79r6-c9m8 in your dependencies?

Find it across Go, including transitive dependencies.

Portainer improperly uses an encryption algorithm in the…