A graphic featuring the text "meshIQ®" in a modern font. The design emphasizes clean lines and a minimalist aesthetic, suitable for branding or logo use.

The meshIQ blog.

Our blog offers insights into pivotal and disruptive technologies, including Hybrid Cloud, Messaging Middleware, AI, and more, contributed by meshIQ experts and innovators.

Featured.

Apache ActiveMQ®, IBM, IBM MQ, IBM WebSphere, MQ

IBM MQ Alternatives: When ActiveMQ and Artemis Make Sense

What IBM MQ costs an organisation is a knowable figure. It comes off a renewal statement, an entitlement count or a licensing review, and finance can put a number against it down to the core. What replacing it would save is not knowable in the same way. There is no independent case study in the public record carrying real durations, team sizes and application counts, and every migration timeline in circulation comes from an organisation selling the migration.

IBM MQ Alternatives: When ActiveMQ and Artemis Make Sense

Apache ActiveMQ®, Messaging, Middleware, Middleware Optimization, MQ

CVE-2025-54539 & CVE-2025-29953: Apache ActiveMQ® .NET Client RCE

Most Apache ActiveMQ® security advice is about the broker. CVE-2025-54539 and CVE-2025-29953 turn that around: the broker attacks the application. A broker that has been compromised, impersonated or simply isn’t yours can send a crafted message to an Apache ActiveMQ® .NET client, and the client runs the attacker’s code while reading it.

CVE-2025-54539 & CVE-2025-29953: Apache ActiveMQ® .NET Client RCE

Apache ActiveMQ®, Messaging, Middleware, Monitoring, MQ

CVE-2026-34197: Apache ActiveMQ® Jolokia RCE (CISA KEV Alert)

CVE-2026-34197 is a Jolokia RCE flaw in Apache ActiveMQ® Classic, reached through the broker’s Jolokia management API. Apache disclosed it on 6 April 2026. Ten days later, CISA added it to its Known Exploited Vulnerabilities (KEV) catalog, with a remediation deadline for US federal agencies of 30 April.

CVE-2026-34197: Apache ActiveMQ® Jolokia RCE (CISA KEV Alert)

Apache ActiveMQ®, Messaging, Middleware, Middleware Optimization, Monitoring, MQ

The Jolokia Problem: Eight CVEs, One Door in Apache ActiveMQ®

The Apache ActiveMQ® Jolokia endpoint has been the route to remote code execution in three separate years. In 2023, it was reflection into the JVM. In 2024, a default configuration left it without a login. In 2026, it was the broker’s own management operations, patched in March, exploited in April, and reopened three more times by summer.

The Jolokia Problem: Eight CVEs, One Door in Apache ActiveMQ®

Apache ActiveMQ®, Messaging, Middleware, Middleware Optimization, Monitoring, MQ

10 Questions to Ask an Apache ActiveMQ® Support Vendor

Deciding to buy open source support for Apache ActiveMQ® is the easy part. Working out which vendor can actually keep a broker alive at three in the morning is considerably harder, because nearly every vendor in this market is vague in exactly the same places.

10 Questions to Ask an Apache ActiveMQ® Support Vendor

AIOps, Cloud Security, Compliance, meshIQ, Observability

Banks Found AI Agents Inside Customer Accounts. Nobody Approved What They Did.

Major US banks have found AI agents operating inside customer accounts, signed in with credentials customers handed over themselves. Nothing was breached. The agents authenticated correctly, and some of them still did things nobody asked for. That gap between having access and having authority is the agentic AI security problem every enterprise running agents now owns.

Banks Found AI Agents Inside Customer Accounts. Nobody Approved What They Did.

Apache ActiveMQ®, Messaging, Middleware, Middleware Optimization, MQ

Apache ActiveMQ® CVE-2023-46604: DripDropper Exploit Explained

When a CVSS 10.0 vulnerability is published, the expectation is that affected software gets patched within days. When it involves an open-source broker that processes business-critical transactions in enterprise environments, the expectation is that the security teams responsible for those brokers treat it as an emergency. “The attacks exploit a maximum-severity security flaw in Apache

Apache ActiveMQ® CVE-2023-46604: DripDropper Exploit Explained

Apache ActiveMQ®, Messaging, Middleware, Middleware Optimization

Apache ActiveMQ® CVE Guide: Complete Vulnerability Reference

This Apache ActiveMQ® CVE guide is the maintained reference for every significant Apache ActiveMQ® vulnerability: what it does, how it is scored, which versions it affects, which release fixes it, and whether it is being exploited.

Apache ActiveMQ® CVE Guide: Complete Vulnerability Reference

AIOps, Cloud Security, Compliance, Integration, meshIQ

What Are AI Agents? How They Work, Why They Matter and Why They Need Governance

An AI agent doesn’t just answer questions—it takes actions in real systems. As teams across the enterprise build their own agents, governance can’t be an afterthought. Learn how agents work, why they create new risks, and what controls are needed before they act, not after.

What Are AI Agents? How They Work, Why They Matter and Why They Need Governance

AIOps, Cloud Security, Compliance, Integration, meshIQ

Agentic AI Is Becoming the Enterprise’s Connective Tissue. Governance Has to Move Into the Flow.

McKinsey’s 2026 tech report calls agentic AI the ‘connective tissue of the enterprise.’ But agents that act at machine speed need governance at machine speed too. Static controls won’t work for dynamic agents—active, in-flow guardrails must run before the action, not after.

Agentic AI Is Becoming the Enterprise’s Connective Tissue. Governance Has to Move Into the Flow.

AIOps, Cloud Security, Compliance, Devops, meshIQ

Governing AI Agents From the Inside: What We Learned Building AgentPatrol™

When every employee is building AI agents, seeing what they did afterward isn’t enough. AgentPatrol™’s in-flow governance runs inside the agent’s execution flow—pausing for human approval, enforcing policies by value, masking PII, and stopping runaway agents before costs spiral.

Governing AI Agents From the Inside: What We Learned Building AgentPatrol™

Apache Kafka®, AWS, Integration, meshIQ, Middleware, Streaming

Moving Mainframe Data to Snowflake and AWS Through Apache Kafka®: Treehouse Software and meshIQ

Treehouse Dataflow Toolkit moves mainframe data from Db2, VSAM, and IMS through Apache Kafka® pipelines into Snowflake and AWS targets. meshIQ keeps the streaming layer visible and stable. Together they give data science teams continuously updated enterprise data for AI and ML.

Moving Mainframe Data to Snowflake and AWS Through Apache Kafka®: Treehouse Software and meshIQ

Cookies preferences

✕

Others

Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.

Necessary

Necessary
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.

Advertisement

Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.

Analytics

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.

Functional

Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.

Performance

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.