CVE-2026-114476

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-21. A secondary CVSS source baseline 7.5; 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 week

Also known asEUVD-2026-107319 (ENISA EUVD) · GHSA-94cg-hqr8-p6wh (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

Upgrade to hMailServer 6.3.7, in which a role is given or taken away, over the REST and the COM APIs, only by a credential that holds manage_roles in the account's domain and takes in both what the account holds now and… (from the CVE record's solution, GitLab Inc.) — apply it.

Incorrect authorization in the REST administration API of Progressive Robot hMailServer 6.3.4 through 6.3.6 allows a remote authenticated user whose credential holds the manage_roles permission in named domains - a full-scope API key issued for those domains, or an account assigned the serveradmin role with a list of domains - to obtain the server administrator's authority. An account's admin level gives it authority, and a role assigned to it replaces that authority, which is how an administrator narrows an account whose admin level is the server administrator's. The route that takes a role away (DELETE /api/v1/role-assignments/{address}) checked only that the credential takes in what the account held at the time, not what it would hold afterwards, so such a credential could take a narrowing role away from an account in its domains whose admin level is the server administrator's, returning it to the server administrator's authority, and, having set that account's password while it held the narrower role, sign in as the server administrator.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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: Upgrade to hMailServer 6.3.7, in which a role is given or taken away, over the REST and the COM APIs, only by a credential that holds manage_roles in the account's domain and takes in both what the account holds now and… (from the CVE record's solution, GitLab Inc.). Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
19th
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.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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 or medium mission impact; Track* at high (mission-essential systems).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 or medium mission impact; Track* at high (mission-essential systems).

Upgrade to hMailServer 6.3.7, in which a role is given or taken away, over the REST and the COM APIs, only by a credential that holds manage_roles in the account's domain and takes in both what the account holds now and… (from the CVE record's solution, GitLab Inc.). Apply it within your standard update timelines.

Exploitation none (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

October 21, 2026

Last Modified

October 29, 2026

Advisory Details (2)

Auto-updated Oct 21, 2026
Fix named in the CVE record's solution (GitLab Inc.).
Web page

hMailServer 6.3.7 · hmailserver / hMailServer · GitLab

https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.7
Web page

Administrator roles: taking a role away was judged only on what the account held, so a credential that manages roles in named domains could return an account there to the server administrator's authority its admin level gives (6.3.4-6.3.6) (#88) · Issues · hmailserver / hMailServer · GitLab

https://gitlab.com/hmailserver/hmailserver/-/work_items/88

Vendor Advisories for CVE-2026-114476(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 23× 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:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-10-29 21:26 UTCEG score recompute
  5. 2026-10-29 21:26 UTCGHSA enrichmentGHSA-94cg-hqr8-p6wh · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-10-29 21:01 UTCEG score recompute
  7. 2026-10-29 21:01 UTCGHSA enrichmentGHSA-94cg-hqr8-p6wh · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-29 07:06 UTCEG score recompute
  10. 2026-10-29 07:06 UTCGHSA enrichmentGHSA-94cg-hqr8-p6wh · GitHub severity HIGH · GitHub CVSS 7.5
  11. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-25 14:50 UTCEG score recompute
  16. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-22 16:27 UTCEG score recompute
  20. 2026-10-22 16:26 UTCGHSA enrichmentGHSA-94cg-hqr8-p6wh · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-10-21 16:29 UTCEG score recompute
  22. 2026-10-21 15:22 UTCEG score recomputeFirst assessed: 7.5 HIGH
  23. 2026-10-21 15:20 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-114476?
CVE-2026-114476 is a high-severity vulnerability; its CVE record was published on October 21, 2026. Incorrect authorization in the REST administration API of Progressive Robot hMailServer 6.3.4 through 6.3.6 allows a remote authenticated user whose credential holds the manage_roles permission in named domains - a full-scope API key issued for those domains, or an account assigned the serveradmin…
When was the CVE record for CVE-2026-114476 published?
The CVE record for CVE-2026-114476 was published on October 21, 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 October 29, 2026; the record at its source may have been updated since.
Is CVE-2026-114476 actively exploited?
CVE-2026-114476 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-114476?
CVE-2026-114476 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-114476?
The CVE record's solution for CVE-2026-114476, written by its CNA GitLab Inc., names the fix: "Upgrade to hMailServer 6.3.7, in which a role is given or taken away, over the REST and the COM APIs, only by a credential that holds manage_roles in the account's domain and takes in both what the account holds now and…" The vendor advisories EchelonGraph has for CVE-2026-114476 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-114476

Explore →

Is Your Infrastructure Affected by CVE-2026-114476?

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

Book a Demo →Browse All CVEs