CVE-2026-44506
Medplum OAuth endpoint leaks client_secret for preconfigured clients.
WAF coverage: Information exposure. WAF can redact known leak patterns.
Also consider: response filtering
Is CVE-2026-44506 being exploited?
Not confirmed. CVE-2026-44506 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-44506?
CVE-2026-44506 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44506?
Yes. A fix has been recorded for CVE-2026-44506. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44506 affect?
CVE-2026-44506 affects Medplum v4.1.10–v5.1.6, /oauth2/register endpoint, defaultOAuthClients configuration. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44506?
Upgrade to Medplum v5.1.7 and rotate exposed client_secrets.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote disclosure of OAuth client_secret via /oauth2/register allowing client impersonation, token issuance, and unauthorized access to protected APIs/PHI.
Immediate action required
- affected>= 4.1.10 and < 5.1.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.