{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-2597 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-2597 is a high-severity vulnerability in LEONT Crypt::SysRandom::XS, published on 26 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-2597 and fix it if it is affected.\n\nWhat it is: CVE-2026-2597 is a high-severity vulnerability in LEONT Crypt::SysRandom::XS, published on 26 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-2597 in the wild and no public exploit code.\n\nAffected product: LEONT Crypt::SysRandom::XS. 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-2597/ (Markdown: https://insights.sbomify.com/CVE-2026-2597/index.md)","id":"CVE-2026-2597","markdown":"https://insights.sbomify.com/CVE-2026-2597/index.md","name":"CVE-2026-2597","record":{"aliases":["DEBIAN-CVE-2026-2597","GHSA-rpp6-x48q-7fq5","UBUNTU-CVE-2026-2597"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl random library","requires_auth":"none","summary":"A heap buffer overflow in the Perl Crypt::SysRandom::XS library allows denial of service via integer overflow when handling negative length parameters.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"crypt\\","vendor":"leont"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"Crypt::SysRandom::XS versions before 0.010 for Perl is vulnerable to a heap buffer overflow in the XS function random_bytes().\n\nThe 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 chosen random function (e.g. getrandom) 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).\n\nIn 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Integer overflow in Crypt::SysRandom::XS","id":"CVE-2026-2597","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2026-2598"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2026-2596"},"products":["Crypt::SysRandom::XS"],"published":"2026-02-26","related":[{"cvss_score":5.3,"headline":"Integer overflow in Crypt::Argon2","id":"CVE-2026-8463","kev_date_added":null,"published":"2026-05-13"}],"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-27","vendors":["LEONT"]},"summary":"A heap buffer overflow in the Perl Crypt::SysRandom::XS library allows denial of service via integer overflow when handling negative length parameters.","url":"https://insights.sbomify.com/CVE-2026-2597/"}