CVE-2025-62826: An Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting') vulnerability [CWE...
An Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting') vulnerability [CWE-113] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.4, FortiOS 7.4 all versions, FortiOS 7.2 all versions, FortiProxy 7.6.0 through 7.6.4, FortiProxy 7.4 all versions, FortiProxy 7.2 all versions may allow an attacker able to intercept and modify a user's captive portal authentication request to inject arbitrary headers via crafted HTTP requests.
Security readout for executives and security teams
Plain-English summary
CVE-2025-62826 is a low-severity Fortinet captive portal issue. If an attacker can intercept and alter a user’s authentication request, they may inject arbitrary HTTP headers. The cited description names FortiOS and FortiProxy; product/version data in the bundle also lists FortiPAM, but that conflicts with the narrative description.
Executive priority
Treat this as a routine but real Fortinet maintenance item, not an emergency. Prioritize environments using captive portal authentication, especially where untrusted networks or interception risk exist. Resolve version ambiguity through the Fortinet advisory before broad remediation.
Technical view
The issue is CWE-113 HTTP response splitting caused by improper neutralization of CRLF sequences in HTTP headers. The CVSS 3.1 score is 3.1, with network access, high attack complexity, required user interaction, no confidentiality impact, low integrity impact, and no availability impact.
Likely exposure
Most relevant exposure is Fortinet captive portal authentication traffic on listed FortiOS or FortiProxy versions. The attack requires interception and modification of a user request, so ordinary internet reachability alone is not enough evidence of exploitable exposure.
Exploitation context
The bundle does not indicate CISA KEV listing or confirmed active exploitation. CVSS marks exploit code maturity as proof-of-concept, but the provided sources do not describe real-world exploitation or provide operational exploit details.
Researcher notes
The main uncertainty is affected-product consistency: the description names FortiOS and FortiProxy, while the structured affected list includes FortiPAM and broader historical branches. Do not overstate FortiPAM exposure without vendor confirmation.
Mitigation direction
Review Fortinet FG-IR-26-153 for fixed releases and official remediation.
Prioritize upgrades for FortiOS and FortiProxy captive portal deployments.
Check whether FortiPAM applicability is confirmed by Fortinet before acting on that listing.
Limit exposure of captive portal authentication paths where operationally feasible.
Monitor Fortinet advisory updates for clarified affected versions.
Validation and detection
Inventory FortiOS, FortiProxy, and any listed FortiPAM versions.
Identify systems using captive portal authentication workflows.
Compare deployed versions against Fortinet FG-IR-26-153 guidance.
Review network paths where user authentication traffic could be intercepted or modified.
Check security monitoring for unusual captive portal header or redirect behavior.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-113: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-113 · source CWE mapping
Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.