Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach WebSocket auth API over network
-
DeliveryScript automated authentication requests
-
ExploitBypass absent rate limiting
-
ExecutionFlood endpoint or brute-force credentials
-
ImpactDenial of service or unauthorized account access
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Brute-force prevention, rate limiting
|
| Exploitation Conditions | The required condition is network reachability to the Monta WebSocket Application Programming Interface's authentication endpoint, which by design handles login requests; exploitation does not need special configuration because the flaw is the absence of any request-rate limiting on that interface (matching AV:N/AC:L/PR:N/UI:N). What LIMITS real impact: the denial-of-service path depends on the attacker generating sufficient request volume to exhaust capacity, while the brute-force-to-unauthorized-access path additionally depends on accounts having weak, guessable, or non-MFA-protected credentials - strong passwords or MFA materially blunt the credential-compromise outcome even though the missing rate limit remains. |
| Impact | This is a CVSS 4.0 8.7 (High) flaw in the Monta EV-charging platform's WebSocket API, reported through CISA ICS-CERT (icscert), stemming from CWE-307 (missing rate limiting on authentication requests). The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) indicates remote, low-complexity, unauthenticated exploitation, but notably scopes impact to availability only (VA:H; VC:N/VI:N/VA... C and I none), meaning the official scoring treats this primarily as a denial-of-service issue rather than a credential-compromise issue. This CONFLICTS with the description, which explicitly states the missing rate limiting 'may allow an attacker to conduct denial-of-service attacks OR brute-force attacks to gain unauthorized access' - brute-force success would produce confidentiality/integrity impact that the provided vector does not capture. No EPSS score, KEV listing, or POC indicator is present in the supplied data, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the 8.7 is a capability-based score, not an exploitation-driven one. Realistically this is a genuine but secondary-tier priority: the network-reachable, unauthenticated, trivial-to-automate nature (brute force and request flooding are inherently scriptable) raises concern, but actual credential compromise depends on weak/guessable account passwords, and the absence of KEV/EPSS/POC signals suggests it is not currently under opportunistic mass exploitation. Patch availability is not stated in the input beyond the CISA/CSAF advisory references, which should be consulted for fixed versions. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker scripts a client against the Monta WebSocket authentication endpoint and submits a high-volume stream of login attempts. Because no rate limiting exists, they can either flood the endpoint to exhaust resources and deny service, or run a credential brute-force/password-spray campaign against known accounts to gain unauthorized access. No public exploit code is identified in the provided data, but the attack requires only standard WebSocket tooling given AV:N/AC:L/PR:N. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 02, 2026
Missing rate limiting on the Monta EV-charging platform's WebSocket API authentication endpoint allows unauthenticated remote attackers to send unlimited login requests, enabling either resource-exhaustion denial of service or sustained credential brute-forcing against Monta accounts. The issue affects monta.app (all versions tracked by EUVD) and carries a CVSS 4.0 base score of 8.7 (High), with the assessed impact concentrated on availability (VA:H) and no direct confidentiality or integrity effect in the base vector; credential compromise via brute force is a downstream outcome that additionally requires weak, guessable, or non-MFA-protected credentials. No public exploit code has been identified at time of analysis, and the flaw has not been confirmed as actively exploited (CISA KEV); reporting originates from CISA ICS-CERT advisory ICSA-26-274-02.
Earlier versions of this analysis (1)
Missing rate limiting in the Monta App WebSocket API authentication handler allows a remote, unauthenticated attacker to send unlimited authentication requests, which can exhaust resources and produce a denial-of-service condition (CVSS 3.1 AV:N/AC:L/PR:N/UI:N with high availability impact) and can also serve as an unlimited oracle for credential brute-force attempts against accounts. All versions of the product are reported as affected (CPE cpe:2.3:a:monta:monta.app, EUVD-2026-91822), so exposure is not gated by a particular release. At time of analysis there is no CISA KEV listing and no public exploit code identified; the issue is rated moderate-priority rather than an emergency, and the credential-guessing path is bounded by the strength of the targeted account's credentials and any out-of-band protections such as MFA or strong random passwords. No vendor patch version is specified in the available references, which point only to the ICS-CERT advisory ICSA-26-274-02.
RemediationAI
No vendor-released patch identified at time of analysis; the cited references (CISA ICS-CERT advisory ICSA-26-274-02 at https://www.cisa.gov/news-events/ics-advisories/icsa-26-274-02 and its CSAF record) provide no fixed version, so remediation currently depends on compensating controls and monitoring for vendor guidance. The most direct control is to enforce authentication rate limiting in front of the WebSocket endpoint rather than inside it - terminate or proxy WebSocket authentication at a reverse proxy, API gateway, or WAF that supports per-IP and per-account request caps, concurrent-connection limits, and exponential backoff or temporary lockout after repeated failures; the trade-off is that overly aggressive thresholds can lock out legitimate Monta clients, charge point hardware, or shared-NAT users, so limits should be tuned with alerting rather than silent blocking. Restrict network exposure of the WebSocket authentication path to known client sources or trusted egress ranges where operationally feasible, accepting that this is impractical for consumer mobile clients. Enforce strong, unique credentials and MFA on Monta accounts, since multi-factor authentication materially blunts the brute-force-to-unauthorized-access path even though the missing rate limit remains; this does not mitigate the raw denial-of-service path. Instrument and alert on anomalous WebSocket authentication volumes, high failure ratios, and connection churn per source so that an in-progress flood or guessing campaign is detected quickly, and be prepared to temporarily block offending sources as a backlog mitigation that sacrifices availability for targeted clients. Monitor the CISA advisory page and Monta's own security channels for a fixed release and re-run this assessment when version-level remediation data becomes available.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the Monta application's WebSocket-based Application Programming Interface, a persistent, full-duplex channel used by Monta clients (mobile apps, charge point integrations, and backend services) to authenticate and exchange session traffic. The root cause is CWE-307, Improper Restriction of Excessive Authentication Attempts: the authentication handler on that WebSocket interface imposes no throttle, lockout, backoff, or per-source cap on how many authentication requests can be issued, so an attacker who can reach the endpoint can drive unbounded request volume. Because WebSocket connections are long-lived and typically cheaper to hold than to re-establish, the same missing control serves two distinct abuse paths - exhausting server, connection-pool, or worker capacity to degrade or deny service, and iterating credential guesses at line-rate without triggering lockout. Per the CPE string cpe:2.3:a:monta:monta.app:*:*:*:*:*:*:*:*, the record covers monta.app without a version constraint, and the EUVD entry lists all versions as affected; the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VA:H) confirms the flaw is remotely reachable, requires no privileges and no user interaction, and has no attack-complexity or additional-precondition barrier, which is consistent with the independent CVSS 3.1 assessment (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Note that the high base score reflects ease of reachability plus high availability impact; it does not itself establish that credential compromise is guaranteed.
Know when Monta App gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Remote unauthenticated WebSocket API with no rate limit gives AV:N/AC:L/PR:N; primary demonstrable impact is availability (DoS), so A:H and C:N/I:N, consistent with the vendor vector.
Primary rating from Vendor (icscert).
CVSS VectorVendor: icscert
Lifecycle Timeline
3DescriptionCVE.org
The WebSocket Application Programming Interface lacks restrictions on the number of authentication requests. This absence of rate limiting may allow an attacker to conduct denial-of-service attacks or brute-force attacks to gain unauthorized access.
Executive ViewAI
Monta EV-charging platform's WebSocket authentication endpoint lacks rate limiting, creating a risk of service exhaustion and sustained credential brute-forcing that could disrupt charging operations or compromise customer and fleet accounts. The issue affects monta.app across all EUVD-tracked versions, and no vendor-released patch has been identified at time of analysis; no public exploit has been identified at time of analysis. Leadership should prioritize interim controls and vendor monitoring because this authentication weakness could lead to operational downtime or account takeover where MFA and strong passwords are not enforced.
Rate limiting and connection throttling at the WAF/API gateway/reverse proxy for the WebSocket authentication endpoint; account lockout with exponential backoff; MFA and strong password enforcement; IP allowlisting or network segmentation for WebSocket API access where feasible; enhanced logging and alerting for repeated login failures, brute-force patterns, and resource-exhaustion indicators; credential rotation for suspicious accounts; monitor CISA ICS-CERT advisory ICSA-26-274-02 and EUVD for vendor mitigation guidance.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Unauthenticated WebSocket endpoints in the Monta EV charging platform (monta.app, all versions) allow any network-reacha
Unauthenticated session prediction in Monta App's WebSocket backend permits remote attackers to impersonate other chargi
Authentication identifiers for Monta-managed charging stations are published on publicly accessible web-based mapping pl
EUVD-2026-91822
GHSA-pfh8-7x9x-2rrf
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB