CVE-2026-25083: GROWI · Missing Authorization
Affects GROWISource CVE Database V5
Not known to be exploited · CVSS 8.3 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 16 Mar 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GROWI, Inc.GROWI | Affected
| Fixed in– |
AI-suggested
Organizations should immediately upgrade GROWI to a version later than 7.4.5 where this vulnerability is patched. If an upgrade is not immediately feasible, implement strict access controls on the AI assistant identifiers to prevent unauthorized users from discovering or using them. Audit and monitor API access logs for unusual activity related to thread/message endpoints. Enforce strong authentication and session management policies to reduce the risk of credential compromise. Consider restricting API endpoint access to trusted networks or VPNs. Conduct a thorough review of user permissions and remove unnecessary privileges. Additionally, implement application-layer authorization checks as a compensating control until official patches are applied. Regularly back up critical data to enable recovery in case of tampering.
Description
GROWI OpenAI thread/message API endpoints do not perform authorization. Affected are v7.4.5 and earlier versions. A logged-in user who knows a shared AI assistant's identifier may view and/or tamper the other user's threads/messages.