Vulnerability in api-platform/core (CVE-2026-49858)
Summary
Vulnerability in api-platform/core (CVE-2026-49858). Confidential information can be exposed externally. Exploitable via componentsCache. Mitigation: upgrade to 4.3.8 or later.
Original description
The description as published by the source.
API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. In versions from 2.6.0 prior to 4.1.29, 4.2.26, and 4.3.12, a missing isCacheKeySafe gate in the JSON:API and HAL item normalizers causes a cross-user attribute leak. #[ApiProperty(security: ...)] is evaluated per request to decide whether a property is exposed. The componentsCache arrays in ApiPlatform\JsonApi\Serializer\ItemNormalizer and ApiPlatform\Hal\Serializer\ItemNormalizer are keyed on $context['cache_key'], which is set unconditionally before delegating to the parent normalizer. The component structure (attributes, relationships, links) computed for one request can therefore be reused for a subsequent request whose user has a different set of accessible properties. A user with lower privileges may end up seeing the structure of properties that the security predicate would otherwise have hidden for them. This issue has been fixed in versions 4.1.29, 4.2.26, and 4.3.12.
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-49858 has been found in api-platform/core.
Attackers can target a specific entry point like componentsCache over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade api-platform/core to 4.3.8 or later.
If unsure, ask your IT team or search "api-platform/core CVE-2026-49858" on the vendor's site.
CVE-2026-49858 (api-platform/core) — CWE-524 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: componentsCache / ItemNormalizer / true / false
Patched: 4.3.8 — apply immediately
Workaround: Override the JSON:API and HAL ItemNormalizer services to gate $context['cache_key'] with a resource-class security check, or avoid #[ApiProperty(security: ...)] on resources served as JSON:API or HAL until the patch is applied.
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-524) exists in api-platform/core. Attackers reach the vulnerable code path via componentsCache without authentication.
Check the vendor advisory for the affected versions of api-platform/core. Attack surface: componentsCache / ItemNormalizer / true / false.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 4.3.8.
Workaround: Override the JSON:API and HAL ItemNormalizer services to gate $context['cache_key'] with a resource-class security check, or avoid #[ApiProperty(security: ...)] on resources served as JSON:API or HAL until the patch is applied.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Override the JSON:API and HAL `ItemNormalizer` services to gate `$context['cache_key']` with a resource-class security check, or avoid `#[ApiProperty(security: ...)]` on resources served as JSON:API or HAL until the patch is applied.パッチが適用されるまでの応急処置として、Override the JSON:API and HAL
ItemNormalizerservices to gate$context['cache_key']with a resource-class security check, or avoid#[ApiProperty(security: ...)]on resources served as JSON:API or HAL until the patch is applied. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade api-platform/core to 4.3.8ステージング環境で 4.3.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-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
- web github.com