Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-114474medium5.9

Use of Less Trusted Source in hMailServer

Impact

hMailServer 6.0.0 through 6.3.6 uses a less trusted source for the envelope sender, allowing a remote unauthenticated attacker to send mail with a forged domain. The attacker needs to know a mailbox that an account collects and forwards to an outside address. This weakness can bypass SPF and DMARC checks.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

What to do

Upgrade to hMailServer 6.3.7, in which a download does not take an address hosted on the server from its From as its envelope sender - it keeps the empty envelope sender, as a download whose From names no address does - and a forward or redirect of it is held to the rule 6.3.7 applies to every copy of mail from outside: it is sent on with an envelope sender, or under a host name, in the organisation of a domain its From names only when the message passed DMARC for that organisation when it arrived, which a download never has. Until then, do not forward or redirect to an outside address the mail of an account that collects an external mailbox where that mail's From can name a domain the server hosts; the spam checks of an external account are off unless they are set, and a download has no DMARC verdict of its own to hold it.

GitLab guidance

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

Progressive Robot Ltd · GitLab

hMailServer

1 range

Compare with this publisher’s ranges. This does not inspect your installation.

affected

6.0.0 → through 6.3.6

semver versions

unaffected

unknown

Other versions: unaffected

Original source description

Use of a less trusted source for the envelope sender in the external-account download of Progressive Robot hMailServer 6.0.0 through 6.3.6 allows a remote unauthenticated attacker to have mail they write in the name of a domain the server hosts sent on by the server with an envelope sender at that domain, so that it passes the domain's SPF and DMARC at other receivers. A message the server downloads from an external POP3 or IMAP account has no SMTP envelope of its own, and the server took the address in its From header as its envelope sender, whatever that address was. A forward or redirect of the downloaded message to an outside address then left with that address as its envelope sender, which the Sender Rewriting Scheme leaves alone for a hosted domain, so that the receiver's SPF check passed for the forged domain, aligned even under strict alignment, with no non-default setting, host name record or DMARC policy needed. An attacker needs to know a mailbox elsewhere that an account here collects and forwards to an outside address; an account holder who adds an external account of their own can collect from a server of their own, which matters where SmtpAuthenticatedSenderCheck holds signed-in senders to their own addresses.

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-114474

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-348 ↗

CWE-348: Use of Less Trusted Source

GitLab

Related →
Contributing organizations · 2
GitLab

Assigning organization

2026-10-21
CISA-ADP

Additional data publisher

2026-10-29

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

2 sources