Quick answers
- Is CVE-2026-118994 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118994 being exploited in the wild.
- How severe is CVE-2026-118994?
- 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-118994?
- Yes: fixed in 0.62.0. Until then: Control characters in login names are now logged as escaped sequences (e.g., \x{0A} for newline) in version 0.62.0 and later, preventing injection of forged log records. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118994 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118994?
- 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
Control characters in login names are now logged as escaped sequences (e.g., \x{0A} for newline) in version 0.62.0 and later, preventing injection of forged log records.
Technical details
The login() RPC method does not escape control characters (specifically newlines) before writing the login name to the application log, allowing log injection. Since the login method requires no authentication, an attacker can craft a login attempt with a newline-delimited payload to inject additional log records in the format of successful authenticated actions.
Affected products
- OETIKER CallBackery before 0.62.0
Timeline
- 2026-10-30: disclosed
- 2026-10-29: patched