● Low · CVSS 2.3

How to Fix CVE-2026-32642: Access Control Bypass in Apache Artemis

Q: Is CVE-2026-32642 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Q: Will a WAF or IDS rule fully mitigate CVE-2026-32642?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Q: How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Apache Artemis run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-33007: NULL Pointer Dereference in Apache HTTP Server — NULL Pointer Dereference in Apache HTTP Server
How to Fix CVE-2026-23906: Authentication Bypass in Apache Druid — Authentication Bypass in Apache Druid
How to Fix CVE-2026-31906: Cross-Site Scripting in Apache OFBiz , Cross-Site Scripting in Apache OFBiz
How to Fix CVE-2026-32690: Exposure of resource to wrong sphere in Apache Airflow , Exposure of resource to wrong sphere in Apache Airflow
How to Fix CVE-2026-29168: Allocation of Resources Without Limits or Throttling in Apache HTTP Server , Allocation of Resources Without Limits or Throttling in Apache HTTP Server

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 2.3 - Low
Actively exploited?	Not currently listed in CISA KEV
Affected	2.50.0 <= 2.52.0, 2.0.0 <= 2.44.0
Fixed in	See vendor advisory
Type (CWE)	CWE-863: Incorrect Authorization

What is CVE-2026-32642?

CVE-2026-32642 is an access control bypass flaw in Apache Artemis. Authenticated or in some cases unauthenticated requests reach endpoints they should not be allowed to call, exposing administrative functionality or sensitive data. Vendor description: Incorrect Authorization (CWE-863) vulnerability in Apache Artemis, Apache ActiveMQ Artemis exists when an application using the OpenWire protocol attempts to create a non-durable JMS topic subscription on an address that doesn't exist with an authenticated user which has the "createDurableQueue" permission but does not have the "createAddress" permission and address auto-creation is disabled. In this circumstance, a temporary address will be created whereas the attempt to create the non-durable subscription should instead fail since the user is not authorized to create the corresponding address.

Why this CVE matters

Access control flaws let an attacker reach endpoints the developers assumed would be reserved for administrators. The impact depends on what those endpoints expose, but for management products the answer is usually configuration changes, log access, or credential reads.

For deployments of Apache Artemis that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Apache Artemis: 2.50.0 <= 2.52.0
Apache Artemis: 2.0.0 <= 2.44.0

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Run the project-specific version command (for example httpd -v, tomcat version, or check pom.xml / package metadata) and compare against the advisory.

How to fix CVE-2026-32642

Read the vendor advisory in full: https://lists.apache.org/thread/4wlrp31ngq2yb54sf4kjb3bl41t4xgtp
Upgrade Apache Artemis to the patched build listed in the vendor advisory.
Back up the configuration (and database, where applicable) before upgrading.
Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
Restart the affected service so the patched binary loads, then verify the new version (see verification section).

The commands below are runnable starting points. Adapt the package name, target version, and host paths to your environment using the vendor advisory linked under References.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade apache2
dpkg -s apache2 | grep -i version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh apache2 -y
rpm -q apache2

Container image


# Vendor advisory: https://lists.apache.org/thread/4wlrp31ngq2yb54sf4kjb3bl41t4xgtp
docker pull <your-registry>/apache2:<patched-tag>
docker build -t <your-app>:patched .
docker stop <your-app> && docker rm <your-app>
docker run -d --name <your-app> <your-app>:patched

PowerShell detect/upgrade/verify/log (Windows)


# CVE-2026-32642 remediation runner. Adapt version checks to your environment.
$log = "C:\Logs\CVE-2026-32642-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Out-File $log -Append }

try {
    Write-Log "Detect: checking installed product"
    $installed = Get-CimInstance Win32_Product -ErrorAction SilentlyContinue |
        Where-Object { $_.Name -match 'Apache Artemis' }
    if (-not $installed) { Write-Log "Product not installed; nothing to do"; return }
    Write-Log "Found version $($installed.Version)"

    Write-Log "Backup: copying program files and registry hive"
    $stamp = Get-Date -Format yyyyMMdd-HHmm
    $backup = "C:\Backup\CVE-2026-32642-$stamp"
    New-Item -ItemType Directory -Force -Path $backup | Out-Null
    Copy-Item $installed.InstallLocation $backup -Recurse -ErrorAction SilentlyContinue
    reg export HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall "$backup\uninstall.reg" /y | Out-Null

    Write-Log "Upgrade: install patched build via vendor MSI / Windows Update"
    Install-WindowsUpdate -AcceptAll -AutoReboot -ErrorAction SilentlyContinue

    Write-Log "Verify: re-reading product version"
    $after = Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'Apache Artemis' }
    Write-Log "Post-patch version: $($after.Version)"
    if ($after.Version -ne $installed.Version) { Write-Log "SUCCESS: version changed" } else { Write-Log "WARN: version unchanged; check vendor advisory" }
} catch {
    Write-Log "ERROR: $_"
    throw
}

Bash detect/upgrade/verify/log (Linux)


#!/usr/bin/env bash
# CVE-2026-32642 remediation runner. Re-runnable, exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2026-32642-fix.log; }

log "Detect: current apache2 version"
if command -v dpkg >/dev/null 2>&1; then
    current=$(dpkg-query -W -f='${Version}' apache2 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
    current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' apache2 2>/dev/null || echo "not-installed")
else
    current="unknown"
fi
log "Current: $current"

log "Backup: snapshotting config"
backup="/var/backups/cve-2026-32642-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d /etc/apache2 ] && cp -a /etc/apache2 "$backup/" || true

log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update -qq
    sudo apt-get install -y --only-upgrade apache2
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade -y apache2
elif command -v yum >/dev/null 2>&1; then
    sudo yum update -y apache2
fi

log "Verify: re-reading apache2 version"
if command -v dpkg >/dev/null 2>&1; then
    after=$(dpkg-query -W -f='${Version}' apache2)
else
    after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' apache2)
fi
log "After: $after"

if [ "$after" != "$current" ]; then
    log "SUCCESS: apache2 upgraded"
else
    log "WARN: version unchanged. Confirm the patched build is in your repository."
    exit 1
fi

If you cannot patch immediately

No official workaround exists beyond restricting network exposure to the affected component. Apply the vendor patch as the primary remediation.

How to verify the fix worked

After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
Confirm the patched build matches the version listed in the vendor advisory.
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-32642.
Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for log entries that do not match your normal request patterns, especially repeated requests to the same uncommon endpoint, and any administrative changes you cannot tie back to a known operator.

Frequently asked questions

Is CVE-2026-32642 being exploited in the wild?