Skip to main content
VulnerabilityPublished

CVE-2026-118995: CallBackery (Perl module) · Permissive Regular Expression

Affects CallBackery (Perl module)Source CVE Database V5

0
Compare

Not known to be exploited : upgrade to 0.62.0 when convenient.

Data as of 30 Oct 2026, 13:33 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 0.62.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade CallBackery (Perl module) to 0.62.0.

Affected software

ProductAffectedFixed in
CallBackeryAffected
  • <0.62.0
Fixed in
  • 0.62.0
CPANCallBackerypkg:cpan/CallBackeryOther threatsAffected
  • <0.62.0
Fixed in
  • 0.62.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade CallBackery to version 0.62.0 or later, where this issue is fixed by properly grouping the regular expression patterns in createRxValidator. No other mitigation is indicated by the vendor advisory.

Description

CallBackery versions before 0.62.0 for Perl contain a permissive regular expression vulnerability in the createRxValidator function. The function is intended to anchor patterns strictly but fails to group alternations properly, allowing unintended values to pass validation. This flaw permits authenticated users to submit values that should be rejected, potentially leading to unsafe data being written into generated configuration files.

References

Community reviews

Loading reviews…