Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exporter HTTP endpoint
-
DeliveryOpen many slow connections
-
ExploitTrickle partial HTTP headers
-
ExecutionExhaust file descriptors
-
ImpactExporter stops serving metrics
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the openstack-network-exporter HTTP metrics server be network-reachable by the attacker; the component ships without a ReadHeaderTimeout (and related timeouts), so any default-configured, exposed instance is affected without authentication or user interaction. The practical limiting factor is network exposure: in typical deployments the exporter is reached only by Prometheus over a management/monitoring network, so risk hinges on whether that endpoint is segmented from untrusted hosts. Impact is confined to loss of metric scraping and alerting availability - it does not grant access to or disrupt the OpenStack data plane itself. |
| Impact | This is a genuine but modest-severity availability issue, best treated as routine hardening rather than an emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, base 5.3 Medium) is internally consistent with the description: a remote, unauthenticated attacker exploits a missing ReadHeaderTimeout on the HTTP server to mount a Slowloris-style slow-header attack, with impact limited to availability (A:L) and no confidentiality or integrity loss. No EPSS score, CISA KEV listing, POC, or SSVC decision data was provided in the input, so there is no signal of active exploitation - exploitation status is 'no public exploit identified at time of analysis.' The technical impact is partial (metric scraping/alerting disruption, not full system compromise), and the affected component is an observability exporter rather than a control-plane service, which caps real-world consequence. One nuance to verify: A:L reflects that only the exporter's metrics endpoint goes down, not the underlying OpenStack workloads - the primary harm is a monitoring blind spot. Slowloris-class flaws are well understood and the technique is trivially automatable, so the low complexity (AC:L) is accurate, but absent any exploitation-probability data this should be prioritized by exposure (is the exporter reachable from untrusted networks?) rather than by raw score. |
| Exploit ScenarioDerived | An attacker with network reachability to the openstack-network-exporter metrics endpoint opens many TCP connections and trickles HTTP header bytes very slowly, never completing a request. Because the server has no ReadHeaderTimeout, each connection is held open indefinitely, exhausting file descriptors until the exporter can no longer accept Prometheus scrapes. No public exploit is identified, but the Slowloris technique is trivial to reproduce with commodity tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Denial of service in the openstack-network-exporter HTTP metrics server, as shipped in Red Hat OpenStack Platform 18.0, allows an unauthenticated remote attacker to open many slow HTTP header connections and exhaust server file descriptors, preventing legitimate Prometheus metric scraping and alerting. The component is deployed without a ReadHeaderTimeout or comparable connection timeouts, so any network-reachable instance is affected with no credentials or user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, 5.3). There is no public exploit identified at time of analysis and no evidence of active exploitation; impact is limited to monitoring availability and does not touch the OpenStack data plane, making this a modest availability issue best handled through routine hardening and network segmentation.
RemediationAI
No vendor-released patch identified at time of analysis, so remediation centers on reducing reachability and bounding connection resources until Red Hat ships an errata - monitor https://access.redhat.com/security/cve/CVE-2026-83536 and https://bugzilla.redhat.com/show_bug.cgi?id=2526401 for that release. The most effective compensating control is network restriction: bind the exporter to the management interface and allow the metrics port only from Prometheus scrape addresses using security groups, iptables/nftables, or Kubernetes NetworkPolicy; the trade-off is that additional or relocated monitoring nodes will silently lose scrape access and require rule updates, and any environment where the exporter is intentionally reachable more broadly must instead front it with a timeout-enforcing reverse proxy (for example nginx with short client_header_timeout/proxy_read_timeout values or HAProxy with an explicit header timeout), accepting the added hop, configuration surface, and proxy as a new single point of failure. Secondary hardening includes lowering the process's open-file descriptor limit or applying systemd/cgroup connection caps to bound the blast radius - noting this only defers exhaustion rather than eliminating it - and alerting on exporter up/down and scrape failures so that resource exhaustion is detected quickly. If the exporter build exposes configurable server timeouts, set ReadHeaderTimeout to a small value (a few seconds) and rebuild/redeploy; if no such knob exists in the shipped build, treat the proxy or network-segmentation workaround as mandatory rather than optional.
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 openstack-network-exporter is a Go-based Prometheus exporter whose embedded net/http server is instantiated without hardening timeouts such as ReadHeaderTimeout, ReadTimeout, IdleTimeout, or WriteTimeout, a configuration class tracked as CWE-400 (Uncontrolled Resource Consumption). Without ReadHeaderTimeout, the server has no deadline for completing the request header phase, so a client can establish a TCP connection and dribble header bytes indefinitely; Go's default behavior holds the connection and its associated file descriptor open while waiting. Repeating this across many sockets consumes the process's file descriptor table and connection slots until new connections - including legitimate Prometheus scrapes on the exporter's /metrics endpoint - can no longer be accepted, producing a slow-header (Slowloris-style) denial of service. Because the exporter typically exposes an unauthenticated HTTP endpoint, the CVSS vector's PR:N/UI:N reflects that no authentication or user interaction stands between the attacker and the resource-exhaustion primitive; the affected CPE is cpe:2.3:a:red_hat:red_hat_openstack_platform_18.0, identifying Red Hat OpenStack Platform 18.0 as the productized distribution carrying the flawed component.
Know when Red Hat Openstack Platform 18 0 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:N/I:N/A:L
Remote unauthenticated slow-header attack with no user interaction (AV:N/AC:L/PR:N/UI:N); only the exporter's availability is affected (A:L), with no confidentiality or integrity impact.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
DescriptionCVE.org
A flaw was found in openstack-network-exporter. The HTTP server within the component is configured without essential timeout settings, such as ReadHeaderTimeout. This vulnerability allows an unauthenticated, remote attacker to initiate multiple slow HTTP header connections. By trickling header bytes, the attacker can exhaust server resources, specifically file descriptors, leading to a Denial of Service (DoS) that prevents legitimate Prometheus metric scraping and alerting.
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
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Affected Products (CPE)CVE.org
Unauthenticated path traversal in gvproxy, the network forwarder shipped in the gvisor-tap-vsock package (used by Podman
Symlink-following file overwrite on the Ansible control node is possible in ansible-core when a user runs `ansible-galax
Jinja2 template injection in Ansible Operator Plugins (CWE-1336) lets an authenticated Kubernetes user who can create or
Remote code execution via unsafe Python pickle deserialization in the community.general Ansible collection's memcached f
openstack-network-exporter can be made to silently skip basic authentication when an operator enables user authenticatio
Unconditional TLS certificate validation disabling in the OCAPI modules (ocapi_command, ocapi_info) of the community.gen
A file descriptor leak in the containers/storage Go library's archive.ApplyLayer and ApplyUncompressedLayer functions ca
EUVD-2026-97777
GHSA-qphq-4x45-237m
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB