# CVE-2026-108729: Corteza through 2024.9.10 Unauthenticated Attachment Access via Compose Attachment Endpoints

> Unauthenticated attackers can download private attachments by manipulating URL segments, bypassing permission boundaries in Corteza.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/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:** 11 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-8hq6-x78m-7h79

## What is CVE-2026-108729?

CVE-2026-108729 is a high-severity missing authorization vulnerability in cortezaproject corteza, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Corteza through 2024.9.10 contains an incorrect authorization vulnerability in compose attachment endpoints that allows unauthenticated attackers to download private attachments by setting the URL kind segment to page, icon, or namespace. Attackers who know a private record or module attachment id can request the original or preview route without a token or signature to retrieve files across namespace and record permission boundaries.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-108729 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108729 is a high-severity missing authorization vulnerability in cortezaproject corteza, published on 11 Oct 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-108729 in the wild and no public exploit code.

Affected product: cortezaproject corteza. 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-108729/ (Markdown: https://insights.sbomify.com/CVE-2026-108729/index.md)
```

## Sources

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

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