Skip to content
Fencer Intel
critical 9.1

CVE-2026-118995 json

CallBackery versions before 0.62.0 for Perl accept unintended values in form fields checked by createRxValidator

published 10d ago modified 3d ago also EUVD-2026-113915

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

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.

Patch / fix

  • cpan CallBackery 0.62.0

Is CVE-2026-118995 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
3d ago

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

  • cpan CallBackery

Classification

Weakness
  • CWE-625 Permissive Regular Expression

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.