← Back
CVE-2026-54164
medium
CVSS 6.5
Vulnerability in api-platform/core (CVE-2026-54164)
Summary
vulnerability in api-platform/core (CVE-2026-54164). Data can be tampered with by attackers. Exploitable via ``AbstractItemNormalizer``. Mitigation: upgrade to `4.3.12` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54164** has been found in api-platform/core.
Attackers can target a specific entry point like ``AbstractItemNormalizer`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade api-platform/core to **4.3.12** or later.
If unsure, ask your IT team or search "api-platform/core CVE-2026-54164" on the vendor's site.
CVE-2026-54164 (api-platform/core) — CWE-843 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `AbstractItemNormalizer` / `is_a` / `InvalidTypeException` / `InvalidArgumentException`
Patched: `4.3.12` — apply immediately
Workaround: Declare a PHP type on every writable relation property (e.g.
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-843) exists in api-platform/core. Attackers reach the vulnerable code path via ``AbstractItemNormalizer`` without authentication.
📍 Affected scope
api-platform/core — . Attack surface: `AbstractItemNormalizer` / `is_a` / `InvalidTypeException` / `InvalidArgumentException`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **4.3.12**.
🛡️ Workaround
Workaround: Declare a PHP type on every writable relation property (e.g.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'api-platform/core' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'api-platform/core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `api-platform/core` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Declare a PHP type on every writable relation property (e.g.パッチが適用されるまでの応急処置として、Declare a PHP type on every writable relation property (e.g. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade api-platform/core to 4.3.12ステージング環境で 4.3.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
api-platform/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.3.12"}]}]
References
- web https://github.com/api-platform/core/security/advisories/GHSA-9rjg-x2p2-h68h
- web https://nvd.nist.gov/vuln/detail/CVE-2026-54164
- web https://github.com/api-platform/core/commit/6bcbeb2dbee53db5bb9b4b8e343bffdf7732de1e
- web https://github.com/api-platform/core/releases/tag/v4.1.30
- web https://github.com/api-platform/core/releases/tag/v4.2.26
- web https://github.com/api-platform/core/releases/tag/v4.3.12
- web https://github.com/advisories/GHSA-9rjg-x2p2-h68h