{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-36137 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-36137 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-36137 is a high-severity vulnerability in IBM Sterling Connect:Direct for Unix, published on 30 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-36137 and fix it if it is affected.\n\nWhat it is: CVE-2025-36137 is a high-severity vulnerability in IBM Sterling Connect:Direct for Unix, published on 30 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-36137 in the wild and no public exploit code.\n\nAffected product: IBM Sterling Connect:Direct for Unix. 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-36137/ (Markdown: https://insights.sbomify.com/CVE-2025-36137/index.md)","id":"CVE-2025-36137","markdown":"https://insights.sbomify.com/CVE-2025-36137/index.md","name":"CVE-2025-36137","record":{"aliases":["GHSA-4c6m-gmp8-84fq"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Sterling Connect:Direct","requires_auth":"high_privilege","summary":"Privileged users can escalate privileges further due to incorrect permission assignments for maintenance tasks in IBM Sterling Connect:Direct for UNIX.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"sterling_connect\\","vendor":"ibm"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-250","name":"Execution with Unnecessary Privileges"}],"description":"IBM Sterling Connect Direct for Unix 6.2.0.7 through 6.2.0.9 iFix004, 6.4.0.0 through 6.4.0.2 iFix001, and 6.3.0.2 through 6.3.0.5 iFix002 incorrectly assigns permissions for maintenance tasks to Control Center Director (CCD) users that could allow a privileged user to escalate their privileges further due to unnecessary privilege assignment for post update scripts.","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 Connect:Direct for UNIX command execution","id":"CVE-2025-36137","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"IBM QRadar SIEM cross-site scripting","id":"CVE-2025-36138"},"packages":[],"prev":{"headline":"IBM denial of service","id":"CVE-2025-36136"},"products":["Sterling Connect:Direct for Unix"],"published":"2025-10-30","related":[{"cvss_score":7.5,"headline":"IBM Connect:Express for UNIX denial of service","id":"CVE-2023-32331","kev_date_added":null,"published":"2024-03-04"},{"cvss_score":7.5,"headline":"Memory corruption in Sterling Connect Direct for Microsoft Windows","id":"CVE-2020-4767","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":6.7,"headline":"Privilege escalation in Sterling Connect:Direct for UNIX","id":"CVE-2018-1903","kev_date_added":null,"published":"2019-04-10"},{"cvss_score":6.5,"headline":"IBM Sterling Connect:Express for UNIX server-side request forgery","id":"CVE-2023-29260","kev_date_added":null,"published":"2023-07-19"},{"cvss_score":6.3,"headline":"Multiple vulnerabilities were addressed in IBM Sterling Connect:Express for UNIX.","id":"CVE-2025-36063","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":6.3,"headline":"Multiple vulnerabilities were addressed in IBM Sterling Connect:Express for UNIX.","id":"CVE-2025-36065","kev_date_added":null,"published":"2026-01-20"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["IBM"]},"summary":"Privileged users can escalate privileges further due to incorrect permission assignments for maintenance tasks in IBM Sterling Connect:Direct for UNIX.","url":"https://insights.sbomify.com/CVE-2025-36137/"}