CVE-2026-9397
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 · uneditedA weakness has been identified in Besen BS20 EV Charging Station up to 20260426. Affected by this issue is some unknown functionality of the component OTA Update Installation Handler. This manipulation causes improper authorization. The attack is possible to be carried out remotely. A high degree of complexity is needed for the attack. The exploitation is known to be difficult. The original disclosure mentions, that "[t]hese vulnerabilities have been reported to Besen and we have received their acknowlegement that they are reviewing this as of April 2026."
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 confidenceThe Besen BS20 EV Charging Station contains an improper authorization vulnerability in its OTA (Over-The-Air) Update Installation Handler. This allows a remote attacker to potentially install unauthorized firmware updates without proper authentication or authorization checks. The vulnerability affects the firmware update mechanism up to the April 2026 version.
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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm device modelIdentify the Besen BS20 EV Charging Station in your environment by checking the device label, management interface, or network inventory. Compare the model number to the affected product name.Affected if The device is a Besen BS20 EV Charging Station and OTA updates are enabled
-
Locate OTA update configurationAccess the device management interface or configuration panel and navigate to the OTA (Over-the-Air) Update settings. Look for options related to firmware updates, remote updates, or update installation.Affected if OTA update functionality is enabled or configured on the device
-
Verify OTA endpoint exposureCheck network configuration to determine if the OTA update endpoint is accessible from network segments outside of authorized management networks. Review firewall rules, ACLs, or network policies applied to the device.Affected if OTA update endpoints are reachable from untrusted or unauthorized network segments
-
Inspect OTA authorization controlsReview the OTA update handler configuration for any authentication requirements, authorization checks, or access control settings. Look for settings that control who can initiate or approve firmware updates.Affected if No strong authentication or authorization is required to trigger or install OTA updates
-
Review update installation logsExamine device logs, system logs, or management platform logs for any OTA update attempts, particularly those from unexpected sources, at unusual times, or lacking proper authorization markers.Affected if Unauthorized or unexpected OTA update attempts are logged or detectable
You are affected if you have a Besen BS20 EV Charging Station with OTA update functionality enabled and the OTA update endpoints are accessible without proper authorization controls.
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 dataApply vendor-supplied firmware patches when available. Until then, isolate the charging station network segment, disable OTA update functionality if possible, and monitor for unauthorized update attempts.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9397 — 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-9397 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