Quick answers
- Is CVE-2026-118993 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118993 being exploited in the wild.
- How severe is CVE-2026-118993?
- 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-118993?
- Yes: fixed in 0.62.0. Until then: The path is now matched as plain text rather than interpolated as a regex pattern, eliminating the backtracking vulnerability. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118993 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118993?
- 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
The path is now matched as plain text rather than interpolated as a regex pattern, eliminating the backtracking vulnerability.
Technical details
The vulnerability exists in the before_dispatch hook, which removes PATH_INFO from the request URI using a substitution that interpolates PATH_INFO unquoted into a regex pattern. Since PATH_INFO originates from the client request, an attacker controls both the regex pattern and the string being matched, allowing them to craft inputs that trigger catastrophic backtracking. An unauthenticated attacker can send a single request to exhaust a worker process.
Affected products
- OETIKER CallBackery before 0.62.0
Timeline
- 2026-10-30: disclosed
- 2026-10-29: patched