Automated Threat Modeling

Brief Summary: Axigen Mail Server CVE-2026-127218, Unauthenticated Denial of Service via Regex Recursion

A brief summary of CVE-2026-127218, an unauthenticated denial of service in Axigen Mail Server where a recursive regular expression check on query parameters and cookies can exhaust a worker thread stack and crash the whole server process. Covers root cause, attack flow, affected versions, and the vendor fix in 10.6.41 and 10.7.3.

CVE Analysis

6 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-16

Brief Summary: Axigen Mail Server CVE-2026-127218, Unauthenticated Denial of Service via Regex Recursion

Introduction

A single unauthenticated HTTP request to Axigen's WebAdmin or WebMail listener can crash the entire Axigen server process, interrupting SMTP, IMAP, and POP3 along with the web interfaces. Because the same request can be replayed after every restart, an attacker who can reach those listeners can keep a mail deployment in a repeated crash-and-restart cycle with very little traffic.

Axigen Mail Server is a mail server platform for Windows and Linux developed by Axigen Messaging SRL, based in Bucharest, Romania. The vendor offers editions ranging from personal and lab use to businesses, managed service providers, and carrier-class ISP deployments, and markets the platform to telecommunications providers, ISPs, and hosting providers. Axigen describes deployments from thousands to millions of users. Those are vendor positioning claims rather than independent installed-base figures, but they place the product in shared messaging infrastructure where a process-level crash affects every user served by that instance.

Technical information

Root cause

CVE-2026-127218 is classified as CWE-674, Uncontrolled Recursion. According to Axigen's advisory, the WebAdmin and WebMail HTTP services validate certain query parameters and cookies against an allowed character set very early in request handling, before the request is routed and authenticated.

That validation was implemented with a recursive regular expression engine. Engines of this type can match repeated input by calling themselves again for each step, so each additional character in the value can add another frame to the call stack. A query parameter or cookie value of a few thousand characters is enough to exhaust the stack of the worker thread processing the request. The server does not handle this as an error. The whole process terminates with a segmentation fault.

The vendor advisory adds two details.

Only a narrow band of input lengths triggers the crash. Axigen's existing request size limit already rejects much longer values, so only values of a few thousand characters reach the vulnerable code path and overflow the stack. The size limit was never intended as a defense against this bug and could not fully prevent it.

The crash takes down the whole process, not just the listener that received the request. SMTP, IMAP, POP3, WebMail, and WebAdmin all run inside the same Axigen process, so a crash triggered through an HTTP listener stops every mail protocol the server provides.

Severity

The CVE data supplied for this post lists a CVSS score of 7.5. When the NVD page was retrieved during research, it did not display a base score, so we could not independently confirm the vector.

Attack flow

Based on the vendor advisory and the CVE description, exploitation looks like this:

  1. The attacker identifies a network-reachable Axigen WebAdmin or WebMail listener. No account or credentials are needed.
  2. The attacker sends one HTTP request containing a query parameter or cookie value a few thousand characters long, sized to stay under the request size limit. The request does not need to reference an existing resource or carry a valid session.
  3. Before routing or authentication, the service runs its character set validation on that value using the recursive regex engine. Recursion depth grows with the input length.
  4. The worker thread stack is exhausted and the Axigen process crashes with a segmentation fault.
  5. SMTP, IMAP, POP3, WebMail, and WebAdmin all become unavailable until the process is restarted.
  6. The attacker repeats the request after each restart, keeping the server in a crash-and-restart cycle until the process supervisor stops restarting it.

Exploitation status

The CVE record and the VulnCheck advisory do not report active exploitation, do not name threat actors, and do not describe a public exploit. The CISA Known Exploited Vulnerabilities catalog, as retrieved, did not list this CVE. The absence of reports reflects the limits of the available information. It does not prove that exploitation has never occurred.

Patch information

Axigen fixed CVE-2026-127218 in two maintenance releases: Axigen 10.6.41 for the 10.6 branch and Axigen 10.7.3 for the 10.7 branch. Both release notes list the same item under SECURITY: Prevent server crash on web requests with very long URL parameters or cookies (AXI-7714). The item is tagged as CVE Pending and links to Axigen knowledge base article #413. The release notes do not give the CVE number. The connection to CVE-2026-127218 comes from VulnCheck's advisory, which cites the KB article and both release notes as fix references.

How the fix works

Axigen did not tighten the length cap. It removed the root cause. In the vendor's words, the problem was solved by "replacing the regular-expression validation with a linear, recursion-free check."

The new check fixes two things. A loop that checks each character against the allowed set uses the same small amount of stack regardless of input length, so no parameter or cookie value can exhaust the thread stack. It also runs in linear time: each character is examined once, so cost grows proportionally with input length. That rules out runaway backtracking, a common related problem with regex-based input validation.

The same allowed character set is still enforced. Only the implementation changed, so legitimate requests should behave as before. The check still runs before authentication, but it can no longer crash the process.

Fixed versions

  • 10.7.x: vulnerable 10.7.0 through 10.7.2, fixed in 10.7.3. The 10.7.3 page notes that the release has been superseded by 10.7.4, which also includes the fix.
  • 10.6.x: vulnerable up to 10.6.40, fixed in 10.6.41.
  • 10.5.x: vulnerable 10.5.29 through 10.5.68. No fix on this branch. Upgrade to a fixed 10.6 or 10.7 release.
  • 10.4.x and 10.3.3.x: vulnerable from 10.4.42 and 10.3.3.67 onward. No fix on these branches. Upgrade to a fixed 10.6 or 10.7 release.

Axigen's advisory recommends updating from WebAdmin and does not specify a temporary workaround.

AXI-7714 shipped alongside several other security fixes. The most closely related is AXI-7689, which rejects SOAP and JSON requests whose bodies exceed a nesting limit, closing another path by which input could drive recursion. The releases also include WebMail output encoding and script injection fixes (AXI-7694 through AXI-7698) and third-party library updates (AXI-7702, AXI-7708, AXI-7720).

No public diff

Axigen is closed source, so there is no public commit or diff for this fix. The details above come from the vendor KB article, the release notes, and the VulnCheck advisory.

Timeline

  • November 2, 2026: Axigen advisory (KB article #413) dated.
  • November 10, 2026: Axigen 10.6.41 and 10.7.3 released.
  • November 16, 2026: CVE-2026-127218 published.

Affected systems and versions

Axigen Mail Server, WebAdmin and WebMail HTTP services (the crash affects all services in the Axigen process, including SMTP, IMAP, and POP3):

  • 10.3.3 line: 10.3.3.67 and later 10.3.3.x builds
  • 10.4 line: 10.4.42 and later 10.4.x builds
  • 10.5 line: 10.5.29 and later 10.5.x builds (Axigen's advisory lists 10.5.29 through 10.5.68)
  • 10.6 line: all 10.6.x versions before 10.6.41
  • 10.7 line: 10.7.x versions before 10.7.3 (10.7.0 through 10.7.2)

Any deployment where an attacker has network access to a WebAdmin or WebMail listener is vulnerable. Authentication is not required.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization