OSSEVA FOR ACTIVEMQ ARTEMIS
ActiveMQ Artemis — patched, protected, operated.
ActiveMQ Artemis is the messaging backbone for thousands of enterprise Java applications. OSSeva provides CVE-patched builds, architectural support, and 24/7 managed operations for 2.x — the production version running in your environment today.
Why now
Red Hat / IBM ownership creates support uncertainty
ActiveMQ Artemis is now embedded in Red Hat AMQ Broker and managed under the Red Hat / IBM umbrella. Community support cadence has slowed, and version lifecycle commitments have become less predictable for non-RHEL deployments.
JMS and AMQP 1.0 vulnerabilities affect payment and integration workloads
ActiveMQ Artemis handles JMS message routing in financial services, healthcare, and enterprise integration platforms. CVEs in the message parsing and authentication layers carry direct compliance implications under PCI DSS and HIPAA.
Legacy ActiveMQ 5.x migration creates compliance gaps
Many enterprises are mid-migration from ActiveMQ Classic 5.x to Artemis 2.x. During migration windows, both versions require CVE coverage — a gap most commercial vendors won't address. OSSeva covers both.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 2.28.x | Extended | Clean |
| 2.29.x | Extended | Clean |
| 2.30.x | Extended | Clean |
| 2.31.x | Current | Clean |
| 2.32.x | Current | Clean |
What you get
Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
CVE patches for Artemis 2.x. Signed builds, all supported versions.
- Quarterly CVE patches for Artemis 2.28.x–2.32.x
- JMS, AMQP 1.0, MQTT, STOMP protocol coverage
- Maven / Docker delivery
- Signed artifacts (GPG)
- CVE disclosure notifications
- Architecture review
- 24/7 managed operations
OSSeva Assure
Patch plus HA architecture review and compliance documentation.
- Everything in Patch
- Live-live HA cluster architecture review
- Message address / queue security audit
- SOC 2 / PCI DSS attestation package
- ActiveMQ Classic → Artemis migration assessment
- AMQP 1.0 configuration hardening guide
- 24/7 managed operations
OSSeva Operate
Full MSP: 24/7 monitoring, 15-min SLA, named JMS engineers.
- Everything in Assure
- 24/7 broker health monitoring
- 15-minute P1 incident response SLA
- Named senior Artemis engineer on your account
- Queue depth and consumer lag alerting
- Quarterly broker performance reviews
- ActiveMQ Classic migration execution
All tiers priced per cluster/application — not per core. Contact for pricing →
How it installs
OSSeva artifacts arrive via your existing package infrastructure. Pull the patched version the same way you pull upstream today — just from the OSSeva registry.
docker pull artifacts.osseva.io/activemq-artemis:2.31.2-osseva-1
docker run -d \
--name artemis-broker \
-p 61616:61616 \
-p 8161:8161 \
-e ARTEMIS_USER=admin \
-e ARTEMIS_PASSWORD=changeme \
artifacts.osseva.io/activemq-artemis:2.31.2-osseva-1<dependency>
<groupId>io.osseva.activemq</groupId>
<artifactId>artemis-jms-client</artifactId>
<version>2.31.2-osseva-1</version>
</dependency>Migrate from Red Hat AMQ Broker / IBM MQ
Red Hat AMQ Broker is built on Artemis but requires RHEL subscriptions for support. IBM MQ customers seeking a cost-effective migration path can move to OSSeva-supported Artemis without proprietary lock-in.
Pricing model
OSSeva for Artemis is priced per broker cluster — not per connection or per message. Contact for scoping.
Compliance library
Frequently asked questions
Which versions of RabbitMQ are past community end-of-life?
RabbitMQ 3.8.x, 3.9.x, 3.10.x, 3.11.x, and 3.12.x have all reached community EOL — meaning no further security patches or CVE fixes are released by the RabbitMQ maintainers for those versions. RabbitMQ 3.13.x reached EOL in late 2024. OSSeva delivers backported CVE patches for 3.11 through 3.13.
Which PostgreSQL versions are no longer receiving community security patches?
PostgreSQL 9.6 through 13 have all reached community EOL. PostgreSQL 11 reached EOL November 2023, PostgreSQL 12 reached EOL November 2024, and PostgreSQL 13 reaches EOL November 2025. OSSeva provides extended security patching for PostgreSQL 11, 12, and 13 for teams that cannot immediately migrate to PG 14 or later.
Is Spring Framework 5.3.x still supported?
Spring Framework 5.3.x reached its community OSS EOL on December 31, 2024. Broadcom's commercial support for Spring 5.3.x is also no longer available under standard terms. OSSeva delivers backported CVE patches for Spring Framework 5.3.x and Spring Boot 2.7.x under our extended lifecycle support program.
Which versions of Apache Kafka are EOL?
Apache Kafka versions 2.x and 3.0 through 3.4 are past their community supported window, meaning no further patch releases. Kafka 3.5 and 3.6 have reached or are approaching EOL. OSSeva supports Kafka 2.8 through 3.5 with backported security patches and compliance documentation.
What happened to Redis licensing? Can I still use Redis for free?
In March 2024, Redis Ltd. changed the Redis license from BSD-3-Clause to the Business Source License (BSL 1.1), which restricts use in competing database products. The Valkey project (a Linux Foundation fork) continues under BSD-3-Clause. OSSeva maintains BSD-licensed, CVE-patched builds of Redis 6.2 and 7.0 for enterprises that need verifiable open-source licensing alongside security coverage.
Is Node.js 18 still receiving security patches?
Node.js 18 (LTS 'Hydrogen') reached its end-of-life date in April 2025 and no longer receives security releases from the Node.js project. OSSeva delivers CVE patches for Node.js 18 for enterprise teams that have not yet migrated to Node.js 20 or 22.
Is Apache Tomcat 8.5 still supported?
Apache Tomcat 8.5 reached its community EOL in March 2024. OSSeva provides extended security patching for Tomcat 8.5.x for teams running Java EE 7 workloads that cannot immediately migrate to Tomcat 9.0 or 10.1.
What .NET versions does OSSeva support?
.NET 6 reached Microsoft end-of-support in November 2024. .NET 7 reached EOL in May 2024. OSSeva delivers CVE patches for .NET 6 and .NET 7 for teams that have not yet migrated to .NET 8 (LTS, supported through November 2026).
Ready to get ActiveMQ Artemis patched and supported?
Start with a 45-minute discovery call. We confirm your version coverage, scope the engagement, and have you onboarded within your first quarter.