CVE-2026-27028: Mobility46 Mobility46.se authentication bypass (CVSS 9.4)

Description

WebSocket endpoints lack proper authentication mechanisms, enabling attackers to perform unauthorized station impersonation and manipulate data sent to the backend. An unauthenticated attacker can connect to the OCPP WebSocket endpoint using a known or discovered charging station identifier, then issue or receive OCPP commands as a legitimate charger. Given that no authentication is required, this can lead to privilege escalation, unauthorized control of charging infrastructure, and corruption of charging network data reported to the backend.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityLow

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Affected products

Mobility46 Mobility46.seall versions

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-057-08.jsonThird Party Advisory
https://www.cisa.gov/news-events/ics-advisories/icsa-26-057-08Third Party AdvisoryUS Government Resource
https://www.mobility46.se/en/contact-usProduct

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-27028 being actively exploited?

CVE-2026-27028 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.96%.

How severe is CVE-2026-27028?

CVE-2026-27028 has a CVSS 3.1 base score of 9.4, rated critical. EPSS estimates a 0.96% probability of exploitation.

Which products are affected by CVE-2026-27028?

Affected products include Mobility46 Mobility46.se.

How do I fix CVE-2026-27028?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-27028 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo