CVE
Dell OpenManage Ansible Modules, versions 2.1.2 through 10.0.3, contains an Improper Certificate Validation vulnerability in the…
Only affects Dell OpenManage Ansible Modules 2.1.2 through 10.0.3 when the iDRACRedfishAPI component runs without certificate verification (validate_certs not set to True). Fixed in 11.0.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 11.0.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 11.0.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Dell OpenManage Ansible Modules contains an improper certificate validation flaw in its iDRACRedfishAPI component. Remotely, without logging in, an attacker could potentially exploit it to expose information and gain unauthorized access.
Read the original description
Dell OpenManage Ansible Modules, versions 2.1.2 through 10.0.3, contains an Improper Certificate Validation vulnerability in the iDRACRedfishAPI component. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to information exposure and unauthorized access.
Who should check
Teams running Dell OpenManage Ansible Modules 2.1.2 through 10.0.3 that use the iDRACRedfishAPI component
Read the source excerpt
“Dell OpenManage Ansible Modules, versions 2.1.2 through 10.0.3, contains an Improper Certificate Validation vulnerability in the iDRACRedfishAPI component”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 11.0.0.
Workaround: Explicitly enable certificate verification by setting validate_certs=True when using iDRACRedfishAPI.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-91873 (Dell OpenManage Ansible Modules, versions 2.1.2 through 10.0.3, contains an Improper Certificate Validation vulnerability in the…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-91873 (entry last updated 2026-11-11):
Affected:
- Dell OpenManage Ansible Modules: version range not reported
Fixed versions: 11.0.0.
Conditions (all must be true for the bug to be hit):
- Dell OpenManage Ansible Modules versions 2.1.2 through 10.0.3 with the iDRACRedfishAPI component (source: https://www.dell.com/support/kbdoc/en-in/000515420/dsa-2026-432-security-update-for-dell-ansible-server-vulnerabilities)
- Certificate verification is not enabled (validate_certs not set to True) when using iDRACRedfishAPI (source: https://www.dell.com/support/kbdoc/en-in/000515420/dsa-2026-432-security-update-for-dell-ansible-server-vulnerabilities)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Explicitly enable certificate verification by setting validate_certs=True when using iDRACRedfishAPI. (source: https://www.dell.com/support/kbdoc/en-in/000515420/dsa-2026-432-security-update-for-dell-ansible-server-vulnerabilities)
CISA KEV: CVE-2026-91873 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-91873 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.dell.com/support/kbdoc/en-in/000515420/dsa-2026-432-security-update-for-dell-ansible-server-vulnerabilities
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-91873
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-91873"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Dell OpenManage Ansible Modules
Version range not reported
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-91873
Is CVE-2026-91873 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The iDRACRedfishAPI component does not properly validate the certificate of the server it connects to. This can lead to information exposure and unauthorized access.Source: dell.com
Am I affected, and how do I check?
Versions 2.1.2 through 10.0.3 of Dell OpenManage Ansible Modules are affected when the iDRACRedfishAPI component is used with certificate verification not enabled. To check, look at the installed version of the Dell OpenManage Ansible Modules collection and at whether validate_certs is set to True in the playbooks that use iDRACRedfishAPI.Source: dell.com
How do I fix CVE-2026-91873?
Upgrade to version 11.0.0 or later, which contains the fix. Until the upgrade is done, set validate_certs=True whenever iDRACRedfishAPI is used.Source: dell.com