# CVE-2026-6805: Vulnerability on Cryptobox external sharing feature

> An attacker with a sharing link can retrieve server information to offline brute-force the access code, compromising shared data confidentiality.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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:** 7 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-p3ph-4r57-hh5x

## What is CVE-2026-6805?

CVE-2026-6805 is a medium-severity vulnerability in Ercom Cryptobox, published on 7 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability on the external sharing feature in Cryptobox allows an attacker knowing a sharing link URL to retrieve information from the server allowing an offline brute-force attack of the access code associated to this sharing link.

Weakness: CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

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

It affects 1 product.


Products: Thalesgroup Ercom Cryptobox.

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

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

## Is CVE-2026-6805 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6805 is a medium-severity vulnerability in Ercom Cryptobox, published on 7 May 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-6805 in the wild and no public exploit code.

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

## Sources

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

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