CVE-2026-53728

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-17. A secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-70698 (ENISA EUVD) · GHSA-m44r-7c5h-m6mj (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Medplum is a developer platform that enables development of healthcare apps. Prior to version 5.1.6, the external identity provider callback at GET /auth/external accepts attacker-controlled redirect URIs that only need to start with a registered client redirect URI, rather than matching exactly. After a successful external IdP login, the server appends Medplum login and code values to that attacker-supplied URL and issues a redirect. Because the external login request state is serialized as raw JSON and later trusted by the callback, an attacker who can tamper with state.redirectUri can cause Medplum to redirect authorization artifacts to an attacker-controlled endpoint. When the registered redirect URI is a bare origin or another prefix that can be extended into a different hostname, this becomes a cross-origin authorization code leak. This issue has been patched in version 5.1.6.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 17, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Sep 3, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

Version 5.1.6

Patch available: medplum/medplum v5.1.6

https://github.com/medplum/medplum/releases/tag/v5.1.6
GitHub commit

commit 7ae10035ddad (medplum/medplum)

Fix landed in medplum/medplum commit 7ae10035ddad — awaiting tagged release

https://github.com/medplum/medplum/commit/7ae10035ddadde4dba7b18d3156553940465b3a1
GitHub pull request

Disable redirect URL partial match

Fix merged in medplum/medplum PR #8749 on 2026-03-31 — awaiting tagged release

https://github.com/medplum/medplum/pull/8749
GitHub advisoryMentions a patch (unverified)

Medplum - Improper Validation of Redirect URI in External Auth Callback allows Authorization Code Leakage · Advisory · medplum/medplum · GitHub

https://github.com/medplum/medplum/security/advisories/GHSA-m44r-7c5h-m6mj

Vendor Advisories for CVE-2026-53728(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@medplum/core @ 5.1.6 (fixes <= 5.1.5)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@medplum/core—
  • every version up to 5.1.6: fixed in 5.1.6
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-11-01 09:11 UTCGHSA enrichmentGHSA-m44r-7c5h-m6mj · GitHub severity HIGH · GitHub CVSS 7.1
  3. 2026-11-01 07:45 UTCGHSA enrichmentGHSA-m44r-7c5h-m6mj · GitHub severity HIGH · GitHub CVSS 7.1
  4. 2026-11-01 07:45 UTCEG score recompute
  5. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-25 14:20 UTCEG score recompute
  13. 2026-10-24 20:48 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-10-18 03:31 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-10-17 08:25 UTCEG score recompute
  24. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
Show 67 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-10-12 15:57 UTCEG score recompute
  5. 2026-10-11 19:40 UTCEG score recompute
  6. 2026-10-11 16:55 UTCEG score recompute
  7. 2026-10-11 14:18 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-10-06 21:46 UTCEG score recompute
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-10-06 09:03 UTCEG score recompute
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-05 11:54 UTCEG score recompute
  17. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-03 17:49 UTCEG score recompute
  19. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-10-02 01:35 UTCEG score recompute
  22. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-09-30 22:43 UTCEG score recompute
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-09-30 10:02 UTCEG score recompute
  26. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  27. 2026-09-28 23:33 UTCEG score recompute
  28. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  29. 2026-09-27 21:43 UTCEG score recompute
  30. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  31. 2026-09-27 08:17 UTCEG score recompute
  32. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  33. 2026-09-25 02:09 UTCEG score recompute
  34. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  35. 2026-09-23 22:04 UTCEG score recompute
  36. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  37. 2026-09-22 20:41 UTCEG score recompute
  38. 2026-09-22 07:32 UTCEG score recompute
  39. 2026-09-21 06:10 UTCEG score recompute
  40. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  41. 2026-09-20 03:18 UTCEG score recompute
  42. 2026-09-18 00:31 UTCEG score recompute
  43. 2026-09-16 23:08 UTCEG score recompute
  44. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  45. 2026-09-16 10:15 UTCEG score recompute
  46. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  47. 2026-09-15 08:35 UTCEG score recompute
  48. 2026-09-14 04:45 UTCEG score recompute
  49. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  50. 2026-09-13 03:23 UTCEG score recompute
  51. 2026-09-12 02:01 UTCEG score recompute
  52. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  53. 2026-09-11 13:19 UTCEG score recompute
  54. 2026-09-10 10:09 UTCEG score recompute
  55. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  56. 2026-09-09 18:29 UTCEG score recompute
  57. 2026-09-09 17:45 UTCEG score recompute
  58. 2026-09-09 03:41 UTCEG score recompute
  59. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  60. 2026-09-07 16:11 UTCEG score recompute
  61. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  62. 2026-09-07 00:45 UTCEG score recompute
  63. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  64. 2026-09-05 23:20 UTCEG score recompute
  65. 2026-09-04 21:54 UTCEG score recompute
  66. 2026-09-03 20:23 UTCEG score recompute
  67. 2026-08-17 13:37 UTCEG score recomputeFirst assessed: 7.1 HIGH

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53728?
CVE-2026-53728 is a high-severity vulnerability; its CVE record was published on August 17, 2026. Medplum is a developer platform that enables development of healthcare apps. Prior to version 5.1.6, the external identity provider callback at GET /auth/external accepts attacker-controlled redirect URIs that only need to start with a registered client redirect URI, rather than matching exactly.…
When was the CVE record for CVE-2026-53728 published?
The CVE record for CVE-2026-53728 was published on August 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-53728 actively exploited?
CVE-2026-53728 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53728?
CVE-2026-53728 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53728?
A fix for CVE-2026-53728 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53728 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-53728

Explore →

Is Your Infrastructure Affected by CVE-2026-53728?

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

Book a Demo →Browse All CVEs