Skip to content

CVE-2026-50734, CVE-2026-53917 ActiveMQ client: OpenWire memory-exhaustion DoS (5.19.4 -> 5.19.8) - #274

Merged
vharseko merged 1 commit into
masterfrom
dependabot/maven/openidm-zip/src/main/resources/samples/audit-jms-sample/consumer/org.apache.activemq-activemq-client-5.19.8
Nov 7, 2026
Merged

vharseko merged 1 commit into
masterfrom
dependabot/maven/openidm-zip/src/main/resources/samples/audit-jms-sample/consumer/org.apache.activemq-activemq-client-5.19.8

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Bumps org.apache.activemq:activemq-client from 5.19.4 to 5.19.8 in openidm-zip/src/main/resources/samples/audit-jms-sample/consumer/pom.xml, addressing Dependabot alerts #80 and #81. This is a direct dependency of the standalone JMS audit sample consumer.

Advisories

CVE-2026-50734 / GHSA-7259-vf48-52q3 — OpenWire negotiation memory exhaustion (CWE-789). An attacker who can reach a broker's OpenWire listener can send malformed WireFormatInfo properties whose encoded sizes drive excessive allocations before authentication, potentially exhausting the broker heap. The fix bounds negotiation properties to 64 entries, limits property buffers to 512 bytes and rejects nested collections. These checks are present in the published 5.19.8 client sources. Apache advisory, 5.19.x fix.

CVE-2026-53917 / GHSA-f77w-px59-cqf5 — OpenWire message-property map memory exhaustion (CWE-789). Apache describes an authenticated sender supplying malformed map sizes that cause excessive allocation during decoding and can exhaust broker memory. The fix validates sizes against the remaining input before allocation, caps the initial map/list capacity at 128 and bounds nesting depth. The associated upstream change also improves broker handling of corrupt messages; that broker-side behavior requires upgrading the broker itself. Apache advisory, 5.19.x fix.

Advisory Severity Affected 5.x versions Fixed in 5.x
CVE-2026-50734 / GHSA-7259-vf48-52q3 High — CVSS 3.1 7.5 < 5.19.8 5.19.8
CVE-2026-53917 / GHSA-f77w-px59-cqf5 High — CVSS 3.1 7.5 < 5.19.8 5.19.8

Both advisories also affect 6.0.0 through versions before 6.2.7 and are fixed in 6.2.7. The scores above are those published by the GitHub Advisory Database. For CVE-2026-53917, its CVSS vector lists PR:N, while Apache's description specifies an authenticated user; the prerequisite above follows Apache's description. GHSA-7259-vf48-52q3, GHSA-f77w-px59-cqf5.

Impact on OpenIDM

The changed dependency belongs to a separately built example. The ZIP assembly copies the sample POM and Java source into samples/audit-jms-sample/consumer; the consumer is not a root Maven reactor module. Updating this POM changes the client resolved when a user builds the consumer, rather than replacing a dependency in the running OpenIDM server. Consumer POM, ZIP assembly.

SimpleConsumer connects to a broker URI supplied on the command line, subscribes to the audit topic and prints TextMessage.getText(). OpenWire negotiation processes the remote broker's WireFormatInfo on the client side too, so the updated shared parser hardens that broker-facing boundary. This is a source-based reachability assessment; no client-side exploit was reproduced. The sample listener does not explicitly read message properties, so its own callback does not establish a direct path to the property-map flaw. Consumer source, client negotiation.

The sample uses an external broker, and its README separately instructs users to install the producer-side ActiveMQ client bundle into OpenIDM. This PR upgrades neither that manually installed bundle nor the external broker. In particular, the README still names client 5.13.2; this POM update does not make installations following those instructions secure. Those components need their own updates to a fixed release. Sample instructions.

Change

openidm-zip/src/main/resources/samples/audit-jms-sample/consumer/pom.xml only: activemq-client 5.19.4 → 5.19.8, one line replaced within the existing 5.19.x series. The upstream comparison includes additional maintenance and protocol-hardening changes beyond these two advisory fixes. Upstream comparison.

Verified:

  • The PR diff, consumer configuration, root module list and assembly inputs were checked at head 462c426.
  • The published Maven Central source JARs for 5.19.4 and 5.19.8 were downloaded and their SHA-1 digests matched Central's published checksums. The 5.19.8 sources contain the negotiation limits and allocation checks described above; the 5.19.4 sources contain the earlier decoding paths. Published artifacts.
  • At the time of checking, querying the GitHub Advisory Database for this exact package/version returns both advisories for 5.19.4 and none for 5.19.8. This check covers that artifact, not its complete transitive dependency graph.
  • Existing CI has passed the Ubuntu/JDK 17 and macOS/JDK 17 Maven jobs and the JavaScript/TypeScript CodeQL analysis. Other checks remain pending or in progress; the full matrix has not yet passed. The workflow builds the root reactor and does not separately build or run this consumer.
  • No new build or exploit reproduction was run for this description update. Standalone sample compatibility remains unverified: its source imports jakarta.jms, whereas both published ActiveMQ 5.19.4 and 5.19.8 clients implement javax.jms. This pre-existing mismatch is outside the one-line dependency change.

References

Bumps [org.apache.activemq:activemq-client](https://github.com/apache/activemq) from 5.19.4 to 5.19.8.
- [Release notes](https://github.com/apache/activemq/releases)
- [Commits](apache/activemq@activemq-5.19.4...activemq-5.19.8)

---
updated-dependencies:
- dependency-name: org.apache.activemq:activemq-client
  dependency-version: 5.19.8
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Nov 6, 2026
@vharseko vharseko changed the title Bump org.apache.activemq:activemq-client from 5.19.4 to 5.19.8 in /openidm-zip/src/main/resources/samples/audit-jms-sample/consumer Update ActiveMQ client to 5.19.8 in the JMS audit sample Nov 6, 2026
@vharseko vharseko changed the title Update ActiveMQ client to 5.19.8 in the JMS audit sample CVE-2026-50734, CVE-2026-53917 ActiveMQ client: OpenWire memory-exhaustion DoS (5.19.4 -> 5.19.8) Nov 6, 2026
@vharseko
vharseko merged commit 5080327 into master Nov 7, 2026
31 checks passed
@vharseko
vharseko deleted the dependabot/maven/openidm-zip/src/main/resources/samples/audit-jms-sample/consumer/org.apache.activemq-activemq-client-5.19.8 branch November 7, 2026 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file java Pull requests that update Java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant