Red Hat Openstack Platform 18 0
Monthly
Jinja2 template injection in Ansible Operator Plugins (CWE-1336) lets an authenticated Kubernetes user who can create or modify a custom resource reconciled by an affected Ansible-based operator execute embedded Jinja2 expressions inside the operator pod, achieving remote code execution and escalating to the operator's service account. Because these operators typically hold cluster-wide RBAC, successful exploitation crosses a privilege boundary (CVSS 3.1 base 8.5, AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H), affecting components of Red Hat Ansible Automation Platform 2, Red Hat Advanced Cluster Management for Kubernetes 2, the Migration Toolkit for Applications/Containers/Virtualization, OpenShift Service Mesh 3 and related Red Hat OpenShift and OpenStack streams. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; the high attack complexity reflects the prerequisite that the targeted operator must pass attacker-controllable CR spec values into Jinja2 templating without sanitization. This is a genuinely high-priority flaw rather than a CVSS-inflated one, but with an important authentication caveat: purely anonymous or read-only users cannot trigger it.
openstack-network-exporter can be made to silently skip basic authentication when an operator enables user authentication but forgets or misconfigures TLS, letting an adjacent-network attacker pull OVS/OVN dataplane metrics without credentials. Only deployments in that specific non-default, inconsistent configuration are exposed; correct TLS deployments and deployments without authentication enabled are unaffected. The published CVSS is 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N), but our assessment narrows this to AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N - adjacency-limited, read-only information disclosure, with no integrity or availability impact and no public exploit identified at time of analysis.
Unauthenticated path traversal in gvproxy, the network forwarder shipped in the gvisor-tap-vsock package (used by Podman Desktop, Red Hat OpenShift/CRC tooling and related Red Hat products), lets an attacker who can reach the /services/forwarder/expose control endpoint supply an arbitrary socket path that is passed unsanitised to os.Remove, resulting in deletion of arbitrary files on the host. The defect is reachable without credentials (PR:N) but requires adjacent/guest-side network access to the forwarder API (AV:A), which is normally bound to the virtual network rather than exposed as a routed internet service; impact is limited to integrity and availability (no data disclosure). No public exploit code has been identified at time of analysis and the flaw is not listed as confirmed actively exploited (CISA KEV); an upstream fix exists in gvisor-tap-vsock PR #718. The vendor score of 9.3 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H) reflects low-complexity, unauthenticated access combined with a scope change and High integrity/availability impact, and the actual risk depends heavily on whether the forwarder control API is reachable by an untrusted guest or adjacent host.
Symlink-following file overwrite on the Ansible control node is possible in ansible-core when a user runs `ansible-galaxy collection install` against a crafted collection tarball, because the archive extractor validates member paths with lexical normalization (os.path.abspath) instead of resolving symlinks (os.path.realpath) and performs no containment check on symlink-typed directory members before creating them, letting chained symlink entries redirect a subsequent file member outside the destination directory. The flaw (CWE-59, CVSS 8.8, vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) is a bypass of the fix for CVE-2020-10691 and requires the victim to actively install the malicious collection, so an attacker can write arbitrary files with the privileges of the ansible-galaxy user and potentially achieve code execution on the control node. No public exploit has been identified at time of analysis and the CVE is not listed in CISA KEV; affected deployments include ansible-core 2.x as shipped in Red Hat Ansible Automation Platform 2 and numerous other Red Hat products, and no patched version is identified in the supplied intelligence, which currently cites only the Red Hat CVE page and Bugzilla 2531646.
Remote code execution via unsafe Python pickle deserialization in the community.general Ansible collection's memcached fact cache plugin gives unauthenticated network-adjacent attackers full control of the Ansible controller. Despite documenting JSON as its storage format, the plugin delegates serialization entirely to python-memcached, which transparently pickles Python objects on write and unpickles them on read - a format that executes arbitrary Python code during deserialization. Because memcached has no native authentication and Ansible fact cache keys are derived from predictable hostnames, any attacker who can write to the target memcached instance can inject a malicious payload that executes when the controller next reads cached facts. No public exploit or CISA KEV entry has been identified at time of analysis.
dnsmasq's DHCPv6 client hostname parser can read one byte past the end of a crafted FQDN option when the server processes a single DHCPv6 packet from an attacker on the same local link. The over-read byte is neither returned to the client nor logged, and no crash or confirmed information disclosure has been demonstrated; the independent assessment scores confidentiality, integrity, and availability impact as none, so real-world risk is low despite the genuine memory-safety defect. No CISA KEV entry or public exploit code was identified at time of analysis.
DHCP lease metadata disclosure in dnsmasq (CVE-2026-93010) occurs when the DHCP leasequery feature has been switched on without an allow-list of permitted query sources, letting any host on the local network pull lease records - assigned IP addresses, MAC addresses, hostnames and related lease metadata. The package is shipped across Red Hat Enterprise Linux 6 through 10 and is bundled into Red Hat OpenShift Container Platform 4, Ceph Storage 9 and OpenStack Platform builds, but the vulnerable feature is off unless an administrator explicitly enables it. Severity is capped at a confidentiality-only leak (CVSS 4.3, adjacent-network attack vector), and no public exploit code or active exploitation has been identified at time of analysis.
TFTP file substitution in dnsmasq allows an attacker on the local network to make a later client receive stale, previously cached transfer data instead of the file it requested; in PXE network-boot deployments this can substitute attacker-chosen boot content for a victim machine, giving both confidentiality and integrity impact. The flaw only exists when dnsmasq is running with its TFTP server feature enabled (a non-default configuration used for network boot), requires adjacent-network access (AV:A) with no authentication (PR:N) and no user interaction (UI:N), but is rated high complexity (AC:H) because the attacker cannot control when another client will request the same file and pick up the cached response. There is no CISA KEV entry and no public exploit code identified at time of analysis, and the vendor-reported CVSS 3.1 score is 6.8, making this a moderate, situational issue rather than an emergency; Red Hat tracks it for remediation within the current monthly cycle.
Denial of service against dnsmasq's TCP DNS service: remote attackers can occupy the entire small fixed pool of TCP child processes by holding idle connections open to port 53, which blocks new TCP DNS queries and any DNSSEC validation that depends on TCP fallback. The flaw is packaged in Red Hat Enterprise Linux 6, 7, 8, 9 and 10 as well as Red Hat OpenShift Container Platform 4, Ceph Storage 9 and OpenStack Platform 13 (Queens) and 18.0, so any of those deployments exposing TCP/53 to untrusted networks is in scope. Impact is confined to availability and is time-bounded rather than permanent - UDP resolution keeps working and occupied slots are released after a fixed lifetime - and no public exploit identified at time of analysis.
dnsmasq builds that include the DNSSEC validator and have validation enabled at runtime can write a few bytes past an internal domain-name buffer when converting names to and from DNS wire format, corrupting adjacent heap metadata. Only deployments where DNSSEC support was compiled in and DNSSEC validation is switched on are exposed; the default dnsmasq build omits DNSSEC entirely, and exploitation further requires an attacker to make the resolver validate a crafted DNSSEC response, for example through a spoofed or attacker-controlled answer for a signed name. Rated CVSS 5.3 (integrity-only, low impact) and no public exploit identified at time of analysis; the priority signal is this_month, not immediate action.
A DNS cache-poisoning flaw in dnsmasq (CWE-345, insufficient verification of data authenticity) lets a malicious or compromised upstream resolver inject cached records for names outside its authoritative zone when dnsmasq follows a CNAME in a response. Only split-DNS deployments that forward specific domains to a designated upstream are realistically exposed, since the attacker must already occupy that trusted upstream position; standard single-forwarder or root-hint setups are far less affected. Impact is integrity-only (attacker-chosen addresses returned to later clients), rated CVSS 6.8 with AC:H, and no public exploit code or KEV entry was identified at time of analysis, so priority follows the vendor's this-month cadence rather than emergency response.
A file descriptor leak in the containers/storage Go library's archive.ApplyLayer and ApplyUncompressedLayer functions causes descriptors to be left open whenever corrupt or malicious image layers or tar streams are unpacked, and repeated processing of such inputs can exhaust the hosting process's file descriptor limit. The weakness is unauthenticated in CVSS terms (PR:N) but local in scope (AV:L) and requires the victim to actually process attacker-influenced layers (UI:R), so an attacker must first get malformed image content in front of a build, pull, or sync loop. Impact is availability-only and confined to the affected process (C:N/I:N/A:L, S:U): no code execution and no data exposure; a single bad input does not cause denial of service, only sustained repetition does. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, and EPSS scoring was not supplied with the source data.
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.
Unconditional TLS certificate validation disabling in the OCAPI modules (ocapi_command, ocapi_info) of the community.general Ansible collection exposes HTTP Basic-Auth credentials to interception and permits response tampering against any managed OCAPI storage or enclosure device. Because the shared request helper disables certificate validation on every call with no parameter to re-enable it, a network-adjacent attacker performing a MITM attack can present any certificate, silently capture credentials, and inject falsified device responses back to the Ansible controller. Red Hat bundles the affected collection in Ceph Storage 5 and 9 and OpenStack Platform 17.1 and 18.0; no public exploit has been identified at time of analysis.
Jinja2 template injection in Ansible Operator Plugins (CWE-1336) lets an authenticated Kubernetes user who can create or modify a custom resource reconciled by an affected Ansible-based operator execute embedded Jinja2 expressions inside the operator pod, achieving remote code execution and escalating to the operator's service account. Because these operators typically hold cluster-wide RBAC, successful exploitation crosses a privilege boundary (CVSS 3.1 base 8.5, AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H), affecting components of Red Hat Ansible Automation Platform 2, Red Hat Advanced Cluster Management for Kubernetes 2, the Migration Toolkit for Applications/Containers/Virtualization, OpenShift Service Mesh 3 and related Red Hat OpenShift and OpenStack streams. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; the high attack complexity reflects the prerequisite that the targeted operator must pass attacker-controllable CR spec values into Jinja2 templating without sanitization. This is a genuinely high-priority flaw rather than a CVSS-inflated one, but with an important authentication caveat: purely anonymous or read-only users cannot trigger it.
openstack-network-exporter can be made to silently skip basic authentication when an operator enables user authentication but forgets or misconfigures TLS, letting an adjacent-network attacker pull OVS/OVN dataplane metrics without credentials. Only deployments in that specific non-default, inconsistent configuration are exposed; correct TLS deployments and deployments without authentication enabled are unaffected. The published CVSS is 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N), but our assessment narrows this to AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N - adjacency-limited, read-only information disclosure, with no integrity or availability impact and no public exploit identified at time of analysis.
Unauthenticated path traversal in gvproxy, the network forwarder shipped in the gvisor-tap-vsock package (used by Podman Desktop, Red Hat OpenShift/CRC tooling and related Red Hat products), lets an attacker who can reach the /services/forwarder/expose control endpoint supply an arbitrary socket path that is passed unsanitised to os.Remove, resulting in deletion of arbitrary files on the host. The defect is reachable without credentials (PR:N) but requires adjacent/guest-side network access to the forwarder API (AV:A), which is normally bound to the virtual network rather than exposed as a routed internet service; impact is limited to integrity and availability (no data disclosure). No public exploit code has been identified at time of analysis and the flaw is not listed as confirmed actively exploited (CISA KEV); an upstream fix exists in gvisor-tap-vsock PR #718. The vendor score of 9.3 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H) reflects low-complexity, unauthenticated access combined with a scope change and High integrity/availability impact, and the actual risk depends heavily on whether the forwarder control API is reachable by an untrusted guest or adjacent host.
Symlink-following file overwrite on the Ansible control node is possible in ansible-core when a user runs `ansible-galaxy collection install` against a crafted collection tarball, because the archive extractor validates member paths with lexical normalization (os.path.abspath) instead of resolving symlinks (os.path.realpath) and performs no containment check on symlink-typed directory members before creating them, letting chained symlink entries redirect a subsequent file member outside the destination directory. The flaw (CWE-59, CVSS 8.8, vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) is a bypass of the fix for CVE-2020-10691 and requires the victim to actively install the malicious collection, so an attacker can write arbitrary files with the privileges of the ansible-galaxy user and potentially achieve code execution on the control node. No public exploit has been identified at time of analysis and the CVE is not listed in CISA KEV; affected deployments include ansible-core 2.x as shipped in Red Hat Ansible Automation Platform 2 and numerous other Red Hat products, and no patched version is identified in the supplied intelligence, which currently cites only the Red Hat CVE page and Bugzilla 2531646.
Remote code execution via unsafe Python pickle deserialization in the community.general Ansible collection's memcached fact cache plugin gives unauthenticated network-adjacent attackers full control of the Ansible controller. Despite documenting JSON as its storage format, the plugin delegates serialization entirely to python-memcached, which transparently pickles Python objects on write and unpickles them on read - a format that executes arbitrary Python code during deserialization. Because memcached has no native authentication and Ansible fact cache keys are derived from predictable hostnames, any attacker who can write to the target memcached instance can inject a malicious payload that executes when the controller next reads cached facts. No public exploit or CISA KEV entry has been identified at time of analysis.
dnsmasq's DHCPv6 client hostname parser can read one byte past the end of a crafted FQDN option when the server processes a single DHCPv6 packet from an attacker on the same local link. The over-read byte is neither returned to the client nor logged, and no crash or confirmed information disclosure has been demonstrated; the independent assessment scores confidentiality, integrity, and availability impact as none, so real-world risk is low despite the genuine memory-safety defect. No CISA KEV entry or public exploit code was identified at time of analysis.
DHCP lease metadata disclosure in dnsmasq (CVE-2026-93010) occurs when the DHCP leasequery feature has been switched on without an allow-list of permitted query sources, letting any host on the local network pull lease records - assigned IP addresses, MAC addresses, hostnames and related lease metadata. The package is shipped across Red Hat Enterprise Linux 6 through 10 and is bundled into Red Hat OpenShift Container Platform 4, Ceph Storage 9 and OpenStack Platform builds, but the vulnerable feature is off unless an administrator explicitly enables it. Severity is capped at a confidentiality-only leak (CVSS 4.3, adjacent-network attack vector), and no public exploit code or active exploitation has been identified at time of analysis.
TFTP file substitution in dnsmasq allows an attacker on the local network to make a later client receive stale, previously cached transfer data instead of the file it requested; in PXE network-boot deployments this can substitute attacker-chosen boot content for a victim machine, giving both confidentiality and integrity impact. The flaw only exists when dnsmasq is running with its TFTP server feature enabled (a non-default configuration used for network boot), requires adjacent-network access (AV:A) with no authentication (PR:N) and no user interaction (UI:N), but is rated high complexity (AC:H) because the attacker cannot control when another client will request the same file and pick up the cached response. There is no CISA KEV entry and no public exploit code identified at time of analysis, and the vendor-reported CVSS 3.1 score is 6.8, making this a moderate, situational issue rather than an emergency; Red Hat tracks it for remediation within the current monthly cycle.
Denial of service against dnsmasq's TCP DNS service: remote attackers can occupy the entire small fixed pool of TCP child processes by holding idle connections open to port 53, which blocks new TCP DNS queries and any DNSSEC validation that depends on TCP fallback. The flaw is packaged in Red Hat Enterprise Linux 6, 7, 8, 9 and 10 as well as Red Hat OpenShift Container Platform 4, Ceph Storage 9 and OpenStack Platform 13 (Queens) and 18.0, so any of those deployments exposing TCP/53 to untrusted networks is in scope. Impact is confined to availability and is time-bounded rather than permanent - UDP resolution keeps working and occupied slots are released after a fixed lifetime - and no public exploit identified at time of analysis.
dnsmasq builds that include the DNSSEC validator and have validation enabled at runtime can write a few bytes past an internal domain-name buffer when converting names to and from DNS wire format, corrupting adjacent heap metadata. Only deployments where DNSSEC support was compiled in and DNSSEC validation is switched on are exposed; the default dnsmasq build omits DNSSEC entirely, and exploitation further requires an attacker to make the resolver validate a crafted DNSSEC response, for example through a spoofed or attacker-controlled answer for a signed name. Rated CVSS 5.3 (integrity-only, low impact) and no public exploit identified at time of analysis; the priority signal is this_month, not immediate action.
A DNS cache-poisoning flaw in dnsmasq (CWE-345, insufficient verification of data authenticity) lets a malicious or compromised upstream resolver inject cached records for names outside its authoritative zone when dnsmasq follows a CNAME in a response. Only split-DNS deployments that forward specific domains to a designated upstream are realistically exposed, since the attacker must already occupy that trusted upstream position; standard single-forwarder or root-hint setups are far less affected. Impact is integrity-only (attacker-chosen addresses returned to later clients), rated CVSS 6.8 with AC:H, and no public exploit code or KEV entry was identified at time of analysis, so priority follows the vendor's this-month cadence rather than emergency response.
A file descriptor leak in the containers/storage Go library's archive.ApplyLayer and ApplyUncompressedLayer functions causes descriptors to be left open whenever corrupt or malicious image layers or tar streams are unpacked, and repeated processing of such inputs can exhaust the hosting process's file descriptor limit. The weakness is unauthenticated in CVSS terms (PR:N) but local in scope (AV:L) and requires the victim to actually process attacker-influenced layers (UI:R), so an attacker must first get malformed image content in front of a build, pull, or sync loop. Impact is availability-only and confined to the affected process (C:N/I:N/A:L, S:U): no code execution and no data exposure; a single bad input does not cause denial of service, only sustained repetition does. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, and EPSS scoring was not supplied with the source data.
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.
Unconditional TLS certificate validation disabling in the OCAPI modules (ocapi_command, ocapi_info) of the community.general Ansible collection exposes HTTP Basic-Auth credentials to interception and permits response tampering against any managed OCAPI storage or enclosure device. Because the shared request helper disables certificate validation on every call with no parameter to re-enable it, a network-adjacent attacker performing a MITM attack can present any certificate, silently capture credentials, and inject falsified device responses back to the Ansible controller. Red Hat bundles the affected collection in Ceph Storage 5 and 9 and OpenStack Platform 17.1 and 18.0; no public exploit has been identified at time of analysis.