{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-2588 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-2588 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-2588 is a critical vulnerability in TIMLEGGE Crypt::NaCl::Sodium, published on 22 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-2588 and fix it if it is affected.\n\nWhat it is: CVE-2026-2588 is a critical vulnerability in TIMLEGGE Crypt::NaCl::Sodium, published on 22 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-2588 in the wild and no public exploit code.\n\nAffected product: TIMLEGGE Crypt::NaCl::Sodium. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-2588/ (Markdown: https://insights.sbomify.com/CVE-2026-2588/index.md)","id":"CVE-2026-2588","markdown":"https://insights.sbomify.com/CVE-2026-2588/index.md","name":"CVE-2026-2588","record":{"aliases":["GHSA-8gq5-mm3m-7h4x"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl cryptography library","requires_auth":"none","summary":"An integer overflow in Crypt::NaCl::Sodium on 32-bit systems may lead to undefined behavior or memory corruption during cryptographic operations.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"crypt\\","vendor":"timlegge"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"Crypt::NaCl::Sodium versions through 2.001 for Perl has an integer overflow flaw on 32-bit systems.\n\nSodium.xs casts a STRLEN (size_t) to unsigned long long when passing a length pointer to libsodium functions.  On 32-bit systems size_t is typically 32-bits while an unsigned long long is at least 64-bits.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Crypt::NaCl::Sodium versions through 2.001 for Perl has an integer overflow flaw on 32-bit systems","id":"CVE-2026-2588","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in Greenshift – animation and page builder blocks","id":"CVE-2026-2589"},"packages":[],"prev":{"headline":"GlassFish's gadget handler is vulnerable to RCE","id":"CVE-2026-2587"},"products":["Crypt::NaCl::Sodium"],"published":"2026-02-22","related":[{"cvss_score":9.8,"headline":"Crypt::NaCl::Sodium versions through 2.002 for Perl has potential integer overflows","id":"CVE-2026-30909","kev_date_added":null,"published":"2026-03-08"},{"cvss_score":8.8,"headline":"Perl's Crypt::Random module after 1.05 and before 1.56 may use rand() function for cryptographic functions","id":"CVE-2025-1828","kev_date_added":null,"published":"2025-03-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-23","vendors":["TIMLEGGE"]},"summary":"An integer overflow in Crypt::NaCl::Sodium on 32-bit systems may lead to undefined behavior or memory corruption during cryptographic operations.","url":"https://insights.sbomify.com/CVE-2026-2588/"}