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 · CVSS 5.5 Medium : upgrade to 0.62.0 when convenient.
Data as of 9 Nov 2026, 11:38 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 5.5 |
|---|
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.62.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation 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 9 Nov 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 vulnerability is fixed. The fixed version ensures that temporary files are created with secure permissions and are properly removed after use, preventing unauthorized access to sensitive data.
Description
CallBackery versions prior to 0.62.0 for Perl create a temporary configuration database dump file in /tmp with insecure permissions. This file is world-readable and not deleted after creation, exposing sensitive data including password hashes. Local users can read the dump or redirect it via a symlink to arbitrary files, leading to potential information disclosure.