CVE-2026-6805
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVulnerability 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe vulnerability exists in Cryptobox's external sharing feature. An attacker who knows or can guess a sharing link URL can retrieve certain information from the server that enables an offline brute-force attack against the access code protecting that sharing link. This is essentially an information disclosure that reveals data allowing the access code to be cracked offline rather than requiring online attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.37.248, < 4.38.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Cryptobox versionRetrieve the installed Cryptobox version from the application or system information panel, or run the appropriate version command for your deployment (e.g., cryptobox --version, or check the about page in the web UI)Affected if The installed version is >= 4.37.248 and < 4.38.0
-
Verify external sharing feature is enabledCheck the Cryptobox administrative settings or configuration file to confirm whether the external sharing feature is currently enabled for usersAffected if External sharing is enabled and the version is in the affected range
-
Identify active sharing linksReview the sharing links created in the system through the admin console or by querying the database for entries with sharing enabledAffected if Any sharing links exist and the version is in the affected range
-
Inspect server response for sharing link requestsMake a test request to a known sharing link URL and capture the server response headers and body to check for information that could aid offline brute-force attacks (such as salts, stretched keys, or authentication artifacts)Affected if The server returns additional authentication-related data beyond what is needed for legitimate link access
A user is affected if Cryptobox version is between 4.37.248 and 4.38.0 (exclusive) and the external sharing feature is enabled with active sharing links.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.38.0
The fix requires modifying the server-side code to stop returning the information that facilitates offline brute-force attacks on sharing link access codes, while maintaining legitimate sharing functionality. Additionally, rate limiting on sharing endpoints and strengthening access code requirements should be considered.
4.38.0 or later
- Identify the current installed version of Ercom Cryptobox
- If the version is >= 4.37.248 and < 4.38.0, the installation is vulnerable
- Upgrade to version 4.38.0 or later to remediate the vulnerability
- Verify the upgrade was successful and the version is no longer in the affected range
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6805 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data