go-guerrilla denial of service via out-of-bounds access in XCLIENT
Only affects go-guerrilla with the non-default xclient_on setting enabled. CVSS scores it High (7.5), and no vendor rating is given. Fixed in 1.6.7-1.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.6.7-1
- Who is exposed
- Specific setups only
Summary
The phires go-guerrilla SMTP server can be crashed by a remote, unauthenticated client that sends a bare XCLIENT command, which terminates the daemon. The flaw applies only when the non-default xclient_on setting is enabled.
Written by a model
Original description
Go-Guerrilla SMTP Daemon is a lightweight SMTP server written in Go. In 1.6.7 and earlier, according to the repository advisory's structured affected range, server.go defines the seven-byte cmdXCLIENT token, but the XCLIENT handler slices input[8:] after matching only that seven-byte verb, so a bare command causes an out-of-bounds panic in handleClient and terminates the daemon because that connection goroutine does not recover the panic. The issue is reachable by an unauthenticated client when the non-default xclient_on setting is enabled; no HELO command is required. The repository fix is present in version 1.6.7-1.
Who should check
Teams running phires go-guerrilla 1.6.7 or earlier with the non-default xclient_on setting enabled, including SMTP servers reachable by unauthenticated clients.
“It is gated by the non-default xclient_on config”
What to do
Check whether your setup matches what the bug needs.
The non-default xclient_on setting is enabledUpgrade to a fixed version: 1.6.7-1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-115578 (go-guerrilla crashes on a bare XCLIENT command (7-byte slice off-by-one panic)), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-115578 (entry last updated 2026-11-19):
Affected:
- phires go-guerrilla: fixed in 1.6.7-1
Fixed versions: 1.6.7-1.
Conditions (all must be true for the bug to be hit):
- The non-default xclient_on setting is enabled (source: https://github.com/phires/go-guerrilla/security/advisories/GHSA-hghq-53p7-c582)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-115578 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-115578 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/phires/go-guerrilla/security/advisories/GHSA-hghq-53p7-c582
- https://github.com/phires/go-guerrilla/commit/b6deed97ff70f52bf34c386d33967694e7330d33
- https://github.com/phires/go-guerrilla/commit/f0d0f2c40dcacf212e3a6a055ae67f7b412affc4
- https://github.com/phires/go-guerrilla/releases/tag/v1.6.7-1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-115578
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-115578"}.Affected versions
- phires go-guerrillafixed in 1.6.7-1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · phires/go-guerrilla · Advisory GHSA-hghq-53p7-c582 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-115578 |
| Record | NVD · CVE-2026-115578 |
| Other links 3 | |
| Repository | GitHub · phires/go-guerrilla · Commit b6deed97 |
| Repository | GitHub · phires/go-guerrilla · Commit f0d0f2c4 |
| Repository | GitHub · phires/go-guerrilla · Release v1.6.7-1 |
Questions about CVE-2026-115578
Is CVE-2026-115578 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A single unauthenticated XCLIENT command, sent bare without its arguments, triggers a slice off-by-one panic that crashes the whole SMTP daemon and causes denial of service.
Source: github.com
Which versions are affected by CVE-2026-115578?
go-guerrilla: before 1.6.7-1.
Source: cve.now feed data
Am I affected, and how do I check?
The affected versions are go-guerrilla releases before 1.6.7-1, and only when the non-default xclient_on setting is enabled. To check, look at the xclient_on value in the go-guerrilla configuration file and see which version is installed.
Source: github.com
How do I fix CVE-2026-115578?
Upgrade go-guerrilla to 1.6.7-1 or later, which is the fixed version.
Source: github.com
Related
- CVE-2025-31135Go-Guerrilla SMTP Daemon allows the PROXY command to be sent multiple times
- CVE-2026-133245parse5 7.0.0 before 8.1.1 Denial of Service via Preprocessor#_processSurrogate
- CVE-2026-130386Contiki-NG through 5.2 Out-of-Bounds Access in MPL Multicast Seed-Set Iteration
- CVE-2026-132150Gimp: out-of-bounds access, invalid free and use-after-free when processing xmc file comments
- CVE-2026-129500@fastify/http-proxy vulnerable to Denial of Service via unhandled error on the WebSocket upgrade socket
- CVE-2026-129502@fastify/http-proxy vulnerable to Denial of Service via a URL fragment in a WebSocket upgrade
No corrections so far. Something wrong on this page? Report an error.