Categories
CVE-2026-55590 medium CVSS 6.1

Open Redirect in cakephp/authentication (CVE-2026-55590)

Summary

Vulnerability in cakephp/authentication (CVE-2026-55590). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.11.1 or later.

Original description

The description as published by the source.

CakePHP Authentication is an authentication plugin for CakePHP that can also be used in PSR-7 based applications. Prior to 2.11.1, 3.3.6, and 4.1.1, the getLoginRedirect() method contains a weakness to backslash bypasses that allows redirect targets with attacker-controlled hostnames through the redirect query string parameter. This issue is fixed in versions 2.11.1, 3.3.6, and 4.1.1.

Source: GitHub Security Advisories (Global) 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-55590 has been found in cakephp/authentication.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade cakephp/authentication to 2.11.1 or later.
If unsure, ask your IT team or search "cakephp/authentication CVE-2026-55590" on the vendor's site.

CVE-2026-55590 (cakephp/authentication) — CWE-601 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.11.1 — apply immediately
Workaround: If you are unable to upgrade, you should consider adding application validation to the redirect query string parameter to mitigate this vulnerability.
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.

❓ What is the problem

A vulnerability (CWE-601) exists in cakephp/authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of cakephp/authentication.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.11.1.

🛡️ Workaround

Workaround: If you are unable to upgrade, you should consider adding application validation to the redirect query string parameter to mitigate this vulnerability.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'cakephp/authentication' . 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

  1. 1
    Identify exposure identify
    grep -r 'cakephp/authentication' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で cakephp/authentication を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    If you are unable to upgrade, you should consider adding application validation to the redirect query string parameter to mitigate this vulnerability.

    パッチが適用されるまでの応急処置として、If you are unable to upgrade, you should consider adding application validation to the redirect query string parameter to mitigate this vulnerability. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade cakephp/authentication to 2.11.1

    ステージング環境で 2.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer cakephp/authentication
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.1"}]}]
Packagist cakephp/authentication
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details