CVE-2026-2402
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 · uneditedCWE-307 Improper Restriction of Excessive Authentication Attempts vulnerability exists that would allow an attacker to gain access to the user account by performing an arbitrary number of authentication attempts with different credentials on a sequence of requests to multiple endpoints.
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 confidenceThis is a CWE-307 vulnerability where the application fails to properly restrict excessive authentication attempts. Attackers can bypass typical account lockout protections by distributing login attempts across multiple endpoints (e.g., /login, /api/auth, /password-reset) instead of targeting a single authentication point. This allows unlimited brute-force attempts with different credentials, potentially leading to account takeover.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.5CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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.
-
Identify installed productLocate Schneider Electric Powerchute Serial Shutdown on the system. Check installed programs list, program files directory, or service list for 'Powerchute Serial Shutdown' or associated processes.Affected if The product is not present on the system.
-
Determine product versionCheck the installed version of Powerchute Serial Shutdown through the application's About dialog, installed programs list, or version information in the executable properties.Affected if The installed version is any version prior to 1.5 (e.g., 1.4.x, 1.3.x, etc.).
-
Verify authentication endpoints existReview application documentation or enumerate available network endpoints/services that handle authentication (such as /login, /api/auth, /password-reset, or serial console login interfaces).Affected if Multiple authentication endpoints exist and are accessible.
-
Check for centralized rate limitingExamine application configuration files, settings, or logs to determine whether failed authentication attempts are tracked across all authentication endpoints as a unified system.Affected if Rate limiting or account lockout is enforced per-endpoint independently rather than centrally.
The environment is affected if Schneider Electric Powerchute Serial Shutdown version 1.5 or higher is not installed and the application exposes multiple authentication endpoints without centralized attempt tracking.
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.
dbcve · scoped1.5
Implement centralized rate limiting and account lockout mechanisms that track failed authentication attempts across ALL authentication endpoints as a unified system, regardless of which specific endpoint is used. Consider adding progressive delays, CAPTCHA after failed attempts, and alerting for suspicious authentication patterns.
Powerchute Serial Shutdown 1.5 or later
- 1. Identify the current version of Powerchute Serial Shutdown installed on the system
- 2. Navigate to Schneider Electric's official download portal at download.schneider-electric.com
- 3. Locate and download Powerchute Serial Shutdown version 1.5 or later
- 4. Review the release notes for any installation prerequisites or special instructions
- 5. Apply the upgrade following Schneider Electric's documented upgrade procedure
- 6. Verify the installed version confirms the update to 1.5 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2402 — 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-2402 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