{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48117 exists.","fix":"No fix has been published for CVE-2026-48117 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-48117 is a medium-severity authentication bypass vulnerability in fduflyer DroneAware-Node-Releases, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-48117 and fix it if it is affected.\n\nWhat it is: CVE-2026-48117 is a medium-severity authentication bypass vulnerability in fduflyer DroneAware-Node-Releases, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48117 exists.\n\nAffected product: fduflyer DroneAware-Node-Releases. 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-48117/ (Markdown: https://insights.sbomify.com/CVE-2026-48117/index.md)","id":"CVE-2026-48117","markdown":"https://insights.sbomify.com/CVE-2026-48117/index.md","name":"CVE-2026-48117","record":{"aliases":[],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Drone detection platform","requires_auth":"none","summary":"Attackers can pre-register accounts with victim emails to hijack them upon activation, requiring server-side patching for the DroneAware platform.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-302","name":"Authentication Bypass by Assumed-Immutable Data"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"DroneAware is a drone detection platform. The centralized DroneAware server backing droneaware.io was vulnerable to an account pre-hijacking attack in which an attacker could register an account using a victim's email address with an attacker-controlled password before the victim completed account activation. When the legitimate owner later activated the account, either by clicking the email verification link or by logging in via Google SSO, the attacker-set password became fully valid, enabling silent and persistent account takeover without any notification to the victim. The vulnerability was fixed server-side on 2025-05-20; no user action is required. Node binaries and self-hosted detection nodes are not affected. There are no workarounds; the fix was deployed server-side and no client-side mitigation is applicable.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"DroneAware's Improper Account Activation in Registration and SSO Flows Leads to Account Takeover","id":"CVE-2026-48117","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Nezha Monitoring: Authenticated agents can forge service-monitor results for other users' services","id":"CVE-2026-48119"},"packages":[],"prev":{"headline":"AnythingLLM: RCE via ripgrep --pre argument injection in filesystem-search-files agent skill","id":"CVE-2026-48116"},"products":["DroneAware-Node-Releases"],"published":"2026-06-17","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-17","vendors":["fduflyer"]},"summary":"Attackers can pre-register accounts with victim emails to hijack them upon activation, requiring server-side patching for the DroneAware platform.","url":"https://insights.sbomify.com/CVE-2026-48117/"}