api-platform core/hal/json-api up to 4.1.28/4.2.24/4.3.7 cache_key cache containing sensitive information

Summaryinfo

A vulnerability was found in api-platform core, hal and json-api up to 4.1.28/4.2.24/4.3.7. It has been classified as problematic. This impacts an unknown function. Performing a manipulation of the argument cache_key results in use of cache containing sensitive information. This vulnerability is identified as CVE-2026-49858. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, was found in api-platform core, hal and json-api up to 4.1.28/4.2.24/4.3.7. This affects an unknown code block. The manipulation of the argument cache_key with an unknown input leads to a use of cache containing sensitive information vulnerability. CWE is classifying the issue as CWE-524. The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. This is going to have an impact on confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-49858 since 06/02/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 4.1.29, 4.2.25 or 4.3.8 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Automation Software

Vendor

• api-platform

Name

• core
• hal
• json-api

Version

• 4.1.0
• 4.1.1
• 4.1.2
• 4.1.3
• 4.1.4
• 4.1.5
• 4.1.6
• 4.1.7
• 4.1.8
• 4.1.9
• 4.1.10
• 4.1.11
• 4.1.12
• 4.1.13
• 4.1.14
• 4.1.15
• 4.1.16
• 4.1.17
• 4.1.18
• 4.1.19
• 4.1.20
• 4.1.21
• 4.1.22
• 4.1.23
• 4.1.24
• 4.1.25
• 4.1.26
• 4.1.27
• 4.1.28
• 4.2.0
• 4.2.1
• 4.2.2
• 4.2.3
• 4.2.4
• 4.2.5
• 4.2.6
• 4.2.7
• 4.2.8
• 4.2.9
• 4.2.10
• 4.2.11
• 4.2.12
• 4.2.13
• 4.2.14
• 4.2.15
• 4.2.16
• 4.2.17
• 4.2.18
• 4.2.19
• 4.2.20
• 4.2.21
• 4.2.22
• 4.2.23
• 4.2.24
• 4.3.0
• 4.3.1
• 4.3.2
• 4.3.3
• 4.3.4
• 4.3.5
• 4.3.6
• 4.3.7

Website

• Product: https://github.com/api-platform/core/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion