Skip to content
statance
MenuClose
medium · CVSS 6.3

CVE-2026-94206

Cloak PBKDF2 field ignores the configured iteration count and runs only :size rounds

Published 6 Oct 2026 · Source updated 19 Nov 2026 · Retrieved 2026-11-19 08:29 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

Use of Password Hash With Insufficient Computational Effort vulnerability in danielberkompas cloak_ecto and danielberkompas cloak allows an attacker who holds the hashed values and the configured secret to brute-force low-entropy plaintexts much faster than configured.

The dump/1 callback that Cloak.Ecto.PBKDF2 (Cloak.Fields.PBKDF2 in cloak before the Ecto code moved to cloak_ecto) injects into a field module calls :pbkdf2.pbkdf2/4 with config[:size] in the iteration-count position. The :iterations setting is validated but never used. With the cloak_ecto defaults (iterations: 600_000, size: 32) each hash runs 32 PBKDF2 rounds instead of 600,000, so offline guessing of values such as email addresses costs about 18,750 times less than configured.

This issue affects cloak_ecto: from 1.0.0-alpha.0 onward; cloak: from 0.7.0 before 1.0.0-alpha.0.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
cloak_ectodanielberkompasaffected: 1.0.0-alpha.0 to < *See vendor advisory
danielberkompas/cloak_ectodanielberkompasaffected: a8fa1642b02f1c445a1ee8794c9095eb0921f8f3 to < *See vendor advisory
cloakdanielberkompasaffected: 0.7.0 to < 1.0.0-alpha.0See vendor advisory
danielberkompas/cloakdanielberkompasaffected: 8699e6417a162c39d9f0ef63511bd23d3f38d1d2 to < 681c9702b7cd9afe0e5a840751ab009f550c69a9See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed