{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-59272 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-59272 is a medium-severity vulnerability in Spring AMQP, published on 27 Aug 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-59272 and fix it if it is affected.\n\nWhat it is: CVE-2026-59272 is a medium-severity vulnerability in Spring AMQP, published on 27 Aug 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-59272 in the wild and no public exploit code.\n\nAffected product: Spring AMQP. 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-59272/ (Markdown: https://insights.sbomify.com/CVE-2026-59272/index.md)","id":"CVE-2026-59272","markdown":"https://insights.sbomify.com/CVE-2026-59272/index.md","name":"CVE-2026-59272","record":{"aliases":["GHSA-fp2f-68v2-xw9x"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Java logging library","requires_auth":"low_privilege","summary":"Attackers can intercept log data via man-in-the-middle attacks because the Log4j2 AmqpAppender disables TLS hostname verification by default.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"spring_advanced_message_queuing_protocol","vendor":"vmware"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-297","name":"Improper Validation of Certificate with Host Mismatch"}],"description":"Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default, is exposed to man-in-the-middle interception of every log event.\nSpring AMQP 4.1.0\nSpring AMQP 4.0.0 - 4.0.4\nSpring AMQP 3.2.0 - 3.2.12\nSpring AMQP 2.4.18 and earlier","ecosystems":[],"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":"Log4j2 AmqpAppender disables TLS hostname verification by default","id":"CVE-2026-59272","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Unbounded decompression in UnZipTransformer enables zip-bomb DoS","id":"CVE-2026-59274"},"packages":[],"prev":{"headline":"Admin password disclosed in BrokerNotAliveException message","id":"CVE-2026-59271"},"products":["Spring AMQP"],"published":"2026-08-27","related":[{"cvss_score":6.6,"headline":"Deserialization in Spring AMQP","id":"CVE-2026-59275","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":6.5,"headline":"In Spring AMQP the link credit never replenished on listener exception path","id":"CVE-2026-59320","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":6.5,"headline":"Unbounded decompression of attacker-supplied compressed message bodies","id":"CVE-2026-47860","kev_date_added":null,"published":"2026-08-26"},{"cvss_score":6.5,"headline":"Deserialization of Untrusted Data in Spring AMQP","id":"CVE-2021-22095","kev_date_added":null,"published":"2021-11-30"},{"cvss_score":6.5,"headline":"Deserialization of Untrusted Data in Spring AMQP","id":"CVE-2021-22097","kev_date_added":null,"published":"2021-10-28"},{"cvss_score":5.3,"headline":"Admin password disclosed in BrokerNotAliveException message","id":"CVE-2026-59271","kev_date_added":null,"published":"2026-08-27"}],"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-08-28","vendors":["Spring"]},"summary":"Attackers can intercept log data via man-in-the-middle attacks because the Log4j2 AmqpAppender disables TLS hostname verification by default.","url":"https://insights.sbomify.com/CVE-2026-59272/"}