VulnerabilityPublished 23 Apr 2026

CVE-2026-41040: GROWI · ReDoS

Affects GROWISource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 30 Oct 2026, 11:34 UTC

CVSS 3.0 base score

7.5High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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

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: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Apr 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 29 Oct 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
GROWI, Inc.GROWI	Affected =v7.5.0 and earlier	Fixed in–

AI-suggested

Until an official fix is available, restrict or sanitize untrusted input that may be processed by regular expressions in GROWI. Monitor vendor channels for updates and apply patches promptly once released.

Description

GROWI, Inc. 's GROWI product version 7.5.0 and earlier contains a vulnerability due to inefficient regular expression complexity, which can be exploited via crafted input strings to cause a denial of service. This vulnerability is classified as a regular expression denial of service (ReDoS). The CVSS v3.0 score is 7.5, indicating a high severity impact primarily affecting availability. There is no information about an official patch or remediation level from the vendor, and no known exploits are reported in the wild. The vulnerability requires no privileges and no user interaction to exploit over the network.

Impact

Successful exploitation of this vulnerability results in denial of service (DoS) by causing the application to consume excessive CPU resources when processing crafted input strings. This impacts system availability but does not affect confidentiality or integrity. The vulnerability can be triggered remotely without authentication or user interaction.

Summary

CVE-2026-41040 is a high severity vulnerability in GROWI, Inc.'s GROWI product (version 7.5.0 and earlier) caused by inefficient regular expression complexity. This flaw allows an attacker to craft input strings that trigger excessive processing time in regular expression evaluation, resulting in a denial of service condition. The vulnerability can be exploited remotely without authentication or user interaction, impacting the availability of the affected system.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Apr 2026, 08:15 UTC

Technical details

References

Community reviews

Related threats