On this page (7 sections)

A critical flaw has been published in mailcow: dockerized, the self-hosted mail server suite. According to the NVD record, versions before 2026-11 contain a server-side template injection issue that lets a domain administrator execute commands in the shared rspamd container by storing a malicious domain-wide footer.

If you run mailcow, especially with several tenants or with domain administrators who are not also full server administrators, check your version and move to release 2026-11 or later. At the time of writing, only one independent publisher covers this story, so the details below come mainly from the CVE record and the project's own references.

What happened

The CVE record was published on 2026-11-10. It describes a flaw in how mailcow handles a domain-wide footer. A domain administrator can store a footer that contains template code, and that code is evaluated by the rspamd MOO_FOOTER prefilter instead of being treated as plain text.

The record points to several project references: a GitHub security advisory (GHSA-jgr3-fv33-x43c), a commit and the 2026-11 release. VulnCheck also published an advisory on the same issue. The CVE text does not spell out which release is the fix, but because it names 2026-11 as the first unaffected point, updating to 2026-11 or later is the sensible reading.

Technical details in plain terms

Server-side template injection happens when user-supplied text is fed into a template engine as if it were trusted template code. Instead of just printing the text, the engine runs whatever logic it contains. This weakness class is tracked as CWE-1336.

Per the CVE record, the stored footer is rendered by the rspamd MOO_FOOTER prefilter, and a Jinja macro in that footer can use an os.execute default value to run commands. The commands run inside the shared rspamd container. Because that container is shared, the record says an attacker can read or inject mail for every tenant and disable filtering.

The important point is the trust boundary. A domain administrator is normally trusted only for their own domain. This flaw lets that role reach a component shared by every tenant. The research does not describe any way to exploit it without a domain administrator account, so the realistic precondition is control of such an account.

Who is affected

  • Hosting providers and agencies that run mailcow for multiple customers and delegate domain administration to them.
  • Organizations with several departments or subsidiaries, each with its own domain administrator.
  • Single-owner installations are lower risk in practice, because the domain administrator is often the same person as the server owner. They are still affected if the version is older than 2026-11, and a stolen or phished domain admin login would be enough to meet the precondition.
The research does not state whether exploitation has been seen in the wild, and the CVE is not marked in CISA KEV. Treat the absence of reports as unconfirmed rather than as proof of safety.

How to check your exposure

First find out which mailcow release you run. The mailcow documentation explains where version information is shown. You can also check the git state of your installation directory. The commands below are read-only. Run them on the mail server from your mailcow-dockerized directory (use your own path) and compare the output with the 2026-11 release tag.

Show the checked-out mailcow release and latest commit (run in your mailcow-dockerized directory)Shell
git describe --tags --always
git log -1 --format='%H %cd'

If the version is older than 2026-11, you are in the affected range. Then review who holds domain administrator rights and whether any domain has a footer you do not recognize. Check the mailcow documentation for where domain-wide footers are managed in your version. Look for footers containing template syntax such as macro or execution constructs, which have no place in an ordinary text footer.

What to do now

  1. Back up your mailcow configuration and data before changing anything.
  2. Update mailcow: dockerized to release 2026-11 or later, following the project's standard update procedure.
  3. Audit all domain administrator accounts. Remove ones you do not need and reset passwords for any you cannot account for.
  4. Enable two-factor authentication for administrator accounts where your setup supports it.
  5. Review every domain-wide footer for unexpected template-like content and clear anything suspicious.
  6. Check rspamd and mail logs for unexpected behavior such as filtering suddenly disabled, odd mail activity, or unfamiliar processes in the rspamd container.
  7. If you suspect a footer was abused, assume mail for all tenants may have been read or altered, rotate credentials and notify affected users.
Caution. Updating mailcow restarts its containers, which interrupts mail delivery for a short time. Schedule the update in a quiet window and take a backup first.

The mailcow project documents its own update procedure. Follow the official mailcow documentation rather than commands from third parties, and confirm afterwards that the version matches 2026-11 or later.

Tip. The research mentions no workaround other than updating. Until you can patch, limit domain administrator access to people you fully trust and avoid creating new domain admins.

Detection and monitoring afterwards

Because the flaw sits in a shared container, the goal after patching is to confirm nothing was changed before you updated. Compare current footers against what you expect, watch for domains whose spam filtering behavior changed, and keep an eye on unusual administrator logins. Keep mailcow on a regular update schedule, since mail servers are exposed by design.

Outside-in checks do not replace this internal review, but they help with the basics. The free SSL certificate checker can confirm your mail host certificate is valid, and Webforta Monitor can alert you to certificate and DNS changes on your mail domains. See also our guide to SPF, DKIM and DMARC to make forged mail easier to spot.

Timeline

Summary
DateEvent
2026-11-10CVE-2026-125757 published in NVD; versions before 2026-11 listed as affected and the 2026-11 release referenced

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-125757: mailcow: dockerized before 2026-11 contains a server-side template injection vulnerability that allows domain administrators to execute commands in the shared…nvd.nist.gov ·
  • mailcow
  • CVE-2026-125757
  • rspamd
  • template injection
  • mail server