Monta's EV Charging Platform Has No Patch for a 9.4 Authentication Gap
Security / news
Monta's EV Charging Platform Has No Patch for a 9.4 Authentication Gap
CISA lists four flaws in monta.app, all versions. The vendor points operators to an optional OCPP security profile and has shipped no fix.

An unauthenticated attacker on the network (no credentials, no user interaction) can impersonate a charging station to the monta.app platform, according to a CISA advisory published October 1, 2026. The flaw, CVE-2026-95102, scores 9.4 on CVSS v3.1. Monta has released no patch for any of the four flaws in ICSA-26-274-02, and the advisory covers all versions of the product.
Monta, headquartered in the Netherlands, runs EV charging management. CISA lists energy and transportation systems as the affected sectors and says exploitation "could enable attackers to gain unauthorized administrative control over vulnerable charging stations or disrupt charging services."
The four CVEs and their preconditions
| CVE | Flaw | CVSS v3.1 | v4.0 |
|---|---|---|---|
| CVE-2026-95102 | Missing authentication on WebSocket endpoints | 9.4 | 9.3 |
| CVE-2026-97363 | No limit on authentication attempts | 7.5 | 8.7 |
| CVE-2026-97212 | Insufficient session expiration, predictable session identifiers | 7.3 | 6.9 |
| CVE-2026-93474 | Station authentication identifiers visible on web mapping platforms | 6.5 | 6.9 |
All four vectors are network-reachable, low-complexity and need no privileges. The 9.4 reflects high confidentiality and integrity impact with low availability impact.
The advisory does not connect the first and last entries, but they fit together. If a station's identifier is public on a map and the WebSocket endpoint does not check who is connecting, knowing the identifier may be all an impersonator needs. That is a reading of the advisory rather than a claim in it.
Monta's response: Security Profile 2, rate limiting, no patch
Per the advisory, Monta offers three responses. It supports "OCPP 1.6 Security Profile 2 (HTTP Basic Auth with TLS)" and encourages operators to turn it on. It is implementing rate limiting and connection throttling at the WebSocket layer. And it handles duplicate connection attempts under the OCPP specification, where "a new authenticated connection supersedes an existing session."
CISA's status line is plain: no patch released, mitigations under development. It also says no known public exploitation targeting these vulnerabilities has been reported, and credits an anonymous researcher.
Why an opt-in security profile matters here
OCPP is the protocol chargers use to talk to a management system, maintained by the Open Charge Alliance. OCPP Lab's write-up on security profiles says the original OCPP 1.6 core specification "treated security as optional," and that the whitepaper adding security profiles was published years later and remains opt-in per deployment.

That makes Monta's mitigation a configuration choice for each deployment, not a platform fix. Operators running Profile 1, or no profile, stay exposed until they switch. The advisory does not say how many stations or operators use monta.app, or how many run a secured profile.
Monta is not alone in leaving CISA's October 1 batch unpatched. The advisory for the Meari IoT Cloud Platform OpenAPI Service, ICSA-26-274-06, lists CVE-2026-101104 (7.7) and CVE-2026-96613 (6.5), says no fix is planned, and says Meari did not respond to CISA's coordination attempts.
What operators can do now
CISA's general guidance applies: minimise network exposure, use firewalls, and keep remote access behind a VPN. For Monta, the specific step is enabling Security Profile 2 on every charger that supports it. Related coverage: Vermont's 110 MW home battery fleet and the Cisco SD-WAN Manager admin API bypass, where a missing authorization check was the whole bug.
The advisory gives no date for the promised rate limiting.
Sources
More in Security
- 01Java4Shell Scores 9.2 From Its Finder and 8.1 From OpenJDK, and Needs an AVX-512 CPUCalif says a 65-character Base64 string overwrites 62 bytes of Java heap and reaches code execution in Keycloak, Jenkins and Jira. A second security firm says the source shows only a crash.
- 02CISA Gave 9 of 16 November KEV Entries a Three-Day Deadline With Forensic Triage, and 7 Got 14 DaysThe catalog's own due-date and forensicTriage fields show two tiers under BOD 26-04. Sorting November's additions by tier shows which exploited bugs CISA treats as already-compromised-until-proven-otherwise.
- 03Project Zero Cuts Its Disclosure Deadline to 60 Days on Feb. 2, 2027, Then 30 in 2028Google's bug-hunting team is dropping the 30-day patch soak period and counting every deadline from the day it reports, citing AI-assisted exploitation.
- 04Google Finds exploit_agent Diffing Patches and Firing Exploits With No Operator in the LoopGTIG's November 16 tracker reports the first fully automated discovery-to-exploit pipeline it has seen, found on an exposed staging server, plus 22 zero-days in August.