{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-45812 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-45812 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-45812 is a medium-severity memory corruption vulnerability in Apache NimBLE, published on 24 Jul 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-45812 and fix it if it is affected.\n\nWhat it is: CVE-2026-45812 is a medium-severity memory corruption vulnerability in Apache NimBLE, published on 24 Jul 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-45812 in the wild and no public exploit code.\n\nAffected product: Apache NimBLE. 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-45812/ (Markdown: https://insights.sbomify.com/CVE-2026-45812/index.md)","id":"CVE-2026-45812","markdown":"https://insights.sbomify.com/CVE-2026-45812/index.md","name":"CVE-2026-45812","record":{"aliases":["GHSA-m9xh-wpcw-qvx9"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Bluetooth Low Energy stack","requires_auth":"low_privilege","summary":"An out-of-bounds read in Apache NimBLE allows attackers to read memory or cause crashes when using third-party controllers that batch advertising reports.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"nimble","vendor":"apache"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-131","name":"Incorrect Calculation of Buffer Size"}],"description":"Incorrect Calculation of Buffer Size vulnerability in Apache NimBLE when processing Legacy Advertising Report HCI event.\n\nWhen a single HCI advertising report event bundles multiple reports, NimBLE miscalculated the offset to the next report. This can cause the host to read past the end of the buffer and deliver a GAP event with bogus data to the application.\n\nSeverity is low: NimBLE's own controller never batches multiple reports into one event, so this only matters when NimBLE's host is paired with a third-party controller that does.\n\nThis issue affects Apache NimBLE: through 1.9.0.\n\nUsers are recommended to upgrade to version 1.10.0, which fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Apache NimBLE: OOB Read via sizeof(pointer) in Legacy Advertising Report Handler","id":"CVE-2026-45812","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":"Apache NimBLE: Incorrect data validation in BASS add/modify source operation","id":"CVE-2026-45813"},"packages":[],"prev":{"headline":"Apache NimBLE: Buffer overflow in socket HCI transport","id":"CVE-2026-45811"},"products":["Apache NimBLE"],"published":"2026-07-24","related":[{"cvss_score":8.8,"headline":"Apache NimBLE: Incorrect data validation in BASS add/modify source operation","id":"CVE-2026-45813","kev_date_added":null,"published":"2026-07-24"},{"cvss_score":8.1,"headline":"Apache Mynewt NimBLE: Incorrect handling of SMP Security Request could lead to undesirable pairing","id":"CVE-2025-62235","kev_date_added":null,"published":"2026-01-10"},{"cvss_score":7.5,"headline":"Apache NimBLE: Buffer overflow in socket HCI transport","id":"CVE-2026-45811","kev_date_added":null,"published":"2026-07-24"},{"cvss_score":7.5,"headline":"Apache NimBLE: Remote reachable assertion in ATT Read Multiple Variable Response handler","id":"CVE-2026-45815","kev_date_added":null,"published":"2026-07-24"},{"cvss_score":7.5,"headline":"Apache NimBLE: NULL pointer dereference vulnerability in SMP LTK request","id":"CVE-2026-45816","kev_date_added":null,"published":"2026-07-24"},{"cvss_score":7.5,"headline":"Apache Mynewt NimBLE: Invalid error handling in pause encryption procedure in NimBLE controller","id":"CVE-2025-52435","kev_date_added":null,"published":"2026-01-10"},{"cvss_score":7.5,"headline":"Apache Mynewt NimBLE: NULL Pointer Dereference in NimBLE host HCI layer","id":"CVE-2025-53477","kev_date_added":null,"published":"2026-01-10"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-24","vendors":["Apache Software Foundation"]},"summary":"An out-of-bounds read in Apache NimBLE allows attackers to read memory or cause crashes when using third-party controllers that batch advertising reports.","url":"https://insights.sbomify.com/CVE-2026-45812/"}