How severe is CVE-2026-27446?

No CVSS score has been assigned to CVE-2026-27446 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-27446?

CVE-2026-27446 affects the following packages: org.apache.activemq:artemis-server (Maven), org.apache.artemis:artemis-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-27446?

No patched version of org.apache.activemq:artemis-server has shipped for CVE-2026-27446 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2026-27446 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.activemq:artemis-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-27446 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-27446?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-27446 can be triaged on real exposure rather than presence alone.

Is CVE-2026-27446 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-27446 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-27446?

CVE-2026-27446 has an EPSS (Exploit Prediction Scoring System) score of 10.0%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2026-27446?

CVE-2026-27446 is classified as Missing Authentication (CWE-306). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-27446 published, and has it been updated?

CVE-2026-27446 was published on March 4, 2026 and was last updated on September 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2026-27446 — artemis-server

CVE-2026-27446 is a Missing Authentication vulnerability in org.apache.activemq:artemis-server. EPSS puts its 30-day exploitation probability at 10.0% (95th percentile). A fix is available for org.apache.activemq:artemis-server — see the affected versions and patch details below.

Apache Artemis, Apache ActiveMQ Artemis: Auth bypass for Core downstream federation

Also known asGHSA-fw88-pf9m-p947

Published

Mar 4, 2026

Updated

Sep 20, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-27446.

EPSS Exploitation Probability

via FIRST.org ↗

10.0%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

☕org.apache.activemq:artemis-server☕org.apache.artemis:artemis-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Missing Authentication for Critical Function (CWE-306) vulnerability in Apache Artemis, Apache ActiveMQ Artemis. An unauthenticated remote attacker can use the Core protocol to force a target broker to establish an outbound Core federation connection to an attacker-controlled rogue broker. This could potentially result in message injection into any queue and/or message exfiltration from any queue via the rogue broker. This impacts environments that allow both:

incoming Core protocol connections from untrusted sources to the broker
outgoing Core protocol connections from the broker to untrusted targets

This issue affects:

Apache Artemis from 2.50.0 through 2.51.0
Apache ActiveMQ Artemis from 2.11.0 through 2.44.0.

Users are recommended to upgrade to Apache Artemis version 2.52.0, which fixes the issue.

The issue can be mitigated by one of the following:

Remove Core protocol support from any acceptor receiving connections from untrusted sources. Incoming Core protocol connections are supported by default via the "artemis" acceptor listening on port 61616. See the "protocols" URL parameter configured for the acceptor. An acceptor URL without this parameter supports all protocols by default, including Core.
Use two-way SSL (i.e. certificate-based authentication) in order to force every client to present the proper SSL certificate when establishing a connection before any message protocol handshake is attempted. This will prevent unauthenticated exploitation of this vulnerability.
Implement and deploy a Core interceptor to deny all Core downstream federation connect packets. Such packets have a type of (int) -16 or (byte) 0xfffffff0. Documentation for interceptors is available at https://artemis.apache.org/components/artemis/documentation/latest/intercepting-operations.html .

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.activemq:artemis-server`	≥ 2.11.0	No fix
☕Maven	`org.apache.artemis:artemis-server`	≥ 2.50.0&&< 2.52.0	2.52.0`org.apache.artemis:artemis-server:2.52.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.activemq:artemis-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of org.apache.activemq:artemis-server has shipped for CVE-2026-27446 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-27446 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2026-27446. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat rates this flaw as IMPORTANT severity because it does not enable remote code execution or system compromise (arbitrary code execution), which is Red Hat's threshold for Critical impact. Its impact is limited to message injection and exfiltration via rogue broker federation. Exploitation requires the broker to…

Product	Fixed in	Advisory
Red Hat AMQ Broker 7.12.6	`artemis-server`	RHSA-2026:3955
Red Hat AMQ Broker 7.13.4	`artemis-server`	RHSA-2026:3957
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14	`artemis-server`	RHSA-2026:17668
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7	`eap7-activemq-artemis-0:2.16.0-22.redhat_00057.1.el7eap`	RHSA-2026:53644
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 8	`eap7-activemq-artemis-0:2.16.0-22.redhat_00057.1.el8eap`	RHSA-2026:53645
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 9	`eap7-activemq-artemis-0:2.16.0-22.redhat_00057.1.el9eap`	RHSA-2026:53646
Red Hat JBoss Enterprise Application Platform 8.1.7.GA	`org.apache.activemq/artemis-server:2.40.0.redhat-00015`	RHSA-2026:18059
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 8	`eap8-activemq-artemis-0:2.40.0-6.redhat_00012.1.el8eap`	RHSA-2026:18054

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-27446 in your dependencies?

O3 Security finds CVE-2026-27446 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works