{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-36005 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-36005 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-36005 is a medium-severity vulnerability in IBM MQ Operator, published on 24 Jul 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-36005 and fix it if it is affected.\n\nWhat it is: CVE-2025-36005 is a medium-severity vulnerability in IBM MQ Operator, published on 24 Jul 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-36005 in the wild and no public exploit code.\n\nAffected product: IBM MQ Operator. 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-36005/ (Markdown: https://insights.sbomify.com/CVE-2025-36005/index.md)","id":"CVE-2025-36005","markdown":"https://insights.sbomify.com/CVE-2025-36005/index.md","name":"CVE-2025-36005","record":{"aliases":["GHSA-vx28-r268-g868"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM MQ Operator","requires_auth":"none","summary":"A malicious user can obtain sensitive information from another TLS session due to improper certificate validation in the IBM MQ Operator.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"mq_operator","vendor":"ibm"},{"product":"supplied_mq_advanced_container_images","vendor":"ibm"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"IBM MQ Operator LTS 2.0.0 through 2.0.29, MQ Operator CD 3.0.0, 3.0.1, 3.1.0 through 3.1.3, 3.3.0, 3.4.0, 3.4.1, 3.5.0, 3.5.1, 3.6.0, and MQ Operator SC2 3.2.0 through 3.2.13 Internet Pass-Thru could allow a malicious user to obtain sensitive information from another TLS session connection by the proxy to the same hostname and port due to improper certificate validation.","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 MQ Operator information disclosure","id":"CVE-2025-36005","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"IBM Db2 denial of service","id":"CVE-2025-36006"},"packages":[],"prev":{"headline":"IBM i privilege escalation","id":"CVE-2025-36004"},"products":["MQ Operator"],"published":"2025-07-24","related":[{"cvss_score":8.8,"headline":"IBM MQ Buffer Overflow","id":"CVE-2026-10572","kev_date_added":null,"published":"2026-10-19"},{"cvss_score":8.8,"headline":"IBM MQ Buffer Overflow","id":"CVE-2026-10574","kev_date_added":null,"published":"2026-10-19"},{"cvss_score":8.8,"headline":"IBM MQ Race Condition","id":"CVE-2026-10743","kev_date_added":null,"published":"2026-10-19"},{"cvss_score":8.1,"headline":"IBM MQ Buffer Overflow","id":"CVE-2026-12665","kev_date_added":null,"published":"2026-10-19"},{"cvss_score":8.1,"headline":"IBM MQ Container authentication bypass","id":"CVE-2024-39742","kev_date_added":null,"published":"2024-07-08"},{"cvss_score":7.5,"headline":"IBM MQ Deserialization of Untrusted Data","id":"CVE-2026-12148","kev_date_added":null,"published":"2026-10-19"},{"cvss_score":7.5,"headline":"IBM MQ security bypass","id":"CVE-2024-40681","kev_date_added":null,"published":"2024-09-07"}],"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":"2025-08-17","vendors":["IBM"]},"summary":"A malicious user can obtain sensitive information from another TLS session due to improper certificate validation in the IBM MQ Operator.","url":"https://insights.sbomify.com/CVE-2025-36005/"}