First published: Wed May 07 2025(Updated: )
IBM Sterling Partner Engagement Manager 6.1.0, 6.2.0, 6.2.2 JWT secret is stored in public Helm Charts and is not stored as a Kubernetes secret.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Sterling Partner Engagement Manager on Cloud | >=6.1.0<6.2.2 | |
IBM Performance Management (PEM) | <=6.1.x | |
IBM Performance Management (PEM) | <=6.2.x |
Product Version(s) Remediation/Fix/Instructions IBM Sterling Partner Engagement Manager Standard Edition / Essentials Edition 6.1.x, 6.2.0,6.2.3, 6.24 6.2.0,6.2.3,6.2.4
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-33093 has a high severity due to the exposure of sensitive JWT secrets in public Helm Charts.
To fix CVE-2025-33093, store the JWT secret as a Kubernetes secret instead of in public Helm Charts.
CVE-2025-33093 affects IBM Sterling Partner Engagement Manager versions 6.1.0 to 6.2.2.
The impact of CVE-2025-33093 includes potential unauthorized access to sensitive data through exposed JWT secrets.
Yes, a patch is available that addresses the issue with CVE-2025-33093 by properly securing JWT secrets.