{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-3157 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3157 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3157 is a medium-severity vulnerability in Ibm Sterling B2b Integrator, published on 28 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-3157 and fix it if it is affected.\n\nWhat it is: CVE-2026-3157 is a medium-severity vulnerability in Ibm Sterling B2b Integrator, published on 28 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-3157 in the wild and no public exploit code.\n\nAffected product: Ibm Sterling B2b Integrator. 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-2026-3157/ (Markdown: https://insights.sbomify.com/CVE-2026-3157/index.md)","id":"CVE-2026-3157","markdown":"https://insights.sbomify.com/CVE-2026-3157/index.md","name":"CVE-2026-3157","record":{"aliases":["GHSA-pcjc-2762-7xwq"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Sterling B2B Integrator","requires_auth":"low_privilege","summary":"Attackers can access sensitive information exposed in source code comments within the mailbox UI of IBM Sterling B2B Integrator and File Gateway.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"sterling_b2b_integrator","vendor":"ibm"},{"product":"sterling_file_gateway","vendor":"ibm"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-615","name":"Inclusion of Sensitive Information in Source Code Comments"}],"description":"IBM Sterling B2B Integrator 6.2.0.0 through 6.2.0.5_2, 6.2.1.0 through 6.2.1.1_2, and 6.2.2.0 through 6.2.2.0_1 and IBM Sterling File Gateway 6.2.0.0 through 6.2.0.5_2, 6.2.1.0 through 6.2.1.1_2, and 6.2.2.0 through 6.2.2.0_1 is vulnerable to an information disclosure due to sensitive information being included in the source code comments of a mailbox component.","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":"Information disclosure in Sterling B2B Integrator","id":"CVE-2026-3157","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:sterling_b2b_integrator","products":["ibm:sterling_b2b_integrator","ibm:sterling_file_gateway"],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Security Vulnerability in IBM Sterling B2B Integrator and IBM Sterling File Gateway due to information disclosure","id":"CVE-2026-3158"},"packages":[],"prev":{"headline":"Missing authorization in OneSignal – Web Push Notifications","id":"CVE-2026-3155"},"products":["Sterling B2B Integrator","Sterling File Gateway"],"published":"2026-07-28","related":[{"cvss_score":9.8,"headline":"IBM WebSphere Application Server and Server Hypervisor Edition Code Injection.","id":"CVE-2015-7450","kev_date_added":"2022-01-10","published":"2016-01-02"},{"cvss_score":8.8,"headline":"IBM Sterling B2B Integrator Standard Edition code execution","id":"CVE-2024-31903","kev_date_added":null,"published":"2025-01-22"},{"cvss_score":8.8,"headline":"Deserialization in Sterling B2B Integrator","id":"CVE-2019-4728","kev_date_added":null,"published":"2021-01-05"},{"cvss_score":8.8,"headline":"Privilege escalation in Sterling B2B Integrator","id":"CVE-2020-4762","kev_date_added":null,"published":"2021-01-05"},{"cvss_score":8.8,"headline":"SQL injection in Sterling B2B Integrator","id":"CVE-2017-1174","kev_date_added":null,"published":"2017-08-10"},{"cvss_score":8.8,"headline":"SQL injection in Sterling B2B Integrator","id":"CVE-2017-1347","kev_date_added":null,"published":"2017-06-23"},{"cvss_score":8.2,"headline":"XML external entity in Sterling B2B Integrator","id":"CVE-2017-1192","kev_date_added":null,"published":"2017-08-10"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-07-29","vendors":["IBM"]},"summary":"Attackers can access sensitive information exposed in source code comments within the mailbox UI of IBM Sterling B2B Integrator and File Gateway.","url":"https://insights.sbomify.com/CVE-2026-3157/"}