CVE-2025-31135: CWE-20: Improper Input Validation in phires go-guerrilla
CVE-2025-31135 is a medium severity vulnerability in the go-guerrilla SMTP daemon versions prior to 1. 6. 7. When the ProxyOn feature is enabled, the server improperly accepts multiple PROXY commands, allowing later commands to override earlier ones. This behavior enables a client to spoof its IP address by sending additional PROXY commands, which the server mistakenly treats as coming from a trusted reverse proxy. The vulnerability stems from improper input validation (CWE-20) and can lead to integrity issues, such as bypassing IP-based access controls or logging incorrect client IPs. No authentication or user interaction is required, and the vulnerability is exploitable remotely over the network. The issue is fixed in version 1. 6. 7.
AI Analysis
Technical Summary
The go-guerrilla SMTP daemon is a lightweight SMTP server implemented in Go, commonly used for mail relay services. In versions prior to 1.6.7, when the ProxyOn feature is enabled, the server accepts the PROXY protocol command multiple times during a single SMTP session. The PROXY protocol is designed to pass client connection information, such as the originating IP address, from a reverse proxy to the backend server. However, the protocol specification only supports a single initial PROXY header; any subsequent PROXY commands should be treated as part of the SMTP data exchange, not as proxy headers. Due to improper input validation (CWE-20), go-guerrilla incorrectly processes multiple PROXY commands, allowing an attacker to send additional PROXY commands with arbitrary data. This flaw enables an attacker to spoof the client IP address as seen by the SMTP server, potentially bypassing IP-based access controls, misleading logging and monitoring systems, or evading detection mechanisms that rely on accurate client IP information. The vulnerability does not affect confidentiality or availability directly but impacts integrity by allowing manipulation of client identity. Exploitation requires no authentication or user interaction and can be performed remotely over the network. The issue was publicly disclosed and fixed in version 1.6.7 of go-guerrilla. No known exploits are currently reported in the wild.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to the integrity of SMTP client identification. Organizations relying on go-guerrilla SMTP servers with ProxyOn enabled may have their IP-based access controls circumvented, allowing unauthorized senders to relay mail or bypass anti-spam and anti-abuse filters. Spoofed IP addresses can also corrupt email logs and monitoring data, complicating incident response and forensic investigations. This could lead to increased spam, phishing, or malware distribution through compromised or misconfigured mail infrastructure. While the vulnerability does not directly compromise data confidentiality or server availability, the trustworthiness of email source information is undermined, which is critical for compliance with European data protection and cybersecurity regulations. Organizations with strict email security policies or those operating in regulated sectors such as finance, healthcare, or government are particularly at risk. The lack of known exploits in the wild suggests limited immediate threat but does not preclude future exploitation attempts.
Mitigation Recommendations
European organizations should immediately upgrade all go-guerrilla SMTP daemon instances to version 1.6.7 or later, where this vulnerability is patched. If upgrading is not immediately feasible, administrators should disable the ProxyOn feature to prevent processing of PROXY commands. Network-level controls should be implemented to restrict SMTP access to trusted reverse proxies only, minimizing exposure to untrusted clients. Additionally, organizations should audit their SMTP logs for suspicious multiple PROXY commands or anomalous IP address changes within sessions. Deploying intrusion detection systems (IDS) or email security gateways capable of detecting proxy protocol anomalies can help identify exploitation attempts. Reviewing and tightening IP-based access control lists and anti-spam rules to consider this vulnerability is advisable. Finally, organizations should ensure that their incident response teams are aware of this issue and prepared to investigate potential spoofing incidents.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Sweden
CVE-2025-31135: CWE-20: Improper Input Validation in phires go-guerrilla
Description
CVE-2025-31135 is a medium severity vulnerability in the go-guerrilla SMTP daemon versions prior to 1. 6. 7. When the ProxyOn feature is enabled, the server improperly accepts multiple PROXY commands, allowing later commands to override earlier ones. This behavior enables a client to spoof its IP address by sending additional PROXY commands, which the server mistakenly treats as coming from a trusted reverse proxy. The vulnerability stems from improper input validation (CWE-20) and can lead to integrity issues, such as bypassing IP-based access controls or logging incorrect client IPs. No authentication or user interaction is required, and the vulnerability is exploitable remotely over the network. The issue is fixed in version 1. 6. 7.
AI-Powered Analysis
Technical Analysis
The go-guerrilla SMTP daemon is a lightweight SMTP server implemented in Go, commonly used for mail relay services. In versions prior to 1.6.7, when the ProxyOn feature is enabled, the server accepts the PROXY protocol command multiple times during a single SMTP session. The PROXY protocol is designed to pass client connection information, such as the originating IP address, from a reverse proxy to the backend server. However, the protocol specification only supports a single initial PROXY header; any subsequent PROXY commands should be treated as part of the SMTP data exchange, not as proxy headers. Due to improper input validation (CWE-20), go-guerrilla incorrectly processes multiple PROXY commands, allowing an attacker to send additional PROXY commands with arbitrary data. This flaw enables an attacker to spoof the client IP address as seen by the SMTP server, potentially bypassing IP-based access controls, misleading logging and monitoring systems, or evading detection mechanisms that rely on accurate client IP information. The vulnerability does not affect confidentiality or availability directly but impacts integrity by allowing manipulation of client identity. Exploitation requires no authentication or user interaction and can be performed remotely over the network. The issue was publicly disclosed and fixed in version 1.6.7 of go-guerrilla. No known exploits are currently reported in the wild.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to the integrity of SMTP client identification. Organizations relying on go-guerrilla SMTP servers with ProxyOn enabled may have their IP-based access controls circumvented, allowing unauthorized senders to relay mail or bypass anti-spam and anti-abuse filters. Spoofed IP addresses can also corrupt email logs and monitoring data, complicating incident response and forensic investigations. This could lead to increased spam, phishing, or malware distribution through compromised or misconfigured mail infrastructure. While the vulnerability does not directly compromise data confidentiality or server availability, the trustworthiness of email source information is undermined, which is critical for compliance with European data protection and cybersecurity regulations. Organizations with strict email security policies or those operating in regulated sectors such as finance, healthcare, or government are particularly at risk. The lack of known exploits in the wild suggests limited immediate threat but does not preclude future exploitation attempts.
Mitigation Recommendations
European organizations should immediately upgrade all go-guerrilla SMTP daemon instances to version 1.6.7 or later, where this vulnerability is patched. If upgrading is not immediately feasible, administrators should disable the ProxyOn feature to prevent processing of PROXY commands. Network-level controls should be implemented to restrict SMTP access to trusted reverse proxies only, minimizing exposure to untrusted clients. Additionally, organizations should audit their SMTP logs for suspicious multiple PROXY commands or anomalous IP address changes within sessions. Deploying intrusion detection systems (IDS) or email security gateways capable of detecting proxy protocol anomalies can help identify exploitation attempts. Reviewing and tightening IP-based access control lists and anti-spam rules to consider this vulnerability is advisable. Finally, organizations should ensure that their incident response teams are aware of this issue and prepared to investigate potential spoofing incidents.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-03-26T15:04:52.627Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 697a92d04623b1157cf6c713
Added to database: 1/28/2026, 10:50:56 PM
Last enriched: 1/28/2026, 11:05:21 PM
Last updated: 1/29/2026, 1:03:12 AM
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-1552: SQL Injection in SEMCMS
MediumCVE-2025-15344: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in Tanium Asset
MediumCVE-2026-1551: SQL Injection in itsourcecode School Management System
MediumCVE-2024-52807: CWE-611: Improper Restriction of XML External Entity Reference in HL7 fhir-ig-publisher
HighCVE-2026-1550: Improper Authorization in PHPGurukul Hospital Management System
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.