Quick answers
- Is CVE-2026-118990 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118990 being exploited in the wild.
- How severe is CVE-2026-118990?
- 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-118990?
- Yes: fixed in 0.62.0. Until then: Delete any leftover /tmp/cbdump* files from the system, and upgrade to version 0.62.0 or later where backups no longer write database dumps to /tmp. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118990 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-118990?
- 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
Delete any leftover /tmp/cbdump* files from the system, and upgrade to version 0.62.0 or later where backups no longer write database dumps to /tmp.
Technical details
The getConfigBlob() function writes an SQLite3 database dump to a predictable filename (/tmp/cbdump<pid>) without restricting file permissions, and the file is never deleted after backup completion. The vulnerability involves a symlink-following race condition with a predictable filename; a local attacker with knowledge of process IDs can create a symlink at the target location to redirect sensitive data. This affects all versions before 0.62.0 and requires local filesystem access.
Affected products
- OETIKER CallBackery before 0.62.0
Timeline
- 2026-10-30: disclosed
- 2026-10-29: patched: Fix released in version 0.62.0