dbcve.org
Powerchute Serial ShutdownApplication · Schneider Electric

CVE-2026-2405

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 1.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
CWE-400 Uncontrolled Resource Consumption vulnerability exists that could cause excessive troubleshooting zip file creation and denial of service when a Web Admin user floods the system with POST /helpabout requests.

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 confidence

A vulnerability in the Web Admin interface allows authenticated users to flood the POST /helpabout endpoint with excessive requests, causing unlimited troubleshooting zip file creation. This uncontrolled resource consumption exhausts disk space, memory, and CPU, leading to denial of service.

MitigationImplement rate limiting and request throttling on the /helpabout endpoint, and add resource constraints (file size limits, timeout controls, queue limits) to the zip file creation process.

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
Powerchute Serial ShutdownApplication
Affected:< 1.5

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Powerchute Serial Shutdown version
    Check the installed software version through the system's installed programs list, application properties, or by querying the software directly (e.g., about dialog, version command, or registry entry if applicable)
    Affected if The installed version is any version prior to 1.5 (versions 1.0 through 1.4.x are affected)
  2. Verify Web Admin interface is enabled
    Check the Powerchute configuration or service settings to determine if the Web Admin interface is currently active and accessible
    Affected if The Web Admin interface is enabled and reachable on the network
  3. Confirm network accessibility of /helpabout endpoint
    Attempt to reach the POST /helpabout endpoint via HTTP/HTTPS on the port where Powerchute Web Admin is hosted (typically port 8080 or 8443) using a tool like curl or a browser
    Affected if The /helpabout endpoint responds to requests (indicates the vulnerable feature is exposed)
  4. Monitor for abnormal resource consumption
    Observe disk space usage, memory consumption, and CPU utilization on the host running Powerchute, particularly in the directory where troubleshooting files would be created
    Affected if Disk space is rapidly depleting, CPU/memory usage is unusually high, or large unexpected zip files are appearing in the system

You are affected if Powerchute Serial Shutdown version is below 1.5 AND the Web Admin interface with the /helpabout endpoint is accessible, leading to potential resource exhaustion from excessive zip file generation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.5 or later
Fixed in 1.5
Interim mitigation

Implement rate limiting and request throttling on the /helpabout endpoint, and add resource constraints (file size limits, timeout controls, queue limits) to the zip file creation process.

Recommended fix Moderate confidence

Powerchute Serial Shutdown 1.5 or later

  1. 1. Identify the currently installed version of Powerchute Serial Shutdown by checking the application or system information.
  2. 2. If the installed version is below 1.5, download Powerchute Serial Shutdown version 1.5 or later from the Schneider Electric official download portal (download.schneider-electric.com).
  3. 3. Follow the standard upgrade procedure documented in the Powerchute Serial Shutdown installation guide.
  4. 4. After upgrading, verify the new version is 1.5 or higher.
  5. 5. Test that the Web Admin interface responds normally to POST /helpabout requests to confirm the vulnerability is remediated.
Caveat Minimal risk - point release upgrade typically maintains compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Powerchute Serial Shutdown Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2405 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2405 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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