What is CVE-2026-77635?

CVE-2026-77635 is a critical-severity SQL injection vulnerability in cakephp/cakephp (composer), affecting versions >= 5.3.0, < 5.3.7. It is fixed in 5.3.7, 5.2.15, 5.1.10. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

Which packages are affected by CVE-2026-77635?

cakephp/cakephp (composer) versions >= 5.3.0, = 5.3.0, < 5.3.7.

Is there a fix for CVE-2026-77635?

Yes. CVE-2026-77635 is fixed in 5.3.7, 5.2.15, 5.1.10. Upgrade to this version or later.

Is CVE-2026-77635 exploitable, and should I be worried?

Whether CVE-2026-77635 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.

What actually determines whether CVE-2026-77635 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.

How do I fix CVE-2026-77635?

Upgrade: cakephp/cakephp to 5.3.7 or later, cakephp/cakephp to 5.2.15 or later, cakephp/cakephp to 5.1.10 or later, cakephp/database to 5.3.7 or later, cakephp/database to 5.2.15 or later, cakephp/database to 5.1.10 or later.

CVE-2026-77635 in cakephp/cakephp

Q: Which packages are affected by CVE-2026-77635?

cakephp/cakephp (composer) versions >= 5.3.0, = 5.3.0, < 5.3.7.

Q: Is there a fix for CVE-2026-77635?

Yes. CVE-2026-77635 is fixed in 5.3.7, 5.2.15, 5.1.10. Upgrade to this version or later.

Q: Is CVE-2026-77635 exploitable, and should I be worried?

Whether CVE-2026-77635 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.

Q: What actually determines whether CVE-2026-77635 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.

Q: How do I fix CVE-2026-77635?

Upgrade: cakephp/cakephp to 5.3.7 or later, cakephp/cakephp to 5.2.15 or later, cakephp/cakephp to 5.1.10 or later, cakephp/database to 5.3.7 or later, cakephp/database to 5.2.15 or later, cakephp/database to 5.1.10 or later.

Summary

CakePHP: FunctionsBuilder::jsonValue() vulerable to SQL injection with PostgresDriver

Workarounds

Don't provide user controlled data to these functions/parameters.

Impact

The FunctionsBuilder::jsonValue($field, $jsonPath) methods with the Postgres driver is vulnerable to SQL injection if user controlled data is supplied to the $jsonPath parameter.

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.

Affected versions

cakephp/cakephp (>= 5.3.0, < 5.3.7) cakephp/cakephp (>= 5.2.0, < 5.2.15) cakephp/cakephp (>= 5.1.0, < 5.1.10) cakephp/database (>= 5.3.0, < 5.3.7) cakephp/database (>= 5.2.0, < 5.2.15) cakephp/database (>= 5.1.0, < 5.1.10)

Security releases

cakephp/cakephp → 5.3.7 (composer) cakephp/cakephp → 5.2.15 (composer) cakephp/cakephp → 5.1.10 (composer) cakephp/database → 5.3.7 (composer) cakephp/database → 5.2.15 (composer) cakephp/database → 5.1.10 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

5.1.10, 5.2.15, 5.3.7

Frequently Asked Questions

What is CVE-2026-77635? CVE-2026-77635 is a critical-severity SQL injection vulnerability in cakephp/cakephp (composer), affecting versions >= 5.3.0, < 5.3.7. It is fixed in 5.3.7, 5.2.15, 5.1.10. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
Which packages are affected by CVE-2026-77635?
- cakephp/cakephp (composer) (versions >= 5.3.0, < 5.3.7)
- cakephp/database (composer) (versions >= 5.3.0, < 5.3.7)
Is there a fix for CVE-2026-77635? Yes. CVE-2026-77635 is fixed in 5.3.7, 5.2.15, 5.1.10. Upgrade to this version or later.
Is CVE-2026-77635 exploitable, and should I be worried? Whether CVE-2026-77635 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
What actually determines whether CVE-2026-77635 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.
How do I fix CVE-2026-77635?
- Upgrade cakephp/cakephp to 5.3.7 or later
- Upgrade cakephp/cakephp to 5.2.15 or later
- Upgrade cakephp/cakephp to 5.1.10 or later
- Upgrade cakephp/database to 5.3.7 or later
- Upgrade cakephp/database to 5.2.15 or later
- Upgrade cakephp/database to 5.1.10 or later