CVE-2026-118996: CallBackery (Perl module) · Improper Removal of Sensitive Information Before Storage or Transfer
Affects CallBackery (Perl module)Source CVE Database V5
Not known to be exploited : upgrade to 0.62.0 soon.
Data as of 30 Oct 2026, 13:33 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
Upgrade CallBackery to version 0.62.0 or later, where this issue is fixed. The vendor has released an official fix that properly restricts access to sensitive fields in getUserConfig and related functions.
Description
CallBackery versions prior to 0.62.0 for Perl improperly expose sensitive information through the getUserConfig function. Non-administrative users can access their own password hash and administrator-only notes, which should be restricted. This flaw allows attackers with a session token to retrieve password hashes and potentially crack them offline.