Red Hat
Monthly
Authenticated users who already hold resource-management permissions can update UMA resources they do not own in Keycloak's authorization services when remote resource management is enabled, letting them alter other users' resource names, URIs and scopes. The flaw is an IDOR-style authorization bypass (CWE-639) rated CVSS 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), so integrity impact is limited and no confidentiality or availability impact is assessed. There is no public exploit identified at time of analysis, no confirmed active exploitation (CISA KEV), and the issue is only reachable when the non-default remote resource management feature is turned on and the attacker is an authenticated user with the relevant permissions.
dnsmasq's DHCPv6 client hostname parser can read one byte past the end of a crafted FQDN option when the server processes a single DHCPv6 packet from an attacker on the same local link. The over-read byte is neither returned to the client nor logged, and no crash or confirmed information disclosure has been demonstrated; the independent assessment scores confidentiality, integrity, and availability impact as none, so real-world risk is low despite the genuine memory-safety defect. No CISA KEV entry or public exploit code was identified at time of analysis.
DHCP lease metadata disclosure in dnsmasq (CVE-2026-93010) occurs when the DHCP leasequery feature has been switched on without an allow-list of permitted query sources, letting any host on the local network pull lease records - assigned IP addresses, MAC addresses, hostnames and related lease metadata. The package is shipped across Red Hat Enterprise Linux 6 through 10 and is bundled into Red Hat OpenShift Container Platform 4, Ceph Storage 9 and OpenStack Platform builds, but the vulnerable feature is off unless an administrator explicitly enables it. Severity is capped at a confidentiality-only leak (CVSS 4.3, adjacent-network attack vector), and no public exploit code or active exploitation has been identified at time of analysis.
TFTP file substitution in dnsmasq allows an attacker on the local network to make a later client receive stale, previously cached transfer data instead of the file it requested; in PXE network-boot deployments this can substitute attacker-chosen boot content for a victim machine, giving both confidentiality and integrity impact. The flaw only exists when dnsmasq is running with its TFTP server feature enabled (a non-default configuration used for network boot), requires adjacent-network access (AV:A) with no authentication (PR:N) and no user interaction (UI:N), but is rated high complexity (AC:H) because the attacker cannot control when another client will request the same file and pick up the cached response. There is no CISA KEV entry and no public exploit code identified at time of analysis, and the vendor-reported CVSS 3.1 score is 6.8, making this a moderate, situational issue rather than an emergency; Red Hat tracks it for remediation within the current monthly cycle.
Denial of service against dnsmasq's TCP DNS service: remote attackers can occupy the entire small fixed pool of TCP child processes by holding idle connections open to port 53, which blocks new TCP DNS queries and any DNSSEC validation that depends on TCP fallback. The flaw is packaged in Red Hat Enterprise Linux 6, 7, 8, 9 and 10 as well as Red Hat OpenShift Container Platform 4, Ceph Storage 9 and OpenStack Platform 13 (Queens) and 18.0, so any of those deployments exposing TCP/53 to untrusted networks is in scope. Impact is confined to availability and is time-bounded rather than permanent - UDP resolution keeps working and occupied slots are released after a fixed lifetime - and no public exploit identified at time of analysis.
dnsmasq builds that include the DNSSEC validator and have validation enabled at runtime can write a few bytes past an internal domain-name buffer when converting names to and from DNS wire format, corrupting adjacent heap metadata. Only deployments where DNSSEC support was compiled in and DNSSEC validation is switched on are exposed; the default dnsmasq build omits DNSSEC entirely, and exploitation further requires an attacker to make the resolver validate a crafted DNSSEC response, for example through a spoofed or attacker-controlled answer for a signed name. Rated CVSS 5.3 (integrity-only, low impact) and no public exploit identified at time of analysis; the priority signal is this_month, not immediate action.
A DNS cache-poisoning flaw in dnsmasq (CWE-345, insufficient verification of data authenticity) lets a malicious or compromised upstream resolver inject cached records for names outside its authoritative zone when dnsmasq follows a CNAME in a response. Only split-DNS deployments that forward specific domains to a designated upstream are realistically exposed, since the attacker must already occupy that trusted upstream position; standard single-forwarder or root-hint setups are far less affected. Impact is integrity-only (attacker-chosen addresses returned to later clients), rated CVSS 6.8 with AC:H, and no public exploit code or KEV entry was identified at time of analysis, so priority follows the vendor's this-month cadence rather than emergency response.
Keycloak's HOTP one-time-password authentication flow can accept the same code more than once: the keycloak-services component verifies the OTP and advances its stored counter in two non-atomic steps, so concurrent login requests can slip through the gap before the counter is updated. The attacker must already know the victim's password and hold one currently valid HOTP code, and must win a narrow race (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N, 4.2), so the practical gain is replay of a single code for simultaneous sessions rather than an authentication bypass; Red Hat build of Keycloak and Red Hat Single Sign-On 7 are the affected distributions. This is a medium-severity, defense-in-depth weakness rather than an emergency - no public exploit code or active exploitation is identified at time of analysis, and the priority label places it in the normal monthly remediation cycle.
Keycloak's keycloak-services PAR (Pushed Authorization Request) implementation can be induced to issue multiple access tokens from a single authorization request that is supposed to be single-use, by restarting the authentication flow so that internal PAR-consumption markers are cleared while the request stays active. Affected components are Red Hat Build of Keycloak and Red Hat Single Sign-On 7 deployments that actually have OAuth 2.0 PAR in use; the CVSS vector (PR:L) means the attacker must already be able to initiate and restart an authentication flow as a client or user, so this is not reachable by a fully unauthenticated outsider. Impact is limited to confidentiality and integrity of the token issuance path (C:L/I:L, no availability impact); there is no CISA KEV entry and no public exploit identified at time of analysis, and the priority label is 'this_month' rather than an emergency.
An information disclosure flaw in Keycloak's client registration component lets an authenticated client owner read secrets they should not be able to access when the deployment uses a vault provider (Vault SPI) to store sensitive values. The attacker sets a client's secret to a crafted reference pointing at a vault entry, then retrieves the client configuration and sees the resolved secret in plain text, exposing credentials such as those held in HashiCorp Vault. Exploitation requires a non-default vault integration plus valid client-owner credentials; the issue is rated moderate (CVSS 5.3, C:H with AC:H in the upstream vector, assessed as AC:L), and no public exploit or active exploitation is identified at time of analysis.
Crashing 389-ds-base directory servers is possible for an authenticated LDAP user who holds ModifyDN permission on an entry: renaming it with a schema alias such as 'commonName' instead of the canonical 'cn' causes a NULL pointer dereference and denial of service. The flaw affects Red Hat Directory Server 11, 12, and 13 and the 389-ds-base packages in Red Hat Enterprise Linux 6 through 10; exploitation requires valid credentials plus an explicit modrdn ACI, so anonymous or read-only users cannot trigger it. No public exploit identified at time of analysis, and the impact is limited to availability with no data disclosure or modification, making this a moderate-priority availability issue rather than a top-tier emergency.
Keycloak's JWT Authorization Grant implementation skips the claim-filtering and login restrictions configured on OIDC or Google identity providers, so an authenticated client using that grant can obtain access tokens for users whose IdP claims should have blocked login. Red Hat Build of Keycloak and Red Hat Single Sign-On 7 are in the affected CPE set, and the issue is rated CVSS 5.4 (PR:L) with low confidentiality and integrity impact and no availability impact. The supplied data contains no CISA KEV entry and no public exploit identified at time of analysis; exploitation requires a restricted OIDC/Google IdP plus an authenticated client able to use the JWT grant flow.
Information disclosure in Red Hat JBoss Enterprise Application Platform 7 and 8 (plus EAP Expansion Pack and Red Hat Single Sign-On 7, which embed the same management layer) lets any authenticated management user holding a low-privileged role such as Monitor read JVM system properties and configuration details that should be restricted, because the handler for the read-resource operation on the platform-mbean runtime resource omits its RBAC check. The CVSS 3.1 score is 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N): the requirement for an existing low-privileged management account (PR:L) caps the severity, and the impact is confidentiality-only with no write, code-execution or denial-of-service path. There is no CISA KEV listing and no public exploit identified at time of analysis, and the vendor-reported issue is tracked as CWE-862 (Missing Authorization); priority is this_month, since the practical value of the leak depends on whether a given deployment stores secrets in JVM system properties.
When cross-site (xsite) TLS is enabled, the Infinispan Operator for Red Hat Data Grid 8 launches the Gossip Router container with the keystore and truststore passwords as plain-text command-line arguments, so any principal holding `get pods` in the namespace - without needing `get secrets` - can read those credentials directly from the Pod spec. The same values are exposed to node-level processes through `/proc/<pid>/cmdline` and are frequently captured in audit and event logs. Rated 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), this is a moderate-priority information-disclosure issue that only manifests in a non-default operator-driven configuration; no public exploit code and no CISA KEV entry were identified at time of analysis.
gssproxy can be persistently crashed by any local user who can reach its Unix domain socket: a GSSX_INIT_SEC_CONTEXT request that omits the target_name field triggers a NULL pointer dereference in the daemon. The issue affects gssproxy deployments on Red Hat Enterprise Linux 7, 8, 9, and 10 and is listed for Red Hat OpenShift Container Platform 4; because gssproxy does not automatically restart, Kerberized NFS and IdM services that depend on it can be disrupted until an administrator intervenes. No public exploit identified at time of analysis.
An out-of-bounds heap read in open-iscsi's iscsiuio daemon allows an attacker on the same network segment to crash the daemon, overwrite a single heap byte, or corrupt the stored iSCSI initiator name by sending a crafted DHCPv6 Advertise message. The flaw is in the DHCPv6 option parser, which calls strlen() on raw option data that carries no guaranteed NUL terminator, so the scan walks past the end of the buffer; open-iscsi packages as shipped in Red Hat Enterprise Linux 6, 7, 8, 9 and 10 are listed as affected, but only hosts that actually run iscsiuio and obtain iSCSI parameters over DHCPv6 (offload/boot deployments) are exposed, since the daemon is not default-active on typical systems. No public exploit code has been identified at time of analysis and there is no CISA KEV listing; combined with the adjacency-only attack path this yields a medium severity (CVSS 6.3) and a this-month rather than emergency priority.
libslirp user-mode networking can disclose the host's real IP address to a guest when an ICMP echo request is handled through the fallback path and the reply length is not updated to match the actual data received. The flaw affects libslirp as shipped in Red Hat Enterprise Linux 8, 9, and 10 and Red Hat OpenShift Container Platform 4, with exposure limited to guests using slirp-style user-mode networking rather than bridged or tap networking. Rated CVSS 3.5 with a monitor priority, exploitation requires a guest-level user able to send ICMP echo requests plus a host-side condition the attacker does not control, and no public exploit has been identified at time of analysis.
Improper authorization in FreeIPA lets any enrolled host retrieve and revoke X.509 certificates belonging to other users or services, disrupting those services, because ownership is checked only by matching the host name to the certificate subject Common Name. The flaw is moderate severity (CVSS 5.4) and requires an authenticated host principal (PR:L); Red Hat tracks it for remediation this month, and no public exploit was identified at time of analysis.
Arbitrary file write in the OpenShift oc client's image extract command allows an attacker who supplies a malicious container image to place content outside the intended extraction directory with the privileges of the user running oc image extract. Red Hat OpenShift Container Platform 4 is affected because the client does not properly sanitize symbolic and hard link targets that are absolute paths or sibling directories, and the impact is limited to integrity (CVSS 5.5, AV:L/UI:R). No public exploit code or confirmed active exploitation has been identified in the available intelligence, and the risk is assessed as real but non-urgent.
Arbitrary file creation outside the intended working directory affects users and automated workflows running GNU patch, specifically when automatic patch reversal processes a crafted patch whose header contains an absolute file path that is accepted instead of rejected. The result is limited to integrity impact: files can be created in arbitrary locations, but only with the permissions of the user or pipeline account executing the utility, with no confidentiality or availability impact and no privilege gain beyond that account's existing rights. Exploitation requires a local attack vector and user interaction - a victim or a CI/CD pipeline must apply the attacker-supplied patch - and no public exploit, PoC reference, or CISA KEV entry is present in the available data; the assigning vendor is Red Hat, with RHEL 6 through 10 and Red Hat Hardened Images listed as affected.
The system CA trust store shipped in Red Hat's ca-certificates RPM packages includes eMudhra root authorities that signed intermediate CA certificates protected by weak private keys, so a man-in-the-middle attacker who can intercept traffic and who can factor or guess those keys could mint certificates for arbitrary hostnames that TLS clients using the system trust store would accept (CVSS 6.8, CWE-295). Affected platforms span Red Hat Enterprise Linux 6 through 10 plus a long list of layered products such as OpenShift Container Platform 4, Satellite 6, Quay 3, Advanced Cluster Management, and the cert-manager and logging operators. Attackers need a privileged network position and a victim client that actually initiates a TLS connection validated against the system store, so this is a trust-anchoring and impersonation problem rather than a remotely reachable code-execution flaw; there is no availability impact and no public exploit code identified at time of analysis. Because individual intermediate certificates cannot be selectively distrusted across every consumer of the system store, Red Hat is removing the parent root CAs outright, which is the crux of the remediation.
Path traversal in OpenSCAP's Source DataStream (SDS) decomposition can allow a crafted datastream to create or modify files outside the intended output directory with the permissions of the process performing the decomposition. The issue affects OpenSCAP as shipped in Red Hat Enterprise Linux 6 through 10 and Red Hat Hardened Images; exploitation is local and requires the victim user or automated system to decompose an attacker-supplied SDS containing directory traversal sequences. No public exploit code or CISA KEV entry was identified at time of analysis, and the CVSS 3.1 score is 6.1 (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L).
Keycloak can bypass mandatory OTP enrollment during login when a realm orders the 'Update User Locale' required action before 'Configure OTP,' allowing an attacker who already holds a valid password to access the account without setting up the required one-time password credential. The issue affects Red Hat build of Keycloak and Red Hat Single Sign-On 7 and carries a low CVSS score of 4.2 because exploitation requires a non-default administrative ordering and prior knowledge of valid credentials. No public exploit code has been identified at time of analysis.
Path traversal in the Undertow web server's PathResourceManager, which serves static files from the filesystem, lets remote attackers read files outside the intended static-content root when a symbolic link resolves into a sibling directory whose name begins with the same characters as an authorized safe directory (for example 'reports' versus 'reports-internal'). The root cause is a string-prefix check that never verifies a full path-segment or directory boundary, so it fails to confirm the link's canonical target actually resides inside the approved directory. Affected deployments are those bundling Undertow's static resource handling, as reflected by Red Hat's CPEs for JBoss Enterprise Application Platform 7 and 8, Red Hat Fuse 7, Red Hat Build of Apache Camel for Spring Boot 4, Red Hat Single Sign-On 7, and RHEL 8/9 packages; the assessed severity is low (CVSS 3.1 base 3.7, AV:N/AC:H/PR:N/UI:N/C:L/I:N/A:N) because exploitation demands a pre-existing symlink plus a directory-name collision, and the outcome is limited to low-confidentiality file disclosure with no write or availability impact. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the signals align on low real-world risk.
A file descriptor leak in the containers/storage Go library's archive.ApplyLayer and ApplyUncompressedLayer functions causes descriptors to be left open whenever corrupt or malicious image layers or tar streams are unpacked, and repeated processing of such inputs can exhaust the hosting process's file descriptor limit. The weakness is unauthenticated in CVSS terms (PR:N) but local in scope (AV:L) and requires the victim to actually process attacker-influenced layers (UI:R), so an attacker must first get malformed image content in front of a build, pull, or sync loop. Impact is availability-only and confined to the affected process (C:N/I:N/A:L, S:U): no code execution and no data exposure; a single bad input does not cause denial of service, only sustained repetition does. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, and EPSS scoring was not supplied with the source data.
An authenticated user who is permitted to submit evaluation jobs in Red Hat OpenShift AI's lm-evaluation-harness component can supply an attacker-controlled model URL in the JobSpec, causing the evaluation job pod to send the tenant's model authentication secret to an external listener the attacker controls. The same user-controlled URL handling allows Server-Side Request Forgery against internal endpoints reachable from the evaluation pod's network namespace, so internal services can be probed or reached with the pod's network position rather than the attacker's. The impact is confidentiality-only (CVSS 3.1 base 6.5, PR:L, C:H/I:N/A:N), no public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation is gated on valid tenant job-submission credentials plus network reachability from the pod.
An out-of-bounds read in libmodulemd's modulemd v2 rpm-map YAML serialization path can crash applications that process crafted module metadata, producing a local denial of service. The bug is triggered only when the metadata declares multiple digest algorithm types and is serialized through the affected path; default single-digest metadata does not trigger it. The assessed impact is availability-only, with no confirmed code execution or data exposure, and no public exploit code or CISA KEV entry was identified at time of analysis.
Stack exhaustion in libmodulemd's xmd (extended metadata) parser lets anyone who can place crafted modulemd YAML in front of a consuming process crash it or exhaust its resources, an availability-only denial of service (CVSS 6.2, C:N/I:N/A:H). The defect is in the recursive YAML mapping/sequence helpers that convert xmd content into nested GVariant values with no recursion-depth or node-count ceiling, so deeply nested input overflows the stack. Affected builds ship in Red Hat Enterprise Linux 8, 9 and 10, Red Hat Hardened Images, and OpenShift Container Platform 4; the vector AV:L/PR:N/UI:N means the attacker must first get the malicious metadata onto a host that parses it (for example an attacker-controlled or third-party module repository consumed by DNF/libdnf), after which no authentication or user interaction is required. No public exploit code and no confirmed active exploitation were identified in the available intelligence at time of analysis.
Denial of service in libmodulemd can be triggered when a build compiled with rpmio support parses a highly compressible modulemd YAML file; the custom decompression read handler does not cap cumulative decompressed output before parsing, allowing CPU and memory exhaustion that can hang or crash the consuming process. The issue is scored CVSS 6.2 with a LOCAL vector, requires no authentication or user interaction once a malicious file reaches the parser, and is associated by CPE data with Red Hat Enterprise Linux 8, 9, and 10 plus related OpenShift and hardened image products. No public exploit code or CISA KEV-listed active exploitation was identified in the supplied intelligence.
An out-of-bounds read in device-mapper-multipath's multipathd daemon allows local users who can submit commands to the daemon's control interface to read past the end of a buffer by supplying a command whose format string ends in a trailing percent character, exposing unintended daemon memory (limited information disclosure) or crashing multipathd to cause a denial of service. Local attackers need no prior privileges on the host per the CVSS vector (PR:N), but exploitation requires a local account on a system where multipathd is running and reachable. Affected products include Red Hat Enterprise Linux 6, 7, 8, 9 and 10 plus Red Hat OpenShift Container Platform 4, which ships the component in its RHEL-based node stack. No public exploit code has been identified at time of analysis and there is no CISA KEV listing; impact is bounded to confidentiality and availability (5.1, C:L/A:L), with no code execution or integrity impact.
Local credential disclosure in cockpit-machines, the Cockpit web module for managing libvirt/KVM virtual machines on Red Hat Enterprise Linux 9 and 10, exposes a guest VM's VNC console password to other unprivileged users on the same host. When an operator saves VNC console settings, the configured password is handed to an underlying system utility as a command-line argument, so any local user able to inspect another user's process entries can read the secret during that brief window. Exploitation requires an already-authenticated local account (PR:L), a host without hidepid-style process hiding, and a concurrent victim save action (UI:R); no public exploit code exists and the flaw is not in CISA KEV.
Information disclosure in cockpit-machines on Red Hat Enterprise Linux 9 and 10 lets a local unprivileged user capture RHSM authentication tokens from the command line of a short-lived image-retrieval helper process when cross-user process inspection is enabled. The attacker needs a local shell account and a concurrent image-retrieval operation by another user; stolen tokens can be used against RHSM resources only until they expire. This is a moderate-risk, low-urgency issue with no public exploit identified at time of analysis, and it does not provide remote access, code execution, or integrity/availability impact.
Denial of service in GIMP is triggered by importing a crafted SBZ palette file that lacks a color-model attribute, causing a NULL pointer dereference during string comparison in the palette parser. The flaw affects GIMP as packaged in Red Hat Enterprise Linux 6 through 10, requires local delivery of a malicious file and user interaction to import it, and results only in application crash with no confidentiality, integrity, or code-execution impact. No public exploit code or confirmed active exploitation was identified at time of analysis.
Denial of service in the GStreamer ASF demuxer (gst-plugins-ugly), rated CVSS 6.5, allows a crafted ASF, WMV, or WMA file to drive an oversized heap allocation because an attacker-controlled Simple Index entry count is not bounded by the object's actual payload. The issue affects gst-plugins-ugly packages in Red Hat Enterprise Linux 7, 8, 9, and 10; exploitation requires a victim to open or preview the malicious media file, with an unauthenticated network vector and user interaction required, and impact is limited to availability loss with no code execution or data exposure. No public exploit identified at time of analysis.
Local privilege escalation in Red Hat rhc's rhc-canonical-facts.service lets an attacker who has already compromised the privileged yggdrasil service account pre-plant a symbolic link so the root-run unit follows it and changes ownership of an arbitrary file, enabling escalation to root. The flaw is CWE-59 link following and affects rhc installations on Red Hat Enterprise Linux 7, 8, 9, and 10 per CPE data; exploitation is local-only and requires high privileges (CVSS PR:H), so risk is confined to systems where the yggdrasil account is already reachable. No public exploit code was identified in the provided sources at time of analysis, and no CISA KEV or EPSS signal was supplied.
Repeated state-notification requests sent to a network-reachable rpc.statd service in nfs-utils cause memory allocated during callback processing to never be released, producing continuous memory growth that can degrade or crash the service and exhaust host resources. The flaw is remotely triggerable without authentication (CVSS:3.1/AV:N/AC:H/PR:N/UI:N) but exploitation is not trivial: a single request is insufficient because the attacker must sustain a stream of requests long enough to exhaust memory, which is why the vector carries AC:H and the impact is availability-only (C:N/I:N/A:H, base score 5.9). Exposure is limited in practice because rpc.statd only runs when NFSv3 locking services are active and is normally bound to internal or trusted networks rather than the public internet, so firewalled or default deployments are not reachable. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; this is a genuine but moderate-priority availability issue rather than a top-tier emergency, and affected services can be recovered by a restart.
Arbitrary file deletion in GNOME Nautilus (GNOME Files) affects desktop users on Red Hat Enterprise Linux 6 through 10 and other distributions shipping the file manager: when a removable drive or disk image is unmounted or ejected, Nautilus offers to empty the trash without verifying that the volume's trash directory paths are symbolic links. An attacker who persuades a local, authenticated user to mount a crafted storage volume and then confirm that prompt can have files the victim has permission to delete removed through the symlinked path. The issue carries a moderate CVSS 3.1 score of 6.6 (AV:L/PR:L/UI:R, integrity and availability High, confidentiality None), and no public exploit identified at time of analysis; successful abuse requires a local desktop session, attacker-supplied media, and explicit user confirmation of the dialog.
Use-after-free in libarchive's archive_entry_copy_mac_metadata() function allows an attacker who can influence the input an application feeds that API to crash the linked application or cause it to read uninitialized heap memory, yielding a CVSS 3.1 base score of 3.6 (AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L). The flaw is not remotely reachable by default and requires the consuming application to perform a self-copy in which the source buffer overlaps the entry's existing mac_metadata pointer; it is a genuinely low-priority memory-safety issue with impact limited to denial of service and minor information disclosure, with no integrity or code-execution outcome. No public exploit code and no confirmed active exploitation were identified at time of analysis, and Red Hat has published an upstream fix (libarchive PR #3318) alongside its advisory and Bugzilla tracking entry.
Denial of service and limited memory disclosure in GIMP's Bohemia Interactive (PAA) texture importer, triggered when a user opens or previews a specially crafted .paa file through the affected plug-in. An integer overflow in the image-dimension calculation during decompression causes an undersized heap buffer to be allocated, and the subsequent out-of-bounds read crashes the plug-in process and may expose fragments of heap memory (CVSS 3.1 base 6.1, AV:L/PR:N/UI:R, C:L/A:H). The attack requires the victim to deliberately load the malicious file locally, so there is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV) - this is assessed as a moderate-severity, low-priority issue in practice.
Unbounded decoding of PMAPPROC_DUMP replies in libtirpc lets a malicious or already-compromised RPC portmapper exhaust the memory and CPU of a client application that calls pmap_getmaps(), crashing or stalling the client process and causing a denial of service. The exposure is conditional and client-side: a remote attacker cannot initiate the exchange, so the victim must direct libtirpc-based tooling (NFS/RPC mount helpers, discovery or inventory scanners) at the attacker-controlled rpcbind, which is why the assessed vector is AV:N/AC:H/PR:N/UI:R with availability-only impact and no confidentiality, integrity, or code-execution consequences. Affected packages are those shipped in Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4. At CVSS 5.3 this is a moderate-severity, low-priority issue in practice, and no public exploit code and no confirmed active exploitation (no CISA KEV listing) were identified at time of analysis.
Denial of service in libtirpc allows an authenticated remote RPC client to exhaust server memory by sending oversized wrapped-data requests to an RPC service that is configured with RPCSEC_GSS integrity (rpc_gss_svc_integrity) or privacy (rpc_gss_svc_privacy) protection. Only services explicitly running in that non-default, Kerberos-backed mode are exposed - most commonly NFS deployments on Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4 - and the impact is availability-only (CVSS 6.5, A:H) with no confidentiality or integrity effect. No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing), so it warrants medium-priority patch tracking rather than emergency response, although affected RPC services can become unstable or terminate under the resource exhaustion.
Local denial of service in the nfs-utils fsidd daemon affects Red Hat Enterprise Linux 6, 7, 8, 9, and 10 as well as Red Hat OpenShift Container Platform 4; an authenticated local user with access to the fsidd Unix domain socket can send a malformed request that omits required arguments, triggering a CWE-617 assertion failure and crashing the daemon. The service remains unavailable for filesystem identifier lookups until restarted, giving this a CVSS 3.1 score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). No public exploit code has been identified at time of analysis.
Argument injection in libblockdev's NTFS and VFAT label-setting routines lets a local, unprivileged user smuggle command-line flags into the ntfslabel and fatlabel utilities through a filesystem label that begins with a dash. The vulnerable paths (bd_fs_ntfs_set_label() and bd_fs_vfat_set_label()) are reachable without administrator authentication via the udisks2 Filesystem.SetLabel() D-Bus method, but exploitation is strictly local and the assessed impact is low integrity only - no confidentiality or availability loss and no privilege escalation. No public exploit code has been identified at time of analysis, and the low CVSS score (3.3, AV:L/PR:L/I:L) reflects the limited blast radius rather than an unexplored attack surface.
Improper boundary validation of metadata slot values in luksmeta allows an attacker who can supply or modify a LUKS disk header to redirect wipe or load operations outside the intended metadata area, overwriting or zeroing encrypted payload data and causing persistent data loss and corrupted storage. The attack is confined to a local vector and requires high privileges - root-level write access to the raw block device, or inducing an administrator to process an attacker-supplied untrusted disk image whose header carries out-of-range slot values together with valid checksums. The impact is limited to integrity and availability, with no information disclosure; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the moderate CVSS of 6.0 reflects the substantial privilege barrier rather than the severity of the data-loss outcome.
Stored cross-site scripting in the Ansible Automation Platform unified UI lets an authenticated user who can publish or upload a collection to Automation Hub embed a link using a script-executing URL scheme (for example javascript:) in that collection's documentation; the Hub documentation renderer (formatPartURL in frontend/hub DocumentationParsers.tsx) writes the URL into a link without validating its protocol, so the script executes in the Hub UI origin when a second authenticated user opens the collection documentation page and clicks the link. Red Hat scores it CVSS 3.1 5.4 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) - low confidentiality and integrity impact with a scope change, since the injected script runs with the privileges of the Hub origin rather than staying inside the published content. The flaw ships in the AAP 2.6 and 2.7 release branches only; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and exploitation requires both a malicious publisher and a victim who actively activates the crafted link.
An out-of-bounds write in the DPDK vhost-crypto backend allows a guest VM to overflow a host-side buffer and crash the host data plane. The flaw combines an integer overflow in the chain-length validation logic with missing length checks on the RSA request path, so crafted virtio-crypto descriptors can bypass size validation and corrupt host memory. Exposure is confined to hosts that have explicitly enabled the vhost-crypto (virtio-crypto) backend, exploitation requires low-privileged access from within a guest, and no public exploit code has been identified at time of analysis, with no confirmed active exploitation (CISA KEV).
An out-of-bounds write in the DPDK lib/vhost vhost-crypto backend lets a guest VM that is authorized to issue vhost-crypto requests corrupt host memory by supplying an avail-ring descriptor index that the backend uses without validating it against the ring size. The affected code ships in Red Hat Fast Datapath packages for RHEL 8, 9, and 10 and is therefore inherited by related RHEL, Red Hat OpenShift Container Platform 4, and Red Hat OpenStack Platform 13 (Queens) deployments that consume those DPDK builds. Exploitation is restricted to hosts where the vhost-crypto backend is actually enabled and a virtio-crypto device is exposed to a guest (CVSS 6.5, AV:L/PR:L/S:C), and the assessed outcome is host datapath denial of service rather than data disclosure or modification; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV.
Guest-to-host denial of service in the DPDK vhost library (lib/vhost) allows a malicious or misbehaving guest to underflow the copy length in the vhost enqueue path by supplying runt RX descriptors, which can stall or crash a shared host-side vhost backend such as OVS-DPDK. The flaw is rated CVSS 6.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H, mapped to CWE-191) and is only reachable by an attacker who already controls a guest VM (local-to-host scope, PR:L) - not by a remote unauthenticated network attacker - with impact limited to availability (no confidentiality or integrity effect). No public exploit was identified at time of analysis and there is no CISA KEV listing for this CVE; no vendor-released patch was identified at the time of analysis.
Host-side denial of service and potential memory corruption in DPDK's lib/vhost arise because memory-region sizes are not adequately validated before mmap during vhost memory-region setup (CWE-770). The affected code ships to customers through Red Hat Fast Datapath for RHEL 8, 9 and 10, and therefore reaches Red Hat Enterprise Linux 8/9/10, Red Hat OpenShift Container Platform 4 and Red Hat OpenStack Platform 13 (Queens) deployments that use DPDK vhost-user acceleration. An attacker who controls a connected vhost-user frontend - typically a guest VM or a process holding the vhost-user socket - can crash the host (CVSS 6.5, AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H); no public exploit code has been identified at time of analysis and there is no confirmation of active exploitation.
A time-of-check/time-of-use race in the DPDK vhost library's handling of virtio indirect descriptor tables allows an attacker who already controls a guest VM attached to a DPDK vhost-user backend to crash or disrupt the host vhost process by mutating the descriptor table length between the host's two reads from guest memory, or by supplying an out-of-range next index against a small host-side copy in the vDPA relay path. Exploitation requires local/guest-level low privilege (PR:L) and is heavily timing-dependent (AC:H), and the impact is confined to availability - the out-of-bounds bytes are consumed internally as descriptor fields for GPA translation and are never returned to the guest as payload, so no confidentiality or integrity loss is assessed. This is a moderate, defense-in-depth-class residual of the CVE-2018-1059 fix rather than an urgent priority, and no public exploit code was identified at time of analysis.
Local authenticated attackers can retrieve LUKS disk-encryption passphrases from hosts using the Clevis PKCS#11 pin because the clevis-pkcs11-afunix-socket-unlock daemon writes passphrases in plaintext to a world-readable log file. This affects Red Hat Enterprise Linux 7 through 10 and Red Hat OpenShift Container Platform 4 deployments where this non-default disk-unlock configuration is in use. No public exploit code has been identified at time of analysis; exploitation requires an existing low-privileged local account and prior logging of a LUKS unlock passphrase.
An out-of-bounds write in GStreamer's H.266/VVC Decoding Capability Information (DCI) parser inside libgstcodecparsers allows a remote attacker to crash or corrupt memory in any third-party application that directly calls the affected parsing API by supplying a crafted H.266 bitstream whose reserved DCI field carries an illegal value the parser wrongly accepts. Red Hat rates it CVSS 6.5 (Medium, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L) - network-reachable, unauthenticated and requiring no user interaction per the supplied vector, but with only Low integrity and Low availability impact and no confidentiality loss, consistent with a bounded out-of-bounds write (CWE-787). Exposure is sharply limited: the description states no standard GStreamer pipeline element invokes this code path, so default GStreamer installations and ordinary playback pipelines are not exploitable, and no public exploit has been identified at time of analysis.
Removing two packages in a single BusyBox dpkg invocation can silently drop the second package's stanza from the dpkg status file when the first package's stanza is larger than the second, leaving the package database inconsistent with what is actually installed. Only environments that compile in and actually use the BusyBox dpkg applet are affected - Red Hat lists Red Hat Hardened Images, whose minimal footprint typically relies on BusyBox applets, and any other image built with CONFIG_DPKG enabled. The assessed vector (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N, score 3.3) requires local execution plus a human performing the removal, yields integrity-only impact on the status file with no confidentiality or availability effect, and no public exploit or code execution path has been identified at time of analysis.
Local information disclosure in Red Hat Clevis's PKCS#11 pin lets an already-logged-in, low-privileged local user capture the PKCS#11 token PIN that clevis-decrypt-pkcs11 passes as a command-line argument to pkcs11-tool, from where it is readable through process listing or /proc/<pid>/cmdline. The issue affects Clevis as shipped with Red Hat Enterprise Linux 7, 8, 9 and 10 as well as Red Hat OpenShift Container Platform 4, and carries a CVSS 3.1 base score of 4.7 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N), reflecting high confidentiality impact but a local-only, high-complexity attack requiring a non-default configuration. Exploitation requires the PKCS#11 pin to be configured, a decryption operation to be in flight at the same moment, and the attacker to win a timing race against the short-lived pkcs11-tool process; no public exploit code and no confirmed active exploitation (not in CISA KEV) have been identified at time of analysis.
The clevis-luks-pkcs11-askpin helper shipped with Red Hat Enterprise Linux (7, 8, 9 and 10) and Red Hat OpenShift Container Platform 4 writes the PKCS#11 token PIN in cleartext to a file that is not given restrictive permissions, so under the default process umask the file is world-readable, and the file is also not reliably removed when the decryption script exits early, leaving the PIN readable indefinitely. The issue is assessed as CVSS 3.1 4.7 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N), meaning an authenticated local user with low privileges can obtain high-confidentiality secret material, but only on systems that actually use the non-default clevis PKCS#11 pin for LUKS unlocking. No public exploit code was identified at time of analysis and there is no CISA KEV listing; exploitation is local-only and the practical risk is confidentiality loss of the token PIN rather than a remote or code-execution threat.
Local attackers can exploit improperly secured AF_UNIX sockets in the clevis PKCS#11 pin to inject arbitrary device/key pairs or intercept LUKS passphrases, potentially gaining unauthorized access to encrypted disks. Affected products include Red Hat Enterprise Linux 7, 8, 9, and 10, as well as Red Hat OpenShift Container Platform 4. Exploitation requires an authenticated local user and a permissive process umask; no public exploit code or active exploitation has been identified, and the issue is rated modest priority due to the local-only attack vector and dependency on non-default umask settings.
Heap out-of-bounds write in the GStreamer ASF muxer plugin (asfmux) occurs when string metadata tags containing Unicode characters outside the Basic Multilingual Plane - such as emoji or supplementary-plane CJK characters - are written into an ASF/WMV container, because the buffer size calculation assumes 2 bytes per code point while UTF-16LE surrogate pairs actually require 4. Exploitation requires a local pipeline that muxes, remuxes, or transcodes attacker-supplied media into ASF while preserving metadata (AV:L, UI:R), enabling a user-assisted heap corruption that can cause a denial of service or limited memory corruption. Rated CVSS 6.1 with C:N/I:L/A:H, this is a medium-severity issue with a narrow attack path; no public exploit code and no confirmed active exploitation were identified at time of analysis, and affected packages are tracked for Red Hat Enterprise Linux 7, 8, 9, and 10.
An out-of-bounds read in BlueZ's btmon Bluetooth monitoring utility, as packaged in Red Hat Enterprise Linux 6 through 10, allows an attacker to crash the tool by getting a user to open a crafted btsnoop capture file containing an HCI Return Link Keys event that advertises more link keys than the packet actually contains. The flaw is local-access and interaction-dependent (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H) - the victim must deliberately load the malicious capture into btmon - which sharply limits real-world exposure given btmon is a diagnostic tool rarely pointed at untrusted input. No public exploit code or confirmed active exploitation was identified at time of analysis, and the practical outcome is a denial of service against the monitoring utility rather than any network- or privilege-escalation impact.
Crashing of the clevis-pkcs11-afunix-socket-unlock daemon in the clevis PKCS#11 pin allows a local attacker to cause a boot-time denial of service on hosts that rely on clevis for LUKS disk decryption. When a client connects to the daemon's AF_UNIX data socket without binding a client address, an integer underflow in the getpeername() result handling corrupts memory (CWE-787) and terminates the daemon, so LUKS unlock never completes and the system cannot finish booting. The issue is availability-only (CVSS 3.1 base 4.7, AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H), affects clevis on Red Hat Enterprise Linux 7, 8, 9 and 10 as well as Red Hat OpenShift Container Platform 4, and no public exploit has been identified at time of analysis; the vulnerable configuration is a non-default deployment choice and not present in a stock RHEL install.
A stack-based out-of-bounds write in GNOME Remote Desktop's VNC TLS read path, as shipped in Red Hat Enterprise Linux 8, 9, and 10, can crash the service and cause denial of service. An unauthenticated remote attacker (per the CVSS vector PR:N) who can reach an enabled VNC TLS listener and drive the connection into a peek/read size mismatch can corrupt memory on the stack; the vector rates this CVSS 5.9 with availability-only impact (C:N/I:N/A:H) and high attack complexity (AC:H), reflecting that the mismatch is non-trivial to trigger reliably. The vulnerable configuration is not default: remote desktop sharing must be explicitly enabled with the VNC backend and a reachable TLS listener, which is uncommon on headless or server RHEL installs; no public exploit code and no confirmed active exploitation were identified at time of analysis, and this should be handled as a routine patch rather than an emergency.
Crafted ISO-2022 encoded text passed to the m17n-lib decoder can trigger an uninitialized stack memory read, potentially leaking small amounts of process memory if the application then returns or displays the decoded output to the attacker. The issue is rated low severity (CVSS 2.5, AV:L/AC:H/UI:R, unauthenticated per vector PR:N) and affects multilanguage library builds shipped across Red Hat Enterprise Linux 6 through 10, though any application embedding m17n-lib's ISO-2022 handling is in scope. No public exploit identified at time of analysis; risk is gated by the fact that the deploying application must both decode attacker-supplied ISO-2022 input and reflect the decoded result back, which is uncommon in typical installations.
Denial of service in the openstack-network-exporter HTTP metrics server, as shipped in Red Hat OpenStack Platform 18.0, allows an unauthenticated remote attacker to open many slow HTTP header connections and exhaust server file descriptors, preventing legitimate Prometheus metric scraping and alerting. The component is deployed without a ReadHeaderTimeout or comparable connection timeouts, so any network-reachable instance is affected with no credentials or user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, 5.3). There is no public exploit identified at time of analysis and no evidence of active exploitation; impact is limited to monitoring availability and does not touch the OpenStack data plane, making this a modest availability issue best handled through routine hardening and network segmentation.
Server-side request forgery in Red Hat Quay allows an authenticated repository administrator to bypass the hostname blacklist enforced by the webhook notification feature, causing the Quay application to issue HTTP requests to attacker-chosen internal destinations such as cloud metadata endpoints or in-cluster services. Successful exploitation can disclose sensitive information returned by those internal services, though the CVSS 3.1 score of 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) reflects a moderate impact: the attacker must already hold a privileged in-application role, must use the webhook functionality, and the yield is bounded by which internal endpoints the Quay pod can actually reach. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the flaw is tracked by Red Hat under CVE-2026-85471 with all Quay 3 and Mirror Registry offerings listed as affected via wildcarded CPEs.
Improper validation of the user-supplied sort parameter in Quarkus REST Data Panache's auto-generated REST endpoints allows remote attackers to learn information about entity fields they should not have access to and to degrade performance by forcing the underlying database to perform expensive ordering operations, up to a denial of service. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L, 6.5) indicates the issue is network-reachable and unauthenticated per PR:N, with low confidentiality and availability impact; real-world exposure is deployment-specific because it requires an application that has enabled and externally exposed these generated endpoints. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Authenticated users of Red Hat Quay 3 can retrieve auto-prune policy configurations belonging to repositories in other namespaces, exposing configuration details that should remain tenant-scoped. Exploitation requires a valid Quay account, control of a repository whose name collides with the target's repository name, and prior knowledge of the target policy's unique identifier - conditions reflected in the CVSS 3.1 base score of 3.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N). Impact is confined to information disclosure, with no modification of data or denial of service, and no public exploit has been identified at time of analysis.
Build trigger management API in Red Hat Quay 3.x fails to verify that a requested trigger belongs to the specified repository, allowing an authenticated repository administrator to view, modify, or delete build triggers and associated write tokens in other repositories if they know the victim trigger's UUID. This is a moderate-severity authorization bypass (CWE-639) requiring prior knowledge of a random, non-enumerable UUID, which raises attack complexity (CVSS AC:H). As of analysis, no public exploit code has been identified; Red Hat has published an advisory and Bugzilla entry.
Authentication bypass in Keycloak's Client-Initiated Backchannel Authentication (CIBA) implementation allows public clients without a client secret to initiate backchannel login requests, enabling an attacker to trick a user into approving a malicious login and gain full access to the user's account. The flaw stems from Keycloak failing to verify that a client is authorized to use the CIBA flow, and exploitation requires the CIBA grant to be enabled, high attack complexity, and active user interaction to approve the request. No public exploit identified at time of analysis; the assessed CVSS is 6.8 (medium).
Broken access control (CWE-863) in Foreman's domain and subnet interface API lets an authenticated user who already holds a host-view permission and can see a shared domain or subnet read interface records for hosts outside their authorized scope; the API checks the host permission but omits its search-limit filter, returning every interface on the domain or subnet. A user who also holds host-edit permission can persist a change to one of those out-of-scope interfaces, giving limited confidentiality and integrity impact (CVSS 5.4, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N). Red Hat Satellite 6, which ships Foreman, is the affected product per CPE; no public exploit identified at time of analysis.
Authenticated users in Red Hat Satellite 6 (and the underlying Foreman permission-filter subsystem) can delete permission filters belonging to roles other than their own by abusing an API path that resolves filters by identifier without re-applying the caller's permission scope. The prerequisite is modest but not trivial: the attacker must already hold filter-delete rights for at least one role, and the victim roles must be unlocked - this is an insider or compromised semi-privileged account vector, not a default unauthenticated remote issue. Resulting impact is integrity-only (I:H, C:N/A:N) at CVSS 6.5, with other roles silently losing the access their deleted filters granted; no public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV).
Local privilege escalation and arbitrary code execution in the BusyBox tar applet (CVE-2026-108119) allow an attacker who supplies a crafted tar archive to create or replace files outside the extraction directory when the archive is extracted with elevated privileges. The flaw is a CWE-59 link-following issue in the applet's deferred symlink/hardlink creation path, with a CVSS 3.1 base score of 6.3 (AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H), affecting BusyBox as shipped in Red Hat Enterprise Linux 6 and Red Hat Hardened Images. No public exploit identified at time of analysis; exploitation requires a privileged user or process to actively extract the malicious archive, and the specific archive construction plus directory-reuse timing makes this high-complexity and local-only.
Opening a specially crafted XCF file in GIMP can crash the application through a NULL pointer dereference in the XCF loader's handling of image-simulation-intent and image-simulation-bpc parasites that carry zero-size data. The issue is confined to a denial of service of the GIMP process - there is no code execution, privilege escalation, or data exposure - and exploitation requires local access plus the victim manually opening an attacker-supplied file (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H, 5.5). No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV), though Red Hat tracks the affected GIMP packages shipped in RHEL 6 through RHEL 10; this is a genuine but low-priority issue.
Denial of service in libhangul can be triggered by a specially crafted Hanja dictionary file that contains an entry with a key but no valid value; parsing the file dereferences a NULL pointer and crashes the consuming application. Affected deployments include Red Hat Enterprise Linux 6 through 10 where the library is packaged, as well as any application that loads and queries such dictionaries. The CVSS vector (AV:L/PR:N/UI:R) means local delivery and user interaction are required, no privileges are needed, and impact is availability-only; no public exploit has been identified at time of analysis.
Null pointer dereference in OpenPrinting CUPS allows unauthenticated remote attackers who can submit jobs to a shared printer queue to crash the cupsd print daemon, causing a temporary denial of service for all printing services. Exploitation requires a vulnerable version that still ships the deprecated embedded job-ticket comment feature and a single crafted PostScript or PDF file submitted via the Print-Job operation whose first lines contain a malformed %cupsJobTicket: entry. Impact is bounded to a brief daemon crash with automatic restart-there is no code execution or data exposure-and no public exploit code has been identified at time of analysis.
Stored cross-site scripting in the login theme rendering component of Keycloak (and its downstream Red Hat Build of Keycloak and Red Hat Single Sign-On 7 products) lets a realm administrator inject malicious JavaScript into display fields that is later executed in the browsers of users loading the affected realm's login page. Exploitation requires an authenticated realm administrator (CVSS PR:H) who can both reach the theme display fields and bypass the input-sanitizing security filter, so this is a privilege-abuse or post-compromise vector rather than an anonymous remote attack; impact is limited to the confidentiality and integrity of affected users' sessions (C:L/I:L) with no availability impact. There is no public exploit identified at time of analysis and no CISA KEV listing; overall this is a genuine but modest-priority issue rather than a high-urgency crisis.
A heap-based buffer overflow in the PNG metadata reader of Eye of GNOME (eog) allows an attacker to potentially achieve arbitrary code execution or cause a denial of service (application crash) when a user opens a specially crafted PNG file. Exploitation requires user interaction and local access, but the vulnerability is unauthenticated (no privileges required) according to the CVSS vector PR:N. No public exploit code or confirmed active exploitation has been identified at time of analysis; the risk is constrained by the need for a user to open the malicious file on a system with eog installed.
Offline tokens issued by Keycloak, Red Hat Build of Keycloak, and Red Hat Single Sign-On 7 can stay valid after a backchannel logout because a serialization bug in the OIDC Dynamic Client Registration (DCR) response omits the backchannel-logout offline-token-revocation setting, silently disabling it whenever a client is updated through the standard update flow (CVE-2026-107623, CVSS 3.1 4.3, CWE-862). The actor must hold client-management/registration privileges (AV:N/PR:L), and the deployment must use DCR and rely on backchannel logout to revoke offline tokens, so this is a loss of a revocation guarantee rather than an account takeover. No public exploit code was identified at time of analysis and the issue is not in CISA KEV; EPSS signal is not available in the supplied data, and the assessed real-world risk remains low.
Keycloak, including the Red Hat Build of Keycloak and Red Hat Single Sign-On 7, exposes the active primary secret of confidential clients to any authenticated realm administrator who holds only the read-only view-clients role. The flaw sits in the installation provider and client registration endpoints, which return client credentials that a read-only administrator should never be able to read; with the leaked secret an attacker can authenticate as the confidential client and inherit its service account permissions across integrated services. Exploitation requires an existing realm administrator account with the view-clients role, so risk scales with how broadly that low-trust role is delegated, and no public exploit has been identified at time of analysis.
Data corruption in luksmeta allows a local attacker who already holds administrative privileges to damage or destroy metadata and encrypted payload data stored on a Linux Unified Key Setup (LUKS) device when a new metadata entry is saved. Because faulty free-space boundary calculations and flawed overlap detection can let new records be written past the available area or on top of existing ones, integrity is fully compromised though confidentiality is not (CVSS 5.1, AV:L/AC:L/PR:H/UI:N/C:N/I:H/A:L), and affected volumes may become inaccessible. Exploitation requires local host access with privileges sufficient to run luksmeta and write to the device; there is no remote or unauthenticated vector, no public exploit identified at time of analysis, and no confirmed active exploitation (not in CISA KEV), so impact is realistically limited to accidental or deliberate corruption by a privileged operator. The issue affects luksmeta as shipped with Red Hat Enterprise Linux 7, 8, 9 and 10, plus Red Hat OpenShift Container Platform 4 through the underlying RHCOS userland.
Information disclosure in flatpak-builder lets a crafted build manifest read sensitive host files and embed their contents into resulting build artifacts, because source download definitions that specify local file:// URIs bypass the tool's directory confinement checks. Exploitation requires a developer or CI system to actually process the untrusted manifest (user interaction per CVSS UI:R), so it is not remotely triggerable without someone initiating a build; no public exploit identified at time of analysis. Red Hat rates it moderate at CVSS 6.1, and the affected package ships in Red Hat Enterprise Linux 8, 9, and 10, with CI/CD pipelines that auto-build community-submitted manifests representing the highest-value target.
An authorization flaw in Katello's Flatpak Remote Repositories API allows an authenticated user who is permitted to view flatpak remotes in one organization to retrieve flatpak remote repository records - including the stored credentials for that remote - belonging to a different organization. The same unscoped lookup is reused by the mirror action, so a user with edit rights on a product in their own organization can create a repository configured with another organization's flatpak remote URL and its stored remote credentials. Exploitation requires an authenticated account holding the flatpak-remote view permission, the flatpak remote feature to be in active use, and a multi-organization Red Hat Satellite 6 / Katello deployment; no public exploit code has been identified at time of analysis, and the flaw is a medium-priority authenticated authorization issue rather than an emergency.
Cross-organization repository metadata disclosure in the Katello (Red Hat Satellite 6) Docker Tags repositories API allows an authenticated user who holds product-view permissions in one organization to retrieve repository configuration data for Docker meta tags owned by a different organization by simply supplying that foreign tag identifier. The weakness is an authorization-scoping gap (CWE-639, IDOR-style) correctly rated CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), with impact limited to low-severity confidentiality loss - there is no write or denial-of-service effect. Exploitation requires valid credentials, multi-organization deployment, and knowledge or enumeration of valid foreign tag identifiers; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and EPSS data was not supplied.
The cluster-samples-operator in Red Hat OpenShift Container Platform 4 assigns an overly permissive RBAC Role (coreos-pull-secret-reader) that grants get/list/watch on all Secrets in the openshift-config namespace, exceeding the operator's requirement for only the pull-secret Secret. This excessive-privilege weakness (CWE-250) does not provide initial access; an attacker must first compromise the operator pod or its service-account token through a separate vulnerability, after which they can read sensitive cluster secrets such as OAuth identity provider credentials and cloud provider credentials. No public exploit code is identified, and the issue is a defense-in-depth concern rather than a directly exploitable flaw (assessed CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).
Heap-based buffer overflow in GIMP's 'Hot' color filter plug-in allows a crafted, extremely large image to corrupt heap memory when the filter is invoked, giving an attacker the ability to crash the plug-in and potentially achieve code execution within the running user's session (CWE-119). The flaw is reachable only locally and requires the victim to open an attacker-supplied image with dimensions so large that the width * height allocation arithmetic overflows 32-bit integers, then actively run the Hot filter on it - hence the assessed vector AV:L/AC:H/PR:N/UI:R with high integrity and availability impact but no confidentiality impact. There is no public exploit identified at time of analysis, no CISA KEV listing, and no EPSS score provided, so this is a targeted, social-engineering-dependent client-side issue rather than an automatable, mass-exploitation threat. Red Hat hosts the primary advisory (access.redhat.com/security/cve/CVE-2026-106067) with tracking in Bugzilla 2547461, and GIMP packages across Red Hat Enterprise Linux 6 through 10 are enumerated as affected via CPE.
Exporting an oversized image through GIMP's raw data export plug-in can under-allocate a heap buffer and cause an out-of-bounds write on the heap, with the failure originating in an integer overflow in the g_malloc() size computation (width × height × bytes-per-pixel). Per the CVSS 3.1 vector (AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H), exploitation is local-only, requires the victim to actively start the export, requires no privileges (PR:N), and is gated by high attack complexity because the image dimensions must be crafted so the size arithmetic wraps; the assessment rates confidentiality impact as none and integrity/availability impact as high. No public exploit code and no confirmed active exploitation (no CISA KEV listing) were identified at time of analysis, and the EPSS-style signals provided are consistent with a moderate-priority rather than critical issue, since the plug-in is standard GIMP functionality but the trigger depends on user-driven export of deliberately large images.
Heap-based buffer overflow in GIMP's PCX export plug-in allows a local attacker to corrupt memory when a user opens or creates an image with extremely large width and height and exports it to PCX format. The flaw, tracked as CVE-2026-106065 with a CVSS score of 6.3 (AV:L/AC:H/PR:N/UI:R), stems from 32-bit integer overflow in the width*height size calculation while GEGL operations use the full extent. Affected GIMP packages ship with Red Hat Enterprise Linux 6 through 10; no public exploit code or active exploitation has been identified at time of analysis.
Symbolic-link traversal during archive unpacking in Red Hat's source-to-image (S2I) tooling lets an attacker who can supply or otherwise influence the builder image consumed by a build create links that resolve to absolute paths outside the extraction directory, allowing file reads or modifications beyond the intended sandbox on the host. The flaw is rated CVSS 3.1 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), so exploitation is not an unauthenticated drive-by: the attacker needs the privileges required to introduce or reference a malicious builder image, and only environments that run S2I builds against untrusted or attacker-influenced images are realistically exposed. The scope is marked Changed because the payload escapes the build container boundary, but confidentiality and integrity impact are each only Low; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Local denial of service in m17n-lib can crash applications on Red Hat Enterprise Linux 6 through 10 when they process specially crafted or truncated UTF-8 input. The flaw is a NULL pointer dereference reachable with a local attack vector and no authentication or user interaction, and it only affects availability, not confidentiality or integrity. No public exploit or confirmed active exploitation has been identified at time of analysis, and the issue is assessed as a moderate-severity local DoS rather than a high-priority remote threat.
Heap use-after-free in m17n-lib's input-method handling allows a local user who supplies specially crafted text to an application using m17n-based input engines to crash that application, producing a denial of service; arbitrary code execution is described as a potential, unverified outcome rather than a demonstrated one. The flaw is rated CVSS 6.2 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), so exploitation is local with no privileges required (PR:N) and no user interaction, and the only confirmed impact is availability loss with no confidentiality or integrity effect. Red Hat tracks the issue for Red Hat Enterprise Linux 6 through 10, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Integer overflow in GIMP's GIF export plug-in leads to a heap-based buffer overflow when a user exports an image whose width and height are large enough to wrap the 32-bit pixel-buffer size calculation, resulting in an out-of-bounds write that can crash the application or corrupt memory. Affected software is the GIMP package as distributed in Red Hat Enterprise Linux 6, 7, 8, 9 and 10, and exploitation is local (AV:L) with high attack complexity (AC:H) and mandatory user interaction (UI:R) while requiring no privileges (PR:N) - the attacker must induce a user to export an image with extreme dimensions. No public exploit identified at time of analysis, and the independent assessment rates this a moderate-severity, genuinely low-urgency issue rather than a top priority.
Local denial of service in m17n-lib, the multilingual input-method library shipped in Red Hat Enterprise Linux 6 through 10, can crash an application that opens an input method: a partial failure during library initialization leaves an internal driver pointer uninitialized, and the subsequent dereference is performed without validation. The assessed risk is genuinely low (CVSS 3.1 base 2.9; AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L), because the trigger - system resource exhaustion or corruption of the input-method database - is rare and cannot be reliably forced, the vector is local rather than remote, and the impact is confined to an application crash with no confidentiality or integrity effect. No public exploit identified at time of analysis, and there is no indication of active exploitation (not in CISA KEV).
Authenticated users who already hold resource-management permissions can update UMA resources they do not own in Keycloak's authorization services when remote resource management is enabled, letting them alter other users' resource names, URIs and scopes. The flaw is an IDOR-style authorization bypass (CWE-639) rated CVSS 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), so integrity impact is limited and no confidentiality or availability impact is assessed. There is no public exploit identified at time of analysis, no confirmed active exploitation (CISA KEV), and the issue is only reachable when the non-default remote resource management feature is turned on and the attacker is an authenticated user with the relevant permissions.
dnsmasq's DHCPv6 client hostname parser can read one byte past the end of a crafted FQDN option when the server processes a single DHCPv6 packet from an attacker on the same local link. The over-read byte is neither returned to the client nor logged, and no crash or confirmed information disclosure has been demonstrated; the independent assessment scores confidentiality, integrity, and availability impact as none, so real-world risk is low despite the genuine memory-safety defect. No CISA KEV entry or public exploit code was identified at time of analysis.
DHCP lease metadata disclosure in dnsmasq (CVE-2026-93010) occurs when the DHCP leasequery feature has been switched on without an allow-list of permitted query sources, letting any host on the local network pull lease records - assigned IP addresses, MAC addresses, hostnames and related lease metadata. The package is shipped across Red Hat Enterprise Linux 6 through 10 and is bundled into Red Hat OpenShift Container Platform 4, Ceph Storage 9 and OpenStack Platform builds, but the vulnerable feature is off unless an administrator explicitly enables it. Severity is capped at a confidentiality-only leak (CVSS 4.3, adjacent-network attack vector), and no public exploit code or active exploitation has been identified at time of analysis.
TFTP file substitution in dnsmasq allows an attacker on the local network to make a later client receive stale, previously cached transfer data instead of the file it requested; in PXE network-boot deployments this can substitute attacker-chosen boot content for a victim machine, giving both confidentiality and integrity impact. The flaw only exists when dnsmasq is running with its TFTP server feature enabled (a non-default configuration used for network boot), requires adjacent-network access (AV:A) with no authentication (PR:N) and no user interaction (UI:N), but is rated high complexity (AC:H) because the attacker cannot control when another client will request the same file and pick up the cached response. There is no CISA KEV entry and no public exploit code identified at time of analysis, and the vendor-reported CVSS 3.1 score is 6.8, making this a moderate, situational issue rather than an emergency; Red Hat tracks it for remediation within the current monthly cycle.
Denial of service against dnsmasq's TCP DNS service: remote attackers can occupy the entire small fixed pool of TCP child processes by holding idle connections open to port 53, which blocks new TCP DNS queries and any DNSSEC validation that depends on TCP fallback. The flaw is packaged in Red Hat Enterprise Linux 6, 7, 8, 9 and 10 as well as Red Hat OpenShift Container Platform 4, Ceph Storage 9 and OpenStack Platform 13 (Queens) and 18.0, so any of those deployments exposing TCP/53 to untrusted networks is in scope. Impact is confined to availability and is time-bounded rather than permanent - UDP resolution keeps working and occupied slots are released after a fixed lifetime - and no public exploit identified at time of analysis.
dnsmasq builds that include the DNSSEC validator and have validation enabled at runtime can write a few bytes past an internal domain-name buffer when converting names to and from DNS wire format, corrupting adjacent heap metadata. Only deployments where DNSSEC support was compiled in and DNSSEC validation is switched on are exposed; the default dnsmasq build omits DNSSEC entirely, and exploitation further requires an attacker to make the resolver validate a crafted DNSSEC response, for example through a spoofed or attacker-controlled answer for a signed name. Rated CVSS 5.3 (integrity-only, low impact) and no public exploit identified at time of analysis; the priority signal is this_month, not immediate action.
A DNS cache-poisoning flaw in dnsmasq (CWE-345, insufficient verification of data authenticity) lets a malicious or compromised upstream resolver inject cached records for names outside its authoritative zone when dnsmasq follows a CNAME in a response. Only split-DNS deployments that forward specific domains to a designated upstream are realistically exposed, since the attacker must already occupy that trusted upstream position; standard single-forwarder or root-hint setups are far less affected. Impact is integrity-only (attacker-chosen addresses returned to later clients), rated CVSS 6.8 with AC:H, and no public exploit code or KEV entry was identified at time of analysis, so priority follows the vendor's this-month cadence rather than emergency response.
Keycloak's HOTP one-time-password authentication flow can accept the same code more than once: the keycloak-services component verifies the OTP and advances its stored counter in two non-atomic steps, so concurrent login requests can slip through the gap before the counter is updated. The attacker must already know the victim's password and hold one currently valid HOTP code, and must win a narrow race (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N, 4.2), so the practical gain is replay of a single code for simultaneous sessions rather than an authentication bypass; Red Hat build of Keycloak and Red Hat Single Sign-On 7 are the affected distributions. This is a medium-severity, defense-in-depth weakness rather than an emergency - no public exploit code or active exploitation is identified at time of analysis, and the priority label places it in the normal monthly remediation cycle.
Keycloak's keycloak-services PAR (Pushed Authorization Request) implementation can be induced to issue multiple access tokens from a single authorization request that is supposed to be single-use, by restarting the authentication flow so that internal PAR-consumption markers are cleared while the request stays active. Affected components are Red Hat Build of Keycloak and Red Hat Single Sign-On 7 deployments that actually have OAuth 2.0 PAR in use; the CVSS vector (PR:L) means the attacker must already be able to initiate and restart an authentication flow as a client or user, so this is not reachable by a fully unauthenticated outsider. Impact is limited to confidentiality and integrity of the token issuance path (C:L/I:L, no availability impact); there is no CISA KEV entry and no public exploit identified at time of analysis, and the priority label is 'this_month' rather than an emergency.
An information disclosure flaw in Keycloak's client registration component lets an authenticated client owner read secrets they should not be able to access when the deployment uses a vault provider (Vault SPI) to store sensitive values. The attacker sets a client's secret to a crafted reference pointing at a vault entry, then retrieves the client configuration and sees the resolved secret in plain text, exposing credentials such as those held in HashiCorp Vault. Exploitation requires a non-default vault integration plus valid client-owner credentials; the issue is rated moderate (CVSS 5.3, C:H with AC:H in the upstream vector, assessed as AC:L), and no public exploit or active exploitation is identified at time of analysis.
Crashing 389-ds-base directory servers is possible for an authenticated LDAP user who holds ModifyDN permission on an entry: renaming it with a schema alias such as 'commonName' instead of the canonical 'cn' causes a NULL pointer dereference and denial of service. The flaw affects Red Hat Directory Server 11, 12, and 13 and the 389-ds-base packages in Red Hat Enterprise Linux 6 through 10; exploitation requires valid credentials plus an explicit modrdn ACI, so anonymous or read-only users cannot trigger it. No public exploit identified at time of analysis, and the impact is limited to availability with no data disclosure or modification, making this a moderate-priority availability issue rather than a top-tier emergency.
Keycloak's JWT Authorization Grant implementation skips the claim-filtering and login restrictions configured on OIDC or Google identity providers, so an authenticated client using that grant can obtain access tokens for users whose IdP claims should have blocked login. Red Hat Build of Keycloak and Red Hat Single Sign-On 7 are in the affected CPE set, and the issue is rated CVSS 5.4 (PR:L) with low confidentiality and integrity impact and no availability impact. The supplied data contains no CISA KEV entry and no public exploit identified at time of analysis; exploitation requires a restricted OIDC/Google IdP plus an authenticated client able to use the JWT grant flow.
Information disclosure in Red Hat JBoss Enterprise Application Platform 7 and 8 (plus EAP Expansion Pack and Red Hat Single Sign-On 7, which embed the same management layer) lets any authenticated management user holding a low-privileged role such as Monitor read JVM system properties and configuration details that should be restricted, because the handler for the read-resource operation on the platform-mbean runtime resource omits its RBAC check. The CVSS 3.1 score is 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N): the requirement for an existing low-privileged management account (PR:L) caps the severity, and the impact is confidentiality-only with no write, code-execution or denial-of-service path. There is no CISA KEV listing and no public exploit identified at time of analysis, and the vendor-reported issue is tracked as CWE-862 (Missing Authorization); priority is this_month, since the practical value of the leak depends on whether a given deployment stores secrets in JVM system properties.
When cross-site (xsite) TLS is enabled, the Infinispan Operator for Red Hat Data Grid 8 launches the Gossip Router container with the keystore and truststore passwords as plain-text command-line arguments, so any principal holding `get pods` in the namespace - without needing `get secrets` - can read those credentials directly from the Pod spec. The same values are exposed to node-level processes through `/proc/<pid>/cmdline` and are frequently captured in audit and event logs. Rated 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), this is a moderate-priority information-disclosure issue that only manifests in a non-default operator-driven configuration; no public exploit code and no CISA KEV entry were identified at time of analysis.
gssproxy can be persistently crashed by any local user who can reach its Unix domain socket: a GSSX_INIT_SEC_CONTEXT request that omits the target_name field triggers a NULL pointer dereference in the daemon. The issue affects gssproxy deployments on Red Hat Enterprise Linux 7, 8, 9, and 10 and is listed for Red Hat OpenShift Container Platform 4; because gssproxy does not automatically restart, Kerberized NFS and IdM services that depend on it can be disrupted until an administrator intervenes. No public exploit identified at time of analysis.
An out-of-bounds heap read in open-iscsi's iscsiuio daemon allows an attacker on the same network segment to crash the daemon, overwrite a single heap byte, or corrupt the stored iSCSI initiator name by sending a crafted DHCPv6 Advertise message. The flaw is in the DHCPv6 option parser, which calls strlen() on raw option data that carries no guaranteed NUL terminator, so the scan walks past the end of the buffer; open-iscsi packages as shipped in Red Hat Enterprise Linux 6, 7, 8, 9 and 10 are listed as affected, but only hosts that actually run iscsiuio and obtain iSCSI parameters over DHCPv6 (offload/boot deployments) are exposed, since the daemon is not default-active on typical systems. No public exploit code has been identified at time of analysis and there is no CISA KEV listing; combined with the adjacency-only attack path this yields a medium severity (CVSS 6.3) and a this-month rather than emergency priority.
libslirp user-mode networking can disclose the host's real IP address to a guest when an ICMP echo request is handled through the fallback path and the reply length is not updated to match the actual data received. The flaw affects libslirp as shipped in Red Hat Enterprise Linux 8, 9, and 10 and Red Hat OpenShift Container Platform 4, with exposure limited to guests using slirp-style user-mode networking rather than bridged or tap networking. Rated CVSS 3.5 with a monitor priority, exploitation requires a guest-level user able to send ICMP echo requests plus a host-side condition the attacker does not control, and no public exploit has been identified at time of analysis.
Improper authorization in FreeIPA lets any enrolled host retrieve and revoke X.509 certificates belonging to other users or services, disrupting those services, because ownership is checked only by matching the host name to the certificate subject Common Name. The flaw is moderate severity (CVSS 5.4) and requires an authenticated host principal (PR:L); Red Hat tracks it for remediation this month, and no public exploit was identified at time of analysis.
Arbitrary file write in the OpenShift oc client's image extract command allows an attacker who supplies a malicious container image to place content outside the intended extraction directory with the privileges of the user running oc image extract. Red Hat OpenShift Container Platform 4 is affected because the client does not properly sanitize symbolic and hard link targets that are absolute paths or sibling directories, and the impact is limited to integrity (CVSS 5.5, AV:L/UI:R). No public exploit code or confirmed active exploitation has been identified in the available intelligence, and the risk is assessed as real but non-urgent.
Arbitrary file creation outside the intended working directory affects users and automated workflows running GNU patch, specifically when automatic patch reversal processes a crafted patch whose header contains an absolute file path that is accepted instead of rejected. The result is limited to integrity impact: files can be created in arbitrary locations, but only with the permissions of the user or pipeline account executing the utility, with no confidentiality or availability impact and no privilege gain beyond that account's existing rights. Exploitation requires a local attack vector and user interaction - a victim or a CI/CD pipeline must apply the attacker-supplied patch - and no public exploit, PoC reference, or CISA KEV entry is present in the available data; the assigning vendor is Red Hat, with RHEL 6 through 10 and Red Hat Hardened Images listed as affected.
The system CA trust store shipped in Red Hat's ca-certificates RPM packages includes eMudhra root authorities that signed intermediate CA certificates protected by weak private keys, so a man-in-the-middle attacker who can intercept traffic and who can factor or guess those keys could mint certificates for arbitrary hostnames that TLS clients using the system trust store would accept (CVSS 6.8, CWE-295). Affected platforms span Red Hat Enterprise Linux 6 through 10 plus a long list of layered products such as OpenShift Container Platform 4, Satellite 6, Quay 3, Advanced Cluster Management, and the cert-manager and logging operators. Attackers need a privileged network position and a victim client that actually initiates a TLS connection validated against the system store, so this is a trust-anchoring and impersonation problem rather than a remotely reachable code-execution flaw; there is no availability impact and no public exploit code identified at time of analysis. Because individual intermediate certificates cannot be selectively distrusted across every consumer of the system store, Red Hat is removing the parent root CAs outright, which is the crux of the remediation.
Path traversal in OpenSCAP's Source DataStream (SDS) decomposition can allow a crafted datastream to create or modify files outside the intended output directory with the permissions of the process performing the decomposition. The issue affects OpenSCAP as shipped in Red Hat Enterprise Linux 6 through 10 and Red Hat Hardened Images; exploitation is local and requires the victim user or automated system to decompose an attacker-supplied SDS containing directory traversal sequences. No public exploit code or CISA KEV entry was identified at time of analysis, and the CVSS 3.1 score is 6.1 (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L).
Keycloak can bypass mandatory OTP enrollment during login when a realm orders the 'Update User Locale' required action before 'Configure OTP,' allowing an attacker who already holds a valid password to access the account without setting up the required one-time password credential. The issue affects Red Hat build of Keycloak and Red Hat Single Sign-On 7 and carries a low CVSS score of 4.2 because exploitation requires a non-default administrative ordering and prior knowledge of valid credentials. No public exploit code has been identified at time of analysis.
Path traversal in the Undertow web server's PathResourceManager, which serves static files from the filesystem, lets remote attackers read files outside the intended static-content root when a symbolic link resolves into a sibling directory whose name begins with the same characters as an authorized safe directory (for example 'reports' versus 'reports-internal'). The root cause is a string-prefix check that never verifies a full path-segment or directory boundary, so it fails to confirm the link's canonical target actually resides inside the approved directory. Affected deployments are those bundling Undertow's static resource handling, as reflected by Red Hat's CPEs for JBoss Enterprise Application Platform 7 and 8, Red Hat Fuse 7, Red Hat Build of Apache Camel for Spring Boot 4, Red Hat Single Sign-On 7, and RHEL 8/9 packages; the assessed severity is low (CVSS 3.1 base 3.7, AV:N/AC:H/PR:N/UI:N/C:L/I:N/A:N) because exploitation demands a pre-existing symlink plus a directory-name collision, and the outcome is limited to low-confidentiality file disclosure with no write or availability impact. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the signals align on low real-world risk.
A file descriptor leak in the containers/storage Go library's archive.ApplyLayer and ApplyUncompressedLayer functions causes descriptors to be left open whenever corrupt or malicious image layers or tar streams are unpacked, and repeated processing of such inputs can exhaust the hosting process's file descriptor limit. The weakness is unauthenticated in CVSS terms (PR:N) but local in scope (AV:L) and requires the victim to actually process attacker-influenced layers (UI:R), so an attacker must first get malformed image content in front of a build, pull, or sync loop. Impact is availability-only and confined to the affected process (C:N/I:N/A:L, S:U): no code execution and no data exposure; a single bad input does not cause denial of service, only sustained repetition does. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, and EPSS scoring was not supplied with the source data.
An authenticated user who is permitted to submit evaluation jobs in Red Hat OpenShift AI's lm-evaluation-harness component can supply an attacker-controlled model URL in the JobSpec, causing the evaluation job pod to send the tenant's model authentication secret to an external listener the attacker controls. The same user-controlled URL handling allows Server-Side Request Forgery against internal endpoints reachable from the evaluation pod's network namespace, so internal services can be probed or reached with the pod's network position rather than the attacker's. The impact is confidentiality-only (CVSS 3.1 base 6.5, PR:L, C:H/I:N/A:N), no public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation is gated on valid tenant job-submission credentials plus network reachability from the pod.
An out-of-bounds read in libmodulemd's modulemd v2 rpm-map YAML serialization path can crash applications that process crafted module metadata, producing a local denial of service. The bug is triggered only when the metadata declares multiple digest algorithm types and is serialized through the affected path; default single-digest metadata does not trigger it. The assessed impact is availability-only, with no confirmed code execution or data exposure, and no public exploit code or CISA KEV entry was identified at time of analysis.
Stack exhaustion in libmodulemd's xmd (extended metadata) parser lets anyone who can place crafted modulemd YAML in front of a consuming process crash it or exhaust its resources, an availability-only denial of service (CVSS 6.2, C:N/I:N/A:H). The defect is in the recursive YAML mapping/sequence helpers that convert xmd content into nested GVariant values with no recursion-depth or node-count ceiling, so deeply nested input overflows the stack. Affected builds ship in Red Hat Enterprise Linux 8, 9 and 10, Red Hat Hardened Images, and OpenShift Container Platform 4; the vector AV:L/PR:N/UI:N means the attacker must first get the malicious metadata onto a host that parses it (for example an attacker-controlled or third-party module repository consumed by DNF/libdnf), after which no authentication or user interaction is required. No public exploit code and no confirmed active exploitation were identified in the available intelligence at time of analysis.
Denial of service in libmodulemd can be triggered when a build compiled with rpmio support parses a highly compressible modulemd YAML file; the custom decompression read handler does not cap cumulative decompressed output before parsing, allowing CPU and memory exhaustion that can hang or crash the consuming process. The issue is scored CVSS 6.2 with a LOCAL vector, requires no authentication or user interaction once a malicious file reaches the parser, and is associated by CPE data with Red Hat Enterprise Linux 8, 9, and 10 plus related OpenShift and hardened image products. No public exploit code or CISA KEV-listed active exploitation was identified in the supplied intelligence.
An out-of-bounds read in device-mapper-multipath's multipathd daemon allows local users who can submit commands to the daemon's control interface to read past the end of a buffer by supplying a command whose format string ends in a trailing percent character, exposing unintended daemon memory (limited information disclosure) or crashing multipathd to cause a denial of service. Local attackers need no prior privileges on the host per the CVSS vector (PR:N), but exploitation requires a local account on a system where multipathd is running and reachable. Affected products include Red Hat Enterprise Linux 6, 7, 8, 9 and 10 plus Red Hat OpenShift Container Platform 4, which ships the component in its RHEL-based node stack. No public exploit code has been identified at time of analysis and there is no CISA KEV listing; impact is bounded to confidentiality and availability (5.1, C:L/A:L), with no code execution or integrity impact.
Local credential disclosure in cockpit-machines, the Cockpit web module for managing libvirt/KVM virtual machines on Red Hat Enterprise Linux 9 and 10, exposes a guest VM's VNC console password to other unprivileged users on the same host. When an operator saves VNC console settings, the configured password is handed to an underlying system utility as a command-line argument, so any local user able to inspect another user's process entries can read the secret during that brief window. Exploitation requires an already-authenticated local account (PR:L), a host without hidepid-style process hiding, and a concurrent victim save action (UI:R); no public exploit code exists and the flaw is not in CISA KEV.
Information disclosure in cockpit-machines on Red Hat Enterprise Linux 9 and 10 lets a local unprivileged user capture RHSM authentication tokens from the command line of a short-lived image-retrieval helper process when cross-user process inspection is enabled. The attacker needs a local shell account and a concurrent image-retrieval operation by another user; stolen tokens can be used against RHSM resources only until they expire. This is a moderate-risk, low-urgency issue with no public exploit identified at time of analysis, and it does not provide remote access, code execution, or integrity/availability impact.
Denial of service in GIMP is triggered by importing a crafted SBZ palette file that lacks a color-model attribute, causing a NULL pointer dereference during string comparison in the palette parser. The flaw affects GIMP as packaged in Red Hat Enterprise Linux 6 through 10, requires local delivery of a malicious file and user interaction to import it, and results only in application crash with no confidentiality, integrity, or code-execution impact. No public exploit code or confirmed active exploitation was identified at time of analysis.
Denial of service in the GStreamer ASF demuxer (gst-plugins-ugly), rated CVSS 6.5, allows a crafted ASF, WMV, or WMA file to drive an oversized heap allocation because an attacker-controlled Simple Index entry count is not bounded by the object's actual payload. The issue affects gst-plugins-ugly packages in Red Hat Enterprise Linux 7, 8, 9, and 10; exploitation requires a victim to open or preview the malicious media file, with an unauthenticated network vector and user interaction required, and impact is limited to availability loss with no code execution or data exposure. No public exploit identified at time of analysis.
Local privilege escalation in Red Hat rhc's rhc-canonical-facts.service lets an attacker who has already compromised the privileged yggdrasil service account pre-plant a symbolic link so the root-run unit follows it and changes ownership of an arbitrary file, enabling escalation to root. The flaw is CWE-59 link following and affects rhc installations on Red Hat Enterprise Linux 7, 8, 9, and 10 per CPE data; exploitation is local-only and requires high privileges (CVSS PR:H), so risk is confined to systems where the yggdrasil account is already reachable. No public exploit code was identified in the provided sources at time of analysis, and no CISA KEV or EPSS signal was supplied.
Repeated state-notification requests sent to a network-reachable rpc.statd service in nfs-utils cause memory allocated during callback processing to never be released, producing continuous memory growth that can degrade or crash the service and exhaust host resources. The flaw is remotely triggerable without authentication (CVSS:3.1/AV:N/AC:H/PR:N/UI:N) but exploitation is not trivial: a single request is insufficient because the attacker must sustain a stream of requests long enough to exhaust memory, which is why the vector carries AC:H and the impact is availability-only (C:N/I:N/A:H, base score 5.9). Exposure is limited in practice because rpc.statd only runs when NFSv3 locking services are active and is normally bound to internal or trusted networks rather than the public internet, so firewalled or default deployments are not reachable. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; this is a genuine but moderate-priority availability issue rather than a top-tier emergency, and affected services can be recovered by a restart.
Arbitrary file deletion in GNOME Nautilus (GNOME Files) affects desktop users on Red Hat Enterprise Linux 6 through 10 and other distributions shipping the file manager: when a removable drive or disk image is unmounted or ejected, Nautilus offers to empty the trash without verifying that the volume's trash directory paths are symbolic links. An attacker who persuades a local, authenticated user to mount a crafted storage volume and then confirm that prompt can have files the victim has permission to delete removed through the symlinked path. The issue carries a moderate CVSS 3.1 score of 6.6 (AV:L/PR:L/UI:R, integrity and availability High, confidentiality None), and no public exploit identified at time of analysis; successful abuse requires a local desktop session, attacker-supplied media, and explicit user confirmation of the dialog.
Use-after-free in libarchive's archive_entry_copy_mac_metadata() function allows an attacker who can influence the input an application feeds that API to crash the linked application or cause it to read uninitialized heap memory, yielding a CVSS 3.1 base score of 3.6 (AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L). The flaw is not remotely reachable by default and requires the consuming application to perform a self-copy in which the source buffer overlaps the entry's existing mac_metadata pointer; it is a genuinely low-priority memory-safety issue with impact limited to denial of service and minor information disclosure, with no integrity or code-execution outcome. No public exploit code and no confirmed active exploitation were identified at time of analysis, and Red Hat has published an upstream fix (libarchive PR #3318) alongside its advisory and Bugzilla tracking entry.
Denial of service and limited memory disclosure in GIMP's Bohemia Interactive (PAA) texture importer, triggered when a user opens or previews a specially crafted .paa file through the affected plug-in. An integer overflow in the image-dimension calculation during decompression causes an undersized heap buffer to be allocated, and the subsequent out-of-bounds read crashes the plug-in process and may expose fragments of heap memory (CVSS 3.1 base 6.1, AV:L/PR:N/UI:R, C:L/A:H). The attack requires the victim to deliberately load the malicious file locally, so there is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV) - this is assessed as a moderate-severity, low-priority issue in practice.
Unbounded decoding of PMAPPROC_DUMP replies in libtirpc lets a malicious or already-compromised RPC portmapper exhaust the memory and CPU of a client application that calls pmap_getmaps(), crashing or stalling the client process and causing a denial of service. The exposure is conditional and client-side: a remote attacker cannot initiate the exchange, so the victim must direct libtirpc-based tooling (NFS/RPC mount helpers, discovery or inventory scanners) at the attacker-controlled rpcbind, which is why the assessed vector is AV:N/AC:H/PR:N/UI:R with availability-only impact and no confidentiality, integrity, or code-execution consequences. Affected packages are those shipped in Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4. At CVSS 5.3 this is a moderate-severity, low-priority issue in practice, and no public exploit code and no confirmed active exploitation (no CISA KEV listing) were identified at time of analysis.
Denial of service in libtirpc allows an authenticated remote RPC client to exhaust server memory by sending oversized wrapped-data requests to an RPC service that is configured with RPCSEC_GSS integrity (rpc_gss_svc_integrity) or privacy (rpc_gss_svc_privacy) protection. Only services explicitly running in that non-default, Kerberos-backed mode are exposed - most commonly NFS deployments on Red Hat Enterprise Linux 6 through 10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4 - and the impact is availability-only (CVSS 6.5, A:H) with no confidentiality or integrity effect. No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing), so it warrants medium-priority patch tracking rather than emergency response, although affected RPC services can become unstable or terminate under the resource exhaustion.
Local denial of service in the nfs-utils fsidd daemon affects Red Hat Enterprise Linux 6, 7, 8, 9, and 10 as well as Red Hat OpenShift Container Platform 4; an authenticated local user with access to the fsidd Unix domain socket can send a malformed request that omits required arguments, triggering a CWE-617 assertion failure and crashing the daemon. The service remains unavailable for filesystem identifier lookups until restarted, giving this a CVSS 3.1 score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). No public exploit code has been identified at time of analysis.
Argument injection in libblockdev's NTFS and VFAT label-setting routines lets a local, unprivileged user smuggle command-line flags into the ntfslabel and fatlabel utilities through a filesystem label that begins with a dash. The vulnerable paths (bd_fs_ntfs_set_label() and bd_fs_vfat_set_label()) are reachable without administrator authentication via the udisks2 Filesystem.SetLabel() D-Bus method, but exploitation is strictly local and the assessed impact is low integrity only - no confidentiality or availability loss and no privilege escalation. No public exploit code has been identified at time of analysis, and the low CVSS score (3.3, AV:L/PR:L/I:L) reflects the limited blast radius rather than an unexplored attack surface.
Improper boundary validation of metadata slot values in luksmeta allows an attacker who can supply or modify a LUKS disk header to redirect wipe or load operations outside the intended metadata area, overwriting or zeroing encrypted payload data and causing persistent data loss and corrupted storage. The attack is confined to a local vector and requires high privileges - root-level write access to the raw block device, or inducing an administrator to process an attacker-supplied untrusted disk image whose header carries out-of-range slot values together with valid checksums. The impact is limited to integrity and availability, with no information disclosure; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the moderate CVSS of 6.0 reflects the substantial privilege barrier rather than the severity of the data-loss outcome.
Stored cross-site scripting in the Ansible Automation Platform unified UI lets an authenticated user who can publish or upload a collection to Automation Hub embed a link using a script-executing URL scheme (for example javascript:) in that collection's documentation; the Hub documentation renderer (formatPartURL in frontend/hub DocumentationParsers.tsx) writes the URL into a link without validating its protocol, so the script executes in the Hub UI origin when a second authenticated user opens the collection documentation page and clicks the link. Red Hat scores it CVSS 3.1 5.4 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) - low confidentiality and integrity impact with a scope change, since the injected script runs with the privileges of the Hub origin rather than staying inside the published content. The flaw ships in the AAP 2.6 and 2.7 release branches only; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and exploitation requires both a malicious publisher and a victim who actively activates the crafted link.
An out-of-bounds write in the DPDK vhost-crypto backend allows a guest VM to overflow a host-side buffer and crash the host data plane. The flaw combines an integer overflow in the chain-length validation logic with missing length checks on the RSA request path, so crafted virtio-crypto descriptors can bypass size validation and corrupt host memory. Exposure is confined to hosts that have explicitly enabled the vhost-crypto (virtio-crypto) backend, exploitation requires low-privileged access from within a guest, and no public exploit code has been identified at time of analysis, with no confirmed active exploitation (CISA KEV).
An out-of-bounds write in the DPDK lib/vhost vhost-crypto backend lets a guest VM that is authorized to issue vhost-crypto requests corrupt host memory by supplying an avail-ring descriptor index that the backend uses without validating it against the ring size. The affected code ships in Red Hat Fast Datapath packages for RHEL 8, 9, and 10 and is therefore inherited by related RHEL, Red Hat OpenShift Container Platform 4, and Red Hat OpenStack Platform 13 (Queens) deployments that consume those DPDK builds. Exploitation is restricted to hosts where the vhost-crypto backend is actually enabled and a virtio-crypto device is exposed to a guest (CVSS 6.5, AV:L/PR:L/S:C), and the assessed outcome is host datapath denial of service rather than data disclosure or modification; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV.
Guest-to-host denial of service in the DPDK vhost library (lib/vhost) allows a malicious or misbehaving guest to underflow the copy length in the vhost enqueue path by supplying runt RX descriptors, which can stall or crash a shared host-side vhost backend such as OVS-DPDK. The flaw is rated CVSS 6.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H, mapped to CWE-191) and is only reachable by an attacker who already controls a guest VM (local-to-host scope, PR:L) - not by a remote unauthenticated network attacker - with impact limited to availability (no confidentiality or integrity effect). No public exploit was identified at time of analysis and there is no CISA KEV listing for this CVE; no vendor-released patch was identified at the time of analysis.
Host-side denial of service and potential memory corruption in DPDK's lib/vhost arise because memory-region sizes are not adequately validated before mmap during vhost memory-region setup (CWE-770). The affected code ships to customers through Red Hat Fast Datapath for RHEL 8, 9 and 10, and therefore reaches Red Hat Enterprise Linux 8/9/10, Red Hat OpenShift Container Platform 4 and Red Hat OpenStack Platform 13 (Queens) deployments that use DPDK vhost-user acceleration. An attacker who controls a connected vhost-user frontend - typically a guest VM or a process holding the vhost-user socket - can crash the host (CVSS 6.5, AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H); no public exploit code has been identified at time of analysis and there is no confirmation of active exploitation.
A time-of-check/time-of-use race in the DPDK vhost library's handling of virtio indirect descriptor tables allows an attacker who already controls a guest VM attached to a DPDK vhost-user backend to crash or disrupt the host vhost process by mutating the descriptor table length between the host's two reads from guest memory, or by supplying an out-of-range next index against a small host-side copy in the vDPA relay path. Exploitation requires local/guest-level low privilege (PR:L) and is heavily timing-dependent (AC:H), and the impact is confined to availability - the out-of-bounds bytes are consumed internally as descriptor fields for GPA translation and are never returned to the guest as payload, so no confidentiality or integrity loss is assessed. This is a moderate, defense-in-depth-class residual of the CVE-2018-1059 fix rather than an urgent priority, and no public exploit code was identified at time of analysis.
Local authenticated attackers can retrieve LUKS disk-encryption passphrases from hosts using the Clevis PKCS#11 pin because the clevis-pkcs11-afunix-socket-unlock daemon writes passphrases in plaintext to a world-readable log file. This affects Red Hat Enterprise Linux 7 through 10 and Red Hat OpenShift Container Platform 4 deployments where this non-default disk-unlock configuration is in use. No public exploit code has been identified at time of analysis; exploitation requires an existing low-privileged local account and prior logging of a LUKS unlock passphrase.
An out-of-bounds write in GStreamer's H.266/VVC Decoding Capability Information (DCI) parser inside libgstcodecparsers allows a remote attacker to crash or corrupt memory in any third-party application that directly calls the affected parsing API by supplying a crafted H.266 bitstream whose reserved DCI field carries an illegal value the parser wrongly accepts. Red Hat rates it CVSS 6.5 (Medium, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L) - network-reachable, unauthenticated and requiring no user interaction per the supplied vector, but with only Low integrity and Low availability impact and no confidentiality loss, consistent with a bounded out-of-bounds write (CWE-787). Exposure is sharply limited: the description states no standard GStreamer pipeline element invokes this code path, so default GStreamer installations and ordinary playback pipelines are not exploitable, and no public exploit has been identified at time of analysis.
Removing two packages in a single BusyBox dpkg invocation can silently drop the second package's stanza from the dpkg status file when the first package's stanza is larger than the second, leaving the package database inconsistent with what is actually installed. Only environments that compile in and actually use the BusyBox dpkg applet are affected - Red Hat lists Red Hat Hardened Images, whose minimal footprint typically relies on BusyBox applets, and any other image built with CONFIG_DPKG enabled. The assessed vector (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N, score 3.3) requires local execution plus a human performing the removal, yields integrity-only impact on the status file with no confidentiality or availability effect, and no public exploit or code execution path has been identified at time of analysis.
Local information disclosure in Red Hat Clevis's PKCS#11 pin lets an already-logged-in, low-privileged local user capture the PKCS#11 token PIN that clevis-decrypt-pkcs11 passes as a command-line argument to pkcs11-tool, from where it is readable through process listing or /proc/<pid>/cmdline. The issue affects Clevis as shipped with Red Hat Enterprise Linux 7, 8, 9 and 10 as well as Red Hat OpenShift Container Platform 4, and carries a CVSS 3.1 base score of 4.7 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N), reflecting high confidentiality impact but a local-only, high-complexity attack requiring a non-default configuration. Exploitation requires the PKCS#11 pin to be configured, a decryption operation to be in flight at the same moment, and the attacker to win a timing race against the short-lived pkcs11-tool process; no public exploit code and no confirmed active exploitation (not in CISA KEV) have been identified at time of analysis.
The clevis-luks-pkcs11-askpin helper shipped with Red Hat Enterprise Linux (7, 8, 9 and 10) and Red Hat OpenShift Container Platform 4 writes the PKCS#11 token PIN in cleartext to a file that is not given restrictive permissions, so under the default process umask the file is world-readable, and the file is also not reliably removed when the decryption script exits early, leaving the PIN readable indefinitely. The issue is assessed as CVSS 3.1 4.7 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N), meaning an authenticated local user with low privileges can obtain high-confidentiality secret material, but only on systems that actually use the non-default clevis PKCS#11 pin for LUKS unlocking. No public exploit code was identified at time of analysis and there is no CISA KEV listing; exploitation is local-only and the practical risk is confidentiality loss of the token PIN rather than a remote or code-execution threat.
Local attackers can exploit improperly secured AF_UNIX sockets in the clevis PKCS#11 pin to inject arbitrary device/key pairs or intercept LUKS passphrases, potentially gaining unauthorized access to encrypted disks. Affected products include Red Hat Enterprise Linux 7, 8, 9, and 10, as well as Red Hat OpenShift Container Platform 4. Exploitation requires an authenticated local user and a permissive process umask; no public exploit code or active exploitation has been identified, and the issue is rated modest priority due to the local-only attack vector and dependency on non-default umask settings.
Heap out-of-bounds write in the GStreamer ASF muxer plugin (asfmux) occurs when string metadata tags containing Unicode characters outside the Basic Multilingual Plane - such as emoji or supplementary-plane CJK characters - are written into an ASF/WMV container, because the buffer size calculation assumes 2 bytes per code point while UTF-16LE surrogate pairs actually require 4. Exploitation requires a local pipeline that muxes, remuxes, or transcodes attacker-supplied media into ASF while preserving metadata (AV:L, UI:R), enabling a user-assisted heap corruption that can cause a denial of service or limited memory corruption. Rated CVSS 6.1 with C:N/I:L/A:H, this is a medium-severity issue with a narrow attack path; no public exploit code and no confirmed active exploitation were identified at time of analysis, and affected packages are tracked for Red Hat Enterprise Linux 7, 8, 9, and 10.
An out-of-bounds read in BlueZ's btmon Bluetooth monitoring utility, as packaged in Red Hat Enterprise Linux 6 through 10, allows an attacker to crash the tool by getting a user to open a crafted btsnoop capture file containing an HCI Return Link Keys event that advertises more link keys than the packet actually contains. The flaw is local-access and interaction-dependent (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H) - the victim must deliberately load the malicious capture into btmon - which sharply limits real-world exposure given btmon is a diagnostic tool rarely pointed at untrusted input. No public exploit code or confirmed active exploitation was identified at time of analysis, and the practical outcome is a denial of service against the monitoring utility rather than any network- or privilege-escalation impact.
Crashing of the clevis-pkcs11-afunix-socket-unlock daemon in the clevis PKCS#11 pin allows a local attacker to cause a boot-time denial of service on hosts that rely on clevis for LUKS disk decryption. When a client connects to the daemon's AF_UNIX data socket without binding a client address, an integer underflow in the getpeername() result handling corrupts memory (CWE-787) and terminates the daemon, so LUKS unlock never completes and the system cannot finish booting. The issue is availability-only (CVSS 3.1 base 4.7, AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H), affects clevis on Red Hat Enterprise Linux 7, 8, 9 and 10 as well as Red Hat OpenShift Container Platform 4, and no public exploit has been identified at time of analysis; the vulnerable configuration is a non-default deployment choice and not present in a stock RHEL install.
A stack-based out-of-bounds write in GNOME Remote Desktop's VNC TLS read path, as shipped in Red Hat Enterprise Linux 8, 9, and 10, can crash the service and cause denial of service. An unauthenticated remote attacker (per the CVSS vector PR:N) who can reach an enabled VNC TLS listener and drive the connection into a peek/read size mismatch can corrupt memory on the stack; the vector rates this CVSS 5.9 with availability-only impact (C:N/I:N/A:H) and high attack complexity (AC:H), reflecting that the mismatch is non-trivial to trigger reliably. The vulnerable configuration is not default: remote desktop sharing must be explicitly enabled with the VNC backend and a reachable TLS listener, which is uncommon on headless or server RHEL installs; no public exploit code and no confirmed active exploitation were identified at time of analysis, and this should be handled as a routine patch rather than an emergency.
Crafted ISO-2022 encoded text passed to the m17n-lib decoder can trigger an uninitialized stack memory read, potentially leaking small amounts of process memory if the application then returns or displays the decoded output to the attacker. The issue is rated low severity (CVSS 2.5, AV:L/AC:H/UI:R, unauthenticated per vector PR:N) and affects multilanguage library builds shipped across Red Hat Enterprise Linux 6 through 10, though any application embedding m17n-lib's ISO-2022 handling is in scope. No public exploit identified at time of analysis; risk is gated by the fact that the deploying application must both decode attacker-supplied ISO-2022 input and reflect the decoded result back, which is uncommon in typical installations.
Denial of service in the openstack-network-exporter HTTP metrics server, as shipped in Red Hat OpenStack Platform 18.0, allows an unauthenticated remote attacker to open many slow HTTP header connections and exhaust server file descriptors, preventing legitimate Prometheus metric scraping and alerting. The component is deployed without a ReadHeaderTimeout or comparable connection timeouts, so any network-reachable instance is affected with no credentials or user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, 5.3). There is no public exploit identified at time of analysis and no evidence of active exploitation; impact is limited to monitoring availability and does not touch the OpenStack data plane, making this a modest availability issue best handled through routine hardening and network segmentation.
Server-side request forgery in Red Hat Quay allows an authenticated repository administrator to bypass the hostname blacklist enforced by the webhook notification feature, causing the Quay application to issue HTTP requests to attacker-chosen internal destinations such as cloud metadata endpoints or in-cluster services. Successful exploitation can disclose sensitive information returned by those internal services, though the CVSS 3.1 score of 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) reflects a moderate impact: the attacker must already hold a privileged in-application role, must use the webhook functionality, and the yield is bounded by which internal endpoints the Quay pod can actually reach. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the flaw is tracked by Red Hat under CVE-2026-85471 with all Quay 3 and Mirror Registry offerings listed as affected via wildcarded CPEs.
Improper validation of the user-supplied sort parameter in Quarkus REST Data Panache's auto-generated REST endpoints allows remote attackers to learn information about entity fields they should not have access to and to degrade performance by forcing the underlying database to perform expensive ordering operations, up to a denial of service. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L, 6.5) indicates the issue is network-reachable and unauthenticated per PR:N, with low confidentiality and availability impact; real-world exposure is deployment-specific because it requires an application that has enabled and externally exposed these generated endpoints. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Authenticated users of Red Hat Quay 3 can retrieve auto-prune policy configurations belonging to repositories in other namespaces, exposing configuration details that should remain tenant-scoped. Exploitation requires a valid Quay account, control of a repository whose name collides with the target's repository name, and prior knowledge of the target policy's unique identifier - conditions reflected in the CVSS 3.1 base score of 3.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N). Impact is confined to information disclosure, with no modification of data or denial of service, and no public exploit has been identified at time of analysis.
Build trigger management API in Red Hat Quay 3.x fails to verify that a requested trigger belongs to the specified repository, allowing an authenticated repository administrator to view, modify, or delete build triggers and associated write tokens in other repositories if they know the victim trigger's UUID. This is a moderate-severity authorization bypass (CWE-639) requiring prior knowledge of a random, non-enumerable UUID, which raises attack complexity (CVSS AC:H). As of analysis, no public exploit code has been identified; Red Hat has published an advisory and Bugzilla entry.
Authentication bypass in Keycloak's Client-Initiated Backchannel Authentication (CIBA) implementation allows public clients without a client secret to initiate backchannel login requests, enabling an attacker to trick a user into approving a malicious login and gain full access to the user's account. The flaw stems from Keycloak failing to verify that a client is authorized to use the CIBA flow, and exploitation requires the CIBA grant to be enabled, high attack complexity, and active user interaction to approve the request. No public exploit identified at time of analysis; the assessed CVSS is 6.8 (medium).
Broken access control (CWE-863) in Foreman's domain and subnet interface API lets an authenticated user who already holds a host-view permission and can see a shared domain or subnet read interface records for hosts outside their authorized scope; the API checks the host permission but omits its search-limit filter, returning every interface on the domain or subnet. A user who also holds host-edit permission can persist a change to one of those out-of-scope interfaces, giving limited confidentiality and integrity impact (CVSS 5.4, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N). Red Hat Satellite 6, which ships Foreman, is the affected product per CPE; no public exploit identified at time of analysis.
Authenticated users in Red Hat Satellite 6 (and the underlying Foreman permission-filter subsystem) can delete permission filters belonging to roles other than their own by abusing an API path that resolves filters by identifier without re-applying the caller's permission scope. The prerequisite is modest but not trivial: the attacker must already hold filter-delete rights for at least one role, and the victim roles must be unlocked - this is an insider or compromised semi-privileged account vector, not a default unauthenticated remote issue. Resulting impact is integrity-only (I:H, C:N/A:N) at CVSS 6.5, with other roles silently losing the access their deleted filters granted; no public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV).
Local privilege escalation and arbitrary code execution in the BusyBox tar applet (CVE-2026-108119) allow an attacker who supplies a crafted tar archive to create or replace files outside the extraction directory when the archive is extracted with elevated privileges. The flaw is a CWE-59 link-following issue in the applet's deferred symlink/hardlink creation path, with a CVSS 3.1 base score of 6.3 (AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H), affecting BusyBox as shipped in Red Hat Enterprise Linux 6 and Red Hat Hardened Images. No public exploit identified at time of analysis; exploitation requires a privileged user or process to actively extract the malicious archive, and the specific archive construction plus directory-reuse timing makes this high-complexity and local-only.
Opening a specially crafted XCF file in GIMP can crash the application through a NULL pointer dereference in the XCF loader's handling of image-simulation-intent and image-simulation-bpc parasites that carry zero-size data. The issue is confined to a denial of service of the GIMP process - there is no code execution, privilege escalation, or data exposure - and exploitation requires local access plus the victim manually opening an attacker-supplied file (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H, 5.5). No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV), though Red Hat tracks the affected GIMP packages shipped in RHEL 6 through RHEL 10; this is a genuine but low-priority issue.
Denial of service in libhangul can be triggered by a specially crafted Hanja dictionary file that contains an entry with a key but no valid value; parsing the file dereferences a NULL pointer and crashes the consuming application. Affected deployments include Red Hat Enterprise Linux 6 through 10 where the library is packaged, as well as any application that loads and queries such dictionaries. The CVSS vector (AV:L/PR:N/UI:R) means local delivery and user interaction are required, no privileges are needed, and impact is availability-only; no public exploit has been identified at time of analysis.
Null pointer dereference in OpenPrinting CUPS allows unauthenticated remote attackers who can submit jobs to a shared printer queue to crash the cupsd print daemon, causing a temporary denial of service for all printing services. Exploitation requires a vulnerable version that still ships the deprecated embedded job-ticket comment feature and a single crafted PostScript or PDF file submitted via the Print-Job operation whose first lines contain a malformed %cupsJobTicket: entry. Impact is bounded to a brief daemon crash with automatic restart-there is no code execution or data exposure-and no public exploit code has been identified at time of analysis.
Stored cross-site scripting in the login theme rendering component of Keycloak (and its downstream Red Hat Build of Keycloak and Red Hat Single Sign-On 7 products) lets a realm administrator inject malicious JavaScript into display fields that is later executed in the browsers of users loading the affected realm's login page. Exploitation requires an authenticated realm administrator (CVSS PR:H) who can both reach the theme display fields and bypass the input-sanitizing security filter, so this is a privilege-abuse or post-compromise vector rather than an anonymous remote attack; impact is limited to the confidentiality and integrity of affected users' sessions (C:L/I:L) with no availability impact. There is no public exploit identified at time of analysis and no CISA KEV listing; overall this is a genuine but modest-priority issue rather than a high-urgency crisis.
A heap-based buffer overflow in the PNG metadata reader of Eye of GNOME (eog) allows an attacker to potentially achieve arbitrary code execution or cause a denial of service (application crash) when a user opens a specially crafted PNG file. Exploitation requires user interaction and local access, but the vulnerability is unauthenticated (no privileges required) according to the CVSS vector PR:N. No public exploit code or confirmed active exploitation has been identified at time of analysis; the risk is constrained by the need for a user to open the malicious file on a system with eog installed.
Offline tokens issued by Keycloak, Red Hat Build of Keycloak, and Red Hat Single Sign-On 7 can stay valid after a backchannel logout because a serialization bug in the OIDC Dynamic Client Registration (DCR) response omits the backchannel-logout offline-token-revocation setting, silently disabling it whenever a client is updated through the standard update flow (CVE-2026-107623, CVSS 3.1 4.3, CWE-862). The actor must hold client-management/registration privileges (AV:N/PR:L), and the deployment must use DCR and rely on backchannel logout to revoke offline tokens, so this is a loss of a revocation guarantee rather than an account takeover. No public exploit code was identified at time of analysis and the issue is not in CISA KEV; EPSS signal is not available in the supplied data, and the assessed real-world risk remains low.
Keycloak, including the Red Hat Build of Keycloak and Red Hat Single Sign-On 7, exposes the active primary secret of confidential clients to any authenticated realm administrator who holds only the read-only view-clients role. The flaw sits in the installation provider and client registration endpoints, which return client credentials that a read-only administrator should never be able to read; with the leaked secret an attacker can authenticate as the confidential client and inherit its service account permissions across integrated services. Exploitation requires an existing realm administrator account with the view-clients role, so risk scales with how broadly that low-trust role is delegated, and no public exploit has been identified at time of analysis.
Data corruption in luksmeta allows a local attacker who already holds administrative privileges to damage or destroy metadata and encrypted payload data stored on a Linux Unified Key Setup (LUKS) device when a new metadata entry is saved. Because faulty free-space boundary calculations and flawed overlap detection can let new records be written past the available area or on top of existing ones, integrity is fully compromised though confidentiality is not (CVSS 5.1, AV:L/AC:L/PR:H/UI:N/C:N/I:H/A:L), and affected volumes may become inaccessible. Exploitation requires local host access with privileges sufficient to run luksmeta and write to the device; there is no remote or unauthenticated vector, no public exploit identified at time of analysis, and no confirmed active exploitation (not in CISA KEV), so impact is realistically limited to accidental or deliberate corruption by a privileged operator. The issue affects luksmeta as shipped with Red Hat Enterprise Linux 7, 8, 9 and 10, plus Red Hat OpenShift Container Platform 4 through the underlying RHCOS userland.
Information disclosure in flatpak-builder lets a crafted build manifest read sensitive host files and embed their contents into resulting build artifacts, because source download definitions that specify local file:// URIs bypass the tool's directory confinement checks. Exploitation requires a developer or CI system to actually process the untrusted manifest (user interaction per CVSS UI:R), so it is not remotely triggerable without someone initiating a build; no public exploit identified at time of analysis. Red Hat rates it moderate at CVSS 6.1, and the affected package ships in Red Hat Enterprise Linux 8, 9, and 10, with CI/CD pipelines that auto-build community-submitted manifests representing the highest-value target.
An authorization flaw in Katello's Flatpak Remote Repositories API allows an authenticated user who is permitted to view flatpak remotes in one organization to retrieve flatpak remote repository records - including the stored credentials for that remote - belonging to a different organization. The same unscoped lookup is reused by the mirror action, so a user with edit rights on a product in their own organization can create a repository configured with another organization's flatpak remote URL and its stored remote credentials. Exploitation requires an authenticated account holding the flatpak-remote view permission, the flatpak remote feature to be in active use, and a multi-organization Red Hat Satellite 6 / Katello deployment; no public exploit code has been identified at time of analysis, and the flaw is a medium-priority authenticated authorization issue rather than an emergency.
Cross-organization repository metadata disclosure in the Katello (Red Hat Satellite 6) Docker Tags repositories API allows an authenticated user who holds product-view permissions in one organization to retrieve repository configuration data for Docker meta tags owned by a different organization by simply supplying that foreign tag identifier. The weakness is an authorization-scoping gap (CWE-639, IDOR-style) correctly rated CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), with impact limited to low-severity confidentiality loss - there is no write or denial-of-service effect. Exploitation requires valid credentials, multi-organization deployment, and knowledge or enumeration of valid foreign tag identifiers; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and EPSS data was not supplied.
The cluster-samples-operator in Red Hat OpenShift Container Platform 4 assigns an overly permissive RBAC Role (coreos-pull-secret-reader) that grants get/list/watch on all Secrets in the openshift-config namespace, exceeding the operator's requirement for only the pull-secret Secret. This excessive-privilege weakness (CWE-250) does not provide initial access; an attacker must first compromise the operator pod or its service-account token through a separate vulnerability, after which they can read sensitive cluster secrets such as OAuth identity provider credentials and cloud provider credentials. No public exploit code is identified, and the issue is a defense-in-depth concern rather than a directly exploitable flaw (assessed CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).
Heap-based buffer overflow in GIMP's 'Hot' color filter plug-in allows a crafted, extremely large image to corrupt heap memory when the filter is invoked, giving an attacker the ability to crash the plug-in and potentially achieve code execution within the running user's session (CWE-119). The flaw is reachable only locally and requires the victim to open an attacker-supplied image with dimensions so large that the width * height allocation arithmetic overflows 32-bit integers, then actively run the Hot filter on it - hence the assessed vector AV:L/AC:H/PR:N/UI:R with high integrity and availability impact but no confidentiality impact. There is no public exploit identified at time of analysis, no CISA KEV listing, and no EPSS score provided, so this is a targeted, social-engineering-dependent client-side issue rather than an automatable, mass-exploitation threat. Red Hat hosts the primary advisory (access.redhat.com/security/cve/CVE-2026-106067) with tracking in Bugzilla 2547461, and GIMP packages across Red Hat Enterprise Linux 6 through 10 are enumerated as affected via CPE.
Exporting an oversized image through GIMP's raw data export plug-in can under-allocate a heap buffer and cause an out-of-bounds write on the heap, with the failure originating in an integer overflow in the g_malloc() size computation (width × height × bytes-per-pixel). Per the CVSS 3.1 vector (AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H), exploitation is local-only, requires the victim to actively start the export, requires no privileges (PR:N), and is gated by high attack complexity because the image dimensions must be crafted so the size arithmetic wraps; the assessment rates confidentiality impact as none and integrity/availability impact as high. No public exploit code and no confirmed active exploitation (no CISA KEV listing) were identified at time of analysis, and the EPSS-style signals provided are consistent with a moderate-priority rather than critical issue, since the plug-in is standard GIMP functionality but the trigger depends on user-driven export of deliberately large images.
Heap-based buffer overflow in GIMP's PCX export plug-in allows a local attacker to corrupt memory when a user opens or creates an image with extremely large width and height and exports it to PCX format. The flaw, tracked as CVE-2026-106065 with a CVSS score of 6.3 (AV:L/AC:H/PR:N/UI:R), stems from 32-bit integer overflow in the width*height size calculation while GEGL operations use the full extent. Affected GIMP packages ship with Red Hat Enterprise Linux 6 through 10; no public exploit code or active exploitation has been identified at time of analysis.
Symbolic-link traversal during archive unpacking in Red Hat's source-to-image (S2I) tooling lets an attacker who can supply or otherwise influence the builder image consumed by a build create links that resolve to absolute paths outside the extraction directory, allowing file reads or modifications beyond the intended sandbox on the host. The flaw is rated CVSS 3.1 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), so exploitation is not an unauthenticated drive-by: the attacker needs the privileges required to introduce or reference a malicious builder image, and only environments that run S2I builds against untrusted or attacker-influenced images are realistically exposed. The scope is marked Changed because the payload escapes the build container boundary, but confidentiality and integrity impact are each only Low; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Local denial of service in m17n-lib can crash applications on Red Hat Enterprise Linux 6 through 10 when they process specially crafted or truncated UTF-8 input. The flaw is a NULL pointer dereference reachable with a local attack vector and no authentication or user interaction, and it only affects availability, not confidentiality or integrity. No public exploit or confirmed active exploitation has been identified at time of analysis, and the issue is assessed as a moderate-severity local DoS rather than a high-priority remote threat.
Heap use-after-free in m17n-lib's input-method handling allows a local user who supplies specially crafted text to an application using m17n-based input engines to crash that application, producing a denial of service; arbitrary code execution is described as a potential, unverified outcome rather than a demonstrated one. The flaw is rated CVSS 6.2 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), so exploitation is local with no privileges required (PR:N) and no user interaction, and the only confirmed impact is availability loss with no confidentiality or integrity effect. Red Hat tracks the issue for Red Hat Enterprise Linux 6 through 10, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Integer overflow in GIMP's GIF export plug-in leads to a heap-based buffer overflow when a user exports an image whose width and height are large enough to wrap the 32-bit pixel-buffer size calculation, resulting in an out-of-bounds write that can crash the application or corrupt memory. Affected software is the GIMP package as distributed in Red Hat Enterprise Linux 6, 7, 8, 9 and 10, and exploitation is local (AV:L) with high attack complexity (AC:H) and mandatory user interaction (UI:R) while requiring no privileges (PR:N) - the attacker must induce a user to export an image with extreme dimensions. No public exploit identified at time of analysis, and the independent assessment rates this a moderate-severity, genuinely low-urgency issue rather than a top priority.
Local denial of service in m17n-lib, the multilingual input-method library shipped in Red Hat Enterprise Linux 6 through 10, can crash an application that opens an input method: a partial failure during library initialization leaves an internal driver pointer uninitialized, and the subsequent dereference is performed without validation. The assessed risk is genuinely low (CVSS 3.1 base 2.9; AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L), because the trigger - system resource exhaustion or corruption of the input-method database - is rare and cannot be reliably forced, the vector is local rather than remote, and the impact is confined to an application crash with no confidentiality or integrity effect. No public exploit identified at time of analysis, and there is no indication of active exploitation (not in CISA KEV).