{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-30909 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-30909 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-30909 is a critical vulnerability in TIMLEGGE Crypt::NaCl::Sodium, published on 8 Mar 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-30909 and fix it if it is affected.\n\nWhat it is: CVE-2026-30909 is a critical vulnerability in TIMLEGGE Crypt::NaCl::Sodium, published on 8 Mar 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-30909 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-30909/ (Markdown: https://insights.sbomify.com/CVE-2026-30909/index.md)","id":"CVE-2026-30909","markdown":"https://insights.sbomify.com/CVE-2026-30909/index.md","name":"CVE-2026-30909","record":{"aliases":["GHSA-qqmj-w4wh-9w2h"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl cryptography library","requires_auth":"none","summary":"Integer overflows in Crypt::NaCl::Sodium functions may cause undersized buffers, potentially leading to crashes or memory issues with extremely large inputs.","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.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"Crypt::NaCl::Sodium versions through 2.002 for Perl has potential integer overflows.\n\nbin2hex, encrypt, aes256gcm_encrypt_afternm and seal functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersized output buffer.\n\nEncountering this issue is unlikely as the message length would need to be very large.\n\nFor bin2hex() the bin_len would have to be \u003e SIZE_MAX / 2 For encrypt() the msg_len would need to be \u003e SIZE_MAX - 16U For aes256gcm_encrypt_afternm() the msg_len would need to be \u003e SIZE_MAX - 16U For seal() the enc_len would need to be \u003e SIZE_MAX - 64U","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.002 for Perl has potential integer overflows","id":"CVE-2026-30909","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows","id":"CVE-2026-30910"},"packages":[],"prev":{"headline":"Privilege escalation in Zoom Rooms","id":"CVE-2026-30906"},"products":["Crypt::NaCl::Sodium"],"published":"2026-03-08","related":[{"cvss_score":9.1,"headline":"Crypt::NaCl::Sodium versions through 2.001 for Perl has an integer overflow flaw on 32-bit systems","id":"CVE-2026-2588","kev_date_added":null,"published":"2026-02-22"},{"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":"total"},"state":"PUBLISHED","updated":"2026-03-10","vendors":["TIMLEGGE"]},"summary":"Integer overflows in Crypt::NaCl::Sodium functions may cause undersized buffers, potentially leading to crashes or memory issues with extremely large inputs.","url":"https://insights.sbomify.com/CVE-2026-30909/"}