VulnerabilityPublished 30 Oct 2026

CVE-2026-13576: CallBackery (Perl module) · Weak Password Hashing

Affects CallBackery (Perl module)Source CVE Database V5

Compare

Not known to be exploited : upgrade to 0.62.0 soon.

Data as of 30 Oct 2026, 13:33 UTC

Severity

High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade CallBackery (Perl module) to 0.62.0.

Affected software

Product	Affected	Fixed in
CallBackery	Affected <0.62.0	Fixed in 0.62.0
CPANCallBackery`pkg:cpan/CallBackery`Other threats	Affected <0.62.0	Fixed in 0.62.0

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. No other mitigation is required as the fix is available.

Description

CallBackery versions prior to 0.62.0 for Perl use unsalted HMAC-SHA1 hashes without a key to store user passwords. This hashing approach lacks a salt and computational work factor, making password hashes vulnerable to fast offline guessing attacks if the user table is obtained. The vulnerability is fixed in version 0.62.0.

Impact

An attacker who obtains the user password table can perform fast offline password guessing due to the use of unsalted, computationally inexpensive HMAC-SHA1 hashes. This compromises password confidentiality and user account security.

Summary

CallBackery before version 0.62.0 stores user passwords using the hmac_sha1_sum() function from Mojo::Util without a key and without salting. This results in unsalted, fast SHA-1 HMAC hashes that produce identical hashes for identical passwords and do not slow down brute-force guessing. An attacker who gains access to the user password table can efficiently recover passwords through offline guessing attacks. The issue is addressed in CallBackery 0.62.0, where presumably a more secure password hashing method is implemented.

CWE-916Use of Password Hash With Insufficient Computational Effort (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product generates a hash for a password, but it uses a scheme that does not provide a sufficient level of computational effort that would make password cracking attacks infeasible or expensive.
Architecture and Design
Use an adaptive hash function that can be configured to change the amount of computational effort needed to compute the hash, such as the number of iterations ("stretching") or the amount of memory required. Some hash functions perform salting automatically.
Implementation · Architecture and Design
When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for preventing common attacks.
OWASP Cheat Sheets
Password Storage (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Cryptographic Storage (opens in a new tab)
HSTS (opens in a new tab)
OWASP ASVS 4.0.3
V2.4.3 (opens in a new tab)
V2.4.4 (opens in a new tab)
V2.4.1 (opens in a new tab)
Attack patterns
Rainbow Table Password Cracking (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-759Use of a One-Way Hash without a Salt (opens in a new tab)
Variant weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product does not also use a salt as part of the input.
Architecture and Design
Use an adaptive hash function that can be configured to change the amount of computational effort needed to compute the hash, such as the number of iterations ("stretching") or the amount of memory required. Some hash functions perform salting automatically.
Architecture and Design
If a technique that requires extra computational effort can not be implemented, then for each password that is processed, generate a new random salt using a strong random number generator with unpredictable seeds. Add the salt to the plaintext password before hashing it. When storing the hash, also store the salt.
Implementation · Architecture and Design
When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for preventing common attacks.
OWASP Cheat Sheets
Password Storage (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Cryptographic Storage (opens in a new tab)
HSTS (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.3 (opens in a new tab)
V8.3.7 (opens in a new tab)
V2.4.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

metacpan.org/release/OETIKER/CallBackery-0.62.0/changes (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 13:19 UTC

WeaknessesCWE-916, CWE-759

Technical details

References

Community reviews

Related threats