CVE-2026-114470
Cross-Site Request Forgery (CSRF) in hMailServer
02 Description
Cross-Site Request Forgery (CSRF) in hMailServer
03 Exploitation and scoring
- Exploitation
- Not assessed. CISA has not published an exploitation assessment for this record, and it is not in the KEV catalog. That is an absence of assessment, not a finding of no risk.
- SSVC decision
- Not assessed by CISA
- EPSS probability
- 0.15% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 4.0% of scored records. A rank, not a probability.
- NVD base score
- 5.3 (CVSS v3.x), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
- NVD analysis status
- Awaiting Analysis. NVD last modified this record on 2026-10-22.
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
04 Metadata
- Published
- 2026-10-21 15:11Z8 DAYS AGO
- Last updated
- 2026-10-21 15:11Z8 DAYS AGO
- Reserved
- 2026-10-21
- Assigning CNA
- GitLab
- Record state
- PUBLISHED
- Severity
- Medium (CVSS 5.3)
- CNA CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
- Weaknesses
- CWE-352Cross-Site Request Forgery (CSRF)Compound
- Data version
- 5.2
- Document digest
- e25ae7f6a7f5c482c1c70399f3121e773c60fd5178b344821dada92600b17649
05 Affected products
06 References
07 Remediation
Upgrade to hMailServer 6.3.7, which refuses a credentialed state-changing REST request a browser reports as cross-site (by Sec-Fetch-Site, or an Origin whose host is not the server's own), covering HTTP Basic and bearer credentials as the cookie session was already covered. Until then, reach the REST API and the Deck from a dedicated browser or profile closed after use so no cached Basic credential is present while browsing other sites; keep the REST API off (RestApiPort=0, the default) or bound to the loopback where it is not needed; and prefer an API key (a Bearer token a cross-site page cannot set) over the Basic box for automated clients. An upgrade does not undo a request already forged: review API keys, accounts, domains and settings for changes nobody made, and revoke any key nobody issued.