dbcve.org
Crypt\Application · Ddick

CVE-2026-2474

HIGH · 7.5 CVSS v3.1 Published 2026-02-16
Fix available
A fix is available. Upgrade to 0.55 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Crypt::URandom versions from 0.41 before 0.55 for Perl is vulnerable to a heap buffer overflow in the XS function crypt_urandom_getrandom(). The function does not validate that the length parameter is non-negative. If a negative value (e.g. -1) is supplied, the expression length + 1u causes an integer wraparound, resulting in a zero-byte allocation. The subsequent call to getrandom(data, length, GRND_NONBLOCK) passes the original negative value, which is implicitly converted to a large unsigned value (typically SIZE_MAX). This can result in writes beyond the allocated buffer, leading to heap memory corruption and application crash (denial of service). In common usage, the length argument is typically hardcoded by the caller, which reduces the likelihood of attacker-controlled exploitation. Applications that pass untrusted input to this parameter may be affected.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Crypt::URandom versions 0.41-0.55 have a heap buffer overflow in crypt_urandom_getrandom() where missing validation of negative length parameters causes integer wraparound (length+1u = 0) during allocation, then getrandom() receives the negative value converted to SIZE_MAX, resulting in writes beyond the allocated buffer and heap corruption.

MitigationUpgrade Crypt::URandom to version 0.55 or later. As a defense-in-depth measure, validate that any caller-provided length values are non-negative before passing to this function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Crypt\Application
Affected:>= 0.41, < 0.55

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Crypt::URandom module is installed
    Run `perl -MCrypt::URandom -e 'print $Crypt::URandom::VERSION'` or check your Perl environment's module list
    Affected if The module is not installed
  2. Determine the installed version of Crypt::URandom
    Extract the version number from the output of the perl command above or from your dependency manifest (cpanfile, Makefile.PL, or similar)
    Affected if The version cannot be determined or the module is not present
  3. Compare version to affected range
    Check if the installed version falls within >= 0.41 and < 0.55
    Affected if Installed version is 0.41, 0.42, 0.43, 0.44, 0.45, 0.46, 0.47, 0.48, 0.49, 0.50, 0.51, 0.52, 0.53, or 0.54
  4. Audit code calling crypt_urandom_getrandom
    Search your codebase for calls to functions that ultimately invoke crypt_urandom_getrandom() and inspect whether any caller-provided length arguments could be negative
    Affected if Code paths exist that can pass negative length values to the vulnerable function

Your environment is affected if Crypt::URandom version is 0.41 through 0.55 and code can invoke crypt_urandom_getrandom() with a negative length parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.55 or later
Fixed in 0.55
Interim mitigation

Upgrade Crypt::URandom to version 0.55 or later. As a defense-in-depth measure, validate that any caller-provided length values are non-negative before passing to this function.

Recommended fix High confidence

Crypt::URandom version 0.55

  1. Check the currently installed version of Crypt::URandom by running: cpan -D Crypt::URandom or perl -MCrypt::URandom -e 'print $Crypt::URandom::VERSION'
  2. Upgrade to version 0.55 or later using your preferred Perl package manager. For cpan: cpan> install Crypt::URandom. For cpanm: cpanm Crypt::URandom. Alternatively, force upgrade to specific version: cpanm Crypt::[email protected]
  3. Verify the upgrade was successful by checking the new version: perl -MCrypt::URandom -e 'print $Crypt::URandom::VERSION'

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Crypt\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2474 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2474 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data