{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-33093 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-33093 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-33093 is a high-severity vulnerability in IBM Sterling Partner Engagement Manager, published on 7 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-33093 and fix it if it is affected.\n\nWhat it is: CVE-2025-33093 is a high-severity vulnerability in IBM Sterling Partner Engagement Manager, published on 7 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-33093 in the wild and no public exploit code.\n\nAffected product: IBM Sterling Partner Engagement Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-33093/ (Markdown: https://insights.sbomify.com/CVE-2025-33093/index.md)","id":"CVE-2025-33093","markdown":"https://insights.sbomify.com/CVE-2025-33093/index.md","name":"CVE-2025-33093","record":{"aliases":["GHSA-4vv5-fg3j-73p8"],"analysis":{"component_type":"cloud_service","fix_type":"configuration_change","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Sterling PEM","requires_auth":"none","summary":"Attackers can access sensitive data or bypass security controls because the JWT secret is exposed in public Helm charts instead of Kubernetes secrets.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"sterling_partner_engagement_manager","vendor":"ibm"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-260","name":"Password in Configuration File"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"IBM Sterling Partner Engagement Manager information disclosure","id":"CVE-2025-33093","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"IBM Engineering Requirements Management Doors Next denial of service","id":"CVE-2025-33096"},"packages":[],"prev":{"headline":"IBM Db2 for Linux code execution","id":"CVE-2025-33092"},"products":["Sterling Partner Engagement Manager"],"published":"2025-05-07","related":[{"cvss_score":7.5,"headline":"Denial of service in Sterling Partner Engagement Manager","id":"CVE-2022-35639","kev_date_added":null,"published":"2022-07-26"},{"cvss_score":7.1,"headline":"XML external entity in Partner Engagement Manager","id":"CVE-2022-34348","kev_date_added":null,"published":"2022-09-23"},{"cvss_score":6.5,"headline":"IBM Sterling Partner Engagement Manager denial of service","id":"CVE-2022-34335","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":6.4,"headline":"IBM Sterling Partner Engagement Manager cross-site scripting","id":"CVE-2023-38722","kev_date_added":null,"published":"2023-10-23"},{"cvss_score":6.4,"headline":"IBM Sterling Partner Engagement Manager cross-site scripting","id":"CVE-2023-23481","kev_date_added":null,"published":"2023-06-08"},{"cvss_score":6.3,"headline":"IBM Sterling Partner Engagement Manager SQL injection","id":"CVE-2022-40615","kev_date_added":null,"published":"2023-01-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-28","vendors":["IBM"]},"summary":"Attackers can access sensitive data or bypass security controls because the JWT secret is exposed in public Helm charts instead of Kubernetes secrets.","url":"https://insights.sbomify.com/CVE-2025-33093/"}