Skip to main content
VulnerabilityPublished

CVE-2026-48117: fduflyer DroneAware-Node-Releases · Improper Authentication

Affects fduflyer DroneAware-Node-ReleasesSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium.

Data as of 30 Oct 2026, 20:25 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
fduflyerDroneAware-Node-ReleasesAffected
  • =< server-2026-05-20
Fixed in–

AI-suggested

The vulnerability was fixed by the vendor with a server-side patch deployed on 2025-05-20. No user action or client-side mitigation is required. There are no workarounds. Users and administrators should ensure they are using the official DroneAware service where the fix is applied.

Description

DroneAware's centralized server was vulnerable to an account pre-hijacking flaw allowing attackers to register accounts with victim emails and attacker-chosen passwords before the victim activated their account. When the victim later activated the account, the attacker-set password remained valid, enabling silent account takeover without notification. The issue was fixed server-side on 2025-05-20, requiring no user action. Node binaries and self-hosted detection nodes are unaffected. No client-side mitigations or workarounds are needed.

References

Community reviews

Loading reviews…