CVE-2025-37164
A remote code execution issue exists in HPE OneView.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. Code injection payloads are often obfuscated, so they slip past generic WAF rules.
Also consider: remove eval sinks · RASP
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-37164 being exploited?
Yes. CVE-2025-37164 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-37164?
CVE-2025-37164 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-37164?
Yes. A fix has been recorded for CVE-2025-37164. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-37164 affect?
CVE-2025-37164 affects hpe:oneview. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 11.00
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Public exploit code: 1 Metasploit module · 3 GitHub proofs of concept · 1 Nuclei template
- exploit/linux/http/hpe_oneview_rce · exploit · excellent
- HPE OneView - Remote Code Execution · detection template · critical
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 8 Jan 2026 (SSVC 2.0.3).
timeline
- 16 Dec 2025Published
- 18 Dec 2025First public exploit or proof of concept · 1 day later
- 7 Jan 2026Added to CISA KEV (exploited in the wild) · 20 days later
- 8 Jan 2026CISA SSVC assessment: exploitation active · 1 day later
- 28 Jan 2026CISA remediation due date (US federal agencies) · 20 days later
- 26 Feb 2026CVE record last updated · 30 days later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
- Advisorysupport.hpe.com /hpesc/public/docDisplay?docId=hpesbgn04985en_us&docLocale=en_US#vulnerability-s
- Exploitgithub.com /rapid7/metasploit-framework/blob/master/modules/exploits/linux/http/hpe_oneview
- Linksupport.hpe.com /hpesc/public/docDisplay?docId=hpesbgn04985en_us&docLocale=en_US
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-37164
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Metasploit Framework: exploit and scanner modules
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.