{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-49943 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-49943 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-49943 is a medium-severity memory corruption vulnerability in NIC BIRD, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-49943 and fix it if it is affected.\n\nWhat it is: CVE-2026-49943 is a medium-severity memory corruption vulnerability in NIC BIRD, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-49943 in the wild and no public exploit code.\n\nAffected product: NIC BIRD. 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-49943/ (Markdown: https://insights.sbomify.com/CVE-2026-49943/index.md)","id":"CVE-2026-49943","markdown":"https://insights.sbomify.com/CVE-2026-49943/index.md","name":"CVE-2026-49943","record":{"aliases":["DEBIAN-CVE-2026-49943","GHSA-64c8-8qx9-25r7","UBUNTU-CVE-2026-49943"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"BGP routing daemon","requires_auth":"low_privilege","summary":"A remote BGP peer can crash the BIRD daemon via a stack buffer overflow in AS_PATH matching when Extended Messages are enabled.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"CZ.NIC BIRD Internet Routing Daemon through 2.19.0 contains a stack-based buffer overflow in the BGP AS_PATH mask matching implementation in nest/a-path.c. The as_path_match() function uses a fixed-size stack array of 2048 + 1 pm_pos entries, while parse_path() expands AS_PATH segments from a received BGP UPDATE without enforcing a corresponding capacity limit. When RFC 8654 BGP Extended Messages are enabled and a BIRD filter evaluates an AS path mask expression such as \"bgp_path ~ [= ... =]\", an established BGP peer can send a long AS_PATH containing more than 2048 expanded ASNs. This causes parse_path()/as_path_match() to write beyond the fixed stack buffer, resulting in a crash of the daemon. NOTE: reportedly, the Supplier's position is that a fix is not being prioritized because all network operators should already be rejecting routes with unusually long attributes.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-06-03","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-06-03T06:26:15Z","kind":"github_poc","ref":"https://github.com/cxwx/CVE-2026-49943-PoC","stars":0,"title":"PoC of CVE-2026-49943"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Memory corruption in BIRD","id":"CVE-2026-49943","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","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-49944"},"packages":[],"prev":{"headline":"Net::CIDR::Set versions through 0.20 for Perl did not validate network masks","id":"CVE-2026-49942"},"products":["BIRD"],"published":"2026-06-02","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-02","vendors":["NIC"]},"summary":"A remote BGP peer can crash the BIRD daemon via a stack buffer overflow in AS_PATH matching when Extended Messages are enabled.","url":"https://insights.sbomify.com/CVE-2026-49943/"}