CVE-2026-118994: CallBackery versions before 0.62.0 for Perl allow log injection via newlines in the login name
Source GCVE Database
Not known to be exploited : upgrade to 0.62.0 soon.
Data as of 30 Oct 2026, 17:03 UTC
Rated High 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
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| CallBackery | Affected
| Fixed in
|
CPANCallBackerypkg:cpan/CallBackeryOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in CallBackery version 0.62.0 and later. Users should upgrade to version 0.62.0 or newer to address this log injection vulnerability. Until then, avoid using vulnerable versions or implement log sanitization to escape control characters in login names.
Description
CallBackery versions before 0.62.0 for Perl are vulnerable to log injection via newlines in the login name. The login() function writes the login name to application logs without escaping control characters, allowing an unauthenticated attacker to forge log records, including fake administrator login entries.