Description
CallBackery versions before 0.62.0 for Perl allow session cookie forgery via a signing secret generated with rand().

The secret that signs session cookies is built from two calls to the built-in rand(), which is seeded with 32 bits. The secret therefore has at most 2**32 possible values, and one signed cookie is enough to test each candidate offline.

An attacker who obtains a single session cookie can recover the secret and sign cookies for any user, including an administrator.
Published: 2026-10-30
Score: n/a
EPSS: n/a
KEV: No
Impact: Session cookie forgery allowing impersonation of any user, including administrators
Action: Immediate Patch
AI Analysis

Impact

The vulnerability arises because CallBackery generates the session cookie signing secret by calling the non-cryptographic rand() function twice, which is seeded with only 32 bits. As a result, the secret can have at most 2^32 possibilities, and a single captured signed cookie is enough to brute‑force the secret offline, after which an attacker can sign arbitrary cookies. This flaw enables an attacker to impersonate any user, including privileged accounts, thereby compromising confidentiality, integrity, and availability of the system. The weakness is an instance of CWE‑338 (Prediction or Guessing of a Secret).

Affected Systems

CallBackery for Perl, versions prior to 0.62.0. No other vendors or products are listed as affected.

Risk and Exploitability

Because the secret’s entropy is limited to 32 bits, brute‑forcing it is computationally trivial; an attacker only needs a single valid session cookie to recover the secret and forge any number of additional cookies. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. The attack vector is inferred to be remote, requiring the attacker to obtain a session cookie in transit or via client‑side exploitation. The risk is high due to the ease of exploitation and the severity of potential impact.

Generated by OpenCVE AI on October 30, 2026 at 14:23 UTC.

Remediation

Vendor Solution

Upgrade to CallBackery 0.62.0 or later.


OpenCVE Recommended Actions

  • Upgrade CallBackery to version 0.62.0 or later, which replaces the rand() based signing secret with a more secure mechanism.
  • Invalidate or delete all existing session cookies on the system to close any existing exploitation window, such as by restarting the application or rotating the session configuration.
  • Reconfigure the application to use a cryptographically secure random number generator for session cookie signing until the official patch is applied, ensuring the signing secret cannot be predicted or reproduced.

Generated by OpenCVE AI on October 30, 2026 at 14:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 30 Oct 2026 13:30:00 +0000

Type Values Removed Values Added
Description CallBackery versions before 0.62.0 for Perl allow session cookie forgery via a signing secret generated with rand(). The secret that signs session cookies is built from two calls to the built-in rand(), which is seeded with 32 bits. The secret therefore has at most 2**32 possible values, and one signed cookie is enough to test each candidate offline. An attacker who obtains a single session cookie can recover the secret and sign cookies for any user, including an administrator.
Title CallBackery versions before 0.62.0 for Perl allow session cookie forgery via a signing secret generated with rand()
Weaknesses CWE-338
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: CPANSec

Published:

Updated: 2026-10-30T13:13:32.845Z

Reserved: 2026-10-29T10:48:23.002Z

Link: CVE-2026-118986

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-10-30T14:16:41.543

Modified: 2026-10-30T17:08:54.633

Link: CVE-2026-118986

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-30T14:30:08Z

Weaknesses
  • CWE-338

    Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)