Event Monitor Cyber
EM-20261108-RLYF VulnerabilityHigh severity

OpenEMR Vulnerability (CVE-2026-124483)

CVE-2026-124483

Share
Status
Developing

Since : signals keep joining.

First Signal
Nov 08 14:18 UTCC6 NVD CVE API 2.0
Page Born
Nov 08 15:31 UTCsecond source joined
Last Signal
Nov 08 15:31 UTC10 hours before snapshot
Sources
20 official · 2 research, news or crowd
Open For
2 hoursso far

Life Of This Page

  1. 1
    Born
    A second, independent source names it.
  2. 2
    Developing · Now
    New signals join; severity can move.
  3. 3
    Confirmed
    Not yet
    CISA KEV lists it, or exploitation in the wild is reported.
  4. 4
    Resolved
    Not yet
    Past the fix deadline and 14 days with no new signal.
  5. 5
    Archived
    Not yet
    30 days after resolved. Read only; the link keeps working. Reopens if it comes back.

The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.

Vulnerability Lifecycle

  1. Disclosed: reached
    Nov 08 14:18 UTC
    C6 NVD published
  2. Scored: reached
    Nov 08 14:18 UTC
    CVSS 8.7
  3. Exploited: not yet
    Not yet
    No exploitation reported
  4. Advisories: not yet
    Not yet
    None yet
  5. Vendor Response: not yet
    Not yet
    None in sources yet
  6. Resolved: not yet
    Not yet
    After 14 quiet days

Timeline

10:0012:0014:0016:00BornC6 NVD CVE API 2.0C29 CIRCL Vulnerability-Lookup

Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.

Signals

  1. GHSA-vwmc-g4gv-2mf9 / CVE-2026-124483 (opens source in a new tab) OpenEMR before 8.4.0 contains an incorrect authorization vulnerability because the prescription REST API routes check the patients.med ACL instead of patients.rx and request no specific permission bit, so read-only… Med severityDatabaseC29 CIRCL Vulnerability-Lookup
  2. CVE-2026-124483 (CVSS 8.7) (opens source in a new tab) OpenEMR before 8.4.0 contains an incorrect authorization vulnerability because the prescription REST API routes check the patients.med ACL instead of patients.rx and request no specific permission bit, so read-only… High severityDatabaseC6 NVD CVE API 2.0