Red Hat
Monthly
Malformed H.266/VVC media processed by GStreamer's gst-plugins-bad parser can trigger an integer overflow in profile, tier, and level parsing that overflows a stack buffer, crashing the application and potentially allowing code execution in its context. The flaw is rated CVSS 7.8 High (AV:L/AC:L/PR:N/UI:R) and affects Red Hat Enterprise Linux 7 through 10 deployments that ship the vulnerable plugin; a victim must open the crafted media, so it is not remotely triggerable without user action. No CISA KEV entry or public exploit is identified in the available data, and an upstream fix is referenced in a GStreamer merge request.
Stack-based buffer overflow in GIMP's PSD plug-in image-resource header loader lets a crafted PSD file crash GIMP and potentially execute arbitrary code with the privileges of the user opening the file. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R) confirms local access and user interaction are required, with no privileges needed, so this is not remote unauthenticated exploitation. No public exploit identified at time of analysis; the 7.8 HIGH score reflects high confidentiality, integrity, and availability impact rather than ease of exploitation.
Unbounded memory growth in the glib-networking TLS 1.3 client-side session cache allows a malicious or compromised server to exhaust client memory by sending excessive session ticket messages, resulting in denial of service. The issue affects glib-networking as tracked in Red Hat Enterprise Linux 6 through 10 when a client negotiates TLS 1.3 and connects to an attacker-controlled or attacker-influenced endpoint. No public exploit code was identified at time of analysis; an upstream fix is available via glib-networking merge request 288, but a released patched version is not independently confirmed.
The openshift-ansible installer container's `run` script fetches remote inventory files and dynamic inventory scripts without any integrity verification, so a remote attacker positioned as a man-in-the-middle - or anyone who has compromised the HTTP server hosting those scripts - can swap in an arbitrary executable that then runs with the installer's UID and full cluster-provisioning privileges, yielding code execution (CWE-494). Unauthenticated remote exploitation is possible (CVSS 3.1 base 7.4 High, AV:N/AC:H/PR:N/UI:N), but the high attack complexity reflects the prerequisite of a MITM position or a pre-compromised script host, and only installs configured to pull these scripts over an unprotected channel during the install run are exposed. No public exploit code or confirmed active exploitation was identified at time of analysis.
Deserialization of untrusted data before authentication in the WildFly IIOP (CORBA) listener, as shipped in Red Hat JBoss EAP 7 and 8, may let a remote attacker who can reach the IIOP port submit crafted serialized objects and have them deserialized ahead of any credential check, potentially leading to code execution or full compromise of confidentiality, integrity and availability. Impact is conditional: the target EJB must expose at least one method taking untyped parameters, and a usable gadget chain must be present on the running classpath. The vendor rates the flaw 7.4 with an AV:L vector while our assessment treats the listener as network-reachable (AV:N/AC:H/PR:N/UI:N), and no public exploit code was identified at time of analysis; priority is this week, not emergency.
Unauthenticated remote code execution is possible in Red Hat JBoss Enterprise Application Platform 7 and 8 when the server runs in -secmgr mode with the openjdk-orb CORBA/IIOP listener exposed on TCP 3528. An attacker who can reach that listener can send a CDR-encoded object whose attacker-supplied codebase URL is honoured by JDKBridge during unmarshalling, causing the server JVM to load and instantiate arbitrary classes from a remote location before EJB security interceptors are evaluated. Exploitation is gated on non-default conditions - the -secmgr startup flag and a network-reachable IIOP/CDR listener - and the sources do not confirm active exploitation (CISA KEV) or verified working exploit code; the decision label is 'this_week', indicating a credible high-severity threat that is not a drop-everything emergency.
ARP/neighbor-table poisoning in the iscsiuio userspace daemon shipped with open-iscsi lets an unauthenticated attacker on the same Layer 2 segment redirect network traffic by sending a single minimal IPv6 Neighbor Advertisement. Affected deployments are those where iscsiuio is actually running for iSCSI hardware offload (typically with supported Broadcom NICs); a default server without iSCSI offload configured is not exposed. The same handler also reads link-layer address options at a fixed offset without confirming the packet carries them, an out-of-bounds read that can leak memory or crash the daemon; no public exploit has been identified at time of analysis.
Heap out-of-bounds read in the iscsiuio DHCPv4 option parser, part of open-iscsi, allows an attacker on the same Layer-2 segment to send a crafted DHCP response that can crash the daemon, corrupt its network configuration, and potentially disclose limited heap data. Deployments at risk are those running iscsiuio for iSCSI offload, notably on Broadcom bnx2/cnic NICs, and using DHCP-driven iSCSI configuration; Red Hat tracks Red Hat Enterprise Linux 6 through 10. No public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV) was provided; the issue is rated moderate priority (this_week).
Goose's optional terminal integration feature captures shell command history and transmits it verbatim, with no redaction, to whichever Large Language Model provider endpoint is configured whenever a query is sent, so any secret typed into the terminal - API tokens, passwords, or environment variables carrying credentials - leaves the local trust boundary. The exposure is a confidentiality-only design flaw (CWE-497) rather than an attacker-triggered exploit: it requires the feature to be enabled and a human to enter the sensitive value (UI:R), and the recipient is the configured provider and its logs rather than an arbitrary remote party. Red Hat tracks the issue against Red Hat Enterprise Linux 9 and 10; no public exploit code has been identified at time of analysis, and the priority label is this_week.
Privilege escalation in the Multicluster Global Hub Operator lets an attacker who already controls the operator or holds its service-account credentials impersonate arbitrary users, groups, and service accounts cluster-wide, then use that identity to obtain full administrative control. The issue is rated CVSS 3.1 7.2 HIGH (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) and stems from an overly permissive RBAC configuration in multicluster-global-hub-operator-bundle. No CISA KEV listing, EPSS score, or public exploit code is present in the supplied data; no public exploit identified at time of analysis.
Server-side request forgery in Kroxylicious's Azure Key Vault KMS provider lets an attacker who can influence wire-deserialized EDEK bytes redirect the proxy's Azure bearer token to a host they control, then replay that token against the real Key Vault to break the record-encryption trust model. The issue affects Red Hat Streams for Apache Kafka 3 deployments only when record encryption is enabled with the Azure Key Vault provider, and the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) reflects the need for low-privileged influence over EDEK input plus a reachable attacker-controlled host. No public exploit code has been identified at time of analysis, and no CISA KEV entry confirms active exploitation.
Authentication bypass in Cruise Control (Red Hat Streams for Apache Kafka 2.x and 3.x) lets adjacent-network attackers reach all 15 administrative REST endpoints without credentials by abusing exact-path Jetty security constraints and servlet path normalization. The CVSS 3.1 score is 8.8 (AV:A/AC:L/PR:N/UI:N), but in AMQ Streams the Strimzi operator NetworkPolicy limits Cruise Control port 9090 to operator pods, so realistic exposure requires that policy to be absent, disabled, or misconfigured. No public exploit was identified at time of analysis.
Cross-tenant privilege escalation in StreamsHub Console for Apache Kafka allows an authenticated Kubernetes tenant that can create or modify Console custom resources to point spec.containers.api.spec.image at an arbitrary container image, which the operator then deploys into a pod running under a ServiceAccount bound by ClusterRoleBinding to cluster-wide Strimzi CRD read access, Kafka/KafkaRebalance patch rights, and cluster-monitoring-view. The attacker-controlled code reads the projected ServiceAccount token and gains read/write control over the Strimzi control plane across tenant boundaries, with high confidentiality and integrity impact (CVSS 9.9, scope changed). Exploitation is gated by the tenant-level RBAC permission rather than being open to the internet, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Credential theft in multi-tenant Red Hat StreamsHub Console for Apache Kafka and Streams for Apache Kafka 2/3 deployments is possible because the operator trusts a namespace field supplied in a Console custom resource. An authenticated tenant with permission to create Console CRs (PR:L) can point spec.kafkaClusters[].credentials.kafkaUser.namespace at a victim namespace, causing the cluster-wide-privileged operator to read that namespace’s KafkaUser Secret-SASL credentials or TLS private keys-and write the plaintext into a Secret in the attacker’s namespace. CVSS 3.1 scores this 7.7 with scope changed and high confidentiality impact; no public exploit identified at time of analysis, so risk is concentrated in multi-tenant clusters where untrusted users can create Console resources.
Ghostscript as shipped with Red Hat Enterprise Linux 8-and, per CPE data, RHEL 6, 7, 9, and 10-may allow an attacker to escape -dSAFER protections when it processes a crafted PostScript file, enabling file access outside permitted paths or command execution with the Ghostscript process's privileges. The root cause is that Red Hat's 9.25-to-9.27 rebase omitted the CVE-2019-14869 correction, leaving privileged .forceput operations in the .charkeys procedure insufficiently protected; the supplied CVSS base score is 7.3, while the independent assessment treats confidentiality and integrity impact as High (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L). No CISA KEV entry is present in the supplied data and no public exploit identified at time of analysis; practical risk is conditional on a service or pipeline actually processing untrusted PostScript/EPS with an affected RHEL build.
Use-after-free in GIMP's XCF loader can crash the application and potentially allow arbitrary code execution when a user opens a crafted .xcf file that selects a path and then fails to load it. The flaw affects GIMP as packaged in Red Hat Enterprise Linux 6 through 10 according to the provided CPE mappings, and exploitation is local and requires user interaction (CVSS 7.8, AV:L/UI:R/PR:N); no public exploit was identified at time of analysis. Because scope is unchanged, any code execution would run with the privileges of the user opening the file rather than automatically gaining root.
Opening a crafted XCF file in GIMP can trigger a use-after-free in the XCF loader's linked-channels handling, crashing the main GIMP process and potentially enabling code execution in the opening user's context. The defect affects GIMP installations that parse XCF files, with Red Hat tracking impact across RHEL 6 through RHEL 10 packages; exploitation requires local delivery and a victim to open the malicious image, and no public exploit code or CISA KEV entry is identified in the provided data.
Heap out-of-bounds read and write in GIMP's PSD thumbnail resource loader allows memory corruption when a victim opens or thumbnail-previews a crafted PSD file containing a grayscale JPEG thumbnail, potentially leading to code execution in the plug-in process. The loader assumes a 3-byte BGR stride and never validates that the embedded thumbnail is RGB, so a single-channel grayscale image drives out-of-bounds indexing. Rated CVSS 7.8 (AV:L/UI:R/PR:N) - a client-side file-parsing bug with no network reachability; no public exploit code identified at time of analysis, and Red Hat tracks it across RHEL 6 through 10.
Heap out-of-bounds read in GIMP's XCF text-layer parasite parsing allows a crafted .xcf file, opened by a victim, to leak adjacent heap memory into layer text and crash the application, causing information disclosure and denial of service. The issue is local and requires user interaction (CVSS 7.1, AV:L/UI:R/PR:N), and the provided intelligence shows no public exploit or CISA KEV entry; it is a moderate-priority issue rather than an urgent remote threat.
Red Hat Advanced Cluster Security for Kubernetes (RHACS) Central's SAML assertion consumer service (ACS) endpoint does not cache used assertion or response identifiers, so a single valid signed SAML response can be replayed to mint multiple distinct Central authentication tokens for the same mapped identity. Deployments are only exposed when Central is configured to authenticate via SAML; an attacker must first obtain a legitimately signed, unexpired SAML response - they cannot forge one - which is why the issue is rated CVSS 7.4 with high attack complexity despite requiring no privileges or user interaction. Successful replay yields full compromise of confidentiality and integrity for the impersonated identity; no public exploit code or confirmed active exploitation was identified at time of analysis, and non-SAML authentication configurations are unaffected.
Signature-verification bypass in bootc and ostree image-mode deployments: a deployment staged while the container signature policy still accepted unsigned content remains bootable after the policy is hardened, because already-staged deployments are finalized on reboot without being revalidated against the current policy. An attacker who can stage a deployment under a permissive policy can therefore get unsigned OS content finalized and booted later, yielding full host compromise (C:H/I:H/A:H); the assessed vector is AV:L/AC:H with operator/local privilege (PR:L) despite the vendor's PR:N rating, and the flaw affects RHEL 8/9/10 image mode, OpenShift Container Platform 4, and Red Hat Hardened Images. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV).
Out-of-bounds heap reads and writes in spice-server's SPICE_MSGC_MIGRATE_DATA handling let an authenticated SPICE client read arbitrary heap memory or corrupt the heap while a VM is undergoing live migration. Consistent with the assessed CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H vector, the attacker must already hold a valid SPICE session and must land the malicious message inside the migration window, so real-world exposure is concentrated in deployments where the SPICE endpoint is reachable by low-privilege or untrusted users. No public exploit code and no CISA KEV entry were identified at time of analysis.
Local privilege escalation in cifs-utils lets an unprivileged local user obtain root on affected hosts by injecting unauthorized options into a privileged CIFS mount. When a root-owned service mounts a Common Internet File System share using a credentials file whose contents the attacker can control or influence - for example a file that is world-writable or lives in an attacker-owned path - cifs-utils assembles those unsanitized values into the mount option string, so the attacker can slip in extra options that bypass permission checks and cause files to be executed with administrative privileges. The flaw is tracked as CWE-88 (argument/option injection) with a CVSS of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); exploitation requires an existing low-privilege local account (authenticated, per PR:L) and a deployment where such a privileged, credentials-file-driven CIFS mount workflow exists, so internet-facing hosts that do not mount attacker-influenced CIFS shares are not at risk. No public exploit code or confirmed active exploitation was identified at time of analysis, and Red Hat has published advisory and Bugzilla tracking pages for RHEL 6 through 10 and OpenShift Container Platform 4.
Kuadrant operator's internal WebAssembly shim can be made to skip Gateway-level authentication and rate-limiting checks in multi-tenant deployments when an authenticated user with Kubernetes/OpenShift RBAC permission to create or modify an HTTPRoute attached to a shared Gateway supplies a crafted path, header, or query match value. The value is not properly escaped during CEL predicate generation, so the predicate can be altered to bypass those policies while the request is still forwarded to the route backend. No public exploit identified at time of analysis, and exploitation is conditional on a shared/multi-tenant Gateway with Gateway-level auth and/or rate limiting configured, making this a genuine but conditional-priority issue rather than a mass-exploitation threat.
Path traversal in wildfly-core's deployment content handler allows an authenticated JBoss EAP, WildFly, Fuse 7, or Single Sign-On 7 user who holds the Deployer RBAC role to escape the restricted deployment directory and create files with attacker-controlled content or delete arbitrary directories on the server, escalating to full management SuperUser privileges. Exploitation requires that the Deployer role be delegated to the attacker (CVSS vector shows PR:L - authenticated, not anonymous) plus a crafted deployment name containing traversal sequences; environments that reserve the Deployer role for fully trusted administrators face little practical exposure. No public exploit code was identified at time of analysis and the flaw is not listed in CISA KEV, so this is a credible, actionable priority rather than an emergency.
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.
Guest-to-host out-of-bounds access in DPDK's vhost-crypto backend lets a low-privileged guest VM that is already attached to a vhost-crypto device corrupt host-side memory by racing the host's two reads of an indirect-descriptor next index, a classic TOCTOU double-fetch (CWE-367). Only hosts running DPDK with lib/vhost's vhost-crypto library enabled and actually processing indirect descriptors are exposed, and the race makes reliable exploitation non-trivial - the assessed vector is AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H, reflecting host-local reach via the guest with cross-boundary (guest-to-host) scope change. Red Hat tracks this for Fast Datapath packages on Red Hat Enterprise Linux 8, 9 and 10; no public exploit code has been identified at time of analysis and there is no CISA KEV entry. Realistic exposure is limited to multi-tenant, untrusted-guest or confidential-computing style deployments where the vhost-crypto feature is deliberately enabled.
A use-after-unmap in DPDK's vhost library gives a local attacker who controls a VDUSE (vDPA Device in USErspace) backend, or a guest able to drive IOTLB invalidations on the vhost device, a path to memory corruption inside the host vhost process. The flaw is that the VDUSE handler does not invalidate cached vring pointers when the IOTLB is invalidated, so the code keeps dereferencing vring addresses that have already been unmapped - a classic CWE-416 use-after-free. The assessed CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, base 8.8) marks this as locally reachable, low-complexity and low-privilege, with a scope change (S:C) reflecting that a confined guest/userspace VDUSE device can compromise the host vhost trust boundary; impact is full confidentiality, integrity and availability loss. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so risk is concentrated in multi-tenant virtualization and NFV hosts that specifically enable DPDK VDUSE. Affected packages are Red Hat's Fast Datapath DPDK channel for RHEL 8, 9 and 10, with downstream exposure noted for RHEL, OpenShift Container Platform 4 and OpenStack Platform 13 Queens.
A double-offset error in DPDK's vhost log-mapping calculation (lib/vhost) lets local attackers with low privileges (PR:L) - including a guest that controls a virtio device serviced by the vulnerable vhost-user backend - trigger incorrect host memory accesses that compromise confidentiality, integrity and availability, giving a 7.8 HIGH rating (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is tracked by Red Hat and ships in Fast Datapath for RHEL 8, 9 and 10, which in turn is consumed by Red Hat Enterprise Linux 8/9/10, OpenShift Container Platform 4 and OpenStack Platform 13 (Queens), so exposure is concentrated in OVS-DPDK accelerated virtualization and NFV hosts that exercise the vhost log-mapping path (for example during guest dirty-page logging/live migration). No public exploit identified at time of analysis, and no CISA KEV listing or exploit code is referenced in the available intelligence.
Heap buffer overflow in DPDK's lib/vhost VDUSE control-queue handler allows a local, low-privileged (authenticated) actor to corrupt heap memory with attacker-controlled content, enabling privilege escalation and loss of host integrity. The root cause is a time-of-check-to-time-of-failure (TOCTOU) double-fetch: the control-queue descriptor is read twice from memory the attacker can modify in between, so the length used for the copy can differ from the length that was validated. Only deployments that actually exercise the VDUSE (vDPA Device in Userspace) control-queue path are exposed, and because winning the race is probabilistic the CVSS base score of 7.8 (AV:L/AC:L/PR:L) is more realistically an AC:H scenario per our assessment; no public exploit code and no confirmed active exploitation were identified at time of analysis. This is a genuine privilege-escalation and host-integrity concern rather than a mass-exploitation threat, since it is strictly local, involves no remote network path, and requires controlling the descriptor memory between fetches.
Privilege escalation in Red Hat OpenShift Container Platform 4's insights-runtime-extractor DaemonSet lets an authenticated low-privileged tenant who can schedule a pod on a node run attacker-controlled code as root in the host user namespace. The extractor scanner enters the workload's namespaces and executes the workload's argv[0] via exec.Command after only seteuid() has changed, leaving real/saved UID 0 and retaining capabilities; a malicious pod binary matching node, python, python3, MainThread, or any path containing java can call setuid(0) and reach the host CRI-O socket from the inherited cwd. CVSS 8.8 (AV:L/PR:L/S:C) reflects local, non-network exploitation requiring workload scheduling, and no public exploit was identified at time of analysis.
Path-restriction bypass in BusyBox httpd's reverse proxy feature allows unauthenticated remote attackers to reach backend paths outside the configured forwarding prefix. When URL-prefix proxying is configured, only the first request on a TCP connection has its path rewritten; a pipelined second request is relayed verbatim, defeating the intended prefix restriction and exposing arbitrary backend routes. Affects BusyBox httpd deployments, including Red Hat Hardened Images, that enable the non-default reverse proxy directive; no public exploit identified at time of analysis. CVSS 3.1 base score 7.2 (High) reflects network reachability, low complexity, no privileges or user interaction, and changed scope impacting the proxied backend.
Arbitrary file write outside the intended extraction directory is possible in BusyBox's dpkg-deb applet because its ar archive handler flushes deferred symlinks after every archive member rather than once after the final member. A crafted .deb containing two data.tar members - the first declaring a symlink to an absolute path such as '/', the second declaring a regular file whose path traverses that now-live link - causes a file to be written at an attacker-chosen location when the package is unpacked (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-59). Affected systems are BusyBox builds compiled with dpkg-deb support, including BusyBox shipped inside Red Hat Hardened Images; the CVSS vector indicates no privileges are required by the attacker (PR:N) but the victim must interact by extracting the untrusted package, and the vector's local attack value plus the non-trivial two-member structure keep this a context-dependent integrity issue rather than a mass-exploitation emergency. No public exploit identified at time of analysis.
Heap-based buffer overflow in GStreamer's gst-plugins-base plugin library lets a local attacker who controls the sending side of a GStreamer inter-process IPC pipeline corrupt memory in the receiving process, yielding a CVSS 3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) with high confidentiality, integrity, and availability impact. The victim process maps a crafted video buffer whose GstVideoMeta declares plane strides and offsets larger than the actual backing allocation, causing out-of-bounds reads and writes that can crash the process or potentially permit code execution in its context. Exploitation is strictly local and requires a deployment where GStreamer buffers cross a trust boundary between a less-trusted producer and a more-trusted consumer; no user interaction or authentication to the victim is needed, and no public exploit has been identified at time of analysis.
Denial of service in GNOME Remote Desktop (gnome-remote-desktop) as shipped in Red Hat Enterprise Linux 8, 9, and 10 allows an unauthenticated remote attacker to pin the daemon's event-loop thread at high CPU by sending traffic to a TLS-enabled VNC listener, causing the service to stop making forward progress. The defect is in the VNC TLS I/O handlers, which treat retryable GnuTLS results (GNUTLS_E_AGAIN and GNUTLS_E_INTERRUPTED) with an unbounded busy loop instead of returning control to the event loop, so the thread spins indefinitely rather than waiting for socket readiness. No public exploit code exists and there is no confirmed active exploitation, and practical exposure is bounded: the VNC backend must be running with a TLS listener reachable over the network, a configuration that is not enabled by default on typical RHEL installs and is far more common on desktops than on servers.
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 attackers can bypass security controls on REST endpoints generated by Quarkus REST Data Panache when a developer uses @MethodProperties to customize an operation without re-declaring class-level security roles, causing the generator to silently drop the security requirement and expose the endpoint. This results in potential unauthorized information disclosure or data modification, with a CVSS 3.1 score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) and CWE-425. No public exploit code has been identified at the time of analysis.
Authenticated users of the Red Hat OpenShift web console can abuse the Helm chart URL input to make the console pod issue requests to arbitrary destinations, turning the console into a Server-Side Request Forgery (SSRF) proxy (CWE-918, CVSS 3.1 base 7.7). Because the console pod typically sits inside the cluster network with broader reachability than the user, a low-privileged console account with the ability to add or load a Helm chart can use leaked error output to read sensitive responses and can perform blind port scanning against internal services. Exploitation requires an authenticated console session and the privilege to supply a chart repository URL (PR:L, unauthenticated outsiders cannot reach it), and the assessed impact is confidentiality-only with no integrity or availability effect; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV).
Use-after-free in GNOME Mutter's Wayland color-management (wp_image_description_v1) path allows a local, authenticated attacker who can run a malicious Wayland client to destroy the image-description resource while an asynchronous ICC file read is still in flight, after which the compositor writes into freed memory and frees a pointer derived from it - typically crashing the GNOME session and potentially enabling code execution inside the compositor process. The flaw is local-only and timing-dependent (it requires winning a race window), only applies to Wayland sessions where the color-management/ICC path is exposed (not X11-only sessions or builds without that code path), and no public exploit code or CISA KEV entry has been identified at time of analysis; in practice the more likely outcome is a session crash rather than reliable code execution. This is a credible local privilege/code-execution risk but not an urgent internet-facing emergency.
Remote code execution in ManageIQ (and its downstream Red Hat CloudForms) is possible because the YamlLoadAliases module overrides YAML.safe_load so that in production a Psych::DisallowedClass error silently falls back to YAML.unsafe_load, deserializing arbitrary Ruby objects. An authenticated attacker holding dialog import privileges (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) can upload a crafted YAML dialog payload containing a disallowed class to trigger an unsafe deserialization path with full confidentiality, integrity, and availability impact. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, but Red Hat CloudForms has reached End of Life and no errata will be issued, so CloudForms operators cannot patch and must depend on restricting the dialog import role.
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.
Red Hat OpenShift Container Platform 4 ships by default with an insights-operator-gather ClusterRole that grants the operator's 'gather' service account cluster-wide get/list access to core-group secrets, with no namespace or resourceNames scoping. An authenticated actor who can create or influence a pod specification in any namespace - and set 'serviceAccountName: gather' on it - can mount that service account and read every secret in every namespace, making this a privilege-escalation and cluster-wide credential-disclosure primitive (CWE-269, CVSS 7.7, scope-changed confidentiality-only). Exploitation requires a pre-existing foothold with pod-create or service-account-binding rights (PR:L), so it is not remotely exploitable by an unauthenticated user; no public exploit code has been identified at time of analysis, and the over-broad grant exists out of the box rather than behind a non-default feature flag.
Cyrus SASL clients that use the DIGEST-MD5 authentication mechanism can be crashed by a malicious or on-path server that supplies a crafted challenge field (such as realm or nonce), because the add_to_challenge() function computes a buffer size before DIGEST-MD5 quoting and fails to account for escaping that lengthens the value, resulting in a heap-based out-of-bounds write. This is a client-side denial-of-service flaw affecting Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4; the assessed CVSS vector is AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:H, meaning unauthenticated remote attackers must control or intercept the server endpoint and the victim must initiate authentication. No public exploit code or confirmed active exploitation is identified at time of analysis.
Candlepin, the entitlement and subscription management engine behind Red Hat Satellite 6, contains an authorization-logic flaw in its central access control filter: when an API operation verifies multiple @Verify-annotated parameters, access is granted if any one of them is permitted rather than requiring permission on all of them. An authenticated attacker with a low-privilege account who legitimately can reach the first referenced object can therefore pass authorization checks on later parameters and, provided they know the victim resource identifiers, read consumer information or modify entitlements and subscription resources - including objects belonging to other organizations (CVSS 3.1: 8.1, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). Exploitation requires a valid account and prior knowledge of target consumer UUIDs, entitlement IDs, or subscription resource IDs, and is limited to endpoints that evaluate more than one verified parameter; no public exploit code was identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV).
Heap-based buffer overflow in GIMP's DirectDraw Surface (DDS) loader allows attackers to corrupt memory and potentially execute arbitrary code by convincing a user to open a crafted .dds image. The flaw affects GIMP as shipped in Red Hat Enterprise Linux 6, 7, 8, 9, and 10, and requires local file access plus user interaction (opening the malicious file) with no authentication required per the CVSS vector (PR:N). No public exploit code has been identified at time of analysis, and exploitation is limited to the privileges of the user running GIMP.
Ghostscript can execute arbitrary shell commands with the privileges of its process when it renders a crafted PostScript or EPS document, chaining memory corruption in document parsing with a runtime bypass of the -dSAFER sandbox. The flaw affects Ghostscript as shipped in Red Hat Enterprise Linux 6, 7, 8, 9, and 10, and the assessed vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, meaning no privileges are required but a victim or automated pipeline must render the malicious file, with the malicious document first reaching the processing system. Publicly available exploit code exists, including a GitHub proof-of-concept, but the provided data does not confirm CISA KEV active exploitation, so -dSAFER should not be treated as a protective mitigation for affected versions.
Unauthenticated Go pprof debug endpoints exposed on the postgres-exporter metrics listener let any attacker who can reach that port from inside the cluster network read process arguments, full goroutine stacks, and heap memory - potentially leaking database connection strings and credentials - and repeatedly trigger CPU profiling to exhaust resources in a denial-of-service condition. The flaw is tracked as CVE-2026-83550 (CVSS 7.1, AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H per the vendor, C:H for confidentiality in our assessment) and affects postgres-exporter as shipped in Red Hat Multicluster Global Hub, where the CPE covers all tracked versions; exploitation requires adjacent/cluster network reachability rather than internet exposure. No public exploit code has been identified at time of analysis, and no CISA KEV listing indicates active exploitation; risk is best characterized as a real design flaw of moderate priority, with exposure materially reducible through NetworkPolicies that restrict access to the metrics port.
Arbitrary code execution in the control plane of Red Hat Multicluster Engine for Kubernetes (HyperShift operator) is possible when an authenticated user with cluster and secret creation permissions supplies a kubeconfig secret containing unauthorized executable credential plugins, which the operator copies without validation into the privileged control plane namespace. Downstream controllers that consume this configuration execute the plugins, granting full control plane compromise. The vulnerability requires low privileges (PR:L) and no user interaction, and no public exploit or CISA KEV entry is identified at time of analysis.
Dogtag PKI (pki-core) and its commercial counterpart, Red Hat Certificate System 9/10/11, contain a fail-open authentication flaw in the CMCAuthForEST plugin that lets an authenticated, low-privileged EST enrollment user obtain CA-signed certificates bearing arbitrary subject names. The bug is triggered when an EST fullcmc enrollment request is sent over BasicAuth without an end-user TLS client certificate; the SSL_CLIENT_CERT session attribute then retains the EST subsystem's agent certificate, so downstream authorization logic wrongly grants agent-level privileges. Exploitation is assessed as requiring only a valid EST user account (CVSS 8.1, PR:L, unauthenticated by client certificate, no user interaction), making it a realistic privilege-escalation path for any provisioned EST user or insider; however, no public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (not in CISA KEV).
StartTLS handling in 389-ds-base does not discard plaintext bytes buffered before the TLS upgrade, allowing an on-path attacker to inject a crafted LDAP message whose messageID collides with a client's pending bind and causes the client to treat a failed authentication as successful. Red Hat Directory Server 11, 12, and 13 and Red Hat Enterprise Linux 6, 7, 8, 9, and 10 deployments using 389-ds-base with StartTLS are affected. Exploitation requires an on-path network position and timing control during StartTLS negotiation, so the real-world bar is higher than the reported 9.0 base score; no public exploit identified at time of analysis.
Denial of service in 389-ds-base (the LDAP engine shipped with Red Hat Directory Server 11/12/13 and Red Hat Enterprise Linux 6 through 10) lets an unauthenticated remote attacker stall the server's worker-thread pool by sending a complete LDAP operation followed by the opening bytes of an incomplete LDAPMessage on the same connection. The server then hands the connection to a second worker thread before the first worker's result is flushed; the second worker blocks on the connection mutex until nsslapd-ioblocktimeout, so the finished operation's response is never delivered. Repeating this over a handful of connections proportional to the configured worker-thread count exhausts the entire pool under default configuration, denying LDAP service to anonymous and authenticated clients over both plaintext and TLS for as long as the attacker holds the connections; no public exploit code has been identified at time of analysis, and no EPSS or KEV signal accompanies the CVE, though the availability-only impact (CVSS 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) is genuine for any internet- or broad-network-reachable directory server.
OS command injection in the Foreman foreman-tail helper utility shipped with Red Hat Satellite 6.19 for RHEL 9 allows a local, authenticated user to execute arbitrary system commands with the privileges of whoever runs the tool, because unsanitized arguments are fed into an eval-based path-expansion string and shell metacharacters such as ;, & and | are interpreted as commands. The flaw is rated 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and is strictly local-scope, so it only matters where a lower-privileged account on a Satellite/Foreman host can reach the utility and thereby escalate its privileges. There is no network-facing attack path, no public exploit code has been identified at time of analysis, and EPSS is low (0.55%, 44th percentile), though Red Hat has issued patched packages (for example 0:3.18.0.14-1.el9sat for Satellite 6.19 on RHEL 9) via several RHSA advisories.
Remote code execution in Foreman's safemode-protected templating engine, shipped in Red Hat Satellite 6.19 for RHEL 9, lets an authenticated user with only low-level template privileges escape the sandbox and execute arbitrary commands on the Satellite server. The flaw stems from improper handling of delegated methods, which allows an attacker to append unauthorized functions to the sandbox's allowed-execution list; no user interaction is required beyond rendering or creating a template, and the Satellite web UI is network-reachable by default. Vendor patches are available via Red Hat errata, EPSS is modest (0.66%, ~50th percentile), and no public exploit code or confirmed active exploitation was identified at time of analysis (SSVC exploitation: none, not automatable).
Authenticated users with low-level Viewer permissions in Red Hat Satellite 6.19 (and upstream Foreman) can exploit template preview endpoints to disclose sensitive data, including host root passwords. In non-default configurations where Safemode protections are disabled, the flaw can escalate to arbitrary command execution as the Foreman system account. No public exploit code or active exploitation has been identified at time of analysis; the CVSS score of 9.1 reflects high confidentiality impact, though the RCE component requires an insecure configuration.
Privileged local attackers who can control Foreman configuration data can chain server-side template injection with insecure deserialization through the foreman-rake initialization logic in /usr/share/foreman/config/settings.rb to execute arbitrary code on Red Hat Satellite 6.19 for RHEL 9 hosts, resulting in full host compromise and downstream supply chain risk. The assessed CVSS 3.1 vector (7.7, AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H) confirms the attack is local and authenticated with high privileges plus a user-interaction component, so it is not remotely or unauthenticated reachable against a default deployment and real exposure is largely confined to compromised or malicious privileged operators. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; Red Hat has published errata RHSA-2026:74503 addressing it.
OS command injection in Foreman's foreman-rake db:dump and db:import_dump tasks lets an attacker who already holds permission to execute those rake tasks - for example through a restricted sudo delegation - append arbitrary shell commands to the destination (backup) or file (import) parameter, achieving command execution with the privileges of the rake process and scoring CVSS 8.2 (AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H). The bug affects Foreman as shipped in Red Hat Satellite 6.19 for RHEL 9 and the broader Red Hat Satellite 6 line, and is tracked under CVE-2026-12541. This is a genuine but access-gated privilege-escalation risk rather than a mass-exploitable remote threat: it is local-only, demands pre-existing delegated or privileged access to the rake tasks, and environments where only root invokes foreman-rake with no restricted sudo delegation are effectively not exposed; no public exploit code has been identified at time of analysis.
Command injection in the Foreman foreman-rake errors:fetch_log task shipped with Red Hat Satellite 6 allows a local user who already holds a sudo grant for that specific rake task to break out of the intended grep invocation and run arbitrary commands with the privileges of the task. The request_id parameter reaches the underlying shell command without adequate metacharacter neutralization, so an attacker can inject ';', '"', or '|' and achieve command execution on the Satellite/Foreman host. The CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) confirms this is a local, high-privilege-context privilege escalation rather than a remotely reachable flaw, and no public exploit code or CISA KEV entry was identified at time of analysis.
Unauthenticated remote attackers can pull the kickstart provisioning template from Red Hat Satellite 6's /unattended/provision endpoint without supplying any token, provided a host is currently mid-provisioning and therefore has an unexpired token recorded in the Satellite database. The flaw is a semantic logic error in Foreman's host_verifier.rb: valid_host_token? validates database state rather than the token presented in the HTTP request, so the check passes even when the request carries no token. Rated CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N), the exposure is gated by the provisioning window and yields information disclosure of the rendered template, not code execution; no public exploit code or active exploitation has been identified at time of analysis.
Command injection in the Red Hat Satellite job invocation API (/api/v2/job_invocations), shipped via the rubygem-foreman_remote_execution plugin, lets an authenticated Satellite user who holds job-template execution permissions run arbitrary shell commands on managed hosts. The injection only applies to job templates whose effective_user property is configured as overridable: true, in which case the user-supplied value is not sanitized before the Satellite server instantiates the job execution environment, so the payload executes during instantiation rather than through the template or playbook content itself. Rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-78), this requires an authenticated account (PR:L) and the non-default overridable setting, and no public exploit identified at time of analysis; Red Hat has published an erratum, RHSA-2026:74503.
Unauthenticated container image tampering in oc-mirror, the mirroring utility shipped with Red Hat OpenShift Container Platform 4 and the Assisted Installer for Red Hat OpenShift Container Platform 2, lets any host on the same adjacent network segment push attacker-controlled images, delete cached images, or read mirrored content while a mirroring operation is running. The embedded local cache registry binds to all network interfaces (0.0.0.0) with neither authentication nor TLS, matching CWE-306, and carries a CVSS 3.1 score of 7.1 (AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N). No public exploit code has been identified at time of analysis, and the exposure window is transient because the vulnerable registry only exists during an active mirroring run.
Arbitrary file write in oc-mirror allows an attacker who controls or tampers with an operator catalog image to write files outside the intended extraction directory when a user mirrors that catalog using the legacy v1 path (--v1) or the OCI feature path (--use-oci-feature). The issue is a path traversal (CWE-22) in tar entry extraction, assessed as local (AV:L), no privileges required (PR:N), but requiring user interaction (UI:R) because an administrator must run the mirror command; impact is high integrity and low availability, with no confidentiality impact per the independent assessment. No public exploit or active exploitation is identified at time of analysis, and the independent assessment characterizes this as a moderate, defender-actionable issue rather than an urgent internet-facing emergency.
Heap-based buffer overflow in RPM's package-header parsing lets a crafted, unsigned RPM overwrite memory when a victim merely inspects it with rpm2cpio, rpm2archive, or 'rpm -qlvp', giving an attacker-controlled heap write past a one-byte allocation (CWE-122, assessed CVSS 3.1 7.1). Affected code ships with RPM as distributed in Red Hat Enterprise Linux 6, 7, 8, 9, and 10 as well as Red Hat Hardened Images, so build farms, CI pipelines, package mirrors, and malware-analysis hosts that routinely open untrusted packages are the realistic exposure surface. Exploitation is local (AV:L), low complexity (AC:L), and unauthenticated (PR:N) but requires user interaction (UI:R) to invoke an rpm tool against the malicious file; signature verification is no barrier because the overflow happens during header decoding. No public exploit identified at time of analysis.
Container escape in CRI-O - the OCI runtime that underpins Red Hat OpenShift Container Platform 4 - is achievable when a workload-level actor can create or influence pod metadata that overwrites CRI-O's own reserved sandbox bookkeeping; the poisoned state is then reloaded as trusted after a CRI-O daemon restart, and a subsequent container recreate inside that sandbox can expose a host-side runtime-management resource to the container. Rated CVSS 3.1 7.8 (AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H), the flaw is not remotely reachable without cluster workload access, and the mandatory restart-then-recreate sequencing is the principal limiter on realistic exploitation. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing); no EPSS score was supplied in the available intelligence.
A heap buffer overflow exists in libsoup's WebSocket permessage-deflate compression path: when a very large outbound message is compressed, truncated size calculations used to grow a GByteArray wrap, allowing zlib to write beyond the allocated buffer. The affected code is the outbound compression routine reached through the permessage-deflate extension (RFC 7692), so exploitation requires that the extension be negotiated on the WebSocket connection and that the endpoint emit a message large enough to cross the integer-truncation boundary - a precondition that materially narrows exploitation below the raw 9.8 base score. The CVSS vector indicates no privileges (PR:N) or user interaction (UI:N) are required, but no public exploit code has been identified and there is no confirmation of active exploitation (SSVC exploitation: none, no CISA KEV entry); EPSS is low at 0.30% (20th percentile), and Red Hat has published errata (RHSA-2026:83384, RHSA-2026:83618) addressing the flaw.
Heap memory corruption in libsoup can be triggered when a WebSocket client using libsoup constructs a masked outgoing frame for an extremely large payload near the 32-bit guint limit, truncating the GByteArray allocation size while the masking routine processes the full length. It affects libsoup as shipped in Red Hat Enterprise Linux 6 through 10. The assessed CVSS vector is network-reachable but high-complexity (AV:N/AC:H/PR:N/UI:N), and no public exploit identified at time of analysis.
Heap out-of-bounds read in libsoup's WebSocket implementation allows a remote, unauthenticated peer to trigger a heap buffer overflow when the application has configured max-incoming-payload-size to unlimited (0), a non-default setting; with the standard payload cap the overflow cannot be reached. The CVSS 3.1 base score is 8.6 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H), but our assessed vector raises complexity to AC:H because exploitation requires both the non-default unlimited setting and a frame large enough to wrap the GByteArray length counter, implying a very large transfer. No public exploit code or active exploitation has been identified at time of analysis.
Out-of-bounds read and application crash in libsoup's soup_uri_decode_data_uri() affect applications that pass attacker-controlled base64 data: URIs to the GLib-based HTTP library, with Red Hat shipping vulnerable packages across Red Hat Enterprise Linux 6, 7, 8, 9 and 10. A crafted data URI whose percent-decoded payload contains embedded NUL bytes causes the decoded length to remain uninitialized and be used as the size of the returned GBytes, yielding a minor confidentiality leak (C:L) alongside a serious availability impact (A:H) rated 8.2 under CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H. The issue is remotely triggerable without authentication (PR:N) and no public exploit code has been identified at time of analysis, though real-world exposure is limited to software that actually processes untrusted data: URIs (WebKit/GTK browsers, feed and mail readers, and other GNOME applications rendering remote content).
Heap corruption and denial of service in libsoup stem from unbounded WebSocket message reassembly: the code accumulates fragmented frames in a GByteArray without checking the total reassembled size against the buffer type's size limit, so an oversized message can truncate the tracked length while the implementation continues to use the full length, producing out-of-bounds memory access (CWE-125) and possible crashes. The flaw is reachable by unauthenticated remote peers that can establish a WebSocket connection with a libsoup-based server, or by a libsoup client that connects to an attacker-controlled or man-in-the-middle server, but the assessed vector (AC:H) reflects that the attacker must drive reassembly to the underlying ~4 GB buffer-type boundary, so ordinary small-message WebSocket traffic does not trigger it. No public exploit code or CISA KEV active-exploitation confirmation was identified at time of analysis.
A type-confusion memory-safety flaw in libsoup's WebSocket handling can crash or corrupt the heap of applications that process incoming Pong frames. When a Pong frame arrives, SoupWebsocketConnection emits its ::pong signal with a GByteArray pointer even though the signal is declared to pass a GBytes object, so any application that connects a ::pong handler written to the documented GBytes API will misinterpret the payload and may suffer heap corruption or a crash. This is not exploitable against default libsoup usage: the target must both act as a WebSocket peer and explicitly register a ::pong handler, and the attacker must control or compromise the WebSocket endpoint (or otherwise inject a crafted Pong frame) into that connection. The recorded CVSS 3.1 base score is 8.6, but the independent assessment rates it AC:H with C:L/I:L/A:H because exploitation is gated on that non-default handler registration; unauthenticated remote attackers (PR:N, UI:N) can reach the code path, however no public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited.
Heap-based out-of-bounds write in the RPM Package Manager (rpm) affects Red Hat Enterprise Linux 6 through 10 and Red Hat Hardened Images, allowing a local, unauthenticated attacker to corrupt memory by crafting an RPM package that is then parsed with rpm2cpio, rpm2archive, or rpm -qlvp. The flaw arises from an integer overflow in iterReadArchiveNext() when a symlink entry declares RPMTAG_LONGFILESIZES as 0xFFFFFFFFFFFFFFFF, shrinking the buffer allocation to one byte and enabling attacker-controlled data from the cpio filesize field to overwrite heap memory. Exploitation requires user interaction to inspect the malicious package and no public exploit code has been identified at time of analysis; the CVSS 3.1 base score is 7.1.
Arbitrary code execution on an operator's workstation is achievable through kube-compare when it processes a 'container://' reference path pointing at an untrusted container image, because the tool launches that image's entrypoint instead of only reading data out of a stopped container. Exploitation is locally scoped and gated: per the assessed vector CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, an unauthenticated (PR:N) attacker must convince the operator to invoke the tool against the malicious reference (UI:R), so the victim's own action is the trigger. This is a genuine but conditionally-gated risk - escalation to full root-mediated impact occurs only where the local Docker daemon runs with elevated privileges - and no public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis; EPSS data was not supplied. The tool is distributed in Red Hat OpenShift Container Platform 4 and the 'Pen Drive Powered by Red Hat Lightspeed' offering.
Authenticated federation peers can cause denial of service and broker state manipulation in Apache ActiveMQ Artemis before 2.34.0 by sending a crafted FEDERATION_DOWNSTREAM_CONNECT packet that forces the broker to load and instantiate arbitrary classes visible to the Artemis module classloader. The vulnerability arises from unsafe reflection (CWE-470) in FederationStreamConnectMessage.getFederationPolicy(), which passes an unvalidated class name from the CORE protocol wire buffer to Class.forName(). Although the original CVSS 3.1 vector reports PR:N (8.2 High), the described authentication requirement means the practical severity is lower; the authoritative assessment uses PR:L. No public exploit code has been identified at time of analysis.
Command injection in NooBaa's cluster_internal_api (set_hostname_internal function) allows an authenticated attacker holding NooBaa administrative privileges on a Red Hat OpenShift Data Foundation 4 Multi-Cloud Object Gateway to execute arbitrary shell commands in the context of the NooBaa process by supplying a hostname value containing shell metacharacters. The flaw carries a CVSS 3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), and the high-privilege prerequisite means it is not reachable by unauthenticated users; realized impact is bounded by the privileges of the NooBaa pod rather than guaranteed node-level root. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
A use-after-free race condition in QEMU's 9pfs (virtfs) passthrough subsystem allows a malicious guest user to escape the shared directory boundary and read or write arbitrary files on the host, potentially achieving code execution as the QEMU process user (VM escape). Only hosts that have enabled 9pfs/virtfs host-directory sharing are exposed, since this is not a default configuration; the attacker must be a local guest user able to issue 9p protocol requests and must win a race between QEMU's main thread and a 9pfs worker thread with concurrent Tlcreate and Twalk requests. No public exploit code or active exploitation telemetry was identified at time of analysis, but the flaw is rated high severity (CVSS 8.8, scope-changed, C:H/I:H/A:H) and affects QEMU packages shipped in Red Hat Enterprise Linux 6 through 10, Red Hat OpenShift Container Platform 4, and related Red Hat products.
Path traversal in the pulpcore content upload API allows an authenticated user holding only low-privilege file-repository permissions to read arbitrary files accessible to the Pulp server process by submitting a crafted 'file:' URL through the 'file_url' parameter, which is dispatched to the file downloader despite an intended scheme check. Baseline impact is confidentiality loss on the Pulp host; in deployments that include Pulp Container the same flaw escalates to theft of the container registry token signing private key, enabling forged bearer tokens and unauthorized access to every private container repository in the registry. Downstream products embedding pulpcore are affected, including Red Hat Satellite 6, Red Hat Ansible Automation Platform 2, and Red Hat Update Infrastructure 4/5. There is no public exploit identified at time of analysis, and EPSS data was not provided; Red Hat tracks the issue under advisory https://access.redhat.com/security/cve/CVE-2026-90959.
Command injection in rpm enables an attacker to run arbitrary shell commands as the invoking user when a victim installs, rebuilds, or otherwise processes a malicious source RPM (.src.rpm) that contains a %() macro construct in a source or spec file basename. The flaw is local and requires user interaction, with impact confined to the privileges of the user running rpm or rpmbuild, typically non-root; build farms and CI/CD pipelines that automatically handle untrusted SRPMs are the highest-risk targets. Red Hat CPEs list RHEL 6 through 10 and Red Hat Hardened Images, and no public exploit was identified in the provided intelligence; monitor the vendor advisory for exploitation and patch updates.
Local attackers can achieve arbitrary code execution by tricking a user or automation into processing a crafted manifest file with 'rpm -q -p', due to unexpected macro expansion of manifest entries in RPM before they are opened. This command injection flaw (CWE-78) affects Red Hat Enterprise Linux 6 through 10 and Red Hat Hardened Images, with a CVSS 3.1 base score of 7.8 (HIGH, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H); exploitation requires user interaction but no privileges, and impact is limited to the privileges of the rpm process. No public exploit code or active exploitation has been identified at time of analysis.
An out-of-bounds write in GIMP's GIMPressionist plug-in allows an attacker to corrupt memory by convincing a user to load a malicious preset file, potentially leading to a crash or arbitrary code execution. The flaw is an unauthenticated local attack (CVSS PR:N) that requires user interaction (UI:R) to open a crafted preset file, and it affects GIMP as packaged in Red Hat Enterprise Linux 6 through 10 plus likely upstream GIMP versions. No public exploit has been identified at time of analysis, and the overall risk is assessed as genuine but not urgent due to the requirement for user interaction with a crafted file.
Unauthenticated path traversal in the OpenShift console's /locales/resource.json endpoint allows remote attackers to read arbitrary *.json files from the console pod filesystem by manipulating the lng and ns query parameters, exposing plugin manifests and configuration files, and potentially enabling traversal against registered dynamic-plugin backends. The flaw is unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 7.5) and affects Red Hat OpenShift Container Platform 4; no public exploit code has been identified at time of analysis and there is no CISA KEV telemetry, but per the independent assessment this remains a credible remote-attack priority because the endpoint is reachable without credentials and yields high-confidentiality reads. Impact is limited to information disclosure - integrity and availability are not affected per the assessed vector.
Improper authentication in the OpenShift Console's CatalogdHandler allows unauthenticated remote attackers to forward the openshift-session-token cookie and send requests to the in-cluster catalogd service, disclosing the internal operator-catalog index and providing a relay into the openshift-catalogd namespace (CVE-2026-75886, CVSS 7.2). This affects Red Hat OpenShift Container Platform 4. No public exploit identified at time of analysis; exploitation requires network reachability to the exposed console endpoint.
Use-after-free in librsvg during rendering of crafted SVG documents with nested XInclude directives and duplicate entity declarations allows unauthenticated local attackers to crash or potentially execute code in applications that use the library. Tracked as CVE-2026-96889 and reported by Red Hat, the flaw affects librsvg as shipped in Red Hat Enterprise Linux 6, 7, 8, 9, and 10. Exploitation requires user interaction (UI:R) because a victim must open, preview, or thumbnail a malicious SVG; the CVSS 3.1 score is 7.8. No public exploit code was identified at time of analysis, and independent assessment indicates that arbitrary code execution is unproven-only denial of service or crash is reliably reachable.
Command injection in the automation controller's external logging (rsyslog) configuration of Red Hat Ansible Automation Platform 2 allows a superuser to achieve arbitrary command execution inside the control-plane rsyslog component, exposing the controller SECRET_KEY and database credentials and enabling decryption of all stored credentials. Exploitation requires authenticated superuser privileges (CVSS 3.1 7.2, PR:H, no user interaction) and only takes effect when external logging is in use, so the malicious RainerScript configuration is actually generated and loaded. No public exploit code was identified and there is no CISA KEV listing indicating active exploitation, meaning real-world risk is strongly gated by the elevated privilege requirement even though the post-exploitation impact is a full control-plane compromise.
Missing authorization checks in the Red Hat Ansible Automation Platform 2 automation-controller allow an authenticated organization workflow-admin - a delegated, non-superuser role - to escalate into the control plane by copying a WorkflowJobTemplate and then launching jobs pinned to instance groups they hold no use_role on. The deep-copy permission sanitizer re-validates only the inventory, unified_job_template, and credentials of each cloned node, silently carrying over instance_groups, execution_environment, and labels, so the copier becomes administrator of a workflow that executes attacker-influenced automation in the control-plane execution context (CVSS 9.9, scope changed, high confidentiality, integrity, and availability impact). Exploitation is confirmed to require only a normal multi-tenant deployment plus workflow-admin rights; no public exploit code has been identified at time of analysis and there is no CISA KEV entry, and no vendor-released patch version was confirmed in the available intelligence.
Authenticated but low-privileged users of Red Hat Ansible Automation Platform 2 can bypass the automation-controller's sanitize_jinja() input-validation guard and have ansible-core evaluate attacker-supplied Jinja inside the execution environment, yielding arbitrary command execution and disclosure of secrets belonging to credentials the attacker cannot normally read. The flaw is exploitable remotely with no user interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N per independent assessment) and requires only a controller account able to set one of the affected launch-time fields. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV; priority is bounded by the required authenticated foothold and the niche deployment footprint.
Remote code execution in Red Hat Ansible Automation Platform 2's automation-controller is possible when a privileged, authenticated user (CVSS PR:H) defines a custom Credential Type and abuses its environment-variable injector to set a process-hijacking loader variable such as BASH_ENV, ENV, LD_PRELOAD, LD_LIBRARY_PATH, PYTHONSTARTUP, or GIT_SSH_COMMAND, which the existing ANSIBLE_* prefix check and fixed ENV_BLOCKLIST fail to catch. Paired with the credential file injector, the attacker plants a script in the execution environment and points the loader variable at it, so arbitrary code executes inside the execution-environment container for any job that later attaches a credential of that type; this requires both the high privilege to author the credential type and a subsequent job consuming it. Red Hat's published CVSS of 7.6 (C:L/I:H/A:N) is lower than our independent assessment of the full vector (C:H/I:H/A:H), and because the vulnerable controller and the impacted execution-environment container are different security scopes, S:C applies. There is no CISA KEV listing and no public exploit identified at time of analysis.
Privilege escalation in Red Hat Ansible Automation Platform 2 (built on the AWX upstream project) lets an authenticated AAP platform administrator escape the container-group sandbox and obtain OpenShift namespace-level access, including the ability to read and exfiltrate namespace secrets. The flaw is reachable over the network (AV:N) with no user interaction (UI:N) and changes scope across the container/namespace boundary (S:C), but it is gated on the highest AAP privilege tier (PR:H), so it is an insider or compromised-admin scenario rather than an unauthenticated attack; only deployments that use container groups backed by OpenShift/Kubernetes are exposed. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); no vendor-released patch has been identified at time of analysis, so mitigation depends on restricting the vulnerable field or the administrators who can reach it.
An authenticated automation-controller administrator in Red Hat Ansible Automation Platform 2 can turn the administrator-controlled format template for API 4XX log messages into a secret-reading primitive, using Python string-format traversal to walk from the interpolated user object into Django settings and pull out the SECRET_KEY and the database password. Because the log destination (external aggregator) is also administrator-controlled, the formatted message - and therefore the secrets - can be shipped off the host, giving the administrator the master key protecting all stored credentials, the ability to forge signed user sessions, and direct database access; the assessed vector is CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N (8.7) with high confidentiality and integrity impact and scope change, since secrets leave the controller's security boundary. No public exploit code has been identified at time of analysis and there is no CISA KEV entry, so this is a high-priority hardening issue rather than an actively exploited one: the practical risk is driven by the very high value of the assets reachable once a privileged administrator account or the log pipeline is compromised.
Stored cross-site scripting in the automation-controller component of Red Hat Ansible Automation Platform 2 lets an authenticated low-privileged user embed a javascript: hyperlink into job, ad hoc command, project update, or inventory update standard output, which is then rendered as a text/html link in the controller's stdout view. Because the HTML conversion escapes HTML metacharacters but never strips ANSI terminal escape sequences, an OSC 8 hyperlink becomes an unfiltered HTML anchor, and the response carries no Content-Security-Policy; a higher-privileged user (for example an administrator) who views that output page and clicks the link executes attacker-controlled JavaScript in their authenticated session, allowing actions up to full platform takeover. The vector is network-reachable with low privileges (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N, 8.7), but exploitation hinges on a privileged victim actively clicking the crafted link; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Stored password survey answers in Red Hat Ansible Automation Platform 2's automation-controller can be recovered in plaintext by an authenticated user holding the delegated JobTemplate Admin role. The attacker tightens the minimum/maximum length constraint on a password-type survey question, then forces revalidation of a schedule or workflow job template node created by a higher-privileged user, causing the controller to decrypt the stored secret and embed it in the HTTP length-validation error response. No public exploit identified at time of analysis; exploitation is not unauthenticated (CVSS PR:L) and requires both the delegated role and an existing password-type survey value, making this a lateral, privilege-crossing credential-disclosure issue rather than a mass-exploitable perimeter break.
Malformed H.266/VVC media processed by GStreamer's gst-plugins-bad parser can trigger an integer overflow in profile, tier, and level parsing that overflows a stack buffer, crashing the application and potentially allowing code execution in its context. The flaw is rated CVSS 7.8 High (AV:L/AC:L/PR:N/UI:R) and affects Red Hat Enterprise Linux 7 through 10 deployments that ship the vulnerable plugin; a victim must open the crafted media, so it is not remotely triggerable without user action. No CISA KEV entry or public exploit is identified in the available data, and an upstream fix is referenced in a GStreamer merge request.
Stack-based buffer overflow in GIMP's PSD plug-in image-resource header loader lets a crafted PSD file crash GIMP and potentially execute arbitrary code with the privileges of the user opening the file. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R) confirms local access and user interaction are required, with no privileges needed, so this is not remote unauthenticated exploitation. No public exploit identified at time of analysis; the 7.8 HIGH score reflects high confidentiality, integrity, and availability impact rather than ease of exploitation.
Unbounded memory growth in the glib-networking TLS 1.3 client-side session cache allows a malicious or compromised server to exhaust client memory by sending excessive session ticket messages, resulting in denial of service. The issue affects glib-networking as tracked in Red Hat Enterprise Linux 6 through 10 when a client negotiates TLS 1.3 and connects to an attacker-controlled or attacker-influenced endpoint. No public exploit code was identified at time of analysis; an upstream fix is available via glib-networking merge request 288, but a released patched version is not independently confirmed.
The openshift-ansible installer container's `run` script fetches remote inventory files and dynamic inventory scripts without any integrity verification, so a remote attacker positioned as a man-in-the-middle - or anyone who has compromised the HTTP server hosting those scripts - can swap in an arbitrary executable that then runs with the installer's UID and full cluster-provisioning privileges, yielding code execution (CWE-494). Unauthenticated remote exploitation is possible (CVSS 3.1 base 7.4 High, AV:N/AC:H/PR:N/UI:N), but the high attack complexity reflects the prerequisite of a MITM position or a pre-compromised script host, and only installs configured to pull these scripts over an unprotected channel during the install run are exposed. No public exploit code or confirmed active exploitation was identified at time of analysis.
Deserialization of untrusted data before authentication in the WildFly IIOP (CORBA) listener, as shipped in Red Hat JBoss EAP 7 and 8, may let a remote attacker who can reach the IIOP port submit crafted serialized objects and have them deserialized ahead of any credential check, potentially leading to code execution or full compromise of confidentiality, integrity and availability. Impact is conditional: the target EJB must expose at least one method taking untyped parameters, and a usable gadget chain must be present on the running classpath. The vendor rates the flaw 7.4 with an AV:L vector while our assessment treats the listener as network-reachable (AV:N/AC:H/PR:N/UI:N), and no public exploit code was identified at time of analysis; priority is this week, not emergency.
Unauthenticated remote code execution is possible in Red Hat JBoss Enterprise Application Platform 7 and 8 when the server runs in -secmgr mode with the openjdk-orb CORBA/IIOP listener exposed on TCP 3528. An attacker who can reach that listener can send a CDR-encoded object whose attacker-supplied codebase URL is honoured by JDKBridge during unmarshalling, causing the server JVM to load and instantiate arbitrary classes from a remote location before EJB security interceptors are evaluated. Exploitation is gated on non-default conditions - the -secmgr startup flag and a network-reachable IIOP/CDR listener - and the sources do not confirm active exploitation (CISA KEV) or verified working exploit code; the decision label is 'this_week', indicating a credible high-severity threat that is not a drop-everything emergency.
ARP/neighbor-table poisoning in the iscsiuio userspace daemon shipped with open-iscsi lets an unauthenticated attacker on the same Layer 2 segment redirect network traffic by sending a single minimal IPv6 Neighbor Advertisement. Affected deployments are those where iscsiuio is actually running for iSCSI hardware offload (typically with supported Broadcom NICs); a default server without iSCSI offload configured is not exposed. The same handler also reads link-layer address options at a fixed offset without confirming the packet carries them, an out-of-bounds read that can leak memory or crash the daemon; no public exploit has been identified at time of analysis.
Heap out-of-bounds read in the iscsiuio DHCPv4 option parser, part of open-iscsi, allows an attacker on the same Layer-2 segment to send a crafted DHCP response that can crash the daemon, corrupt its network configuration, and potentially disclose limited heap data. Deployments at risk are those running iscsiuio for iSCSI offload, notably on Broadcom bnx2/cnic NICs, and using DHCP-driven iSCSI configuration; Red Hat tracks Red Hat Enterprise Linux 6 through 10. No public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV) was provided; the issue is rated moderate priority (this_week).
Goose's optional terminal integration feature captures shell command history and transmits it verbatim, with no redaction, to whichever Large Language Model provider endpoint is configured whenever a query is sent, so any secret typed into the terminal - API tokens, passwords, or environment variables carrying credentials - leaves the local trust boundary. The exposure is a confidentiality-only design flaw (CWE-497) rather than an attacker-triggered exploit: it requires the feature to be enabled and a human to enter the sensitive value (UI:R), and the recipient is the configured provider and its logs rather than an arbitrary remote party. Red Hat tracks the issue against Red Hat Enterprise Linux 9 and 10; no public exploit code has been identified at time of analysis, and the priority label is this_week.
Privilege escalation in the Multicluster Global Hub Operator lets an attacker who already controls the operator or holds its service-account credentials impersonate arbitrary users, groups, and service accounts cluster-wide, then use that identity to obtain full administrative control. The issue is rated CVSS 3.1 7.2 HIGH (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) and stems from an overly permissive RBAC configuration in multicluster-global-hub-operator-bundle. No CISA KEV listing, EPSS score, or public exploit code is present in the supplied data; no public exploit identified at time of analysis.
Server-side request forgery in Kroxylicious's Azure Key Vault KMS provider lets an attacker who can influence wire-deserialized EDEK bytes redirect the proxy's Azure bearer token to a host they control, then replay that token against the real Key Vault to break the record-encryption trust model. The issue affects Red Hat Streams for Apache Kafka 3 deployments only when record encryption is enabled with the Azure Key Vault provider, and the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) reflects the need for low-privileged influence over EDEK input plus a reachable attacker-controlled host. No public exploit code has been identified at time of analysis, and no CISA KEV entry confirms active exploitation.
Authentication bypass in Cruise Control (Red Hat Streams for Apache Kafka 2.x and 3.x) lets adjacent-network attackers reach all 15 administrative REST endpoints without credentials by abusing exact-path Jetty security constraints and servlet path normalization. The CVSS 3.1 score is 8.8 (AV:A/AC:L/PR:N/UI:N), but in AMQ Streams the Strimzi operator NetworkPolicy limits Cruise Control port 9090 to operator pods, so realistic exposure requires that policy to be absent, disabled, or misconfigured. No public exploit was identified at time of analysis.
Cross-tenant privilege escalation in StreamsHub Console for Apache Kafka allows an authenticated Kubernetes tenant that can create or modify Console custom resources to point spec.containers.api.spec.image at an arbitrary container image, which the operator then deploys into a pod running under a ServiceAccount bound by ClusterRoleBinding to cluster-wide Strimzi CRD read access, Kafka/KafkaRebalance patch rights, and cluster-monitoring-view. The attacker-controlled code reads the projected ServiceAccount token and gains read/write control over the Strimzi control plane across tenant boundaries, with high confidentiality and integrity impact (CVSS 9.9, scope changed). Exploitation is gated by the tenant-level RBAC permission rather than being open to the internet, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Credential theft in multi-tenant Red Hat StreamsHub Console for Apache Kafka and Streams for Apache Kafka 2/3 deployments is possible because the operator trusts a namespace field supplied in a Console custom resource. An authenticated tenant with permission to create Console CRs (PR:L) can point spec.kafkaClusters[].credentials.kafkaUser.namespace at a victim namespace, causing the cluster-wide-privileged operator to read that namespace’s KafkaUser Secret-SASL credentials or TLS private keys-and write the plaintext into a Secret in the attacker’s namespace. CVSS 3.1 scores this 7.7 with scope changed and high confidentiality impact; no public exploit identified at time of analysis, so risk is concentrated in multi-tenant clusters where untrusted users can create Console resources.
Ghostscript as shipped with Red Hat Enterprise Linux 8-and, per CPE data, RHEL 6, 7, 9, and 10-may allow an attacker to escape -dSAFER protections when it processes a crafted PostScript file, enabling file access outside permitted paths or command execution with the Ghostscript process's privileges. The root cause is that Red Hat's 9.25-to-9.27 rebase omitted the CVE-2019-14869 correction, leaving privileged .forceput operations in the .charkeys procedure insufficiently protected; the supplied CVSS base score is 7.3, while the independent assessment treats confidentiality and integrity impact as High (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L). No CISA KEV entry is present in the supplied data and no public exploit identified at time of analysis; practical risk is conditional on a service or pipeline actually processing untrusted PostScript/EPS with an affected RHEL build.
Use-after-free in GIMP's XCF loader can crash the application and potentially allow arbitrary code execution when a user opens a crafted .xcf file that selects a path and then fails to load it. The flaw affects GIMP as packaged in Red Hat Enterprise Linux 6 through 10 according to the provided CPE mappings, and exploitation is local and requires user interaction (CVSS 7.8, AV:L/UI:R/PR:N); no public exploit was identified at time of analysis. Because scope is unchanged, any code execution would run with the privileges of the user opening the file rather than automatically gaining root.
Opening a crafted XCF file in GIMP can trigger a use-after-free in the XCF loader's linked-channels handling, crashing the main GIMP process and potentially enabling code execution in the opening user's context. The defect affects GIMP installations that parse XCF files, with Red Hat tracking impact across RHEL 6 through RHEL 10 packages; exploitation requires local delivery and a victim to open the malicious image, and no public exploit code or CISA KEV entry is identified in the provided data.
Heap out-of-bounds read and write in GIMP's PSD thumbnail resource loader allows memory corruption when a victim opens or thumbnail-previews a crafted PSD file containing a grayscale JPEG thumbnail, potentially leading to code execution in the plug-in process. The loader assumes a 3-byte BGR stride and never validates that the embedded thumbnail is RGB, so a single-channel grayscale image drives out-of-bounds indexing. Rated CVSS 7.8 (AV:L/UI:R/PR:N) - a client-side file-parsing bug with no network reachability; no public exploit code identified at time of analysis, and Red Hat tracks it across RHEL 6 through 10.
Heap out-of-bounds read in GIMP's XCF text-layer parasite parsing allows a crafted .xcf file, opened by a victim, to leak adjacent heap memory into layer text and crash the application, causing information disclosure and denial of service. The issue is local and requires user interaction (CVSS 7.1, AV:L/UI:R/PR:N), and the provided intelligence shows no public exploit or CISA KEV entry; it is a moderate-priority issue rather than an urgent remote threat.
Red Hat Advanced Cluster Security for Kubernetes (RHACS) Central's SAML assertion consumer service (ACS) endpoint does not cache used assertion or response identifiers, so a single valid signed SAML response can be replayed to mint multiple distinct Central authentication tokens for the same mapped identity. Deployments are only exposed when Central is configured to authenticate via SAML; an attacker must first obtain a legitimately signed, unexpired SAML response - they cannot forge one - which is why the issue is rated CVSS 7.4 with high attack complexity despite requiring no privileges or user interaction. Successful replay yields full compromise of confidentiality and integrity for the impersonated identity; no public exploit code or confirmed active exploitation was identified at time of analysis, and non-SAML authentication configurations are unaffected.
Signature-verification bypass in bootc and ostree image-mode deployments: a deployment staged while the container signature policy still accepted unsigned content remains bootable after the policy is hardened, because already-staged deployments are finalized on reboot without being revalidated against the current policy. An attacker who can stage a deployment under a permissive policy can therefore get unsigned OS content finalized and booted later, yielding full host compromise (C:H/I:H/A:H); the assessed vector is AV:L/AC:H with operator/local privilege (PR:L) despite the vendor's PR:N rating, and the flaw affects RHEL 8/9/10 image mode, OpenShift Container Platform 4, and Red Hat Hardened Images. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV).
Out-of-bounds heap reads and writes in spice-server's SPICE_MSGC_MIGRATE_DATA handling let an authenticated SPICE client read arbitrary heap memory or corrupt the heap while a VM is undergoing live migration. Consistent with the assessed CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H vector, the attacker must already hold a valid SPICE session and must land the malicious message inside the migration window, so real-world exposure is concentrated in deployments where the SPICE endpoint is reachable by low-privilege or untrusted users. No public exploit code and no CISA KEV entry were identified at time of analysis.
Local privilege escalation in cifs-utils lets an unprivileged local user obtain root on affected hosts by injecting unauthorized options into a privileged CIFS mount. When a root-owned service mounts a Common Internet File System share using a credentials file whose contents the attacker can control or influence - for example a file that is world-writable or lives in an attacker-owned path - cifs-utils assembles those unsanitized values into the mount option string, so the attacker can slip in extra options that bypass permission checks and cause files to be executed with administrative privileges. The flaw is tracked as CWE-88 (argument/option injection) with a CVSS of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); exploitation requires an existing low-privilege local account (authenticated, per PR:L) and a deployment where such a privileged, credentials-file-driven CIFS mount workflow exists, so internet-facing hosts that do not mount attacker-influenced CIFS shares are not at risk. No public exploit code or confirmed active exploitation was identified at time of analysis, and Red Hat has published advisory and Bugzilla tracking pages for RHEL 6 through 10 and OpenShift Container Platform 4.
Kuadrant operator's internal WebAssembly shim can be made to skip Gateway-level authentication and rate-limiting checks in multi-tenant deployments when an authenticated user with Kubernetes/OpenShift RBAC permission to create or modify an HTTPRoute attached to a shared Gateway supplies a crafted path, header, or query match value. The value is not properly escaped during CEL predicate generation, so the predicate can be altered to bypass those policies while the request is still forwarded to the route backend. No public exploit identified at time of analysis, and exploitation is conditional on a shared/multi-tenant Gateway with Gateway-level auth and/or rate limiting configured, making this a genuine but conditional-priority issue rather than a mass-exploitation threat.
Path traversal in wildfly-core's deployment content handler allows an authenticated JBoss EAP, WildFly, Fuse 7, or Single Sign-On 7 user who holds the Deployer RBAC role to escape the restricted deployment directory and create files with attacker-controlled content or delete arbitrary directories on the server, escalating to full management SuperUser privileges. Exploitation requires that the Deployer role be delegated to the attacker (CVSS vector shows PR:L - authenticated, not anonymous) plus a crafted deployment name containing traversal sequences; environments that reserve the Deployer role for fully trusted administrators face little practical exposure. No public exploit code was identified at time of analysis and the flaw is not listed in CISA KEV, so this is a credible, actionable priority rather than an emergency.
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.
Guest-to-host out-of-bounds access in DPDK's vhost-crypto backend lets a low-privileged guest VM that is already attached to a vhost-crypto device corrupt host-side memory by racing the host's two reads of an indirect-descriptor next index, a classic TOCTOU double-fetch (CWE-367). Only hosts running DPDK with lib/vhost's vhost-crypto library enabled and actually processing indirect descriptors are exposed, and the race makes reliable exploitation non-trivial - the assessed vector is AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H, reflecting host-local reach via the guest with cross-boundary (guest-to-host) scope change. Red Hat tracks this for Fast Datapath packages on Red Hat Enterprise Linux 8, 9 and 10; no public exploit code has been identified at time of analysis and there is no CISA KEV entry. Realistic exposure is limited to multi-tenant, untrusted-guest or confidential-computing style deployments where the vhost-crypto feature is deliberately enabled.
A use-after-unmap in DPDK's vhost library gives a local attacker who controls a VDUSE (vDPA Device in USErspace) backend, or a guest able to drive IOTLB invalidations on the vhost device, a path to memory corruption inside the host vhost process. The flaw is that the VDUSE handler does not invalidate cached vring pointers when the IOTLB is invalidated, so the code keeps dereferencing vring addresses that have already been unmapped - a classic CWE-416 use-after-free. The assessed CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, base 8.8) marks this as locally reachable, low-complexity and low-privilege, with a scope change (S:C) reflecting that a confined guest/userspace VDUSE device can compromise the host vhost trust boundary; impact is full confidentiality, integrity and availability loss. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so risk is concentrated in multi-tenant virtualization and NFV hosts that specifically enable DPDK VDUSE. Affected packages are Red Hat's Fast Datapath DPDK channel for RHEL 8, 9 and 10, with downstream exposure noted for RHEL, OpenShift Container Platform 4 and OpenStack Platform 13 Queens.
A double-offset error in DPDK's vhost log-mapping calculation (lib/vhost) lets local attackers with low privileges (PR:L) - including a guest that controls a virtio device serviced by the vulnerable vhost-user backend - trigger incorrect host memory accesses that compromise confidentiality, integrity and availability, giving a 7.8 HIGH rating (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is tracked by Red Hat and ships in Fast Datapath for RHEL 8, 9 and 10, which in turn is consumed by Red Hat Enterprise Linux 8/9/10, OpenShift Container Platform 4 and OpenStack Platform 13 (Queens), so exposure is concentrated in OVS-DPDK accelerated virtualization and NFV hosts that exercise the vhost log-mapping path (for example during guest dirty-page logging/live migration). No public exploit identified at time of analysis, and no CISA KEV listing or exploit code is referenced in the available intelligence.
Heap buffer overflow in DPDK's lib/vhost VDUSE control-queue handler allows a local, low-privileged (authenticated) actor to corrupt heap memory with attacker-controlled content, enabling privilege escalation and loss of host integrity. The root cause is a time-of-check-to-time-of-failure (TOCTOU) double-fetch: the control-queue descriptor is read twice from memory the attacker can modify in between, so the length used for the copy can differ from the length that was validated. Only deployments that actually exercise the VDUSE (vDPA Device in Userspace) control-queue path are exposed, and because winning the race is probabilistic the CVSS base score of 7.8 (AV:L/AC:L/PR:L) is more realistically an AC:H scenario per our assessment; no public exploit code and no confirmed active exploitation were identified at time of analysis. This is a genuine privilege-escalation and host-integrity concern rather than a mass-exploitation threat, since it is strictly local, involves no remote network path, and requires controlling the descriptor memory between fetches.
Privilege escalation in Red Hat OpenShift Container Platform 4's insights-runtime-extractor DaemonSet lets an authenticated low-privileged tenant who can schedule a pod on a node run attacker-controlled code as root in the host user namespace. The extractor scanner enters the workload's namespaces and executes the workload's argv[0] via exec.Command after only seteuid() has changed, leaving real/saved UID 0 and retaining capabilities; a malicious pod binary matching node, python, python3, MainThread, or any path containing java can call setuid(0) and reach the host CRI-O socket from the inherited cwd. CVSS 8.8 (AV:L/PR:L/S:C) reflects local, non-network exploitation requiring workload scheduling, and no public exploit was identified at time of analysis.
Path-restriction bypass in BusyBox httpd's reverse proxy feature allows unauthenticated remote attackers to reach backend paths outside the configured forwarding prefix. When URL-prefix proxying is configured, only the first request on a TCP connection has its path rewritten; a pipelined second request is relayed verbatim, defeating the intended prefix restriction and exposing arbitrary backend routes. Affects BusyBox httpd deployments, including Red Hat Hardened Images, that enable the non-default reverse proxy directive; no public exploit identified at time of analysis. CVSS 3.1 base score 7.2 (High) reflects network reachability, low complexity, no privileges or user interaction, and changed scope impacting the proxied backend.
Arbitrary file write outside the intended extraction directory is possible in BusyBox's dpkg-deb applet because its ar archive handler flushes deferred symlinks after every archive member rather than once after the final member. A crafted .deb containing two data.tar members - the first declaring a symlink to an absolute path such as '/', the second declaring a regular file whose path traverses that now-live link - causes a file to be written at an attacker-chosen location when the package is unpacked (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-59). Affected systems are BusyBox builds compiled with dpkg-deb support, including BusyBox shipped inside Red Hat Hardened Images; the CVSS vector indicates no privileges are required by the attacker (PR:N) but the victim must interact by extracting the untrusted package, and the vector's local attack value plus the non-trivial two-member structure keep this a context-dependent integrity issue rather than a mass-exploitation emergency. No public exploit identified at time of analysis.
Heap-based buffer overflow in GStreamer's gst-plugins-base plugin library lets a local attacker who controls the sending side of a GStreamer inter-process IPC pipeline corrupt memory in the receiving process, yielding a CVSS 3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) with high confidentiality, integrity, and availability impact. The victim process maps a crafted video buffer whose GstVideoMeta declares plane strides and offsets larger than the actual backing allocation, causing out-of-bounds reads and writes that can crash the process or potentially permit code execution in its context. Exploitation is strictly local and requires a deployment where GStreamer buffers cross a trust boundary between a less-trusted producer and a more-trusted consumer; no user interaction or authentication to the victim is needed, and no public exploit has been identified at time of analysis.
Denial of service in GNOME Remote Desktop (gnome-remote-desktop) as shipped in Red Hat Enterprise Linux 8, 9, and 10 allows an unauthenticated remote attacker to pin the daemon's event-loop thread at high CPU by sending traffic to a TLS-enabled VNC listener, causing the service to stop making forward progress. The defect is in the VNC TLS I/O handlers, which treat retryable GnuTLS results (GNUTLS_E_AGAIN and GNUTLS_E_INTERRUPTED) with an unbounded busy loop instead of returning control to the event loop, so the thread spins indefinitely rather than waiting for socket readiness. No public exploit code exists and there is no confirmed active exploitation, and practical exposure is bounded: the VNC backend must be running with a TLS listener reachable over the network, a configuration that is not enabled by default on typical RHEL installs and is far more common on desktops than on servers.
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 attackers can bypass security controls on REST endpoints generated by Quarkus REST Data Panache when a developer uses @MethodProperties to customize an operation without re-declaring class-level security roles, causing the generator to silently drop the security requirement and expose the endpoint. This results in potential unauthorized information disclosure or data modification, with a CVSS 3.1 score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) and CWE-425. No public exploit code has been identified at the time of analysis.
Authenticated users of the Red Hat OpenShift web console can abuse the Helm chart URL input to make the console pod issue requests to arbitrary destinations, turning the console into a Server-Side Request Forgery (SSRF) proxy (CWE-918, CVSS 3.1 base 7.7). Because the console pod typically sits inside the cluster network with broader reachability than the user, a low-privileged console account with the ability to add or load a Helm chart can use leaked error output to read sensitive responses and can perform blind port scanning against internal services. Exploitation requires an authenticated console session and the privilege to supply a chart repository URL (PR:L, unauthenticated outsiders cannot reach it), and the assessed impact is confidentiality-only with no integrity or availability effect; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV).
Use-after-free in GNOME Mutter's Wayland color-management (wp_image_description_v1) path allows a local, authenticated attacker who can run a malicious Wayland client to destroy the image-description resource while an asynchronous ICC file read is still in flight, after which the compositor writes into freed memory and frees a pointer derived from it - typically crashing the GNOME session and potentially enabling code execution inside the compositor process. The flaw is local-only and timing-dependent (it requires winning a race window), only applies to Wayland sessions where the color-management/ICC path is exposed (not X11-only sessions or builds without that code path), and no public exploit code or CISA KEV entry has been identified at time of analysis; in practice the more likely outcome is a session crash rather than reliable code execution. This is a credible local privilege/code-execution risk but not an urgent internet-facing emergency.
Remote code execution in ManageIQ (and its downstream Red Hat CloudForms) is possible because the YamlLoadAliases module overrides YAML.safe_load so that in production a Psych::DisallowedClass error silently falls back to YAML.unsafe_load, deserializing arbitrary Ruby objects. An authenticated attacker holding dialog import privileges (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) can upload a crafted YAML dialog payload containing a disallowed class to trigger an unsafe deserialization path with full confidentiality, integrity, and availability impact. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, but Red Hat CloudForms has reached End of Life and no errata will be issued, so CloudForms operators cannot patch and must depend on restricting the dialog import role.
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.
Red Hat OpenShift Container Platform 4 ships by default with an insights-operator-gather ClusterRole that grants the operator's 'gather' service account cluster-wide get/list access to core-group secrets, with no namespace or resourceNames scoping. An authenticated actor who can create or influence a pod specification in any namespace - and set 'serviceAccountName: gather' on it - can mount that service account and read every secret in every namespace, making this a privilege-escalation and cluster-wide credential-disclosure primitive (CWE-269, CVSS 7.7, scope-changed confidentiality-only). Exploitation requires a pre-existing foothold with pod-create or service-account-binding rights (PR:L), so it is not remotely exploitable by an unauthenticated user; no public exploit code has been identified at time of analysis, and the over-broad grant exists out of the box rather than behind a non-default feature flag.
Cyrus SASL clients that use the DIGEST-MD5 authentication mechanism can be crashed by a malicious or on-path server that supplies a crafted challenge field (such as realm or nonce), because the add_to_challenge() function computes a buffer size before DIGEST-MD5 quoting and fails to account for escaping that lengthens the value, resulting in a heap-based out-of-bounds write. This is a client-side denial-of-service flaw affecting Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4; the assessed CVSS vector is AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:H, meaning unauthenticated remote attackers must control or intercept the server endpoint and the victim must initiate authentication. No public exploit code or confirmed active exploitation is identified at time of analysis.
Candlepin, the entitlement and subscription management engine behind Red Hat Satellite 6, contains an authorization-logic flaw in its central access control filter: when an API operation verifies multiple @Verify-annotated parameters, access is granted if any one of them is permitted rather than requiring permission on all of them. An authenticated attacker with a low-privilege account who legitimately can reach the first referenced object can therefore pass authorization checks on later parameters and, provided they know the victim resource identifiers, read consumer information or modify entitlements and subscription resources - including objects belonging to other organizations (CVSS 3.1: 8.1, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). Exploitation requires a valid account and prior knowledge of target consumer UUIDs, entitlement IDs, or subscription resource IDs, and is limited to endpoints that evaluate more than one verified parameter; no public exploit code was identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV).
Heap-based buffer overflow in GIMP's DirectDraw Surface (DDS) loader allows attackers to corrupt memory and potentially execute arbitrary code by convincing a user to open a crafted .dds image. The flaw affects GIMP as shipped in Red Hat Enterprise Linux 6, 7, 8, 9, and 10, and requires local file access plus user interaction (opening the malicious file) with no authentication required per the CVSS vector (PR:N). No public exploit code has been identified at time of analysis, and exploitation is limited to the privileges of the user running GIMP.
Ghostscript can execute arbitrary shell commands with the privileges of its process when it renders a crafted PostScript or EPS document, chaining memory corruption in document parsing with a runtime bypass of the -dSAFER sandbox. The flaw affects Ghostscript as shipped in Red Hat Enterprise Linux 6, 7, 8, 9, and 10, and the assessed vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, meaning no privileges are required but a victim or automated pipeline must render the malicious file, with the malicious document first reaching the processing system. Publicly available exploit code exists, including a GitHub proof-of-concept, but the provided data does not confirm CISA KEV active exploitation, so -dSAFER should not be treated as a protective mitigation for affected versions.
Unauthenticated Go pprof debug endpoints exposed on the postgres-exporter metrics listener let any attacker who can reach that port from inside the cluster network read process arguments, full goroutine stacks, and heap memory - potentially leaking database connection strings and credentials - and repeatedly trigger CPU profiling to exhaust resources in a denial-of-service condition. The flaw is tracked as CVE-2026-83550 (CVSS 7.1, AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H per the vendor, C:H for confidentiality in our assessment) and affects postgres-exporter as shipped in Red Hat Multicluster Global Hub, where the CPE covers all tracked versions; exploitation requires adjacent/cluster network reachability rather than internet exposure. No public exploit code has been identified at time of analysis, and no CISA KEV listing indicates active exploitation; risk is best characterized as a real design flaw of moderate priority, with exposure materially reducible through NetworkPolicies that restrict access to the metrics port.
Arbitrary code execution in the control plane of Red Hat Multicluster Engine for Kubernetes (HyperShift operator) is possible when an authenticated user with cluster and secret creation permissions supplies a kubeconfig secret containing unauthorized executable credential plugins, which the operator copies without validation into the privileged control plane namespace. Downstream controllers that consume this configuration execute the plugins, granting full control plane compromise. The vulnerability requires low privileges (PR:L) and no user interaction, and no public exploit or CISA KEV entry is identified at time of analysis.
Dogtag PKI (pki-core) and its commercial counterpart, Red Hat Certificate System 9/10/11, contain a fail-open authentication flaw in the CMCAuthForEST plugin that lets an authenticated, low-privileged EST enrollment user obtain CA-signed certificates bearing arbitrary subject names. The bug is triggered when an EST fullcmc enrollment request is sent over BasicAuth without an end-user TLS client certificate; the SSL_CLIENT_CERT session attribute then retains the EST subsystem's agent certificate, so downstream authorization logic wrongly grants agent-level privileges. Exploitation is assessed as requiring only a valid EST user account (CVSS 8.1, PR:L, unauthenticated by client certificate, no user interaction), making it a realistic privilege-escalation path for any provisioned EST user or insider; however, no public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (not in CISA KEV).
StartTLS handling in 389-ds-base does not discard plaintext bytes buffered before the TLS upgrade, allowing an on-path attacker to inject a crafted LDAP message whose messageID collides with a client's pending bind and causes the client to treat a failed authentication as successful. Red Hat Directory Server 11, 12, and 13 and Red Hat Enterprise Linux 6, 7, 8, 9, and 10 deployments using 389-ds-base with StartTLS are affected. Exploitation requires an on-path network position and timing control during StartTLS negotiation, so the real-world bar is higher than the reported 9.0 base score; no public exploit identified at time of analysis.
Denial of service in 389-ds-base (the LDAP engine shipped with Red Hat Directory Server 11/12/13 and Red Hat Enterprise Linux 6 through 10) lets an unauthenticated remote attacker stall the server's worker-thread pool by sending a complete LDAP operation followed by the opening bytes of an incomplete LDAPMessage on the same connection. The server then hands the connection to a second worker thread before the first worker's result is flushed; the second worker blocks on the connection mutex until nsslapd-ioblocktimeout, so the finished operation's response is never delivered. Repeating this over a handful of connections proportional to the configured worker-thread count exhausts the entire pool under default configuration, denying LDAP service to anonymous and authenticated clients over both plaintext and TLS for as long as the attacker holds the connections; no public exploit code has been identified at time of analysis, and no EPSS or KEV signal accompanies the CVE, though the availability-only impact (CVSS 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) is genuine for any internet- or broad-network-reachable directory server.
OS command injection in the Foreman foreman-tail helper utility shipped with Red Hat Satellite 6.19 for RHEL 9 allows a local, authenticated user to execute arbitrary system commands with the privileges of whoever runs the tool, because unsanitized arguments are fed into an eval-based path-expansion string and shell metacharacters such as ;, & and | are interpreted as commands. The flaw is rated 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and is strictly local-scope, so it only matters where a lower-privileged account on a Satellite/Foreman host can reach the utility and thereby escalate its privileges. There is no network-facing attack path, no public exploit code has been identified at time of analysis, and EPSS is low (0.55%, 44th percentile), though Red Hat has issued patched packages (for example 0:3.18.0.14-1.el9sat for Satellite 6.19 on RHEL 9) via several RHSA advisories.
Remote code execution in Foreman's safemode-protected templating engine, shipped in Red Hat Satellite 6.19 for RHEL 9, lets an authenticated user with only low-level template privileges escape the sandbox and execute arbitrary commands on the Satellite server. The flaw stems from improper handling of delegated methods, which allows an attacker to append unauthorized functions to the sandbox's allowed-execution list; no user interaction is required beyond rendering or creating a template, and the Satellite web UI is network-reachable by default. Vendor patches are available via Red Hat errata, EPSS is modest (0.66%, ~50th percentile), and no public exploit code or confirmed active exploitation was identified at time of analysis (SSVC exploitation: none, not automatable).
Authenticated users with low-level Viewer permissions in Red Hat Satellite 6.19 (and upstream Foreman) can exploit template preview endpoints to disclose sensitive data, including host root passwords. In non-default configurations where Safemode protections are disabled, the flaw can escalate to arbitrary command execution as the Foreman system account. No public exploit code or active exploitation has been identified at time of analysis; the CVSS score of 9.1 reflects high confidentiality impact, though the RCE component requires an insecure configuration.
Privileged local attackers who can control Foreman configuration data can chain server-side template injection with insecure deserialization through the foreman-rake initialization logic in /usr/share/foreman/config/settings.rb to execute arbitrary code on Red Hat Satellite 6.19 for RHEL 9 hosts, resulting in full host compromise and downstream supply chain risk. The assessed CVSS 3.1 vector (7.7, AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H) confirms the attack is local and authenticated with high privileges plus a user-interaction component, so it is not remotely or unauthenticated reachable against a default deployment and real exposure is largely confined to compromised or malicious privileged operators. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; Red Hat has published errata RHSA-2026:74503 addressing it.
OS command injection in Foreman's foreman-rake db:dump and db:import_dump tasks lets an attacker who already holds permission to execute those rake tasks - for example through a restricted sudo delegation - append arbitrary shell commands to the destination (backup) or file (import) parameter, achieving command execution with the privileges of the rake process and scoring CVSS 8.2 (AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H). The bug affects Foreman as shipped in Red Hat Satellite 6.19 for RHEL 9 and the broader Red Hat Satellite 6 line, and is tracked under CVE-2026-12541. This is a genuine but access-gated privilege-escalation risk rather than a mass-exploitable remote threat: it is local-only, demands pre-existing delegated or privileged access to the rake tasks, and environments where only root invokes foreman-rake with no restricted sudo delegation are effectively not exposed; no public exploit code has been identified at time of analysis.
Command injection in the Foreman foreman-rake errors:fetch_log task shipped with Red Hat Satellite 6 allows a local user who already holds a sudo grant for that specific rake task to break out of the intended grep invocation and run arbitrary commands with the privileges of the task. The request_id parameter reaches the underlying shell command without adequate metacharacter neutralization, so an attacker can inject ';', '"', or '|' and achieve command execution on the Satellite/Foreman host. The CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) confirms this is a local, high-privilege-context privilege escalation rather than a remotely reachable flaw, and no public exploit code or CISA KEV entry was identified at time of analysis.
Unauthenticated remote attackers can pull the kickstart provisioning template from Red Hat Satellite 6's /unattended/provision endpoint without supplying any token, provided a host is currently mid-provisioning and therefore has an unexpired token recorded in the Satellite database. The flaw is a semantic logic error in Foreman's host_verifier.rb: valid_host_token? validates database state rather than the token presented in the HTTP request, so the check passes even when the request carries no token. Rated CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N), the exposure is gated by the provisioning window and yields information disclosure of the rendered template, not code execution; no public exploit code or active exploitation has been identified at time of analysis.
Command injection in the Red Hat Satellite job invocation API (/api/v2/job_invocations), shipped via the rubygem-foreman_remote_execution plugin, lets an authenticated Satellite user who holds job-template execution permissions run arbitrary shell commands on managed hosts. The injection only applies to job templates whose effective_user property is configured as overridable: true, in which case the user-supplied value is not sanitized before the Satellite server instantiates the job execution environment, so the payload executes during instantiation rather than through the template or playbook content itself. Rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-78), this requires an authenticated account (PR:L) and the non-default overridable setting, and no public exploit identified at time of analysis; Red Hat has published an erratum, RHSA-2026:74503.
Unauthenticated container image tampering in oc-mirror, the mirroring utility shipped with Red Hat OpenShift Container Platform 4 and the Assisted Installer for Red Hat OpenShift Container Platform 2, lets any host on the same adjacent network segment push attacker-controlled images, delete cached images, or read mirrored content while a mirroring operation is running. The embedded local cache registry binds to all network interfaces (0.0.0.0) with neither authentication nor TLS, matching CWE-306, and carries a CVSS 3.1 score of 7.1 (AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N). No public exploit code has been identified at time of analysis, and the exposure window is transient because the vulnerable registry only exists during an active mirroring run.
Arbitrary file write in oc-mirror allows an attacker who controls or tampers with an operator catalog image to write files outside the intended extraction directory when a user mirrors that catalog using the legacy v1 path (--v1) or the OCI feature path (--use-oci-feature). The issue is a path traversal (CWE-22) in tar entry extraction, assessed as local (AV:L), no privileges required (PR:N), but requiring user interaction (UI:R) because an administrator must run the mirror command; impact is high integrity and low availability, with no confidentiality impact per the independent assessment. No public exploit or active exploitation is identified at time of analysis, and the independent assessment characterizes this as a moderate, defender-actionable issue rather than an urgent internet-facing emergency.
Heap-based buffer overflow in RPM's package-header parsing lets a crafted, unsigned RPM overwrite memory when a victim merely inspects it with rpm2cpio, rpm2archive, or 'rpm -qlvp', giving an attacker-controlled heap write past a one-byte allocation (CWE-122, assessed CVSS 3.1 7.1). Affected code ships with RPM as distributed in Red Hat Enterprise Linux 6, 7, 8, 9, and 10 as well as Red Hat Hardened Images, so build farms, CI pipelines, package mirrors, and malware-analysis hosts that routinely open untrusted packages are the realistic exposure surface. Exploitation is local (AV:L), low complexity (AC:L), and unauthenticated (PR:N) but requires user interaction (UI:R) to invoke an rpm tool against the malicious file; signature verification is no barrier because the overflow happens during header decoding. No public exploit identified at time of analysis.
Container escape in CRI-O - the OCI runtime that underpins Red Hat OpenShift Container Platform 4 - is achievable when a workload-level actor can create or influence pod metadata that overwrites CRI-O's own reserved sandbox bookkeeping; the poisoned state is then reloaded as trusted after a CRI-O daemon restart, and a subsequent container recreate inside that sandbox can expose a host-side runtime-management resource to the container. Rated CVSS 3.1 7.8 (AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H), the flaw is not remotely reachable without cluster workload access, and the mandatory restart-then-recreate sequencing is the principal limiter on realistic exploitation. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing); no EPSS score was supplied in the available intelligence.
A heap buffer overflow exists in libsoup's WebSocket permessage-deflate compression path: when a very large outbound message is compressed, truncated size calculations used to grow a GByteArray wrap, allowing zlib to write beyond the allocated buffer. The affected code is the outbound compression routine reached through the permessage-deflate extension (RFC 7692), so exploitation requires that the extension be negotiated on the WebSocket connection and that the endpoint emit a message large enough to cross the integer-truncation boundary - a precondition that materially narrows exploitation below the raw 9.8 base score. The CVSS vector indicates no privileges (PR:N) or user interaction (UI:N) are required, but no public exploit code has been identified and there is no confirmation of active exploitation (SSVC exploitation: none, no CISA KEV entry); EPSS is low at 0.30% (20th percentile), and Red Hat has published errata (RHSA-2026:83384, RHSA-2026:83618) addressing the flaw.
Heap memory corruption in libsoup can be triggered when a WebSocket client using libsoup constructs a masked outgoing frame for an extremely large payload near the 32-bit guint limit, truncating the GByteArray allocation size while the masking routine processes the full length. It affects libsoup as shipped in Red Hat Enterprise Linux 6 through 10. The assessed CVSS vector is network-reachable but high-complexity (AV:N/AC:H/PR:N/UI:N), and no public exploit identified at time of analysis.
Heap out-of-bounds read in libsoup's WebSocket implementation allows a remote, unauthenticated peer to trigger a heap buffer overflow when the application has configured max-incoming-payload-size to unlimited (0), a non-default setting; with the standard payload cap the overflow cannot be reached. The CVSS 3.1 base score is 8.6 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H), but our assessed vector raises complexity to AC:H because exploitation requires both the non-default unlimited setting and a frame large enough to wrap the GByteArray length counter, implying a very large transfer. No public exploit code or active exploitation has been identified at time of analysis.
Out-of-bounds read and application crash in libsoup's soup_uri_decode_data_uri() affect applications that pass attacker-controlled base64 data: URIs to the GLib-based HTTP library, with Red Hat shipping vulnerable packages across Red Hat Enterprise Linux 6, 7, 8, 9 and 10. A crafted data URI whose percent-decoded payload contains embedded NUL bytes causes the decoded length to remain uninitialized and be used as the size of the returned GBytes, yielding a minor confidentiality leak (C:L) alongside a serious availability impact (A:H) rated 8.2 under CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H. The issue is remotely triggerable without authentication (PR:N) and no public exploit code has been identified at time of analysis, though real-world exposure is limited to software that actually processes untrusted data: URIs (WebKit/GTK browsers, feed and mail readers, and other GNOME applications rendering remote content).
Heap corruption and denial of service in libsoup stem from unbounded WebSocket message reassembly: the code accumulates fragmented frames in a GByteArray without checking the total reassembled size against the buffer type's size limit, so an oversized message can truncate the tracked length while the implementation continues to use the full length, producing out-of-bounds memory access (CWE-125) and possible crashes. The flaw is reachable by unauthenticated remote peers that can establish a WebSocket connection with a libsoup-based server, or by a libsoup client that connects to an attacker-controlled or man-in-the-middle server, but the assessed vector (AC:H) reflects that the attacker must drive reassembly to the underlying ~4 GB buffer-type boundary, so ordinary small-message WebSocket traffic does not trigger it. No public exploit code or CISA KEV active-exploitation confirmation was identified at time of analysis.
A type-confusion memory-safety flaw in libsoup's WebSocket handling can crash or corrupt the heap of applications that process incoming Pong frames. When a Pong frame arrives, SoupWebsocketConnection emits its ::pong signal with a GByteArray pointer even though the signal is declared to pass a GBytes object, so any application that connects a ::pong handler written to the documented GBytes API will misinterpret the payload and may suffer heap corruption or a crash. This is not exploitable against default libsoup usage: the target must both act as a WebSocket peer and explicitly register a ::pong handler, and the attacker must control or compromise the WebSocket endpoint (or otherwise inject a crafted Pong frame) into that connection. The recorded CVSS 3.1 base score is 8.6, but the independent assessment rates it AC:H with C:L/I:L/A:H because exploitation is gated on that non-default handler registration; unauthenticated remote attackers (PR:N, UI:N) can reach the code path, however no public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited.
Heap-based out-of-bounds write in the RPM Package Manager (rpm) affects Red Hat Enterprise Linux 6 through 10 and Red Hat Hardened Images, allowing a local, unauthenticated attacker to corrupt memory by crafting an RPM package that is then parsed with rpm2cpio, rpm2archive, or rpm -qlvp. The flaw arises from an integer overflow in iterReadArchiveNext() when a symlink entry declares RPMTAG_LONGFILESIZES as 0xFFFFFFFFFFFFFFFF, shrinking the buffer allocation to one byte and enabling attacker-controlled data from the cpio filesize field to overwrite heap memory. Exploitation requires user interaction to inspect the malicious package and no public exploit code has been identified at time of analysis; the CVSS 3.1 base score is 7.1.
Arbitrary code execution on an operator's workstation is achievable through kube-compare when it processes a 'container://' reference path pointing at an untrusted container image, because the tool launches that image's entrypoint instead of only reading data out of a stopped container. Exploitation is locally scoped and gated: per the assessed vector CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, an unauthenticated (PR:N) attacker must convince the operator to invoke the tool against the malicious reference (UI:R), so the victim's own action is the trigger. This is a genuine but conditionally-gated risk - escalation to full root-mediated impact occurs only where the local Docker daemon runs with elevated privileges - and no public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis; EPSS data was not supplied. The tool is distributed in Red Hat OpenShift Container Platform 4 and the 'Pen Drive Powered by Red Hat Lightspeed' offering.
Authenticated federation peers can cause denial of service and broker state manipulation in Apache ActiveMQ Artemis before 2.34.0 by sending a crafted FEDERATION_DOWNSTREAM_CONNECT packet that forces the broker to load and instantiate arbitrary classes visible to the Artemis module classloader. The vulnerability arises from unsafe reflection (CWE-470) in FederationStreamConnectMessage.getFederationPolicy(), which passes an unvalidated class name from the CORE protocol wire buffer to Class.forName(). Although the original CVSS 3.1 vector reports PR:N (8.2 High), the described authentication requirement means the practical severity is lower; the authoritative assessment uses PR:L. No public exploit code has been identified at time of analysis.
Command injection in NooBaa's cluster_internal_api (set_hostname_internal function) allows an authenticated attacker holding NooBaa administrative privileges on a Red Hat OpenShift Data Foundation 4 Multi-Cloud Object Gateway to execute arbitrary shell commands in the context of the NooBaa process by supplying a hostname value containing shell metacharacters. The flaw carries a CVSS 3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), and the high-privilege prerequisite means it is not reachable by unauthenticated users; realized impact is bounded by the privileges of the NooBaa pod rather than guaranteed node-level root. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
A use-after-free race condition in QEMU's 9pfs (virtfs) passthrough subsystem allows a malicious guest user to escape the shared directory boundary and read or write arbitrary files on the host, potentially achieving code execution as the QEMU process user (VM escape). Only hosts that have enabled 9pfs/virtfs host-directory sharing are exposed, since this is not a default configuration; the attacker must be a local guest user able to issue 9p protocol requests and must win a race between QEMU's main thread and a 9pfs worker thread with concurrent Tlcreate and Twalk requests. No public exploit code or active exploitation telemetry was identified at time of analysis, but the flaw is rated high severity (CVSS 8.8, scope-changed, C:H/I:H/A:H) and affects QEMU packages shipped in Red Hat Enterprise Linux 6 through 10, Red Hat OpenShift Container Platform 4, and related Red Hat products.
Path traversal in the pulpcore content upload API allows an authenticated user holding only low-privilege file-repository permissions to read arbitrary files accessible to the Pulp server process by submitting a crafted 'file:' URL through the 'file_url' parameter, which is dispatched to the file downloader despite an intended scheme check. Baseline impact is confidentiality loss on the Pulp host; in deployments that include Pulp Container the same flaw escalates to theft of the container registry token signing private key, enabling forged bearer tokens and unauthorized access to every private container repository in the registry. Downstream products embedding pulpcore are affected, including Red Hat Satellite 6, Red Hat Ansible Automation Platform 2, and Red Hat Update Infrastructure 4/5. There is no public exploit identified at time of analysis, and EPSS data was not provided; Red Hat tracks the issue under advisory https://access.redhat.com/security/cve/CVE-2026-90959.
Command injection in rpm enables an attacker to run arbitrary shell commands as the invoking user when a victim installs, rebuilds, or otherwise processes a malicious source RPM (.src.rpm) that contains a %() macro construct in a source or spec file basename. The flaw is local and requires user interaction, with impact confined to the privileges of the user running rpm or rpmbuild, typically non-root; build farms and CI/CD pipelines that automatically handle untrusted SRPMs are the highest-risk targets. Red Hat CPEs list RHEL 6 through 10 and Red Hat Hardened Images, and no public exploit was identified in the provided intelligence; monitor the vendor advisory for exploitation and patch updates.
Local attackers can achieve arbitrary code execution by tricking a user or automation into processing a crafted manifest file with 'rpm -q -p', due to unexpected macro expansion of manifest entries in RPM before they are opened. This command injection flaw (CWE-78) affects Red Hat Enterprise Linux 6 through 10 and Red Hat Hardened Images, with a CVSS 3.1 base score of 7.8 (HIGH, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H); exploitation requires user interaction but no privileges, and impact is limited to the privileges of the rpm process. No public exploit code or active exploitation has been identified at time of analysis.
An out-of-bounds write in GIMP's GIMPressionist plug-in allows an attacker to corrupt memory by convincing a user to load a malicious preset file, potentially leading to a crash or arbitrary code execution. The flaw is an unauthenticated local attack (CVSS PR:N) that requires user interaction (UI:R) to open a crafted preset file, and it affects GIMP as packaged in Red Hat Enterprise Linux 6 through 10 plus likely upstream GIMP versions. No public exploit has been identified at time of analysis, and the overall risk is assessed as genuine but not urgent due to the requirement for user interaction with a crafted file.
Unauthenticated path traversal in the OpenShift console's /locales/resource.json endpoint allows remote attackers to read arbitrary *.json files from the console pod filesystem by manipulating the lng and ns query parameters, exposing plugin manifests and configuration files, and potentially enabling traversal against registered dynamic-plugin backends. The flaw is unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 7.5) and affects Red Hat OpenShift Container Platform 4; no public exploit code has been identified at time of analysis and there is no CISA KEV telemetry, but per the independent assessment this remains a credible remote-attack priority because the endpoint is reachable without credentials and yields high-confidentiality reads. Impact is limited to information disclosure - integrity and availability are not affected per the assessed vector.
Improper authentication in the OpenShift Console's CatalogdHandler allows unauthenticated remote attackers to forward the openshift-session-token cookie and send requests to the in-cluster catalogd service, disclosing the internal operator-catalog index and providing a relay into the openshift-catalogd namespace (CVE-2026-75886, CVSS 7.2). This affects Red Hat OpenShift Container Platform 4. No public exploit identified at time of analysis; exploitation requires network reachability to the exposed console endpoint.
Use-after-free in librsvg during rendering of crafted SVG documents with nested XInclude directives and duplicate entity declarations allows unauthenticated local attackers to crash or potentially execute code in applications that use the library. Tracked as CVE-2026-96889 and reported by Red Hat, the flaw affects librsvg as shipped in Red Hat Enterprise Linux 6, 7, 8, 9, and 10. Exploitation requires user interaction (UI:R) because a victim must open, preview, or thumbnail a malicious SVG; the CVSS 3.1 score is 7.8. No public exploit code was identified at time of analysis, and independent assessment indicates that arbitrary code execution is unproven-only denial of service or crash is reliably reachable.
Command injection in the automation controller's external logging (rsyslog) configuration of Red Hat Ansible Automation Platform 2 allows a superuser to achieve arbitrary command execution inside the control-plane rsyslog component, exposing the controller SECRET_KEY and database credentials and enabling decryption of all stored credentials. Exploitation requires authenticated superuser privileges (CVSS 3.1 7.2, PR:H, no user interaction) and only takes effect when external logging is in use, so the malicious RainerScript configuration is actually generated and loaded. No public exploit code was identified and there is no CISA KEV listing indicating active exploitation, meaning real-world risk is strongly gated by the elevated privilege requirement even though the post-exploitation impact is a full control-plane compromise.
Missing authorization checks in the Red Hat Ansible Automation Platform 2 automation-controller allow an authenticated organization workflow-admin - a delegated, non-superuser role - to escalate into the control plane by copying a WorkflowJobTemplate and then launching jobs pinned to instance groups they hold no use_role on. The deep-copy permission sanitizer re-validates only the inventory, unified_job_template, and credentials of each cloned node, silently carrying over instance_groups, execution_environment, and labels, so the copier becomes administrator of a workflow that executes attacker-influenced automation in the control-plane execution context (CVSS 9.9, scope changed, high confidentiality, integrity, and availability impact). Exploitation is confirmed to require only a normal multi-tenant deployment plus workflow-admin rights; no public exploit code has been identified at time of analysis and there is no CISA KEV entry, and no vendor-released patch version was confirmed in the available intelligence.
Authenticated but low-privileged users of Red Hat Ansible Automation Platform 2 can bypass the automation-controller's sanitize_jinja() input-validation guard and have ansible-core evaluate attacker-supplied Jinja inside the execution environment, yielding arbitrary command execution and disclosure of secrets belonging to credentials the attacker cannot normally read. The flaw is exploitable remotely with no user interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N per independent assessment) and requires only a controller account able to set one of the affected launch-time fields. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV; priority is bounded by the required authenticated foothold and the niche deployment footprint.
Remote code execution in Red Hat Ansible Automation Platform 2's automation-controller is possible when a privileged, authenticated user (CVSS PR:H) defines a custom Credential Type and abuses its environment-variable injector to set a process-hijacking loader variable such as BASH_ENV, ENV, LD_PRELOAD, LD_LIBRARY_PATH, PYTHONSTARTUP, or GIT_SSH_COMMAND, which the existing ANSIBLE_* prefix check and fixed ENV_BLOCKLIST fail to catch. Paired with the credential file injector, the attacker plants a script in the execution environment and points the loader variable at it, so arbitrary code executes inside the execution-environment container for any job that later attaches a credential of that type; this requires both the high privilege to author the credential type and a subsequent job consuming it. Red Hat's published CVSS of 7.6 (C:L/I:H/A:N) is lower than our independent assessment of the full vector (C:H/I:H/A:H), and because the vulnerable controller and the impacted execution-environment container are different security scopes, S:C applies. There is no CISA KEV listing and no public exploit identified at time of analysis.
Privilege escalation in Red Hat Ansible Automation Platform 2 (built on the AWX upstream project) lets an authenticated AAP platform administrator escape the container-group sandbox and obtain OpenShift namespace-level access, including the ability to read and exfiltrate namespace secrets. The flaw is reachable over the network (AV:N) with no user interaction (UI:N) and changes scope across the container/namespace boundary (S:C), but it is gated on the highest AAP privilege tier (PR:H), so it is an insider or compromised-admin scenario rather than an unauthenticated attack; only deployments that use container groups backed by OpenShift/Kubernetes are exposed. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); no vendor-released patch has been identified at time of analysis, so mitigation depends on restricting the vulnerable field or the administrators who can reach it.
An authenticated automation-controller administrator in Red Hat Ansible Automation Platform 2 can turn the administrator-controlled format template for API 4XX log messages into a secret-reading primitive, using Python string-format traversal to walk from the interpolated user object into Django settings and pull out the SECRET_KEY and the database password. Because the log destination (external aggregator) is also administrator-controlled, the formatted message - and therefore the secrets - can be shipped off the host, giving the administrator the master key protecting all stored credentials, the ability to forge signed user sessions, and direct database access; the assessed vector is CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N (8.7) with high confidentiality and integrity impact and scope change, since secrets leave the controller's security boundary. No public exploit code has been identified at time of analysis and there is no CISA KEV entry, so this is a high-priority hardening issue rather than an actively exploited one: the practical risk is driven by the very high value of the assets reachable once a privileged administrator account or the log pipeline is compromised.
Stored cross-site scripting in the automation-controller component of Red Hat Ansible Automation Platform 2 lets an authenticated low-privileged user embed a javascript: hyperlink into job, ad hoc command, project update, or inventory update standard output, which is then rendered as a text/html link in the controller's stdout view. Because the HTML conversion escapes HTML metacharacters but never strips ANSI terminal escape sequences, an OSC 8 hyperlink becomes an unfiltered HTML anchor, and the response carries no Content-Security-Policy; a higher-privileged user (for example an administrator) who views that output page and clicks the link executes attacker-controlled JavaScript in their authenticated session, allowing actions up to full platform takeover. The vector is network-reachable with low privileges (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N, 8.7), but exploitation hinges on a privileged victim actively clicking the crafted link; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Stored password survey answers in Red Hat Ansible Automation Platform 2's automation-controller can be recovered in plaintext by an authenticated user holding the delegated JobTemplate Admin role. The attacker tightens the minimum/maximum length constraint on a password-type survey question, then forces revalidation of a schedule or workflow job template node created by a higher-privileged user, causing the controller to decrypt the stored secret and embed it in the HTTP length-validation error response. No public exploit identified at time of analysis; exploitation is not unauthenticated (CVSS PR:L) and requires both the delegated role and an existing password-type survey value, making this a lateral, privilege-crossing credential-disclosure issue rather than a mass-exploitable perimeter break.