CVE-2026-22099
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe charging station does not require authentication for Bluetooth commands to perform actions. The functionality exposed includes sensitive information leakage, triggering reboots, or pushing a firmware update URL.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAuthentication bypass vulnerability in charging station Bluetooth interface allows unauthenticated attackers within Bluetooth range to execute commands, including leaking sensitive information, triggering device reboots, and pushing malicious firmware update URLs. The lack of authentication on the Bluetooth communication channel is the root cause.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Bluetooth is enabled on the charging stationCheck the device's network/Bluetooth settings or review system logs for active Bluetooth interfaces (e.g., hciconfig on Linux, or check device management console for Bluetooth status)Affected if Bluetooth is actively enabled and discoverable
-
Identify Bluetooth services listening for connectionsUse Bluetooth scanning tools (hcitool, btmon, or proprietary manufacturer tools) to discover available Bluetooth services and UUIDs exposed by the charging stationAffected if Any Bluetooth service is accepting connections without requiring authentication
-
Test if Bluetooth commands require authenticationAttempt to connect to the device's Bluetooth interface and send a basic command (e.g., status query) without providing credentials, or review authentication configuration if accessibleAffected if Unauthenticated Bluetooth commands are accepted and processed
-
Check firmware update configurationLocate the firmware update settings in the device configuration (web UI, mobile app, or config file) and examine whether the firmware update URL field accepts arbitrary URLs without validationAffected if Firmware update URLs can be set to arbitrary addresses without signature or validation checks
-
Review Bluetooth security modeInspect the device's Bluetooth security settings (if accessible via config or BLE sniffer) to determine if authentication (PIN, key exchange, or pairing) is enforced for command executionAffected if Bluetooth security mode is set to 'open' or 'no auth' rather than requiring mutual authentication
The environment is affected if the charging station has Bluetooth enabled with unauthenticated command acceptance or allows unsigned/unvalidated firmware update URLs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement authentication and encryption for all Bluetooth commands, require mutual authentication before executing sensitive operations, and add cryptographic signing/verification for firmware updates to prevent tampering.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $23,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22099 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22099 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data