VulnerabilityPublished 9 Nov 2026

CVE-2026-117477: GMO Prime Strategy KUSANAGI 7 Security Edition · HTTP Request/Response Splitting

Affects GMO Prime Strategy KUSANAGI 7 Security EditionSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.1 Medium.

Data as of 9 Nov 2026, 23:48 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (jpcert)	CVSS 3.1	6.1
CNA (jpcert)	CVSS 4.0	5.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GMO Prime Strategy Co., Ltd.KUSANAGI 7 Security Edition	Affected <=10.7.2-1	Fixed in–
GMO Prime Strategy Co., Ltd.KUSANAGI 7 Enterprise Edition	Affected <=10.7.2-1	Fixed in–
GMO Prime Strategy Co., Ltd.KUSANAGI 8 Security Edition	Affected <=10.7.2-1	Fixed in–
GMO Prime Strategy Co., Ltd.KUSANAGI 8 Enterprise Edition	Affected <=10.7.2-1	Fixed in–
GMO Prime Strategy Co., Ltd.KUSANAGI 9 Security Edition	Affected <=10.7.2-1	Fixed in–
GMO Prime Strategy Co., Ltd.KUSANAGI 9 Enterprise Edition	Affected <=10.7.2-1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is available, users should monitor vendor communications for updates. No specific mitigation steps are provided in the input data.

Description

KUSANAGI 7 Security Edition by GMO Prime Strategy Co., Ltd. contains an HTTP header injection vulnerability due to improper neutralization of CRLF sequences in HTTP headers. This flaw may allow an attacker to inject arbitrary HTTP headers into the response when a user accesses a specially crafted URL. The vulnerability has a CVSS 3.1 score of 6.1, indicating a medium severity level.

Impact

An attacker can inject arbitrary HTTP headers into the response, potentially leading to HTTP response splitting attacks. This can result in partial control over the HTTP response, which may be leveraged for web cache poisoning, cross-site scripting (XSS), or other attacks that rely on manipulating HTTP headers. The confidentiality and integrity impacts are rated as low, with no availability impact.

References

Community reviews

Loading reviews…