Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain access to provider error output or logs
-
ExploitTrigger or locate API client error
-
ExecutionRead sensitive data leaked by error handler
-
ImpactReuse exposed credentials or endpoint data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Error message sanitization
MITRE ATT&CK
1 technique across 1 tactic: Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the Dell Terraform Provider for OME (v1.0.0-1.2.3) to hit an API client error path, after which sensitive information is written into an externally-accessible file or location (consistent with CWE-209 - error output such as logs, Terraform state, or debug artifacts). Realistic exploitation is LIMITED by the attacker needing read access to wherever that error output is stored; the provider is operator-run IaC tooling, so exposure typically depends on shared log aggregation, publicly-readable CI/CD output, or state files rather than a directly network-exposed service. The vendor's AV:N/PR:N vector is not clearly supported by the described file-insertion mechanism and should be verified against Dell DSA-2026-434. |
| Impact | Dell rates this CVSS 3.1 8.6 (High) with vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L, implying remote, unauthenticated, low-complexity exploitation with high confidentiality impact. However, the signals conflict with the described mechanism: the flaw is CWE-209 (sensitive information in error handling) that inserts data 'into an externally-accessible file or directory' - a disclosure primitive that in practice depends on an attacker being able to read that file (logs, Terraform state, or a debug artifact produced by the provider), which is characteristically a local/post-compromise condition rather than a clean network-reachable service. The I:L and A:L sub-scores are also hard to reconcile with a pure information-exposure weakness, which normally carries no integrity or availability impact; this suggests the vendor vector may be padded or reflects a broader advisory. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no evidence of real-world exploitation - this is a vendor-disclosed issue, not an actively-attacked one. Net: treat as a moderate, patch-on-normal-cycle issue for the small population running the affected provider, NOT an emergency. Verify the true attack vector (network vs. local file read) with Dell advisory DSA-2026-434 before accepting the AV:N/PR:N framing. |
| Exploit ScenarioDerived | The Dell Terraform Provider for OME, while managing OpenManage Enterprise, encounters an API client error whose handler writes sensitive details (e.g., credentials, tokens, or internal endpoint data) into an error message or file that is accessible beyond the intended trust boundary. An attacker who can reach that artifact - a shared log store, exported state, or CI output - reads the leaked secrets and reuses them. No public exploit identified at time of analysis; exploitation requires access to the location where the error output lands. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Information exposure in the Dell Terraform Provider for OME, versions 1.0.0 through 1.2.3, occurs when the provider's API client error-handling path writes sensitive information into an externally accessible file or directory (CWE-209). Dell rates this CVSS 3.1 8.6 (High) with a remote, unauthenticated vector (AV:N/PR:N/UI:N/S:U/C:H/I:L/A:L), but independent assessment maps realistic exploitation to AV:L/AC:L/PR:N/UI:N/C:H/I:N/A:N, because an attacker must already be able to read wherever the provider's error output is persisted - typically shared log aggregation, publicly readable CI/CD output, or exposed Terraform state/debug artifacts - rather than reaching a directly network-exposed service. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the vendor's AV:N vector should be validated against Dell DSA-2026-434 before treating this as a remotely exploitable unauthenticated issue.
RemediationAI
Upgrade the Dell Terraform Provider for OME to a fixed release identified in Dell DSA-2026-434 (https://www.dell.com/support/kbdoc/en-in/000515444/dsa-2026-434-security-update-for-dell-terraform-provider-for-dell-server-multiple-vulnerabilities); the input data confirms a vendor security update exists but does not state an exact fixed version, so the advisory is the authoritative source and version numbers should not be assumed. Because the exposure mechanism is a sensitive error artifact written to an accessible location, compensating controls matter: restrict filesystem and object-store permissions on Terraform state files and provider debug logs to the operator identity only, avoid committing plan/apply output or provider logs to shared CI/CD artifact stores, and scrub or rotate any logs already aggregated where sensitive fields may have leaked - noting each of these reduces only the read-side exposure and does not fix the underlying error-handling defect until the provider is upgraded. If Dell's DSA-2026-434 confirms a fixed provider release, pin the provider version in required_providers and re-run terraform init -upgrade; if it does not, coordinate with Dell support for a patched build and, in the interim, disable provider debug logging (TF_LOG) at levels that capture HTTP bodies and avoid applying the provider against production OME where a shared log sink is in use.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Dell Terraform Provider for OME is a Go-based Terraform plugin that talks to Dell OpenManage Enterprise (OME) over its REST API to provision and manage Dell server infrastructure as code; it runs in the operator's environment (developer workstation, CI/CD runner, or automation host) rather than as a network service. The flaw is rooted in CWE-209 (Generation of Error Message Containing Sensitive Information): when the API client hits an error path, the resulting diagnostic output - which may include API response bodies, credentials, session tokens, host details, or other sensitive fields - is inserted into an externally accessible file or directory such as Terraform state, plan/apply output, provider debug logs, or CI job logs. The CPE cpe:2.3:a:dell:terraform_provider_for_ome:*:*:*:*:*:*:*:* is a wildcard entry, so scanners may flag every version of the provider even though the description scopes impact to 1.0.0 through 1.2.3. Exploitation is not a direct network exploit against OME; it depends on a downstream reader gaining access to the error artifact, which is why the independent assessment lowers the vector to AV:L and limits impact to confidentiality (C:H) with no integrity or availability loss.
Know when Terraform Provider For Ome 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
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
CWE-209 disclosure into an externally-accessible file realistically requires reading that local artifact (AV:L); pure information exposure yields C:H with no integrity or availability impact, unlike the vendor's I:L/A:L.
Primary rating from Vendor (dell).
CVSS VectorVendor: dell
Lifecycle Timeline
2DescriptionCVE.org
Dell Terraform Provider for OME, versions 1.0.0 through 1.2.3, contains an Insertion of Sensitive Information into Externally-Accessible File or Directory vulnerability in the API client error handling component. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to information exposure.
Executive ViewAI
The Dell Terraform Provider for OME (versions 1.0.0 through 1.2.3) can write sensitive credential and configuration data into log files, CI/CD job output, and Terraform state or debug artifacts that are frequently readable well beyond the team that owns them. No vendor patch is available and no public exploit has been identified at time of analysis, but because the leaked material typically includes credentials used to manage Dell OpenManage Enterprise infrastructure, exposure through shared logging or pipeline storage could give unintended parties direct control over managed hardware. Leadership should treat this as a secrets-hygiene and access-control issue owned jointly by platform engineering, DevOps, and security operations rather than as an externally reachable network vulnerability.
No vendor patch available. Interim mitigations: restrict access to log aggregation platforms, CI/CD job output, and Terraform state backends to the minimum personnel and service accounts required; enable secret masking/redaction in the CI/CD system and disable verbose or debug Terraform logging that captures provider error output; store Terraform state in an encrypted backend with strict access controls and versioning so disclosure is detectable and reversible; rotate Dell OpenManage Enterprise credentials and API keys used through affected provider versions; avoid running affected provider versions on shared or multi-tenant runners; monitor and alert on access to logs and state artifacts containing OME-related data; and validate exposure against Dell advisory DSA-2026-434, applying the vendor fix as soon as a remediated provider version is released.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-101159
GHSA-gjrr-q5h7-3grr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB