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.
CVE-2026-63099
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 45(Track)EG Risk 45/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 11.1%
- KEV
- Not listed
Published
July 17, 2026
Last Modified
July 17, 2026
Advisory Details (2)
Auto-updated Jul 17, 2026TheHive 4.1.24 Broken Object Level Authorization via Attachment Download Endpoints | Advisories | VulnCheck
https://www.vulncheck.com/advisories/thehive-broken-object-level-authorization-via-attachment-download-endpointsoss/TheHive.md at main · geo-chen/oss · GitHub
https://github.com/geo-chen/oss/blob/main/TheHive.md#finding-2-cross-organisation-attachment-disclosure-via-unauthorized-datastore-endpoint-missing-object-level-authorizationVendor Advisories for CVE-2026-63099(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-17 18:06 UTCEG score recompute
- 2026-07-17 15:50 UTCEG score recompute
- 2026-07-17 15:49 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-63099?
When was CVE-2026-63099 disclosed?
Is CVE-2026-63099 actively exploited?
What is the CVSS score of CVE-2026-63099?
How do I remediate CVE-2026-63099?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63099
Is Your Infrastructure Affected by CVE-2026-63099?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.