Mailu bug bounty programs
mailu.io Updated
Mailu runs one public program: a Sorona bug bounty paying up to $1,500.
- Top reward
- $1,500
- Sorona
- Programs
- 1
- 1 pays cash
- Targets in scope
- 11
- 2 types
- Last change
- None yet
- Tracked since Nov 2026
Where to report
The one public program Mailu runs.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
|
Mailu
Sorona · Bug bounty |
– | – | – | $100 | $1,500 | Partial | – | – | Open |
-
- Critical
- –
- High
- –
- Medium
- –
- Low
- $100
- Safe harbor
- Partial
Amounts are the top reward per severity in the currency each program pays. First response is the platform's measured average when it publishes one, else what the policy promises.
What is in scope
11 targets. 6 excluded.
-
https://mailu.io
Web
-
Certificate handling and the ACME integration behind it
Products and areas
-
Fetchmail, forwarding, aliases and every other rule deciding where a message ends up
Products and areas
-
The admin front end in full: authentication, session handling, and every page an administrator, a domain manager or a mailbox user can reach
Products and areas
-
The API, including token issuance, token management and every endpoint sitting behind them
Products and areas
-
The authentication service the mail daemons call to check a credential, including the header-based proxy authentication path
Products and areas
-
The container set and its configuration: the compose definitions, the environment variables holding secrets, and the reverse proxy Mailu ships in front of everything
Products and areas
-
The multi-tenant model: domains, aliases, per-domain administrators, and the checks keeping one domain's configuration out of another's reach
Products and areas
-
The policy accepts severe security issues at a private address and sets no boundary on which part of Mailu they may be in. Everything Mailu itself writes or wires together is inside that
Products and areas
-
The setup utility that generates a deployment's configuration, since a defect there ships into every new installation
Products and areas
-
The webmail integration, covering the single sign-on handoff into Roundcube or SnappyMail and the session that lands on the other side
Products and areas
No target matches. Try part of a host name, such as the company name.
Out of scope 6
Don't test these. A program can exclude a host another program covers; the program you report to decides.
-
Defects inside the bundled upstreams themselves. Postfix, Dovecot, rspamd, Roundcube and SnappyMail are separate projects with their own reporting channels
-
Findings against release lines the project no longer ships
-
Operator configuration, including a deployment exposed without the intended reverse proxy in front of it
-
The Docker daemon, the host operating system and whatever orchestration an operator chose
-
Upstream Python dependencies, unless Mailu's own use of them is what makes the defect reachable
-
Volumetric denial of service against a mail server that accepts mail from strangers by design
Recent changes
Reward and scope changes across every Mailu program, newest first.
No changes recorded yet. New targets and reward moves show up here and in the RSS feed.
Recent CVEs
Published vulnerabilities in Mailu products, from the NVD.
-
CVE-2020-5239 High
In Mailu before version 1.7, an authenticated user can exploit a vulnerability in Mailu fetchmail script and gain full access to a Mailu instance. Mailu servers that have open registration or untrusted users are most impacted. The master and 1.7 branches are patched on our git repository. All Docker images published on docker.io/mailu for tags 1.5, 1.6, 1.7 and master are patched. For detailed ins
About this page
This page gathers every public program listed under mailu.io: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.
Something wrong or missing? Report a correction.