{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-30910 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-30910 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-30910 is a high-severity vulnerability in IAMB Crypt::Sodium::XS, 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-30910 and fix it if it is affected.\n\nWhat it is: CVE-2026-30910 is a high-severity vulnerability in IAMB Crypt::Sodium::XS, 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-30910 in the wild and no public exploit code.\n\nAffected product: IAMB Crypt::Sodium::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-30910/ (Markdown: https://insights.sbomify.com/CVE-2026-30910/index.md)","id":"CVE-2026-30910","markdown":"https://insights.sbomify.com/CVE-2026-30910/index.md","name":"CVE-2026-30910","record":{"aliases":["GHSA-2qjg-jrhf-99vr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl cryptography library","requires_auth":"none","summary":"Integer overflows in Crypt::Sodium::XS can cause buffer overflows or crashes when processing extremely large inputs, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"crypt\\","vendor":"iamb"}],"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-190","name":"Integer Overflow or Wraparound"}],"description":"Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows.\n\nCombined aead encryption, combined signature creation, and bin2hex functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersized output buffer. This can cause a crash in bin2hex and encryption algorithms other than aes256gcm. For aes256gcm encryption and signatures, an undersized buffer could lead to buffer overflow.\n\nEncountering this issue is unlikely as the message length would need to be very large.\n\nFor bin2hex the input size would have to be \u003e SIZE_MAX / 2 For aegis encryption the input size would need to be \u003e SIZE_MAX - 32U For other encryption the input size would need to be \u003e SIZE_MAX - 16U For signatures the input size 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":null,"headline":"Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows","id":"CVE-2026-30910","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Apache Airflow: Execution API HITL Endpoints Missing Per-Task Authorization","id":"CVE-2026-30911"},"packages":[],"prev":{"headline":"Crypt::NaCl::Sodium versions through 2.002 for Perl has potential integer overflows","id":"CVE-2026-30909"},"products":["Crypt::Sodium::XS"],"published":"2026-03-08","related":[{"cvss_score":9.8,"headline":"Crypt::Sodium::XS module versions prior to 0.000042, for Perl, include a vulnerable version of libsodium","id":"CVE-2025-15444","kev_date_added":null,"published":"2026-01-06"}],"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-03-10","vendors":["IAMB"]},"summary":"Integer overflows in Crypt::Sodium::XS can cause buffer overflows or crashes when processing extremely large inputs, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2026-30910/"}