CVE-2026-118990: CallBackery versions before 0.62.0 for Perl leave a world-readable dump of the configuration
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
Upgrade to CallBackery version 0.62.0 or later where this issue is fixed. Until then, restrict local user access to the /tmp directory and monitor for unauthorized symlinks named cbdump<pid>. Remove any existing dump files promptly after backups.
Description
CallBackery versions prior to 0.62.0 for Perl create a world-readable configuration dump file in /tmp during backups. This dump contains sensitive data including all user password hashes and form values. The dump file is not removed after creation and inherits the process umask, allowing local users to read it or redirect it via a symlink to a file of their choosing.