CVE-2025-33093 Details
Description
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.
A vulnerability exists in IBM Sterling Partner Engagement Manager versions 6.1.0, 6.2.0, and 6.2.2, where the JSON Web Token (JWT) secret is publicly stored in Helm Charts instead of being secured as a Kubernetes secret. This flaw can lead to unauthorized access or manipulation of JWTs, potentially allowing for session hijacking or other security breaches.
Users can upgrade to the latest version of the IBM Sterling Partner Engagement Manager Helm Chart, where this issue has been addressed. Guidance on downloading the updated Helm Charts is available in the IBM Sterling Partner Engagement Manager documentation. Additionally, users should provide a valid, non-empty JWT secret key during deployment to ensure secure configurations.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed May 7, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://www.ibm.com/support/pages/node/7232762 | [email protected] | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-522 | Insufficiently Protected Credentials | [email protected] |
| CWE-260 | Password in Configuration File | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| ibm sterling partner engagement manager | 6.1.0 6.1.2 6.2.0 6.2.2 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Nov 13, 2025 | Modified Analysis | [email protected] |
| Aug 20, 2025 | Initial Analysis | [email protected] |
| May 7, 2025 | New CVE Received | [email protected] |