Vulnerability in phalcon/cphalcon (CVE-2026-57584)
Summary
Vulnerability in phalcon/cphalcon (CVE-2026-57584). Risk of unauthorized operations or information disclosure. Exploitable via URI_SOURCE_GET_URL. Mitigation: upgrade to 5.15.0 or later.
Original description
The description as published by the source.
Phalcon is a high-performance, full-stack PHP framework. Prior to 5.15.0, every Phalcon MVC application built with a default router registers a built-in route whose compiled PCRE pattern contains the nested quantifier (/.), and the same construct is produced by the /:params placeholder and the CLI router. Phalcon\Mvc\Router::handle() matches this pattern against the attacker-controlled request URI on every request, so a crafted path such as one containing repeated slashes followed by decoded newlines can trigger catastrophic backtracking and cause CPU exhaustion or route-matching failure. This issue is fixed in version 5.15.0.
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-57584 has been found in phalcon/cphalcon.
Attackers can target a specific entry point like URI_SOURCE_GET_URL over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade phalcon/cphalcon to 5.15.0 or later.
If unsure, ask your IT team or search "phalcon/cphalcon CVE-2026-57584" on the vendor's site.
CVE-2026-57584 (phalcon/cphalcon) — CWE-1333
Attack surface: URI_SOURCE_GET_URL / URI_SOURCE_SERVER_REQUEST_URI / REQUEST_URI / pcre.backtrack_limit
Patched: 5.15.0 — apply immediately
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-1333) exists in phalcon/cphalcon. Attackers reach the vulnerable code path via URI_SOURCE_GET_URL.
Check the vendor advisory for the affected versions of phalcon/cphalcon. Attack surface: URI_SOURCE_GET_URL / URI_SOURCE_SERVER_REQUEST_URI / REQUEST_URI / pcre.backtrack_limit.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.15.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'phalcon/cphalcon' . 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 'phalcon/cphalcon' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
phalcon/cphalconを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade phalcon/cphalcon to 5.15.0ステージング環境で 5.15.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com