dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2026-27663

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges 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
A vulnerability has been identified in CPCI85 Central Processing/Communication (All versions < V26.10), RTUM85 RTU Base (All versions < V26.10). The affected application contains denial-of-service (DoS) vulnerability. The remote operation mode is susceptible to a resource exhaustion condition when subjected to a high volume of requests. Sending multiple requests can exhaust resources, preventing parameterization and requiring a reset or reboot to restore functionality.

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 · high confidence

The vulnerability is a denial-of-service condition in CPCI85 and RTUM85 devices where remote operation mode is susceptible to resource exhaustion when subjected to a high volume of requests. Attackers can send multiple requests to exhaust device resources, preventing parameterization and requiring a reset or reboot to restore functionality.

MitigationUpgrade to version V26.10 or later per vendor guidance. As a compensating control, implement network-level rate limiting or access controls to restrict the volume of remote requests reaching the affected devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:A/AC:L/PR:N/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 device model
    Check device label, management interface, or SNMP inventory for model number CPCI85 or RTUM85
    Affected if Device is a CPCI85 or RTUM85 unit
  2. Check firmware version
    Access device web interface, CLI, or management software and locate firmware version information. Compare against V26.10
    Affected if Firmware version is prior to V26.10 or cannot be determined
  3. Verify remote operation mode status
    Access device configuration settings via web interface, CLI, or management protocol. Look for remote operation, remote access, or remote management mode settings
    Affected if Remote operation mode is enabled and accessible over network
  4. Assess network exposure
    Review firewall rules, ACLs, or network segmentation to determine if remote management interface is exposed to untrusted networks
    Affected if Remote operation interface is reachable from untrusted or external networks
  5. Check for resource exhaustion symptoms
    Review device logs, SNMP counters, or management interface for indicators of high request volume, memory exhaustion, or service degradation
    Affected if Device shows signs of resource exhaustion or abnormal request processing

Device is affected if it is a CPCI85 or RTUM85 with remote operation mode enabled, firmware before V26.10, and accessible over the network to attackers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version V26.10 or later per vendor guidance. As a compensating control, implement network-level rate limiting or access controls to restrict the volume of remote requests reaching the affected devices.

Recommended fix Moderate confidence

V26.10 for both CPCI85 Central Processing/Communication and RTUM85 RTU Base

  1. Upgrade CPCI85 Central Processing/Communication to version V26.10 or later
  2. Upgrade RTUM85 RTU Base to version V26.10 or later
  3. After upgrade, verify the remote operation mode no longer experiences resource exhaustion under high request volumes
  4. Test that normal parameterization functionality is restored
  5. Document the upgrade in change management system
Caveat Industrial control system upgrades may require compatibility testing with connected systems; verify all integrations function correctly after upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27663 — 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-27663 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