Live › vulnerability › CVE-2026-118995
CallBackery's createRxValidator builds an unanchored-group regex, so alternation patterns like yes|no match values that merely start or end with those words, and a trailing newline is accepted. An authenticated user can submit values the form was meant to reject, which the application may write into generated configuration files.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 13:30 UTC. All times on this page are UTC.
Applications built on CallBackery for Perl that use createRxValidator on form fields, especially those whose submitted values are written into generated configuration files. The sources require an authenticated user to exploit it, so public pages without login are less exposed. Teams not using CallBackery can skip it.
No product ranges from the sources yet.
0.62.0 are affected.yes|no) whose values feed generated config files.0.62.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
CallBackery versions before 0.62.0 for Perl accept unintended values in form fields checked by createRxValidator.
createRxValidator() is documented to anchor the supplied pattern at both ends, but builds /^${rx}$/ without grouping the pattern. An alternation such as yes|no then accepts any value starting with yes or ending with no, and $ also accepts a value with one trailing newline.
An authenticated user can submit values the pattern was meant to reject, which an application may then write into generated configuration files.
This page as .md · .json · in your agent: get_signal("CVE-2026-118995")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.