# CVE-2026-42253: Apache ActiveMQ, Apache ActiveMQ Web: HTTP Response Header Injection via JMS Message Properties

> Attackers can inject HTTP response headers via JMS message properties in the ActiveMQ web console, potentially bypassing security controls.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** BIT-activemq-2026-42253, DEBIAN-CVE-2026-42253, GHSA-8wm6-6fqh-phmc, MINI-2m22-g7jx-cchc, MINI-46vv-vwv8-cq6r, MINI-5h6m-q7c6-qcrp, MINI-v6pr-c5c2-586p, UBUNTU-CVE-2026-42253

## What is CVE-2026-42253?

CVE-2026-42253 is a medium-severity cross-site scripting vulnerability in Apache Activemq, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Apache ActiveMQ, Apache ActiveMQ Web.

The MessageServlet in the ActiveMQ web console API copies every JMS message
property into an HTTP response header without any validation. This can allow overwriting and injecting security headers by setting them on JMS messages that are returned by the servlet.

This issue affects Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ Web: before 5.19.7, from 6.0.0 before 6.2.6.

Users are recommended to upgrade to version 5.19.7 or 6.2.6, which fixes the issue. The MessageServlet has now been deprecated and disabled by default.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

9 open source packages ship an affected version, including org.apache.activemq:activemq-web, activemq and org.apache.activemq:apache-activemq. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.activemq:activemq-web` | Maven | All versions | 5.19.7 |
| `org.apache.activemq:activemq-web` | Maven | All versions | 5.19.7 |
| `org.apache.activemq:activemq-web` | Maven | From 6.0.0 | 6.2.6 |
| `org.apache.activemq:activemq-web` | Maven | From 6.0.0 | 6.2.6 |
| `activemq` | Bitnami | All versions | 5.19.7, 6.2.6 |
| `org.apache.activemq:apache-activemq` | Maven | All versions | 5.19.7 |
| `org.apache.activemq:apache-activemq` | Maven | All versions | 5.19.7 |
| `org.apache.activemq:apache-activemq` | Maven | From 6.0.0 | 6.2.6 |
| `org.apache.activemq:apache-activemq` | Maven | From 6.0.0 | 6.2.6 |

Products: Apache Activemq, Apache Activemq Web.

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

Upgrade org.apache.activemq:activemq-web to a fixed version for your release line: 5.19.7 or 6.2.6.

## Is CVE-2026-42253 being exploited?

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

## Other vulnerabilities in Apache Activemq

- [CVE-2023-46604](https://insights.sbomify.com/CVE-2023-46604/): Apache ActiveMQ Deserialization of Untrusted Data (critical 10.0, exploited in the wild)
- [CVE-2016-3088](https://insights.sbomify.com/CVE-2016-3088/): Apache ActiveMQ Improper Input Validation (critical 9.8, exploited in the wild)
- [CVE-2026-34197](https://insights.sbomify.com/CVE-2026-34197/): Apache ActiveMQ Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2020-11998](https://insights.sbomify.com/CVE-2020-11998/): Remote code execution in Apache ActiveMQ (critical 9.8)
- [CVE-2013-7285](https://insights.sbomify.com/CVE-2013-7285/): Command Injection in Xstream (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42253 is a medium-severity cross-site scripting vulnerability in Apache Activemq, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-42253 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.activemq:activemq-web (Maven): affected all versions; fixed in 5.19.7
- org.apache.activemq:activemq-web (Maven): affected all versions; fixed in 5.19.7
- org.apache.activemq:activemq-web (Maven): affected from 6.0.0; fixed in 6.2.6
- org.apache.activemq:activemq-web (Maven): affected from 6.0.0; fixed in 6.2.6
- activemq (Bitnami): affected all versions; fixed in 5.19.7, 6.2.6
- org.apache.activemq:apache-activemq (Maven): affected all versions; fixed in 5.19.7
- org.apache.activemq:apache-activemq (Maven): affected all versions; fixed in 5.19.7
- org.apache.activemq:apache-activemq (Maven): affected from 6.0.0; fixed in 6.2.6
- org.apache.activemq:apache-activemq (Maven): affected from 6.0.0; fixed in 6.2.6

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-42253/ (Markdown: https://insights.sbomify.com/CVE-2026-42253/index.md)
```

## Sources

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

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