CVE-2026-49858: Api platform/core API And HAL Item Normalizers Vulnerability

MODERATE
Advisory Identifier: GHSA-pjhx-3c3w-9v23
CVSS 5.9
CWE-639 CWE-524
Published
Advisory Summary

CVE-2026-49858 is a MODERATE (CVSS 5.9) api and hal item normalizers vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Api platform/core libraries in the Packagist ecosystem. The issue involves api and hal item normalizers due to missing iscachekeysafe gate. Remediation is available by upgrading affected packages to version 4.1.29, 4.2.25, 4.3.8.

CVE-2026-49858 at a Glance

CVE Identifier CVE-2026-49858
GHSA Identifier GHSA-pjhx-3c3w-9v23
Severity MODERATE
CVSS v3.1 Base Score 5.9
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Api platform/core
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 5.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-49858

To remediate this vulnerability, upgrade all affected Api platform/core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

api-platform/core fixed: 4.1.29
Upgrade api-platform/core to 4.1.29
api-platform/core fixed: 4.2.25
Upgrade api-platform/core to 4.2.25
api-platform/core fixed: 4.3.8
Upgrade api-platform/core to 4.3.8
api-platform/json-api fixed: 4.1.29
Upgrade api-platform/json-api to 4.1.29
api-platform/json-api fixed: 4.2.25
Upgrade api-platform/json-api to 4.2.25
api-platform/json-api fixed: 4.3.8
Upgrade api-platform/json-api to 4.3.8
api-platform/hal fixed: 4.1.29
Upgrade api-platform/hal to 4.1.29
api-platform/hal fixed: 4.2.25
Upgrade api-platform/hal to 4.2.25
api-platform/hal fixed: 4.3.8
Upgrade api-platform/hal to 4.3.8
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for api-platform/core

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-49858, inspect your project dependencies for Api platform/core:

inspect dependencies for api-platform/core

Analyze the terminal output to locate any version of Api platform/core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.1.29), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In Api platform/core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact `#[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 is the same vulnerability class as [GHSA-428q-q3vv-3fq3](https://github.com/api-platform/core/security/advisories/GHSA-428q-q3vv-3fq3) / CVE-2025-31485, which fixed only the GraphQL `ItemNormalizer`. The JSON:API and HAL paths were not addressed at the time. ### Exploitation conditions Exploitation requires all of the following to coincide: - The application exposes a resource via the JSON:API and/or HAL formats. - At least one property of that resource uses `#[ApiProperty(security: ...)]` with a predicate whose result depends on the current user (or on per-request state). - A request from a user for whom the predicate evaluates to `true` populates `componentsCache` before a request from a user for whom the predicate evaluates to `false`, within the lifetime of the same PHP process. - The deployment uses a long-running PHP runtime that keeps the normalizer instance alive across requests (FrankenPHP worker mode, RoadRunner, Swoole, ReactPHP, etc.). With classic `php-fpm` workers the cache only survives the duration of a single request, which makes the issue much harder to observe in practice. ### Patches - 4.1.29 - 4.2.25 - 4.3.8 All three branches receive patched releases of `api-platform/core`, `api-platform/json-api`, and `api-platform/hal`. ### Workarounds 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. Pinning the deployment to classic `php-fpm` workers also limits exposure since the cache does not survive across requests. ### Credits - Tillmann Baumgart (@tillmon) — originally identified the broader cache-key gap and proposed moving `isCacheKeySafe` to `AbstractItemNormalizer`. - Antoine Bluchet (@soyuka) — extended the gate to JSON:API and HAL normalizers.

CVE-2026-49858 Affected Api platform/core Versions

9 component(s)
Fixed Versions:
4.1.294.2.254.3.8
Product / Package Ecosystem Affected Versions Fixed Version
api-platform/core
Packagist
≥ 2.6.0
< 4.1.29
4.1.29
api-platform/core
Packagist
≥ 4.2.0
< 4.2.25
4.2.25
api-platform/core
Packagist
≥ 4.3.0
< 4.3.8
4.3.8
api-platform/json-api
Packagist
≥ 4.0.0
< 4.1.29
4.1.29
api-platform/json-api
Packagist
≥ 4.2.0
< 4.2.25
4.2.25
api-platform/json-api
Packagist
≥ 4.3.0
< 4.3.8
4.3.8
api-platform/hal
Packagist
≥ 4.0.0
< 4.1.29
4.1.29
api-platform/hal
Packagist
≥ 4.2.0
< 4.2.25
4.2.25
api-platform/hal
Packagist
≥ 4.3.0
< 4.3.8
4.3.8

References

Frequently Asked Questions

What is CVE-2026-49858?
CVE-2026-49858 is a security vulnerability in Api platform/core involving API and HAL item normalizers due to missing isCacheKeySafe gate under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Api platform/core versions are affected?
Affected versions include releases prior to 4.1.29, 4.2.25, 4.3.8 across affected packages: api-platform/core, api-platform/json-api, api-platform/hal.
What version fixes CVE-2026-49858?
Upgrading to 4.1.29, 4.2.25, 4.3.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is api-platform/core affected?
Yes, api-platform/core is affected in releases prior to 4.1.29, 4.2.25, 4.3.8. Upgrade your dependency to 4.1.29, 4.2.25, 4.3.8 or later.
Is api-platform/json-api affected?
Yes, api-platform/json-api is affected in releases prior to 4.1.29, 4.2.25, 4.3.8. Upgrade your dependency to 4.1.29, 4.2.25, 4.3.8 or later.
What is the CVSS score of CVE-2026-49858?
CVE-2026-49858 has a CVSS v3.1 base score of 5.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-49858?
CVE-2026-49858 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check Packagist dependencies for CVE-2026-49858?
Run the dependency tree command: 'inspect dependencies for api-platform/core'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pjhx-3c3w-9v23",
  "modified" : "2026-07-10T14:32:01Z",
  "published" : "2026-07-10T14:32:01Z",
  "aliases" : [ "CVE-2026-49858" ],
  "summary" : "API Platform Core vulnerable to cross-user attribute leak in JSON:API and HAL item normalizers due to missing isCacheKeySafe gate",
  "details" : "### Impact\n\n`#[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.\n\nThis is the same vulnerability class as [GHSA-428q-q3vv-3fq3](https://github.com/api-platform/core/security/advisories/GHSA-428q-q3vv-3fq3) / CVE-2025-31485, which fixed only the GraphQL `ItemNormalizer`. The JSON:API and HAL paths were not addressed at the time.\n\n### Exploitation conditions\n\nExploitation requires all of the following to coincide:\n\n- The application exposes a resource via the JSON:API and/or HAL formats.\n- At least one property of that resource uses `#[ApiProperty(security: ...)]` with a predicate whose result depends on the current user (or on per-request state).\n- A request from a user for whom the predicate evaluates to `true` populates `componentsCache` before a request from a user for whom the predicate evaluates to `false`, within the lifetime of the same PHP process.\n- The deployment uses a long-running PHP runtime that keeps the normalizer instance alive across requests (FrankenPHP worker mode, RoadRunner, Swoole, ReactPHP, etc.). With classic `php-fpm` workers the cache only survives the duration of a single request, which makes the issue much harder to observe in practice.\n\n### Patches\n\n- 4.1.29\n- 4.2.25\n- 4.3.8\n\nAll three branches receive patched releases of `api-platform/core`, `api-platform/json-api`, and `api-platform/hal`.\n\n### Workarounds\n\nOverride 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. Pinning the deployment to classic `php-fpm` workers also limits exposure since the cache does not survive across requests.\n\n### Credits\n\n- Tillmann Baumgart (@tillmon) — originally identified the broader cache-key gap and proposed moving `isCacheKeySafe` to `AbstractItemNormalizer`.\n- Antoine Bluchet (@soyuka) — extended the gate to JSON:API and HAL normalizers.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "api-platform/core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.6.0"
      }, {
        "fixed" : "4.1.29"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "api-platform/core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.2.0"
      }, {
        "fixed" : "4.2.25"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "api-platform/core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.3.0"
      }, {
        "fixed" : "4.3.8"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "api-platform/json-api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "4.1.29"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "api-platform/json-api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.2.0"
      }, {
        "fixed" : "4.2.25"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "api-platform/json-api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.3.0"
      }, {
        "fixed" : "4.3.8"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "api-platform/hal"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "4.1.29"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "api-platform/hal"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.2.0"
      }, {
        "fixed" : "4.2.25"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "api-platform/hal"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.3.0"
      }, {
        "fixed" : "4.3.8"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/api-platform/core/security/advisories/GHSA-pjhx-3c3w-9v23"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-49858"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/api-platform/core"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-524", "CWE-639" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-10T14:32:01Z",
    "nvd_published_at" : "2026-07-01T20:17:10Z"
  }
}