News
BridgeLink 26.6.0 Is Here
BridgeLink 26.6.0 is available now. It is a security-focused release, batch-upgrading third-party libraries across every module, and it is the release that BridgeLink WebAdmin ships alongside.
Security: CVE dependency upgrades
Third-party libraries were upgraded across all modules (server, client, donkey, CLI, manager, and WebAdmin) to remediate known CVEs. netty moves from 4.1.119.Final to 4.1.135.Final, addressing CVE-2026-44249, CVE-2026-45416, and CVE-2026-50010. log4j moves from 2.25.3 to 2.25.4, addressing CVE-2026-34477, CVE-2026-34478, CVE-2026-34479, and CVE-2026-34480. Jetty, commons-io, commons-configuration2, commons-fileupload, commons-compress, pdfbox, and the PostgreSQL JDBC driver were upgraded as well.
Two deliberate exceptions: Rhino stays at 1.7.13 for JavaScript compatibility and stability, and the xstream and BouncyCastle upgrades were evaluated and intentionally deferred to a future release pending regression testing.
Phone-home disabled
Server-side usage and registration reporting is now disabled. BridgeLink no longer attempts to send usage statistics to external endpoints.
BridgeLink WebAdmin
The new browser-based administration console debuts with this release. There is no Java runtime to install and nothing to deploy per workstation.
MySQL table case migration
Older releases could create the message storage tables in lowercase on case-sensitive MySQL servers, which then failed when the engine later referenced the uppercase names. 26.6.0 ships a schema migration that renames those tables to uppercase on first startup.
It runs only on MySQL configured with lower_case_table_names=0, the Linux default; Windows and macOS installations are case-insensitive and are skipped. It is also skipped automatically when the tables are already uppercase, so a healthy installation needs no action. No serialized data changes, and all other database types are unaffected.
Channel context in server logs
Server log lines can now be enriched with the channel context they were emitted from, including channel ID, channel name, connector name, message ID, and script phase. Triage across many channels gets considerably easier.
It is opt-in: set log.channelcontext.enabled=true in mirth.properties. The default is false, which preserves the legacy log format. Context propagates through source and destination connectors, poll jobs, recovery tasks, and user script execution.
Version History and Message Trends
Version History 3.0.2 adds a configurable commit limit to the history views (Channel, Code Template, Global Scripts, and Library), preventing slow loads and timeouts on repositories with long histories.
Message Trends 1.1.0 now replaces time-series rollup windows atomically using database upserts on MySQL, PostgreSQL, SQL Server, and Oracle, preventing duplicate or stale aggregate rows when a window is recalculated.