{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-14858 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-14858 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14858 is a medium-severity 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-14858 and fix it if it is affected.\n\nWhat it is: CVE-2025-14858 is a medium-severity 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-14858 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-14858/ (Markdown: https://insights.sbomify.com/CVE-2025-14858/index.md)","id":"CVE-2025-14858","markdown":"https://insights.sbomify.com/CVE-2025-14858/index.md","name":"CVE-2025-14858","record":{"aliases":["GHSA-pq38-4mfg-vpxj"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_read","security_bypass"],"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 read decrypted firmware from residual memory, bypassing encryption protections in Semtech LR11xx transceivers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SWI","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/AU:N/R:A/V:C/RE:M","version":"4.0"},"cwes":[{"id":"CWE-226","name":"Sensitive Information in Resource Not Removed Before Reuse"}],"description":"The Semtech LR11xx LoRa transceivers running early versions of firmware contains an information disclosure vulnerability in its firmware validation functionality. When a host issues a firmware validity check command via the SPI interface, the device decrypts the provided encrypted firmware package block-by-block to validate its integrity. However, the last decrypted firmware block remains uncleared in memory after the validation process completes. An attacker with access to the SPI interface can subsequently issue memory read commands to retrieve the decrypted firmware contents from this residual memory, effectively bypassing the firmware encryption protection mechanism. The attack requires physical access to the device's SPI interface.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Semtech LR11xx Encrypted Firmware Disclosure","id":"CVE-2025-14858","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Semtech LR11xx Secure Boot Bypass","id":"CVE-2025-14859"},"packages":[],"prev":{"headline":"Semtech LR11xx Memory Write Access Control Bypass","id":"CVE-2025-14857"},"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["Semtech"]},"summary":"An attacker with physical SPI access can read decrypted firmware from residual memory, bypassing encryption protections in Semtech LR11xx transceivers.","url":"https://insights.sbomify.com/CVE-2025-14858/"}