CVE-2026-118990: CallBackery (Perl module) · Creation of Temporary File in Directory with Insecure Permissions
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 fixed version removes the insecure temporary file creation and ensures the dump file is properly handled and removed. No other mitigation is indicated.
Description
CallBackery versions prior to 0.62.0 for Perl create a temporary configuration database dump in /tmp with insecure permissions. The dump file is world-readable and not removed after creation, exposing sensitive data including password hashes. A local user can exploit this by reading the dump or redirecting it via a symlink to a file of their choosing.