Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to RMC with privileged account
  2. Delivery
    Submit crafted input to vulnerable RMC function
  3. Exploit
    Command injection into underlying OS shell
  4. Execution
    Execute arbitrary commands on RMC
  5. Impact
    Full compromise of management controller

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK

2 techniques across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation targets the Remote Management Controller (RMC) interface of the affected HPE scale-up servers and requires network reachability to that management interface. The CVSS vector's PR:H means the attacker must authenticate with HIGH privileges on the RMC before injecting commands - this is the primary limiting factor and rules out unauthenticated exploitation. No user interaction is required (UI:N) and attack complexity is low (AC:L) once privileged access is held. Risk is further bounded by whether the RMC management network is segmented/isolated from general networks per HPE best practice; exposure of the RMC to untrusted networks significantly raises real-world risk. The exact RMC feature/parameter that accepts the injected command is not specified in the available data.

Impact

This is a CWE-78 OS command injection flaw on the Remote Management Controller (RMC) of HPE's high-end Compute Scale-up 3200/3250 and Superdome Flex / Flex 280 platforms, rated CVSS 7.2 (High). The vendor-supplied vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N shows network reachability with low attack complexity but HIGH privileges required (PR:H), so this is NOT an unauthenticated remote takeover - an attacker must already hold a privileged RMC account. Full C:H/I:H/A:H with unchanged scope (S:U) means complete compromise of the management controller itself once authenticated. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no evidence of active exploitation or widespread automated attacks. The practical priority is moderate: although arbitrary command execution on a management controller is serious, the PR:H requirement and the niche, limited deployment footprint of these specialized servers substantially narrow the realistic attacker population. Treat as a privilege-escalation / post-authentication hardening fix on the management plane rather than a mass-exploitation emergency; prioritize patching where RMC interfaces are network-exposed.

Exploit ScenarioDerived

An attacker who has obtained valid privileged (PR:H) credentials to the RMC management interface - for example a malicious insider, or an outsider who harvested or reused administrative credentials - sends a crafted request whose parameter is passed unsanitized into an OS command. This injects and executes arbitrary commands on the RMC, yielding full control of the server's management controller. No public exploit code is identified at time of analysis, and no user interaction is required.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 19, 2026

OS command injection on the Remote Management Controller (RMC) of HPE Compute Scale-up Server 3200/3250 and Superdome Flex / Flex 280 platforms allows an attacker who already holds high-privilege credentials on the RMC to run arbitrary operating system commands on the controller. The flaw is rated CVSS 7.2 (High) with a vector of AV:N/AC:L/PR:H/UI:N, so exploitation is remote and low-complexity once the privileged foothold exists - the high-privilege requirement is the principal limiting factor and rules out unauthenticated attacks. No public exploit code or confirmed active exploitation is identified in the available data, though the sensitive nature of the RMC as a system-management plane makes exposure to untrusted networks a significant risk multiplier.

RemediationAI

Apply the RMC firmware update referenced in HPE Security Bulletin hpesbhf05153 (https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbhf05153en_us&docLocale=en_US) to all Compute Scale-up 3200/3250 and Superdome Flex / Flex 280 RMCs; the advisory is the only authoritative source for the exact fixed firmware revisions, so verify current RMC firmware against it before and after upgrading and schedule the update in a maintenance window since RMC firmware updates typically require a management-plane restart and may briefly interrupt console and partitioning functions. Because exploitation requires high-privilege RMC credentials, the highest-value compensating controls are credential hygiene and network isolation: enforce strong, unique RMC administrative credentials with MFA where supported, audit and prune dormant or shared admin accounts, and rotate any credentials that may have been exposed - side effect is added operational overhead for admin access. Segregate the RMC management network from production and general user networks with strict firewall ACLs allowing only designated administrative jump hosts, which materially reduces the AV:N exposure; the trade-off is that legitimate remote management must be proxied through the jump hosts, and any existing direct-access workflows for operators will break. Remove any internet-facing or broadly routed RMC interfaces, and monitor RMC audit logs for anomalous command or shell-metacharacter input from administrative sessions, since such patterns are the clearest indicator of attempted exploitation of this injection flaw.

Affected VersionsENISA

HPE Superdome Flex Server 0 <4.17.03
HPE Superdome Flex 280 server 0 <2.17.03
HPE Compute Scale-up Server 3250 platform 0 <1.03.38
HPE Compute Scale-up Server 3200 platform 0 <1.77.30

Affected Packages

euvd hpe_compute_scale_up_server_3200_platform fix: 1.77.30
euvd hpe_compute_scale_up_server_3250_platform fix: 1.03.38
euvd hpe_superdome_flex_280_server fix: 2.17.03
euvd hpe_superdome_flex_server fix: 4.17.03

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 4 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected systems are HPE's high-end scale-up x86 platforms - Compute Scale-up Server 3200 and 3250, and Superdome Flex / Flex 280 - whose out-of-band management is handled by a dedicated Remote Management Controller (RMC). The RMC is the supervisory component that handles hardware configuration, partitioning, console access, and firmware operations for the chassis, which is why C/I/A impact is rated High across the board: compromise of the RMC is effectively compromise of the platform's management plane. The root cause class is CWE-78 (Improper Neutralization of Special Elements used in an OS Command), meaning user- or API-supplied input is passed to a shell or command interpreter without adequate sanitization or parameterization, letting metacharacters break out into arbitrary command execution. The CVSS 3.1 vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H confirms the RMC interface is network-reachable and the injection is straightforward to trigger, but requires high privileges (PR:H) on the RMC beforehand; scope is unchanged, so the impact is contained to the RMC itself rather than escalating to managed host OSes via the vulnerability alone. The specific RMC endpoint, parameter, or CLI function that accepts the injected input is not disclosed in the available data, which constrains precise workaround guidance.

Know when Hpe Compute Scale Up Server 3200 Platform 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

Vendor (hpe) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.2 HIGH

RMC is network-reachable (AV:N) with low complexity (AC:L); command injection requires an authenticated privileged RMC account (PR:H); full compromise of the controller gives C:H/I:H/A:H, scope unchanged.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (hpe).

CVSS VectorVendor: hpe

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 19, 2026 - 08:01 EUVD
CVE Published
Oct 19, 2026 - 06:25 cve.org
HIGH 7.2

DescriptionCVE.org

A security vulnerability in HPE Compute Scale-up Server 3200 and 3250 platforms, Superdome Flex and Superdome Flex 280 servers could be exploited remotely to execute arbitrary commands on the RMC.

Executive ViewAI

Why It Matters

HPE Compute Scale-up Server 3200/3250 and Superdome Flex platforms carry a high-severity flaw in the Remote Management Controller (RMC) that lets someone holding elevated RMC credentials execute arbitrary operating-system commands on the controller itself. Because the RMC is the management plane for these large scale-up systems - typically hosting the organization's most critical in-memory and mission-critical workloads - a compromise there can undermine the integrity and availability of the servers it governs, not just the controller. There is currently no vendor patch and no identified public exploit code, so the immediate risk is concentrated in how widely the RMC management interface is exposed and how tightly privileged RMC accounts are controlled.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict RMC management interfaces to a dedicated, tightly segmented administrative network with allow-listed source addresses and no internet exposure; enforce multi-factor authentication and least privilege on RMC accounts, minimizing the population holding high-privilege credentials; rotate credentials and remove dormant or shared privileged accounts; enable centralized logging and alerting for RMC command execution and configuration changes; and apply HPE-published workarounds as directed by the vendor.

Threat Intelligence Overview

EPSS Score
0.4%
Top 70% exploitable
Prevalence
Low
niche high-end enterprise scale-up/Superdome Flex hardware, limited deployments
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

OS command injection occurs when an application passes unsanitized user input directly into system shell commands.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy