Skip to content
Fencer Intel
high 7.5

CVE-2026-118991 json

CallBackery versions before 0.62.0 for Perl encrypt configuration backups with the padded password as the AES key

published 10d ago modified 3d ago also EUVD-2026-113919

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

Summary

CallBackery versions before 0.62.0 for Perl encrypt configuration backups with the padded password as the AES key.

getCrypt() pads the backup password with "x" characters and cuts it to 32 bytes to form the AES key, with no salt and no key derivation. The first block of a backup holds a 16 hex digit length field, so decrypting one block confirms a password guess at raw AES speed.

An attacker who obtains a backup can recover its password by fast offline guessing, and with it every credential the backup holds.

Patch / fix

  • cpan CallBackery 0.62.0

Is CVE-2026-118991 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
3d ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

  • cpan CallBackery

Classification

Weakness
  • CWE-916 Use of Password Hash With Insufficient Computational Effort

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.