# CVE-2026-63099: TheHive 4.1.24 Broken Object Level Authorization via Attachment Download Endpoints

> Authenticated users can download attachments from other organizations due to missing authorization checks in TheHive.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-6392-9v2x-r546

## What is CVE-2026-63099?

CVE-2026-63099 is a high-severity missing authorization vulnerability in TheHive-Project TheHive, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TheHive through 4.1.24 contains a broken object-level authorization vulnerability in the attachment download endpoints that allows any authenticated user to access attachments belonging to other organizations by supplying a content-hash identifier. Attackers can exploit the missing organization-scoped authorization check in AttachmentSrv.visible, which is implemented as a pass-through traversal, to download arbitrary attachments.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-63099 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63099 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63099 is a high-severity missing authorization vulnerability in TheHive-Project TheHive, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63099 exists.

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

## Sources

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

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