Quick answers
- Is CVE-2026-118995 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118995 being exploited in the wild.
- How severe is CVE-2026-118995?
- 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-118995?
- 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-118995 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118995?
- 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 createRxValidator() function constructs regex patterns as /^${rx}$/ without grouping, causing alternation operators (|) to behave unexpectedly: a pattern like "yes|no" matches any value starting with "yes" or ending with "no", and the trailing $ anchor accepts values with a trailing newline. An authenticated user can exploit this to bypass form validation and submit unintended values that an application may write into generated configuration files.
Affected products
- OETIKER CallBackery before 0.62.0
Timeline
- 2026-10-30: disclosed