CVE-2026-13576

CallBackery versions before 0.62.0 for Perl store user passwords as unsalted HMAC-SHA1 hashes

Published Oct 30, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
CallBackery versions before 0.62.0 for Perl store user passwords as unsalted HMAC-SHA1 hashes.

Passwords are hashed with hmac_sha1_sum() from Mojo::Util with no key, a single fast SHA-1 HMAC. There is no salt, so equal passwords give equal hashes, and no work factor slows down guessing.

An attacker who obtains the user table can recover passwords by fast offline guessing.

Analysis

AI-generated

Technical impact

CallBackery versions before 0.62.0 store user passwords as unsalted HMAC‑SHA1 hashes using hmac_sha1_sum() with no key. The hashes are identical for equal passwords and lack any work factor, making them vulnerable to offline brute‑force or dictionary attacks. While the vendor does not recommend storing passwords in clear text, the use of an unsalted fast hash permits rapid credential harvesting if the password storage is exfiltrated.

Affected Systems

All CallBackery releases prior to version 0.62.0 are affected. The product is a Perl library used for authentication, and the vulnerability applies to any deployment that relies on the default password hashing routine in these versions.

Risk and Exploitability

The EPSS score indicates a very low exploitation probability (< 1%), and the vulnerability is not listed in CISA KEV. Exploitation requires possession of the stored password table. This could arise from a database breach, misconfigured database permissions, or an administrative data exposure, which are inferred based on common attack scenarios. Once the table is obtained, the unsalted hashes enable rapid recovery of plain‑text passwords. The risk level depends on the number of exposed accounts and the sensitivity of the protected services. The CVSS score of 7.5 indicates a high risk for credential compromise.

Remediation

Vendor Solution

Upgrade to CallBackery 0.62.0 or later.


OpenCVE Recommended Actions

  • Upgrade CallBackery to version 0.62.0 or later.
  • After upgrading, rehash existing user passwords with a salted algorithm such as bcrypt or Argon2 to eliminate stale unsalted hashes.
  • Review database access controls and audit logs to ensure that unauthorized access to the user table is detected.

Generated by OpenCVE AI on November 6, 2026 at 19:09 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Type Values Removed Values Added
First Time appeared Perl
Perl callbackery
Vendors & Products Perl
Perl callbackery
Type Values Removed Values Added
Description CallBackery versions before 0.62.0 for Perl store user passwords as unsalted HMAC-SHA1 hashes. Passwords are hashed with hmac_sha1_sum() from Mojo::Util with no key, a single fast SHA-1 HMAC. There is no salt, so equal passwords give equal hashes, and no work factor slows down guessing. An attacker who obtains the user table can recover passwords by fast offline guessing.
Title CallBackery versions before 0.62.0 for Perl store user passwords as unsalted HMAC-SHA1 hashes
Weaknesses CWE-759
CWE-916
References
Weaknesses
  • CWE-759

    Use of a One-Way Hash without a Salt

  • CWE-916

    Use of Password Hash With Insufficient Computational Effort

Sources

Status
PUBLISHED
Assigner
CPANSec
Published
Updated
Nov 6, 2026, 4:54 PM
Reserved
Jun 28, 2026, 8:49 PM
Status
Deferred
Published
Oct 30, 2026, 1:18 PM
Modified
Nov 6, 2026, 5:17 PM