Vulnerability in cakephp/cakephp (CVE-2026-77634)
Summary
Vulnerability in cakephp/cakephp (CVE-2026-77634). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.3.7 or later.
Original description
The description as published by the source.
Impact
Custom mail headers added with Message::setHeaders() or addHeaders() do not have CRLF replaced allowing header injection if user controlled data is added to message headers without stripping CRLF bytes.
Patches
5.3.7, 5.2.14, 5.1.9, 4.6.5, 4.5.12 contain fixes for this issue.
Workarounds
You can strip CRLF bytes from email header values before setting header values.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-77634 has been found in cakephp/cakephp.
Risk of unauthorized operations or information disclosure.
What to do: upgrade cakephp/cakephp to 5.3.7 or later.
If unsure, ask your IT team or search "cakephp/cakephp CVE-2026-77634" on the vendor's site.
CVE-2026-77634 (cakephp/cakephp) — CWE-93
Patched: 5.3.7 — apply immediately
Workaround: You can strip CRLF bytes from email header values before setting header values.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-93) exists in cakephp/cakephp.
Check the vendor advisory for the affected versions of cakephp/cakephp.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.3.7.
Workaround: You can strip CRLF bytes from email header values before setting header values.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'cakephp/cakephp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'cakephp/cakephp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
cakephp/cakephpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
You can strip CRLF bytes from email header values before setting header values.パッチが適用されるまでの応急処置として、You can strip CRLF bytes from email header values before setting header values. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade cakephp/cakephp to 5.3.7ステージング環境で 5.3.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-77634 cakephp
- Ubuntu UBUNTU-CVE-2026-77634 cakephp
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com