Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-2jp3-2923-9h52

Apache ActiveMQ Vulnerable to Cross-site Scripting

CVSS 6.5 MediumEPSS 0.0056 · 47th percentile

Published by the GitHub Advisory Database at 24 Apr 2026, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.activemq:apache-activemqMaven<5.19.6 || >=6.0.0, <6.2.55.19.6, 6.2.5
org.apache.activemq:activemq-allMaven<5.19.6 || >=6.0.0, <6.2.55.19.6, 6.2.5
org.apache.activemq:activemq-brokerMaven<5.19.6 || >=6.0.0, <6.2.55.19.6, 6.2.5
Identifiers
GHSA-2jp3-2923-9h52 · BIT-activemq-2026-41043 · CVE-2026-41043
Weakness (CWE)
CWE-79 · CWE-915
Tags
Published
24 Apr 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache ActiveMQ (packages apache-activemq, activemq-all and activemq-broker) before 5.19.6 and from 6.0.0 before 6.2.5 is vulnerable to cross-site scripting in the web console. An authenticated attacker can inject HTML through a JMS selector field and override the content type, so malicious content is displayed when a user browses queues. Upgrade to version 5.19.6 or 6.2.5.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0056, the 47th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.