Quick answers
- Is CVE-2026-118991 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118991 being exploited in the wild.
- How severe is CVE-2026-118991?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- OETIKER CallBackery before 0.62.0.
- Is there a fix for CVE-2026-118991?
- Yes: fixed in 0.62.0. Until then: Until upgrading, protect backup files with strict file permissions and ensure they are not accessible to untrusted parties. Use strong, high-entropy backup passwords to increase the computational cost of offline guessing attacks. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118991 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-118991?
- Check whether you run OETIKER CallBackery at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.62.0
Until upgrading, protect backup files with strict file permissions and ensure they are not accessible to untrusted parties. Use strong, high-entropy backup passwords to increase the computational cost of offline guessing attacks.
Technical details
The getCrypt() function in CallBackery pads the backup password with "x" characters, truncates it to 32 bytes, and uses it directly as an AES key with no salt or key derivation function. The first block of encrypted backups contains a 16-character hex length field that allows an attacker to confirm password guesses at raw AES speed during offline dictionary attacks. Successful decryption yields every credential stored in the backup.
Affected products
- OETIKER CallBackery before 0.62.0
Timeline
- 2026-10-30: disclosed
- 2026-10-29: patched