CVE-2026-27446

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 10.0%, top 5% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 .

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
1.2%
EPSS %ILE
66th
KEV
Not listed

Published

March 4, 2026

Last Modified

September 18, 2026

Advisory Details (12)

Auto-updated Oct 9, 2026
Patch available. Sources: redhat.
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7. Red Hat Product Security has rated this update as having a security impact of Important. A Common

https://access.redhat.com/errata/RHSA-2026:53644
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:3957
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:3955
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8. Red Hat Product Security has rated this update as having a security impact of Important. A Common

https://access.redhat.com/errata/RHSA-2026:18059
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9. Red Hat Product Security has rated this update as having a security impact of Important. A Common

https://access.redhat.com/errata/RHSA-2026:18055
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8. Red Hat Product Security has rated this update as having a security impact of Important. A Common

https://access.redhat.com/errata/RHSA-2026:18054
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:17668
generic

oss-security - Re: CVE-2026-27446: Apache Artemis, Apache ActiveMQ Artemis: Auth bypass for Core downstream federation

http://www.openwall.com/lists/oss-security/2026/03/04/1
generic

oss-security - CVE-2026-27446: Apache Artemis, Apache ActiveMQ Artemis: Auth bypass for Core downstream federation

http://www.openwall.com/lists/oss-security/2026/03/03/4
redhatMentions a patch (unverified)

CVE-2026-27446 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-27446

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhateap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el9eap2026-08-11redhat
redhateap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el7eap2026-08-11redhat
redhatartemis-server2026-08-11redhat
redhateap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el8eap2026-08-11redhat
redhateap8-activemq-artemis-0:2.40.0-6.redhat_00012.1.el9eap2026-05-18redhat
redhatorg.apache.activemq/artemis-server:2.40.0.redhat-000152026-05-18redhat
redhateap8-activemq-artemis-0:2.40.0-6.redhat_00012.1.el8eap2026-05-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
org.apache.activemq:artemis-server2.11.0 ... 2.44.0 (39 versions)
  • 2.11.0 through 2.44.0: no fix on record
—
org.apache.artemis:artemis-server2.50.0, 2.51.0
  • 2.50.0 up to 2.52.0: fixed in 2.52.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 252 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:11 UTCEPSS rescore
  3. 2026-10-08 07:24 UTCOSV refresh
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-06 15:17 UTCEPSS rescore
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-04 23:21 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-26 00:26 UTCEPSS rescore
  14. 2026-09-20 20:15 UTCEPSS rescore
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-18 19:27 UTCEPSS rescore
  18. 2026-09-18 13:18 UTCVendor advisory
  19. 2026-09-18 12:20 UTCEG score recompute
  20. 2026-09-18 12:20 UTCVendor advisory
  21. 2026-09-17 19:30 UTCEPSS rescore
  22. 2026-09-16 14:08 UTCEPSS rescore
  23. 2026-09-16 05:15 UTCEPSS rescore
  24. 2026-09-15 12:14 UTCEG score recompute
  25. 2026-09-15 12:14 UTCVendor advisory
Show 75 more
  1. 2026-09-14 13:39 UTCVendor advisory
  2. 2026-09-14 12:36 UTCEG score recompute
  3. 2026-09-14 12:36 UTCVendor advisory
  4. 2026-09-12 15:01 UTCEPSS rescore
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:11 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-09-01 00:04 UTCOSV refresh
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:48 UTCEPSS rescore
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
  26. 2026-08-18 13:48 UTCEPSS rescore
  27. 2026-08-17 13:47 UTCEPSS rescore
  28. 2026-08-16 14:56 UTCEPSS rescore
  29. 2026-08-16 02:14 UTCEPSS rescore
  30. 2026-08-15 01:30 UTCEPSS rescore
  31. 2026-08-15 00:36 UTCVendor advisory
  32. 2026-08-14 20:58 UTCVendor advisory
  33. 2026-08-14 15:55 UTCVendor advisory
  34. 2026-08-14 12:16 UTCVendor advisory
  35. 2026-08-14 08:37 UTCEG score recompute
  36. 2026-08-14 08:37 UTCVendor advisory
  37. 2026-08-13 22:00 UTCEPSS rescore
  38. 2026-08-13 04:04 UTCVendor advisory
  39. 2026-08-13 00:26 UTCEG score recompute
  40. 2026-08-13 00:26 UTCVendor advisory
  41. 2026-08-12 13:50 UTCEPSS rescore
  42. 2026-08-12 12:39 UTCVendor advisory
  43. 2026-08-12 12:14 UTCVendor advisory
  44. 2026-08-11 23:18 UTCEG score recompute
  45. 2026-08-11 23:18 UTCVendor advisory
  46. 2026-08-11 13:42 UTCEPSS rescore
  47. 2026-08-11 05:52 UTCEG score recompute
  48. 2026-08-11 05:52 UTCVendor advisory
  49. 2026-08-11 00:00 UTCEPSS rescore
  50. 2026-08-10 13:05 UTCVendor advisory
  51. 2026-08-10 08:16 UTCVendor advisory
  52. 2026-08-10 04:37 UTCVendor advisory
  53. 2026-08-10 00:55 UTCVendor advisory
  54. 2026-08-09 21:16 UTCVendor advisory
  55. 2026-08-09 17:37 UTCVendor advisory
  56. 2026-08-09 13:38 UTCVendor advisory
  57. 2026-08-09 08:15 UTCEG score recompute
  58. 2026-08-09 08:15 UTCVendor advisory
  59. 2026-08-08 16:37 UTCEPSS rescore
  60. 2026-08-08 11:33 UTCVendor advisory
  61. 2026-08-08 07:04 UTCVendor advisory
  62. 2026-08-08 03:25 UTCVendor advisory
  63. 2026-08-07 23:47 UTCVendor advisory
  64. 2026-08-07 20:08 UTCEG score recompute
  65. 2026-08-07 20:08 UTCVendor advisory
  66. 2026-08-06 13:46 UTCEPSS rescore
  67. 2026-08-06 06:22 UTCVendor advisory
  68. 2026-08-06 02:43 UTCEG score recompute
  69. 2026-08-06 02:43 UTCVendor advisory
  70. 2026-08-05 19:17 UTCEPSS rescore
  71. 2026-08-04 15:10 UTCEPSS rescore
  72. 2026-08-04 13:27 UTCVendor advisory
  73. 2026-08-04 12:36 UTCEG score recompute
  74. 2026-08-04 12:36 UTCVendor advisory
  75. 2026-08-04 04:25 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-27446?
CVE-2026-27446 is a critical vulnerability published on March 4, 2026. 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…
When was CVE-2026-27446 disclosed?
CVE-2026-27446 was first published on March 4, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27446 actively exploited?
CVE-2026-27446 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27446?
CVE-2026-27446 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-27446?
A fix for CVE-2026-27446 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-27446 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27446

Explore →

Is Your Infrastructure Affected by CVE-2026-27446?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.