CVE-2026-49858

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Jul 3, 2026
Patch available. Sources: github.
githubMentions a patch (unverified)

Cross-user attribute leak in JSON:API and HAL item normalizers due to missing isCacheKeySafe gate · Advisory · api-platform/core · GitHub

https://github.com/api-platform/core/security/advisories/GHSA-pjhx-3c3w-9v23

Vendor Advisories for CVE-2026-49858(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 1 ecosystem)
Packagist(3)
PackageVulnerable rangeFix by version rangeDependents
api-platform/corev4.3.0 ... v4.3.7 (8 versions)
  • 2.6.0 up to 4.1.29: fixed in 4.1.29
  • 4.2.0 up to 4.2.25: fixed in 4.2.25
  • 4.3.0 up to 4.3.8: fixed in 4.3.8
—
api-platform/halv4.3.0 ... v4.3.7 (8 versions)
  • 4.0.0 up to 4.1.29: fixed in 4.1.29
  • 4.2.0 up to 4.2.25: fixed in 4.2.25
  • 4.3.0 up to 4.3.8: fixed in 4.3.8
—
api-platform/json-apiv4.3.0 ... v4.3.7 (8 versions)
  • 4.0.0 up to 4.1.29: fixed in 4.1.29
  • 4.2.0 up to 4.2.25: fixed in 4.2.25
  • 4.3.0 up to 4.3.8: fixed in 4.3.8
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 116 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-03 14:25 UTCEPSS rescore
  7. 2026-10-01 19:50 UTCEPSS rescore
  8. 2026-09-30 15:03 UTCEPSS rescore
  9. 2026-09-28 13:51 UTCEPSS rescore
  10. 2026-09-27 13:48 UTCEPSS rescore
  11. 2026-09-26 15:59 UTCEPSS rescore
  12. 2026-09-26 00:27 UTCEPSS rescore
  13. 2026-09-23 06:49 UTCEG score recompute
  14. 2026-09-20 20:16 UTCEPSS rescore
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-18 06:28 UTCEG score recompute
  17. 2026-09-16 14:08 UTCEPSS rescore
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-14 00:21 UTCEG score recompute
  20. 2026-09-13 16:47 UTCEPSS rescore
  21. 2026-09-12 14:37 UTCEG score recompute
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-10 09:35 UTCEPSS rescore
  24. 2026-09-08 22:01 UTCEPSS rescore
  25. 2026-09-07 16:01 UTCEPSS rescore
Show 75 more
  1. 2026-09-06 13:47 UTCEPSS rescore
  2. 2026-09-06 00:45 UTCEG score recompute
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 11:43 UTCEG score recompute
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-28 21:41 UTCEPSS rescore
  11. 2026-08-27 22:24 UTCEG score recompute
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-25 16:16 UTCEG score recompute
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-24 10:50 UTCEG score recompute
  17. 2026-08-22 06:58 UTCEG score recompute
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-21 04:46 UTCEG score recompute
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 04:37 UTCEG score recompute
  22. 2026-08-19 17:04 UTCEPSS rescore
  23. 2026-08-18 23:29 UTCEG score recompute
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-17 23:19 UTCEG score recompute
  26. 2026-08-17 13:47 UTCEPSS rescore
  27. 2026-08-16 18:32 UTCEG score recompute
  28. 2026-08-16 14:56 UTCEPSS rescore
  29. 2026-08-16 02:14 UTCEPSS rescore
  30. 2026-08-15 18:24 UTCEG score recompute
  31. 2026-08-15 01:30 UTCEPSS rescore
  32. 2026-08-14 18:15 UTCEG score recompute
  33. 2026-08-13 22:00 UTCEPSS rescore
  34. 2026-08-12 17:36 UTCEG score recompute
  35. 2026-08-12 13:51 UTCEPSS rescore
  36. 2026-08-11 17:28 UTCEG score recompute
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-09 16:54 UTCEG score recompute
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-08 16:46 UTCEG score recompute
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-07 16:37 UTCEG score recompute
  43. 2026-08-06 16:29 UTCEG score recompute
  44. 2026-08-06 13:47 UTCEPSS rescore
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-05 16:20 UTCEG score recompute
  47. 2026-08-04 15:10 UTCEPSS rescore
  48. 2026-08-04 15:02 UTCEG score recompute
  49. 2026-08-04 10:39 UTCEPSS rescore
  50. 2026-08-03 14:54 UTCEG score recompute
  51. 2026-08-03 10:36 UTCEPSS rescore
  52. 2026-08-02 14:45 UTCEG score recompute
  53. 2026-08-02 02:27 UTCEPSS rescore
  54. 2026-08-01 14:36 UTCEG score recompute
  55. 2026-08-01 04:16 UTCEPSS rescore
  56. 2026-07-31 14:27 UTCEG score recompute
  57. 2026-07-30 16:28 UTCEPSS rescore
  58. 2026-07-30 14:12 UTCEG score recompute
  59. 2026-07-30 01:30 UTCEPSS rescore
  60. 2026-07-29 14:02 UTCEG score recompute
  61. 2026-07-28 15:37 UTCEPSS rescore
  62. 2026-07-28 13:53 UTCEG score recompute
  63. 2026-07-27 13:22 UTCEG score recompute
  64. 2026-07-26 14:54 UTCEPSS rescore
  65. 2026-07-26 13:13 UTCEG score recompute
  66. 2026-07-25 14:18 UTCEPSS rescore
  67. 2026-07-24 14:18 UTCEPSS rescore
  68. 2026-07-23 14:18 UTCEPSS rescore
  69. 2026-07-23 03:18 UTCEG score recompute
  70. 2026-07-22 14:08 UTCEPSS rescore
  71. 2026-07-21 15:25 UTCEPSS rescore
  72. 2026-07-20 17:08 UTCEPSS rescore
  73. 2026-07-19 14:31 UTCEPSS rescore
  74. 2026-07-19 14:31 UTCEPSS rescore
  75. 2026-07-19 02:29 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-49858?
CVE-2026-49858 is a medium vulnerability published on July 1, 2026. 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…
When was CVE-2026-49858 disclosed?
CVE-2026-49858 was first published on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49858 actively exploited?
CVE-2026-49858 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49858?
CVE-2026-49858 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-49858?
A fix for CVE-2026-49858 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-49858 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49858

Explore →

Is Your Infrastructure Affected by CVE-2026-49858?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.