{"answers":{"affected":"2 open source packages ship an affected version, including smallbitvec.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44983 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-44983 is a high-severity vulnerability in servo smallbitvec, published on 26 May 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-44983 and fix it if it is affected.\n\nWhat it is: CVE-2026-44983 is a high-severity vulnerability in servo smallbitvec, published on 26 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44983 exists.\n\nAffected packages and fixed versions:\n- smallbitvec (crates.io): affected from 1.0.1 up to 2.6.0; no fix listed\n- smallbitvec (crates.io): affected from 1.0.1 up to 2.6.0; no fix listed\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-44983/ (Markdown: https://insights.sbomify.com/CVE-2026-44983/index.md)","id":"CVE-2026-44983","markdown":"https://insights.sbomify.com/CVE-2026-44983/index.md","name":"CVE-2026-44983","record":{"aliases":["DEBIAN-CVE-2026-44983","GHSA-97wc-2hqc-cjgr","UBUNTU-CVE-2026-44983"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust bit-vector library","requires_auth":"none","summary":"An integer overflow in smallbitvec causes heap buffer overflows via safe APIs, potentially allowing memory corruption or crashes.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"smallbitvec is a growable bit-vector for Rust, optimized for size. From 1.0.1 to 2.6.0, an integer overflow in the internal capacity calculation of smallbitvec can lead to an undersized heap allocation, resulting in a heap buffer overflow through safe APIs only. This allows memory corruption without requiring unsafe code from the caller. This vulnerability is fixed in 2.6.1.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"smallbitvec: Safe API Triggered Heap Buffer Overflow via Integer Overflow","id":"CVE-2026-44983","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Dozzle: Cross-Site WebSocket Hijacking (CSWSH) on exec/attach endpoints bypasses authentication","id":"CVE-2026-44985"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["1.0.1"],"last_affected":["2.6.0"],"package":"smallbitvec","purl":null,"source":"GHSA-97wc-2hqc-cjgr"},{"ecosystem":"crates.io","fixed":[],"introduced":["1.0.1"],"last_affected":["2.6.0"],"package":"smallbitvec","purl":"pkg:cargo/smallbitvec","source":"GHSA-97wc-2hqc-cjgr"}],"prev":{"headline":"CrowdSec AppSec silently drops request body for chunked / HTTP-2 requests","id":"CVE-2026-44982"},"products":["smallbitvec"],"published":"2026-05-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-27","vendors":["servo"]},"summary":"An integer overflow in smallbitvec causes heap buffer overflows via safe APIs, potentially allowing memory corruption or crashes.","url":"https://insights.sbomify.com/CVE-2026-44983/"}