---
id: "CVE-2026-114477"
kind: "vulnerability"
aliases: ["CVE-2026-114477"]
title: "hMailServer: domain-confined API keys can read server-wide traffic totals"
severity: "medium"
cvss: 4.3
epss: 0.00214
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["hmailserver", "mail-server", "package", "rest-api", "self-hosted"]
not_affected_if: ["auth-required", "no-domain-scoped-credentials"]
published_at: "2026-10-21T16:17:35+00:00"
first_seen_at: "2026-10-23T21:57:29+00:00"
updated_at: "2026-10-25T04:37:40+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-114477", "first_seen_at": "2026-10-23T21:57:29+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-114477", "first_seen_at": "2026-10-24T13:15:54+00:00"}]
---

# hMailServer: domain-confined API keys can read server-wide traffic totals

The REST metrics route GET /api/v1/metrics/history in hMailServer 6.2.25 through 6.3.6 skips the authorization check that limits domain-confined credentials, so an authenticated domain administrator or confined API key can read server-wide traffic counters for the last 30 days. The exposed data is aggregate operational counters, not messages or account details.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- unknown

## Fix

- unknown

## Timeline

- 2026-10-23T21:57:29+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-114477
- 2026-10-24T13:15:54+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-114477

## From the sources

Missing authorization in the REST metrics route of Progressive Robot hMailServer 6.2.25 through 6.3.6 allows a remote authenticated user whose credential is confined to named domains to read the server-wide traffic history. GET /api/v1/metrics/history returns the server's traffic counters over the last 30 days; those counters are server-wide and carry no domain, which is why the report routes already refuse the same counters to a credential confined to named domains. The metrics route was not among the routes the server's authorization gate refuses a confined credential and its handler was not given the caller, so a domain administrator, an account given another role that holds view_configuration in named domains (the auditor role given a domain list among them), or an API key issued for named domains could read the whole server's traffic totals rather than its own domains'. The disclosure is of aggregate operational counters, not of any message or account.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_