CVE-2026-39971: CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') in s9y Serendipity
Serendipity versions prior to 2. 6. 0 contain a vulnerability where the HTTP Host header is inserted into the SMTP Message-ID header without proper validation. This allows attackers who can control the Host header during email-triggering actions to inject arbitrary SMTP headers. The vulnerability enables identity spoofing, reply hijacking, and abuse of email reputation by embedding attacker-controlled domains in legitimate email headers. The issue is fixed in Serendipity version 2. 6. 0.
AI Analysis
Technical Summary
CVE-2026-39971 is an HTTP request/response splitting vulnerability (CWE-113) in Serendipity weblog engine versions before 2.6.0. The email sending function in include/functions.inc.php uses the $_SERVER['HTTP_HOST'] value directly in the SMTP Message-ID header without applying the sanitization function serendipity_isResponseClean(). An attacker able to manipulate the Host header during email-triggering events (e.g., comment notifications) can inject arbitrary SMTP headers into outgoing emails. This can lead to identity spoofing, reply hijacking through manipulated Message-ID threading, and email reputation abuse by inserting attacker-controlled domains into email headers. The vulnerability has been addressed in version 2.6.0.
Potential Impact
An attacker controlling the Host header can inject arbitrary SMTP headers into emails sent by Serendipity, enabling identity spoofing and reply hijacking. This can undermine email trust and reputation by associating attacker domains with legitimate emails. There is no indication of direct system compromise or denial of service. The CVSS score of 7.2 reflects a high severity with network attack vector, no privileges required, no user interaction, and partial confidentiality and integrity impact.
Mitigation Recommendations
Upgrade Serendipity to version 2.6.0 or later, where this vulnerability is fixed. Since the vendor advisory confirms the issue is resolved in 2.6.0, applying this official fix is the recommended remediation. No other mitigations are specified or required.
CVE-2026-39971: CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') in s9y Serendipity
Description
Serendipity versions prior to 2. 6. 0 contain a vulnerability where the HTTP Host header is inserted into the SMTP Message-ID header without proper validation. This allows attackers who can control the Host header during email-triggering actions to inject arbitrary SMTP headers. The vulnerability enables identity spoofing, reply hijacking, and abuse of email reputation by embedding attacker-controlled domains in legitimate email headers. The issue is fixed in Serendipity version 2. 6. 0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-39971 is an HTTP request/response splitting vulnerability (CWE-113) in Serendipity weblog engine versions before 2.6.0. The email sending function in include/functions.inc.php uses the $_SERVER['HTTP_HOST'] value directly in the SMTP Message-ID header without applying the sanitization function serendipity_isResponseClean(). An attacker able to manipulate the Host header during email-triggering events (e.g., comment notifications) can inject arbitrary SMTP headers into outgoing emails. This can lead to identity spoofing, reply hijacking through manipulated Message-ID threading, and email reputation abuse by inserting attacker-controlled domains into email headers. The vulnerability has been addressed in version 2.6.0.
Potential Impact
An attacker controlling the Host header can inject arbitrary SMTP headers into emails sent by Serendipity, enabling identity spoofing and reply hijacking. This can undermine email trust and reputation by associating attacker domains with legitimate emails. There is no indication of direct system compromise or denial of service. The CVSS score of 7.2 reflects a high severity with network attack vector, no privileges required, no user interaction, and partial confidentiality and integrity impact.
Mitigation Recommendations
Upgrade Serendipity to version 2.6.0 or later, where this vulnerability is fixed. Since the vendor advisory confirms the issue is resolved in 2.6.0, applying this official fix is the recommended remediation. No other mitigations are specified or required.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-08T00:01:47.627Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69ded57682d89c981f20b4a8
Added to database: 4/15/2026, 12:01:58 AM
Last enriched: 4/15/2026, 12:16:54 AM
Last updated: 4/15/2026, 1:03:48 AM
Views: 5
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.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.