{"answers":{"affected":"3 open source packages ship an affected version, including github.com/osrg/gobgp/v4.","exploited":"There is no known exploitation of CVE-2026-49837 in the wild and no public exploit code.","fix":"Upgrade github.com/osrg/gobgp/v4 to 4.6.0 or later.","what":"CVE-2026-49837 is a medium-severity vulnerability in osrg gobgp, published on 10 Sep 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-49837 and fix it if it is affected.\n\nWhat it is: CVE-2026-49837 is a medium-severity vulnerability in osrg gobgp, published on 10 Sep 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-49837 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/osrg/gobgp/v4 (Go): affected all versions; fixed in 4.6.0\n- github.com/osrg/gobgp/v4 (Go): affected all versions; fixed in 4.6.0\n- github.com/osrg/gobgp/v4 (Go): affected all versions; fixed in 4.6.0\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-49837/ (Markdown: https://insights.sbomify.com/CVE-2026-49837/index.md)","id":"CVE-2026-49837","markdown":"https://insights.sbomify.com/CVE-2026-49837/index.md","name":"CVE-2026-49837","record":{"aliases":["DEBIAN-CVE-2026-49837","GHSA-gjrg-jjr3-56cm","GO-2026-5955","UBUNTU-CVE-2026-49837"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"BGP routing software","requires_auth":"none","summary":"A malformed BGP OPEN message can cause the parser to read adjacent memory, potentially leaking data or bypassing peer AS validation checks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"GoBGP is an open source Border Gateway Protocol (BGP) implementation in the Go Programming Language. Versions prior to 4.6.0 contain a BGP OPEN capability parsing issue where several concrete capability decoders may parse data from the full remaining capability buffer instead of the slice bounded by the declared capability length, `CapLen`. A malformed BGP OPEN message can cause bytes from a following capability to be interpreted as part of the current capability. The most security-relevant case is the 4-octet AS capability, where a capability with `CapLen == 0` may cause the parser to read bytes from the following capability as the 4-octet AS value. This parsed value may later affect peer AS validation during BGP session establishment. Version 4.6.0 patches the issue.","ecosystems":["Go"],"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":"GoBGP: BGP OPEN capability parser may read capability values outside declared CapLen boundaries","id":"CVE-2026-49837","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"GoBGP confederation validation panics on empty AS_PATH attribute","id":"CVE-2026-49838"},"packages":[{"ecosystem":"Go","fixed":["4.6.0"],"introduced":["0"],"last_affected":[],"package":"github.com/osrg/gobgp/v4","purl":null,"source":"GHSA-gjrg-jjr3-56cm"},{"ecosystem":"Go","fixed":["4.6.0"],"introduced":["0"],"last_affected":[],"package":"github.com/osrg/gobgp/v4","purl":"pkg:golang/github.com/osrg/gobgp/v4","source":"GHSA-gjrg-jjr3-56cm"},{"ecosystem":"Go","fixed":["4.6.0"],"introduced":["0"],"last_affected":[],"package":"github.com/osrg/gobgp/v4","purl":"pkg:golang/github.com/osrg/gobgp/v4","source":"GO-2026-5955"}],"prev":{"headline":"psd-tools: arbitrary file write via smart-object filename","id":"CVE-2026-49836"},"products":["gobgp"],"published":"2026-09-10","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":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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-09-15","vendors":["osrg"]},"summary":"A malformed BGP OPEN message can cause the parser to read adjacent memory, potentially leaking data or bypassing peer AS validation checks.","url":"https://insights.sbomify.com/CVE-2026-49837/"}