Droneaware Node Releases
Approved changes feed: RSS · Atom
cpe:2.3:a:fduflyer:droneaware-node-releases:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Fduflyer (170417b1-1422-563a-a62f-2b7e81eddeed) |
|---|---|
| Product | Droneaware Node Releases (5c2a6393-8626-5aa4-b8dc-36c4ad7010f3) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-48117 |
vulnerable | 2026-07-29 00:55:01.087596 |
DroneAware's Improper Account Activation in Registration and SSO Flows Leads to Account Takeover
MEDIUM (6.8)
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.
Published: 2026-06-17T14:02:39.164Z
Updated: 2026-06-17T15:41:14.311Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.