How severe is CVE-2024-54085?

No CVSS score has been assigned to CVE-2024-54085 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-54085?

Affected package information for CVE-2024-54085 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2024-54085?

No fixed release is recorded for CVE-2024-54085 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2024-54085 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2024-54085 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2024-54085 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-54085 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-54085?

CVE-2024-54085 has an EPSS (Exploit Prediction Scoring System) score of 60.7%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2024-54085 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2024-54085 (AMI MegaRAC SPx Authentication Bypass by Spoofing Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-06-25. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-07-16. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2024-54085?

CVE-2024-54085 is classified as CWE-290 (CWE-290). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-54085 published, and has it been updated?

CVE-2024-54085 was published on March 11, 2025 and was last updated on February 26, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV · ACTIVELY EXPLOITED

CVE-2024-54085

CVE-2024-54085 is a CWE-290 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-06-25) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

AMI’s SPx contains a vulnerability in the BMC where an Attacker may bypass authentication remotely through the Redfish Host Interface. A successful exploitation of this vulnerability…

Published

Mar 11, 2025

Updated

Feb 26, 2026

Affected

10 products

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-06-25. Federal agencies were required to remediate by 2025-07-16.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2024-54085.

EPSS Exploitation Probability

via FIRST.org ↗

60.7%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

AMI’s SPx contains a vulnerability in the BMC where an Attacker may bypass authentication remotely through the Redfish Host Interface. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.

Affected Products

10 products · 11 configurations

megarac sp-xami

≥ 13 && < 13.5

range

h300s firmwarenetapp

all

h410c firmwarenetapp

all

h410s firmwarenetapp

all

h500s firmwarenetapp

all

h700s firmwarenetapp

all

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2024-54085 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-54085 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works