Possible Apache ActiveMQ RCE via Jolokia addNetworkConnector (via webserver)

PremiumReviewedSigma · High · v1
Category
webserver
Author
HuntRule
Published
2026-09-27
Updated
2026-09-27

ATT&CK techniques

Initial Access → Execution
  1. Recon

  2. Resource Dev

  3. Persistence

  4. Priv Esc

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects HTTP requests to the ActiveMQ Jolokia API that invoke the addNetworkConnector broker operation with a remote xbean configuration URI. This corresponds to CVE-2026-34197 remote code execution where the broker loads an attacker hosted Spring bean. Administrators rarely add network connectors that reference external HTTP xbean configs.

Related detections9 linkedT1059 — drag to rearrange
Possible LiteLLM Unauthenticated Command Execution via MCP Test Endpoints (via webserver)
Possible Ivanti Cloud Services Appliance Command Injection via datetime.php (via webserver)
Possible Log4Shell Exploitation via Java Spawning Shell or Download Utility
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Possible Craft CMS RCE via Query-String CLI Option Injection
Possible Aspera Faspex Pre-Auth RCE via YAML Deserialization in package_relay (via webserver)
Possible Sitecore Pre-Auth RCE via Report.ashx Insecure Deserialization (via webserver)
Possible WatchGuard Pre-Auth RCE via agent login XML-RPC CVE-2022-26318
Possible Oracle Opera CGI Webshell Command Execution via operabin
Possible Apache ActiveMQ RCE via Jolokia addNetworkConnector (via webserver)
Pivot detection · T1059 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.