# CVE-2026-59272: Log4j2 AmqpAppender disables TLS hostname verification by default

> Attackers can intercept log data via man-in-the-middle attacks because the Log4j2 AmqpAppender disables TLS hostname verification by default.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-fp2f-68v2-xw9x

## What is CVE-2026-59272?

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.

### Official 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.
Spring AMQP 4.1.0
Spring AMQP 4.0.0 - 4.0.4
Spring AMQP 3.2.0 - 3.2.12
Spring AMQP 2.4.18 and earlier

Weakness: CWE-297 (Improper Validation of Certificate with Host Mismatch)

## Which versions are affected by CVE-2026-59272?

It affects 1 product.


Products: Vmware Spring Advanced Message Queuing Protocol.

## How do I fix CVE-2026-59272?

Upgrade to a fixed version.

## Is CVE-2026-59272 being exploited?

There is no known exploitation of CVE-2026-59272 in the wild and no public exploit code.

## Other vulnerabilities in Spring AMQP

- [CVE-2026-59275](https://insights.sbomify.com/CVE-2026-59275/): Deserialization in Spring AMQP (medium 6.6)
- [CVE-2026-59320](https://insights.sbomify.com/CVE-2026-59320/): In Spring AMQP the link credit never replenished on listener exception path (medium 6.5)
- [CVE-2026-47860](https://insights.sbomify.com/CVE-2026-47860/): Unbounded decompression of attacker-supplied compressed message bodies (medium 6.5)
- [CVE-2021-22095](https://insights.sbomify.com/CVE-2021-22095/): Deserialization of Untrusted Data in Spring AMQP (medium 6.5)
- [CVE-2021-22097](https://insights.sbomify.com/CVE-2021-22097/): Deserialization of Untrusted Data in Spring AMQP (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59272 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-59272 in the wild and no public exploit code.

Affected product: Spring AMQP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59272/ (Markdown: https://insights.sbomify.com/CVE-2026-59272/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59272
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59272
- OSV: https://osv.dev/vulnerability/CVE-2026-59272

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59272/
Summaries are generated and may contain mistakes; the official description above is the record.