CVE-2026-31891

Cockpit CMS has SQL Injection in MongoLite Aggregation Optimizer via toJsonExtractRaw()

This is a SQL Injection vulnerability in the MongoLite Aggregation Optimizer.

Any Cockpit CMS instance running version 2.13.4 or earlier with API access enabled
is potentially affected.

Who is impacted:

• Any deployment where the /api/content/aggregate/{model} endpoint is publicly
  accessible or reachable by untrusted users.
• Attackers in possession of a valid read-only API key (the lowest privilege level)
  can exploit this vulnerability, no admin access is required.

What an attacker can do:

• Inject arbitrary SQL via unsanitized field names in aggregation queries.
• Bypass the _state=1 published-content filter to access unpublished or restricted content.
• Extract unauthorized data from the underlying SQLite content database.

Confidentiality impact is High. Integrity and availability are not directly affected
by this vulnerability.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2026-31891 has a CVSS score of 7.7 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.13.5); upgrading removes the vulnerable code path.

Kodem intelligence

This vulnerability has been patched in version 2.13.5.

All users running Cockpit CMS version 2.13.4 or earlier are strongly advised to
upgrade to 2.13.5 or later immediately.

• https://github.com/Cockpit-HQ/Cockpit/releases/tag/2.13.5

The fix applies the same field-name sanitization introduced in v2.13.3 for toJsonPath()
to the toJsonExtractRaw() method in lib/MongoLite/Aggregation/Optimizer.php,
closing the injection vector in the Aggregation Optimizer.

1. What is CVE-2026-31891? CVE-2026-31891 is a high-severity SQL injection vulnerability in cockpit-hq/cockpit (composer), affecting versions < 2.13.5. It is fixed in 2.13.5. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2026-31891? CVE-2026-31891 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of cockpit-hq/cockpit are affected by CVE-2026-31891? cockpit-hq/cockpit (composer) versions < 2.13.5 is affected.
4. Is there a fix for CVE-2026-31891? Yes. CVE-2026-31891 is fixed in 2.13.5. Upgrade to this version or later.
5. Is CVE-2026-31891 exploitable, and should I be worried? Whether CVE-2026-31891 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-31891 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-31891? Upgrade cockpit-hq/cockpit to 2.13.5 or later.