# CVE-2026-119419: CakePHP through 5.4.3 SQL Injection via StringExpression and IdentifierExpression Collation


- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 30 Oct 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-6q38-2qcr-3x34, UBUNTU-CVE-2026-119419

## What is CVE-2026-119419?

CVE-2026-119419 is a critical vulnerability in cakephp, published on 30 Oct 2026. 

### Official description

CakePHP through 5.4.3 contains an sql injection vulnerability that allows attackers to inject SQL by supplying unvalidated collation values to StringExpression and IdentifierExpression. Attackers controlling a collation name passed to the constructor or setCollation() can append SQL after the unquoted COLLATE clause, affecting every database driver within the connection's privileges.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-119419?


## How do I fix CVE-2026-119419?

Upgrade to a fixed version.

## Is CVE-2026-119419 being exploited?

There is no known exploitation of CVE-2026-119419 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119419 and fix it if it is affected.

What it is: CVE-2026-119419 is a critical vulnerability in cakephp, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119419 in the wild and no public exploit code.

Affected product: cakephp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119419/ (Markdown: https://insights.sbomify.com/CVE-2026-119419/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119419
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119419
- OSV: https://osv.dev/vulnerability/CVE-2026-119419

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119419/
Summaries are generated and may contain mistakes; the official description above is the record.