# CVE-2026-80191: GROWI before 8.0.2 Missing Authorization on Attachment Retrieval for Unauthenticated Requests

> Unauthenticated attackers can retrieve private attachments from GROWI by bypassing permission checks, exposing sensitive files.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 29 Aug 2026
- **Also known as:** GHSA-c3h5-hg99-q693

## What is CVE-2026-80191?

CVE-2026-80191 is a high-severity missing authorization vulnerability in GROWI, Inc. GROWI, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GROWI applies its page-viewer permission check to attachment requests only when the request carries an authenticated user. retrieveAttachmentFromIdParam in apps/app/src/server/routes/attachment/get.ts guards the check with a condition requiring the user to be non-null, so a request that carries no session skips the check entirely and the handler returns the file. The routes reached this way, /attachment/:id and /download/:id, take the attachment identifier from the path, so an unauthenticated caller who has an attachment identifier receives the file regardless of whether the page owning it is private and regardless of whether that caller would be permitted to view the page. Identifiers can be retained by a user whose access was later removed, or recovered from anywhere the identifier was previously exposed. Version 8.0.2 runs the check for authenticated and unauthenticated requests alike, skipping it only where a valid share link has already bound the requested file to that link's page.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-80191?


## How do I fix CVE-2026-80191?

No fix has been published for CVE-2026-80191 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-80191 being exploited?

There is no known exploitation of CVE-2026-80191 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80191 and fix it if it is affected.

What it is: CVE-2026-80191 is a high-severity missing authorization vulnerability in GROWI, Inc. GROWI, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80191 in the wild and no public exploit code.

Affected product: GROWI, Inc. GROWI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80191/ (Markdown: https://insights.sbomify.com/CVE-2026-80191/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80191
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80191
- OSV: https://osv.dev/vulnerability/CVE-2026-80191

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80191/
Summaries are generated and may contain mistakes; the official description above is the record.