Quick answers
- Is CVE-2026-118992 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118992 being exploited in the wild.
- How severe is CVE-2026-118992?
- 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-118992?
- Yes: fixed in 0.62.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118992 attacked?
- It is attacked with local access or over the network, in a software library.
- Am I affected by CVE-2026-118992?
- 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
Technical details
The restoreConfigBlob() function passes a database dump directly to the sqlite3 shell without sanitizing input, allowing shell metacommands like .shell, .system, and .load to execute arbitrary code. This requires an attacker to supply a malicious backup file that will be restored, and the vulnerability is fixed in version 0.62.0 by replaying the database as plain SQL and refusing shell commands and certain SQL constructs.
Affected products
- Oetiker CallBackery before 0.62.0
Timeline
- 2026-10-29: patched
- 2026-10-30: disclosed