Software 45229 Published by

Matomo 5.14.3 has been released as a routine patch with no major new features or database upgrade. The release hardens the AI machinery it launched in September, adding consent gates, per-request search caps, cost reporting, and usage metering to make AI tools safer and more billable. It also gives admins a documented escape hatch, letting them suppress the October PHP vulnerability alert via a new config setting. As a maintenance build, it polishes AI governance and compliance auditing rather than introducing anything flashy, with a 6.0.0 release candidate already on the horizon.



Matomo 5.14.3 ships as a patch that leans into AI governance and silences the PHP vulnerability nag

Matomo, the open-source privacy-first analytics platform that bills itself as a Google Analytics alternative, released v5.14.3. This is a maintenance release, so there are no new features and major database changes here.

Matomo 5.14.3 has been released with various small updates. Matomo is quietly turning its AI machinery into something you can actually govern. Second, admins finally get a documented way to mute the scary PHP alert that the platform spent the last month screaming about.

screenshot_from_2026_08_17_06_07_43.webp?ver=1786940806153

AI is about the plumbing now

The AI Providers plugin shipped in 5.14.0. It centralizes credentials for OpenAI, Anthropic, Google, and AWS Bedrock, then powers everything from goal recommendations to grounding, where the tool searches the web before answering. The 5.14.3 changes are the unglamorous but necessary plumbing around that.

Matomo now requires AI data-processing consent before running goal recommendations ( #25380, #25405, #25557). It reports provider-billed cost directly in responses ( #25392), and caps how many web searches a single grounded call may make at a default of two ( #25470). It also publishes lifecycle events like beforeRequest and usage so external systems can meter or limit AI spending ( #25515, #25440).

Grounding isn't free, after all. Every search costs money, and each retrieved page gets billed as input tokens, so a runaway API call can quietly eat into your budget over time. The per-request search cap is the guardrail that keeps a clever demo from becoming a surprise invoice.

The compliance side got smaller but sharper work. A new audit trail ( #25375) shows exactly which policy settings a request changed, and plugins can now order their controls instead of being stuck in discovery order ( #25400). Regulators increasingly care less about whether you have a setting and more about whether you can prove who changed what and when.

Muting the October PHP alarm

You can't fully grasp 5.14.3 without the scare that shaped the last two releases. On October 21, the PHP security team published an accelerated advisory for two critical vulnerabilities in the interpreter that Matomo itself runs on. CVE-2026-109618 and CVE-2026-109619 both score 9.2 out of 10. Both enable remote code execution. In the worst case, an unauthenticated remote attacker could take over a server before any application code even runs, particularly via Apache with mod_php. CISA, Cisco, and Palo Alto's Unit 42 all flagged it as a top-tier alert.

Fixes rolled out fast: PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. But the remediation depends on where you run Matomo. Cloud customers needed nothing. Matomo's managed infrastructure was already patched. Self-hosted users had to patch their server's PHP immediately, and the company made a deliberate point that updating the app alone wouldn't fix the hole. The flaw lives in the runtime, not the code.

That warning went live in 5.14.2. By mid-November, a lot of admins had either patched their PHP or simply wanted the banner gone. Some Linux distros backported the fix without bumping the version number, which is exactly the scenario that makes a heuristic warning keep firing when it shouldn't.

So 5.14.3 adds an official, config-based escape hatch. A new [General] disabled_notifications[] setting lists notification IDs to hide. Right now it can suppress exactly one: PhpSecurityAdvisory_2026_10_21, the warning about the critical PHP vulnerabilities. Same contributor who built the original alert, chippison.

A few more loose ends

The rest of the patch rounds out a handful of features. Weekly and monthly scheduled reports now respect a site's local timezone ( #25495, #24980), which matters for anyone running a multi-national setup where report timing used to drift. And the redesigned Marketplace from 5.14.0 got more rough edges smoothed: top controls are now hidden on the overview ( #25457), a cluster of Marketplace issues is fixed ( #25511), and bodyless requests now use GET for cleaner HTTP semantics ( #25541).

That Marketplace overhaul was the most visible part of the whole 5.14 cycle, and it took three patch releases just to make it presentable. It's arguably competing with the best of them now, but for a platform this size, that kind of late going is worth raising an eyebrow at.

Matomo 5.14.3 is available now. Head here to the GitHub release page.

Install Matomo on Debian 13: Complete Self-Hosted Analytics Guide

This tutorial walks through installing the latest Matomo version on Debian 13, bypassing the outdated repository release to access features like AI chatbot detection, Dark Mode, and improved segment management.

Install Matomo on Debian 13: Complete Self-Hosted Analytics Guide