# CVE-2026-118995: CallBackery regex pattern validation bypass in form fields

Source: https://junglewise.ai/threats/cve-2026-118995-callbackery-versions-before-0-62-0-for-perl-accept-unintended  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-30. Updated: 2026-10-30  
License: CC BY 4.0 with a link back

CVE-2026-118995 · Severity: info · Published 2026-10-30

CallBackery is a Perl-based framework for building interactive web applications. The createRxValidator() function fails to properly anchor regular expression patterns, allowing authenticated users to submit form values that should have been rejected, potentially leading to malformed configuration data being written to the system.

Technologies: [OETIKER CallBackery](https://junglewise.ai/threats/technologies/callbackery). Vendors: [OETIKER](https://junglewise.ai/threats/vendors/oetiker).

## 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

## References

- [https://cpan.org/modules](https://cpan.org/modules)
- [https://metacpan.org/release/OETIKER/CallBackery-0.62.0/changes](https://metacpan.org/release/OETIKER/CallBackery-0.62.0/changes)

## Related threats

- [CallBackery session cookie age validation bypass in X-Session-Cookie header](https://junglewise.ai/threats/cve-2026-118987-callbackery-versions-before-0-62-0-for-perl-accept-session)
- [CallBackery Perl session cookie forgery via weak random secret](https://junglewise.ai/threats/cve-2026-118986-callbackery-versions-before-0-62-0-for-perl-allow-session-cookie)
- [CallBackery unsalted HMAC-SHA1 password hashing](https://junglewise.ai/threats/cve-2026-13576-callbackery-versions-before-0-62-0-for-perl-store-user-passwords)
- [CallBackery log injection via newlines in login name](https://junglewise.ai/threats/cve-2026-118994-callbackery-versions-before-0-62-0-for-perl-allow-log-injection)
- [CallBackery denial of service via regex backtracking in request path](https://junglewise.ai/threats/cve-2026-118993-callbackery-versions-before-0-62-0-for-perl-allow-denial-of)