{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-14857 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-14857 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14857 is a medium-severity memory corruption vulnerability in Semtech LR1110, published on 7 Apr 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-2025-14857 and fix it if it is affected.\n\nWhat it is: CVE-2025-14857 is a medium-severity memory corruption vulnerability in Semtech LR1110, published on 7 Apr 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-2025-14857 in the wild and no public exploit code.\n\nAffected product: Semtech LR1110. 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-2025-14857/ (Markdown: https://insights.sbomify.com/CVE-2025-14857/index.md)","id":"CVE-2025-14857","markdown":"https://insights.sbomify.com/CVE-2025-14857/index.md","name":"CVE-2025-14857","record":{"aliases":["GHSA-xjjj-2993-4g39"],"analysis":{"component_type":"hardware_firmware","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"LoRa transceiver firmware","requires_auth":"none","summary":"An attacker with physical SPI access can overwrite stack memory to hijack control flow and execute arbitrary code during the session.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SWI","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/AU:N/R:A/V:D/RE:M","version":"4.0"},"cwes":[{"id":"CWE-123","name":"Write-what-where Condition"}],"description":"An improper access control vulnerability exists in Semtech LoRa LR11xxx transceivers running early versions of firmware where the memory write command accessible via the physical SPI interface fails to enforce write protection on the program call stack. An attacker with physical access to the SPI interface can overwrite stack memory to hijack program control flow and achieve limited arbitrary code execution. However, the impact is limited to the active attack session: the device's secure boot mechanism prevents persistent firmware modification, the crypto engine isolates cryptographic keys from direct firmware access, and all modifications are lost upon device reboot or loss of physical access.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-01-04","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-01-04T08:58:42Z","kind":"github_poc","ref":"https://github.com/Ermensonx/CVE-2025-14857-MongoBleed","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"Semtech LR11xx Memory Write Access Control Bypass","id":"CVE-2025-14857","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Semtech LR11xx Encrypted Firmware Disclosure","id":"CVE-2025-14858"},"packages":[],"prev":{"headline":"y_project RuoYi getnames code injection","id":"CVE-2025-14856"},"products":["LR1110","LR1120","LR1121"],"published":"2026-04-07","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":"total"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["Semtech"]},"summary":"An attacker with physical SPI access can overwrite stack memory to hijack control flow and execute arbitrary code during the session.","url":"https://insights.sbomify.com/CVE-2025-14857/"}