{"answers":{"affected":"2 open source packages ship an affected version, including com.rabbitmq:amqp-client. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-106123 in the wild and no public exploit code.","fix":"Upgrade com.rabbitmq:amqp-client to 5.35.0 or later.","what":"CVE-2026-106123 is a medium-severity vulnerability in com.rabbitmq amqp-client, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-106123 and fix it if it is affected.\n\nWhat it is: CVE-2026-106123 is a medium-severity vulnerability in com.rabbitmq amqp-client, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-106123 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.rabbitmq:amqp-client (Maven): affected all versions; fixed in 5.35.0\n- com.rabbitmq:amqp-client (Maven): affected all versions; fixed in 5.35.0\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-106123/ (Markdown: https://insights.sbomify.com/CVE-2026-106123/index.md)","id":"CVE-2026-106123","markdown":"https://insights.sbomify.com/CVE-2026-106123/index.md","name":"CVE-2026-106123","record":{"aliases":["CLEANSTART-2026-DU73207","CLEANSTART-2026-EV52382","CLEANSTART-2026-OH67049","DEBIAN-CVE-2026-106123","ECHO-98f3-0922-9fc4","GHSA-h6w7-qmcm-q6xr","MINI-28g9-wxjp-3mxw","MINI-464j-p54x-r26m","MINI-59mh-mhmh-8fwq","MINI-6h38-v8mf-h9p7","MINI-7p6q-fx7c-3ff2","MINI-cq42-mf8h-r6h6","MINI-fhc2-6vwf-w332","MINI-h4wj-6qf6-8cp6","MINI-j4r9-3xhj-xgpj","MINI-jcc5-8r32-gcj8","MINI-jjjh-vhwc-f8r8","MINI-q7rw-c2rr-vc9r","MINI-qw4x-6p6c-wqhm","MINI-r95f-cff5-mj67","UBUNTU-CVE-2026-106123"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RabbitMQ Java client","requires_auth":"low_privilege","summary":"Attackers can view RabbitMQ broker credentials in logs or stack traces when URI parsing fails, exposing sensitive authentication data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rabbitmq_java_client","vendor":"vmware"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.35.0, ConnectionFactoryConfigurator.load() includes the raw uri value in wrapped exceptions when AMQP URI parsing fails. Because the URI may contain a plaintext username and password, startup logs, application performance monitoring systems, CI logs, and copied stack traces can disclose broker credentials to users who should not have access to them. This issue is fixed in version 5.35.0.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"RabbitMQ Java client: plaintext broker credentials leaked in exception message from ConnectionFactoryConfigurator.load()","id":"CVE-2026-106123","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Command Injection","id":"CVE-2026-106126"},"packages":[{"ecosystem":"Maven","fixed":["5.35.0"],"introduced":["0"],"last_affected":[],"package":"com.rabbitmq:amqp-client","purl":null,"source":"GHSA-h6w7-qmcm-q6xr"},{"ecosystem":"Maven","fixed":["5.35.0"],"introduced":["0"],"last_affected":[],"package":"com.rabbitmq:amqp-client","purl":"pkg:maven/com.rabbitmq/amqp-client","source":"GHSA-h6w7-qmcm-q6xr"}],"prev":{"headline":"RabbitMQ: Malformed UTF-8 in shortstr properties permanently disables RPC consumers","id":"CVE-2026-106122"},"products":["amqp-client","rabbitmq-java-client"],"published":"2026-10-06","related":[{"cvss_score":6,"headline":"RabbitMQ: Malformed UTF-8 in shortstr properties permanently disables RPC consumers","id":"CVE-2026-106122","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":4.9,"headline":"RabbitMQ: JSONReader in the default JSON-RPC mapper never terminates on truncated input, causing DoS","id":"CVE-2026-106121","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":4.9,"headline":"RabbitMQ Java client's lack of message size limitation leads to remote DoS attack","id":"CVE-2023-46120","kev_date_added":null,"published":"2023-10-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-10-19","vendors":["com.rabbitmq","rabbitmq"]},"summary":"Attackers can view RabbitMQ broker credentials in logs or stack traces when URI parsing fails, exposing sensitive authentication data.","url":"https://insights.sbomify.com/CVE-2026-106123/"}