{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-49762 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-49762 is a medium-severity denial of service vulnerability in elixir-lang elixir, published on 9 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-49762 and fix it if it is affected.\n\nWhat it is: CVE-2026-49762 is a medium-severity denial of service vulnerability in elixir-lang elixir, published on 9 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-49762 in the wild and no public exploit code.\n\nAffected product: elixir-lang elixir. 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-49762/ (Markdown: https://insights.sbomify.com/CVE-2026-49762/index.md)","id":"CVE-2026-49762","markdown":"https://insights.sbomify.com/CVE-2026-49762/index.md","name":"CVE-2026-49762","record":{"aliases":["AZL-89672","DEBIAN-CVE-2026-49762","EEF-CVE-2026-49762","GHSA-w2h8-8x3g-278p","OESA-2026-2787","UBUNTU-CVE-2026-49762"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elixir standard library","requires_auth":"none","summary":"Attackers can cause CPU and memory exhaustion denial of service by supplying large version strings to the Elixir Version module.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Uncontrolled Resource Consumption vulnerability in the Elixir standard library's Version module allows an attacker who controls a version string to cause a denial of service through CPU and memory exhaustion.\n\nThe version parser converts numeric version components (major, minor, patch and numeric pre-release/build identifiers) to integers without bounding their length. A single large all-digit component therefore forces a super-linear, non-yielding base-10 to arbitrary-precision integer conversion (String.to_integer/1, i.e. :erlang.binary_to_integer/1) that pins a BEAM scheduler, and a larger component raises an uncaught SystemLimitError that crashes the calling process. A single moderately sized string (around one megabyte) is enough; no authentication is required.\n\nThis is reachable from the public entry points Version.parse/1, Version.parse!/1, Version.match?/3, Version.compare/2, and Version.parse_requirement/1, which applications routinely call on untrusted input such as HTTP parameters, dependency-manifest fields, and package metadata.\n\nThis vulnerability is associated with program files lib/version.ex and program routines 'Elixir.Version.Parser':parse_digits/2.\n\nThis issue affects elixir: from 0.9.3 before 1.20.1.","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":"Unbounded integer parsing in the Version module enables CPU and memory exhaustion denial of service","id":"CVE-2026-49762","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"WordPress Integration for Contact Form 7 HubSpot plugin \u003c= 1.3.7 - PHP Object Injection vulnerability","id":"CVE-2026-49763"},"packages":[],"prev":{"headline":"Stack Buffer Overflow in ei_s_print_term at Very Large Integer","id":"CVE-2026-49760"},"products":["elixir"],"published":"2026-06-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-06","vendors":["elixir-lang"]},"summary":"Attackers can cause CPU and memory exhaustion denial of service by supplying large version strings to the Elixir Version module.","url":"https://insights.sbomify.com/CVE-2026-49762/"}