CVE-2026-48009

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 62% 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
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Shopware is an open commerce platform. Prior to 6.6.10.18 and 6.7.10.1, a low-privilege admin user with user_recovery:read ACL can take over any admin account by triggering POST /api/_action/user/user-recovery, reading the password recovery hash through POST /api/search/user-recovery, and using PATCH /api/_action/user/user-recovery/password; the root cause is that src/Core/System/User/Recovery/UserRecoveryDefinition.php exposes the hash field through the Admin API without ApiAware(false) or ReadProtection. This issue is fixed in versions 6.6.10.18 and 6.7.10.1.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium 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
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

Published

June 4, 2026

Last Modified

July 17, 2026

Advisory Details (6)

Auto-updated Jul 17, 2026
Patch available. Sources: github_release, github, github_commit.
github_release Patch Available

Security Release v6.7.10.1

Patch available: shopware/shopware v6.7.10.1

https://github.com/shopware/shopware/releases/tag/v6.7.10.1
github_release Patch Available

Security Release v6.6.10.18

Patch available: shopware/shopware v6.6.10.18

https://github.com/shopware/shopware/releases/tag/v6.6.10.18
github_commit

commit d82c23d8d5b2 (shopware/shopware)

Fix landed in shopware/shopware commit d82c23d8d5b2 — awaiting tagged release

https://github.com/shopware/shopware/commit/d82c23d8d5b22dd722c8f76c4f66785d1a7a72d8
github_commit

commit 9ef4873f810e (shopware/shopware)

Fix landed in shopware/shopware commit 9ef4873f810e — awaiting tagged release

https://github.com/shopware/shopware/commit/9ef4873f810e26fb38da051624f7f2720139279a
github_commit

commit 06f8b9aa4fec (shopware/shopware)

Fix landed in shopware/shopware commit 06f8b9aa4fec — awaiting tagged release

https://github.com/shopware/shopware/commit/06f8b9aa4fecb239a2ff33a6546192d7ce7ed0f8
githubMentions a patch (unverified)

Admin Account Takeover via User Recovery Hash Exposure · Advisory · shopware/shopware · GitHub

https://github.com/shopware/shopware/security/advisories/GHSA-8v9p-g828-v98f

Vendor Advisories for CVE-2026-48009(1)

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

Affected Packages

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFix by version rangeDependents
shopware/core6.3.0.0 ... v6.6.9.0 (166 versions)
  • 6.7.0.0 up to 6.7.10.1: fixed in 6.7.10.1
  • every version up to 6.6.10.18: fixed in 6.6.10.18
—
shopware/platform6.3.0.0 ... v6.6.9.0 (166 versions)
  • 6.7.0.0 up to 6.7.10.1: fixed in 6.7.10.1
  • every version up to 6.6.10.18: fixed in 6.6.10.18
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× 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.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-48009?
CVE-2026-48009 is a medium vulnerability published on June 4, 2026. Shopware is an open commerce platform. Prior to 6.6.10.18 and 6.7.10.1, a low-privilege admin user with userrecovery:read ACL can take over any admin account by triggering POST /api/action/user/user-recovery, reading the password recovery hash through POST /api/search/user-recovery, and using PATCH…
When was CVE-2026-48009 disclosed?
CVE-2026-48009 was first published on June 4, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48009 actively exploited?
CVE-2026-48009 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48009?
CVE-2026-48009 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48009?
A fix for CVE-2026-48009 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48009 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-48009

Explore →

Is Your Infrastructure Affected by CVE-2026-48009?

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

Book a Demo →Browse All CVEs