Red Hat
Monthly
Sustained CPU consumption in m17n-lib allows an unauthenticated local attacker to hang applications that parse attacker-influenced text, because a crafted invalid UTF-8 byte sequence drives the library's text-parsing routine into a non-terminating loop (CWE-835) and pins a CPU core indefinitely, producing a denial of service (CVSS 6.2, AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Only systems where an application actually routes externally supplied text through m17n-lib's parsing path are exposed; hosts that never load the library are unaffected, and there is no code execution, data leakage, or integrity impact. There is no public exploit identified at time of analysis, and no vendor-released patch identified at time of analysis; Red Hat is tracking the issue under CVE-2026-107168 with Bugzilla 2547409.
Missing authentication in the smart_proxy_dynflow remote-execution callback handlers lets an unauthenticated network attacker forge progress and completion reports for a running job, causing the job to be recorded as a success or a failure with attacker-supplied output. The flaw (CWE-306) applies only when Red Hat Satellite 6 remote execution is configured in pull or pull-mqtt mode, and the attacker must already know the identifier of a live job and submit the forged report during that job's execution window, which is why the assessed severity is moderate (CVSS 5.9, AC:H, integrity-only). No public exploit code and no confirmed active exploitation were identified at time of analysis.
Keycloak's SMTP email configuration can silently fall back to unencrypted communication when STARTTLS is enabled, allowing an attacker who can intercept and tamper with traffic between the Keycloak server and its mail relay to capture SMTP credentials and email message content in cleartext. Affected deployments include Red Hat Build of Keycloak and Red Hat Single Sign-On 7 (CVSS 6.5, AV:N/AC:H/PR:N/UI:N), but exploitation is conditional: it requires a man-in-the-middle position on the SMTP path and an instance configured for opportunistic STARTTLS rather than implicit TLS. No public exploit code or confirmed active exploitation has been identified at time of analysis.
Path traversal in pulp-rpm's distribution tree publishing allows an authenticated user with sync or upload privileges to write files outside the intended task work area on the Pulp server. Crafted addon or variant ids in a .treeinfo file are used as directory names without sanitization, enabling the creation of new directories and writing of repository metadata and packages as the Pulp worker user. This is an integrity-only issue with no data disclosure or service disruption; no public exploit has been identified, and the practical risk is lower than the base CVSS 5.0 suggests due to the required privileges and the create-only constraint.
Pulp Ansible's bearer-token refresh for collection remotes can disclose access tokens to an authenticated attacker who can create or sync a remote and point it at a malicious server. The attacker must then reuse the token at the issuing service, and exploitation is only possible if another token download for a different remote has run on the same worker process, meaning shared, multi-tenant deployments are primarily at risk. No public exploit code exists, and the assessed attack complexity is high (AC:H), so this is a moderate-priority information disclosure issue rather than a top-tier emergency.
Authenticated users with permission to create and sync container remotes in Pulp can obtain upstream registry credentials-usernames, passwords, or bearer tokens-stored for other remotes because the pulp-container worker reuses authentication material across sync operations. This affects deployments built on Red Hat Ansible Automation Platform 2, Red Hat Satellite 6, and Red Hat Update Infrastructure 4/5, particularly multi-tenant environments where remotes share worker processes. No public exploit code or confirmed active exploitation has been identified; the flaw rates CVSS 6.5 (moderate) and requires no user interaction beyond the attacker's own sync, though it does require an authenticated user with remote-creation and sync privileges.
Out-of-bounds heap reads in GIMP's XMC (X cursor) thumbnail loader can crash the application or corrupt process memory when a victim opens a crafted XMC file, or when thumbnail generation is triggered for one by a file manager. The root cause is an integer overflow: the loader sizes a pixel buffer using width * height computed in 32-bit signed arithmetic, so an oversized product wraps to a small allocation that a later GEGL buffer read then indexes using the unwrapped dimensions. Exploitation is strictly local and user-interaction dependent (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H, 5.5), with no network attack surface and no confidentiality or integrity impact; no public exploit code and no confirmed active exploitation were identified at time of analysis, and Red Hat tracks the issue across RHEL 6 through 10.
Local denial of service in the SSSD autofs responder allows an authenticated user on an affected host to exhaust memory by repeatedly racing concurrent map enumeration requests against map invalidation requests. Per the assessed vector (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H), the attack requires local, valid credentials and depends on winning a narrow timing window, so successful sustained exploitation is non-deterministic; hosts that do not run the autofs responder are not exposed. Impact is confined to availability - leaked memory accumulates until the autofs service is degraded or crashes - with no confidentiality or integrity effect. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing), and the 4.7 base score reflects the local, high-complexity prerequisites rather than the broad enterprise presence of SSSD.
Memory exhaustion in the SSSD (System Security Services Daemon) can be triggered by an unauthenticated local attacker who repeatedly initiates Identity Provider (IdP) pre-authentication flows without completing them, causing uncleared in-memory state to accumulate until authentication services degrade or terminate (denial of service, CVSS 6.2). The flaw (CWE-770) affects SSSD on Red Hat Enterprise Linux 6, 7, 8, 9, and 10 as well as Red Hat OpenShift Container Platform 4, but only when IdP authentication is explicitly enabled, which is not the default configuration. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
DOM-based cross-site scripting in the Red Hat Ansible Automation Platform UI allows an attacker-crafted link to execute arbitrary JavaScript inside a logged-in user's session, because a specific redirect route takes the destination from the 'next' query parameter and assigns it straight to the browser's location.href while bypassing the platform's own URL and scheme validation. Exploitation is constrained by two concrete prerequisites: the victim must already be authenticated to the platform UI (PR:L) and must actively click the malicious link (UI:R), which is why the issue carries a moderate CVSS 3.1 base score of 5.4 rather than a critical rating. No public exploit code and no confirmed active exploitation were identified at the time of analysis, and the risk is best characterized as a moderate, not top-priority, issue that should be scheduled rather than emergency-patched.
A local, authenticated user on hosts running sssd (System Security Services Daemon) can stall the daemon's responder service by opening and holding a large number of concurrent connections to a responder socket while continuing to queue new connection attempts, driving the responder past its file-descriptor limit into an unthrottled retry loop. The result is a denial-of-service condition with high CPU consumption that blocks legitimate identity and authentication lookups (NSS/PAM) for other users. Exploitation requires local access and is rated high complexity (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H, base 4.7), so realistic exposure is concentrated on shared or multi-user systems rather than single-administrator hosts; there is no public exploit identified at time of analysis and no confirmed active exploitation (no CISA KEV listing).
Authentication bypass in Keycloak's OIDC Device Authorization Grant flow allows an attacker who already possesses a valid user password to evade a client's configured minimum authentication level, including mandatory multi-factor authentication, and gain unauthorized access to the Keycloak Admin REST API, according to Red Hat. The flaw is a missing enforcement check (CWE-287) affecting Red Hat Build of Keycloak and Red Hat Single Sign-On 7 deployments where the device authorization flow is enabled for a client that requires elevated authentication. Exploitation requires prior credential compromise (CVSS PR:L) and the targeted client must actually mandate MFA or another authentication level; no public exploit code or CISA KEV active exploitation is identified in the available data, and EPSS is not provided. The CVSS score is 5.4 (moderate), with limited confidentiality and integrity impact.
Denial of service in sssd passkey authentication handling allows any local user to crash the PAM responder by sending a crafted PAM request. The flaw, a missing state validation check leading to an uninitialized pointer dereference (CWE-476), affects sssd on Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 when passkey authentication is enabled-a non-default configuration. With a CVSS score of 6.2 (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), impact is limited to availability; no public exploit has been identified at time of analysis, and exploitation requires local access and the passkey feature to be active.
A local denial of service in SSSD's Name Service Switch (NSS) responder lets an attacker who can reach the responder's UNIX socket crash the name-resolution service by sending a crafted request containing an undersized packet header, which causes an integer underflow followed by an out-of-bounds read during packet parsing. Affected deployments are Red Hat Enterprise Linux 6, 7, 8, 9, and 10, plus Red Hat OpenShift Container Platform 4 nodes running SSSD. The impact is availability-only (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), exploitation requires prior local access and socket reachability, and no public exploit identified at time of analysis.
A local, low-privilege attacker can crash the SSSD PAM responder on Red Hat Enterprise Linux (versions 6 through 10) and Red Hat OpenShift Container Platform 4 by sending a crafted PAM request that contains a zero-length authentication token. The flaw, tracked as CVE-2026-104042 with a CVSS score of 5.5, stems from missing length validation that leads to an out-of-bounds read and a denial of service; it requires an existing local account and no user interaction. No public exploit code has been identified at time of analysis, and this is a moderate-severity local DoS rather than a remote or privilege-escalation issue.
Unprivileged local users can exhaust memory in the SSSD NSS responder by repeatedly requesting lookups for nonexistent entries, causing denial of service on Red Hat Enterprise Linux 6 through 10 and Red Hat OpenShift Container Platform 4. The negative cache in SSSD lacks a bound on total stored entries and only evicts expired records when an existing key is rechecked, so the cache grows until the responder becomes unresponsive or terminates. This is a local, availability-only issue requiring an authenticated account (CVSS 5.5, PR:L); no public exploit code or active exploitation is identified at time of analysis.
SSSD configured with the Microsoft Entra ID identity provider fails to neutralize single quotes in lookup names before embedding them into Microsoft Graph OData queries, enabling an authenticated local attacker to inject filter syntax. This can broaden user or group searches, leading to information disclosure of unintended directory objects and a denial of service through excessive processing and cache population. The CVSS vector (AV:L/PR:L) confirms the attack is local and requires low privileges, and exploitation is only possible when the non-default Entra ID backend is enabled; no public exploit or active exploitation is reported, and no EPSS score was provided.
Denial of service in SSSD allows a local, already-authenticated user who can reach the PAM responder and complete a GSSAPI authentication request to send a follow-up request over the same connection, dereferencing freed cached connection state and terminating the service, which disrupts system authentication. Per the authoritative assessment the issue is rated CVSS 4.7 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H): it is local-only, requires valid low-level credentials on the host, and is constrained by high attack complexity because the dangling-pointer dereference depends on request timing and sequencing over a reused connection. Impact is availability-only - no confidentiality or integrity effect - and no public exploit identified at time of analysis (no CISA KEV listing and no publicly available exploit code in the provided intelligence).
Denial of service in SSSD (the System Security Services Daemon) allows remote unauthenticated attackers to crash the daemon by presenting a certificate that is missing the expected Security Identifier (SID) extension during authentication or lookup operations. Only deployments explicitly configured with SID-based certificate mapping rules reach the vulnerable code path, since the certificate-to-user lookup logic dereferences the SID extension without first confirming it exists; standard installations that do not use SID-based certificate mapping are not affected. The flaw is rated CVSS 5.9 (AV:N/AC:H/PR:N/UI:N/C:N/I:N/A:H, availability-only) and, per available intelligence, no public exploit code exists and exploitation has not been confirmed as active - no public exploit identified at time of analysis.
Denial of service in SSSD's autofs responder allows a local attacker with an existing account on the host to crash the responder process by writing a specially crafted request containing an invalid packet length to its UNIX domain socket. The malformed length triggers an integer underflow that produces an out-of-bounds read (CWE-125), terminating the responder and disrupting automount map lookups; there is no confidentiality or integrity impact and no remote vector. Exploitation requires the autofs responder to be enabled in sssd.conf and local reachability of its socket (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 5.5); no public exploit code and no confirmed active exploitation were identified at time of analysis. Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 (via packaged SSSD) are listed as affected.
Access control bypass in SSSD when configured with non-default ordering that evaluates password-expiration warnings before restrictive access rules allows remote authenticated users with expired passwords to gain unauthorized access to protected systems via alternative authentication methods such as SSH public key authentication. This flaw (CWE-393) affects Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 deployments using LDAP access control. Exploitation requires a specific non-default configuration, an expired password, and a non-password authentication path, making it a moderate conditional risk; no public exploit identified at time of analysis.
SSSD's NFS idmap plugin contains an out-of-bounds write (CWE-787): when a cached user or group name is larger than the destination buffer it is copied into, the size check fires but the copy proceeds anyway. An authenticated, low-privileged local attacker can request identity lookups that resolve to such oversized cached entries, crashing the identity-mapping service (denial of service) and potentially corrupting adjacent process memory; the attack is local-only and depends on the oversized-cache precondition, giving it high attack complexity (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H, 5.8). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
Local denial of service in the SSSD Kerberos Credential Manager (KCM) responder allows an authenticated local user to exhaust host memory and make the service unresponsive by holding a persistent connection open while repeatedly storing and destroying Kerberos credentials. The flaw is a resource-lifecycle defect (CWE-772): cached objects are not released when credentials are removed, so memory grows monotonically until the responder stalls. Exploitation requires a valid local account and sustained store-then-destroy activity, yields availability impact only (CVSS 5.5, AV:L/PR:L/UI:N/A:H), and does not provide code execution or privilege escalation; no public exploit code or confirmed active exploitation was identified at time of analysis, and systems that do not use the KCM responder are not affected.
The SSSD Kerberos Credential Manager (KCM) responder can be crashed by an authenticated local user who holds a renewable Kerberos ticket-granting ticket, because a deferred callback in the TGT renewal path dereferences memory that has already been freed. Exploitation is conditional on the host being explicitly configured for KCM-based credential renewal (a non-default, feature-dependent prerequisite), and the assessed vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (4.7) reflects local access, high attack complexity, and an availability-only impact confined to the sssd-kcm service. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); overall this is a medium/low-priority denial-of-service issue rather than a high-CVSS/low-real-risk outlier.
Authentication bypass in SSSD permits a user with valid credentials for an already-expired account to authenticate to the system when SSSD is configured to enforce account expiration using LDAP shadow attributes and the expiration value is stored as zero. This moderate-severity logic flaw (CVSS 5.4, CWE-193) affects Red Hat Enterprise Linux 6, 7, 8, 9, and 10, as well as Red Hat OpenShift Container Platform 4; exploitation requires the non-default shadowExpire=0 configuration and valid credentials for the expired account. No public exploit code or active exploitation has been identified at time of analysis.
Denial of service in SSSD's autofs responder allows an authenticated local unprivileged user to repeatedly request master automount map updates, triggering global cache invalidation and forcing repeated backend directory lookups, which degrades automount availability and elevates resource consumption. Affects Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 when SSSD-backed automount maps are served from a backend directory provider such as LDAP or Active Directory. This is a moderate-priority local availability issue (CVSS 5.5) with no public exploit code identified at time of analysis.
Memory exhaustion in the SSSD autofs responder can let a local, authenticated unprivileged user deny service on affected hosts by holding an open client connection while repeatedly submitting valid requests, since per-request memory is only reclaimed when the connection closes. The flaw affects SSSD deployments on Red Hat Enterprise Linux 6 through 10 and Red Hat OpenShift Container Platform 4, but the vulnerable code path is only reachable when the autofs responder is explicitly enabled in sssd.conf - a non-default configuration. Exploitation is limited to local access (AV:L/PR:L) with no impact on confidentiality or integrity, so it is correctly rated medium (CVSS 5.5); no CISA KEV entry and no public exploit code have been identified at time of analysis, and a realistic impact generally requires a shared, multi-user host where one user's resource consumption degrades service for others.
Authentication bypass in the maestro gRPC broker shipped with Red Hat Multicluster Engine for Kubernetes lets a client that already holds a valid mTLS client certificate skip the broker's authentication check and then subscribe to other consumers' event streams or publish forged agent status messages. The consequence is unauthorized information disclosure and loss of data integrity inside the broker, with no availability impact and scope unchanged; the assessed CVSS 3.1 base score is 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N). There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis, and the valid-client-certificate prerequisite confines abuse to trusted-but-lower-privileged or already-compromised clients rather than anonymous remote attackers.
Crashing the SSSD autofs responder process via a crafted request to its UNIX socket allows a local, low-privileged attacker to cause a denial of service on affected Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 systems. The vulnerability stems from improper buffer offset calculation during request parsing, leading to an out-of-bounds read (CWE-125) that terminates the responder process; it carries a CVSS 3.3 (Low) score with no confidentiality or integrity impact. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and the autofs responder service must be enabled for the flaw to be exploitable.
A local, low-privileged user can crash the sssd authentication daemon by submitting a crafted passkey (FIDO2/WebAuthn) authentication token that omits expected null terminators, causing an out-of-bounds read and terminating the service, which disrupts authentication for all users relying on that host. Rated CVSS 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), the flaw is purely an availability issue confined to systems where sssd's passkey authentication path is configured and reachable; there is no confidentiality or integrity impact and no remote or unauthenticated route. At the time of analysis, no public exploit code has been identified and there is no confirmed active exploitation (not listed in CISA KEV), and no vendor-released patch has been identified.
Unauthenticated REST API write access in Maestro, the messaging and resourcing component shipped with Red Hat Multicluster Engine for Kubernetes, lets a remote attacker create, modify, or delete consumers and resource bundles without supplying any credentials, token, or session. Because the affected endpoints were registered without authentication middleware (CWE-306), preconditions reduce to network reachability of the Maestro API: deployments where the API is cluster-internal, gated by NetworkPolicy, or fronted by an authenticating gateway/service mesh are materially less exposed, while anything publishing those endpoints are directly exploitable with no user interaction. The exploitability posture is driven by impact rather than by observed activity - integrity is assessed as high and availability as low, and no public exploit code or confirmed in-the-wild exploitation (CISA KEV) was identified at time of analysis.
SQL injection in the maestro component of Red Hat Multicluster Engine for Kubernetes (MCE) allows remote attackers to perform read-only blind extraction of database contents through the orderBy parameter on REST API list endpoints. The vendor CVSS vector specifies PR:L, indicating a low-privileged authenticated account may be needed, while the description and independent assessment note that authentication may not be required; defenders should resolve this discrepancy because it changes exposure materially. At time of analysis there is no public exploit identified, and exploitation is constrained by blind, read-only extraction and the requirement for network reachability to the vulnerable MCE API; CVSS is 6.4 medium severity.
Argument injection in the OpenPrinting CUPS mailto notifier can let a low-privileged user or authorized subscription creator influence the configured sendmail command when CUPS email notifications are enabled. Exploitation requires a crafted notify-recipient-uri beginning with '-' and an MTA that interprets it as an option; the assessed risk is low because email notification is non-default, CUPS is typically local-only (AV:L), complexity is high, and impact is limited to low confidentiality and integrity in the assessed vector. No public exploit identified at time of analysis. Affected deployments include upstream OpenPrinting CUPS and CUPS in Red Hat Enterprise Linux 8, 9, 10, and Red Hat Hardened Images.
Cross-site scripting in Red Hat Quay 3 lets an unauthenticated remote attacker execute arbitrary script in a victim's authenticated browser session by tricking the user into completing login through a crafted URL, because the application does not validate the post-login redirect destination before navigating. Exploitation is tightly constrained: the deployment must be configured with direct database authentication (installs delegating to OIDC/LDAP/SSO are unaffected) and the victim must both click the malicious login link and finish authenticating through it. Severity is low-to-moderate (CVSS 4.2, AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N), impact is confined to the victim's own session, and no public exploit identified at time of analysis.
Cross-site scripting in the OAuth callback handler of Red Hat Quay 3 lets an unauthenticated remote attacker run arbitrary JavaScript in a logged-in user's browser session by luring that user to a crafted URL, with no attacker privileges required (PR:N) but mandatory victim interaction (UI:R), giving a CVSS 3.1 score of 5.4. Successful exploitation is scoped to the victim's Quay application session (S:U, low confidentiality and integrity impact, no availability impact), potentially exposing registry metadata or allowing actions to be performed as the victim, rather than yielding server-side compromise. The vulnerability class is CWE-79 improper neutralization of input during web page generation; no public exploit code was identified in the available intelligence at the time of analysis, and CISA KEV status was not indicated.
Denial of service in FreeType's CID-keyed font loader allows attackers to exhaust memory and CPU by supplying a crafted font that triggers repeated allocation and decryption of subroutine data across multiple font dictionaries, causing the consuming application or service to hang or terminate. The issue is rated CVSS 5.5 with availability-only impact (A:H, C:N/I:N) and is gated by user interaction - someone or some automated process must actually load and parse the malicious font, which can be delivered by embedding it in a document, web page, or other parsed content. No public exploit code and no confirmed active exploitation were identified at time of analysis, but the Red Hat advisory points to an upstream FreeType fix commit (f3ca71c9900fe860849b3163a6e2c1e765b291d9) and tracks the flaw under Bugzilla 2462295, so a patched release should be expected; the practical risk is highest for unattended font- or document-processing pipelines rather than interactive desktop use.
Information disclosure and denial of service in Keycloak's X.509 client certificate authenticator occur when CRL Distribution Point checking is enabled and an unauthenticated remote attacker submits a crafted client certificate. The server fails to properly validate file paths from the certificate, allowing limited local file reads and extreme memory consumption that can crash the system; exploitation requires the non-default combination of certificate-based client authentication and CRL checking, and no public exploit was identified at time of analysis.
An authorization bypass in Red Hat Satellite's Katello RegistryProxiesController allows an authenticated low-privilege attacker to enumerate valid Users, Organizations, and Products across the instance via differential responses. The flaw stems from a missing return statement in the registry_authorize filter, which flags unauthorized requests but fails to halt execution, letting the request proceed into database validation filters that leak internal state. No public exploit identified at time of analysis; the vendor has released an errata (RHSA-2026:74503).
An authenticated low-privileged user can inject SQL through the Katello Registry Proxy in Red Hat Satellite 6 by placing a crafted label in the request path, allowing them to read arbitrary data from the Satellite database. The vulnerable code paths (check_blob_push_org_label and get_matching_products_from_org) interpolate request-supplied labels straight into raw SQL, and the only prerequisite is an account holding the create_personal_access_tokens permission - even a heavily restricted account with no Organization or Location assigned, which makes the effective privilege bar unusually low. Impact is limited to confidentiality (CVSS 6.5, C:H/I:N/A:N); no public exploit code has been identified at time of analysis, and Red Hat has published erratum RHSA-2026:74503 to address the flaw. This is a genuine but moderate-priority issue, not a critical drop-everything vulnerability.
Command injection in Red Hat Satellite's Hammer CLI (rubygem-hammer_cli) allows a local authenticated user to run arbitrary shell commands by controlling the $EDITOR environment variable, which the application interpolates into a single-string Ruby system() call that is then interpreted by /bin/sh. The flaw affects Red Hat Satellite 6 and Satellite 6.19 for RHEL 9, and exploitation requires an attacker to already hold a valid local account, be able to set $EDITOR, and trigger a CLI operation that launches an external editor (such as editing a resource), meaning remote or unauthenticated exploitation is not possible. Public exploit code and confirmed active exploitation are not indicated in the available intelligence, and Red Hat has published an erratum (RHSA-2026:74503) to address the issue.
Path traversal and symlink-validation flaws in ansible-runner's unstream_dir() (CVE-2026-103754) let an authenticated, low-privilege actor who can inject crafted archive content into the transmit/worker protocol create files, create symlinks, or change permissions outside the intended extraction directory, which can be leveraged toward code execution. The issue affects ansible-runner as shipped in Red Hat Ansible Automation Platform 2 (and upstream/AWX deployments) prior to the PR #1550 fix and carries a vendor-assigned CVSS 3.1 base score of 5.9 (AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L). No public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation is constrained by the need to supply crafted archive members into this specific worker protocol path.
Post-login redirection in OpenShift's oauth-proxy fails to validate the `rd` destination parameter, so a remote unauthenticated attacker who convinces a user to follow a crafted link can send that user's browser to an arbitrary external website once authentication completes (CWE-601, CVSS 6.1). Red Hat OpenShift Container Platform 4 deployments that expose oauth-proxy login flows are affected, and exploitation depends on the victim clicking the attacker's link and authenticating through that proxy (UI:R); the resulting impact is a browser redirect rather than code execution or data compromise, with real risk arising when the victim is socially engineered into trusting the attacker-controlled landing page for phishing or credential harvesting. No public exploit identified at time of analysis, no CISA KEV listing, and no EPSS score was supplied with the source data.
GEGL's Radiance HDR loader reads past the end of a memory-mapped image when a crafted .hdr file declares a scanline width larger than the actual data present in an uncompressed scanline, crashing the application that consumes the library - most notably GIMP, which uses GEGL for image processing. Any local user who opens such a file is affected; no authentication is required to the library, but the attacker must convince a victim to open the crafted file (UI:R), and the impact is availability-only (CVSS 5.5, AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, consistent with a low-priority, local denial-of-service rather than a code-execution primitive.
HTTP request smuggling in libsoup's SoupServer - as shipped in Red Hat Enterprise Linux 6, 7, 8, 9, and 10 - allows remote, unauthenticated attackers to have an attacker-controlled HTTP request processed as an unintended subsequent request on a keep-alive connection. The issue triggers when an HTTP/1.x client sends 'Expect: 100-continue' with a declared body and the SoupServer-based application issues an early final (non-1xx) response before that body is read; SoupServer then neither drains the body bytes nor closes the connection, so the leftover bytes are parsed as the next request. Rated CVSS 3.1 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N), the flaw carries limited integrity impact on request handling while leaving confidentiality and availability unaffected, and it is inert unless the specific combination of keep-alive, a declared body, and an early final response is present. No public exploit code and no confirmed active exploitation were identified at time of analysis.
An out-of-bounds write in the printf builtin of the dash shell allows a local user to corrupt one or two bytes past a four-byte reservation when a crafted Unicode \u or \U escape expanding to a five- or six-byte token is processed, including via 'dash -c' with the escape passed as a positional argument to printf or 'echo %b'. The flaw affects dash as shipped in Red Hat Enterprise Linux 6 (CPE cpe:2.3:a:red_hat:red_hat_enterprise_linux_6) and is rated CVSS 4.0 (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N). No public exploit code was identified at time of analysis, and the bounded write stays within the caller's own shell process, so it provides no inherent privilege escalation.
Local denial of service in the dash shell affects builds compiled without libc fnmatch, where the internal pmatch() matcher handles the '*' wildcard by unbounded recursion over candidate positions. A local attacker who can plant filenames in a directory that later gets globbed - or otherwise feed the internal matcher - can supply a short multi-star pattern such as *.*.*.*.*.tar.gz and drive excessive CPU consumption in the affected shell process. The issue requires a non-default build configuration (PR:L, AV:L, no remote reachability, no privilege escalation or data disclosure), maps to CWE-1333 (inefficient regular expression complexity) with a CVSS 3.1 score of 5.5, and there is no public exploit identified at time of analysis and no confirmed actively exploited status (CISA KEV).
ServiceAccount token exfiltration in the StreamsHub Console for Apache Kafka lets a user who already holds RBAC permission to create or modify the Console custom resource point the console-api AdminClient at an attacker-controlled broker. Tenant-supplied Kafka client properties are copied into the AdminClient configuration without filtering security-sensitive keys, so setting config.providers and bootstrap.servers causes the console-api ServiceAccount token to be read and leaked off-cluster. The issue is rated CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, CWE-470) and is a moderate-severity, privilege-dependent information disclosure: it requires an authenticated, semi-trusted role with write access to Console CRs (PR:L), so clusters with tight RBAC on those resources are substantially less exposed, and unauthenticated external actors cannot trigger it. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV); no EPSS score was provided.
Keycloak's Micrometer user-event metrics listener can be forced to create unbounded metric time series by unauthenticated remote requests to the identity broker login endpoint with arbitrary provider aliases, leading to memory exhaustion and performance degradation. This is a low-priority issue because exploitation requires the non-default configuration of including the 'idp' tag in the listener, and the impact is limited to a gradual availability degradation (A:L). No public exploit code has been identified at the time of analysis.
Privilege escalation in the Fine-Grained Admin Permissions v2 (FGAP v2) feature of Keycloak lets an authenticated delegated administrator with role-assignment rights grant a composite role whose transitive contents are never inspected, silently conferring full realm administrative control. Exploitation requires that FGAP v2 be enabled for delegated administration, a limited-admin credential holding role-mapping permissions (CVSS vector PR:H), and the presence of a composite role that transitively contains realm-admin privileges within that administrator's assignable scope; the high attack complexity (AC:H) reflects these preconditions rather than any exploitation difficulty, and the resulting impact is a complete confidentiality, integrity, and availability compromise of the realm (CVSS 6.6). No public exploit code and no confirmed active exploitation have been identified at time of analysis, so this should be treated as a genuine but conditional authorization-logic flaw rather than a remotely exploitable takeover.
mTLS holder-of-key certificate binding is not enforced in Keycloak's Standard Token Exchange V2 flow, so an attacker who already holds valid confidential client credentials can obtain a standard, unrestricted token that escapes the certificate-binding protection the deployment believed was in place. Affected distributions include Red Hat Build of Keycloak and Red Hat Single Sign-On 7, and exploitation is conditional on three things being true at once: the attacker must already possess a stolen client secret or key (the CVSS vector rates this PR:L - a precondition the flaw itself does not grant), the deployment must have Standard Token Exchange V2 enabled and in active use, and the deployment must be relying on mTLS holder-of-key binding as a hardening control. No public exploit code has been identified at time of analysis and there is no CISA KEV listing; the assessed vector (AV:N/AC:H/PR:L/UI:N, C:H/I:H/A:N) reflects a genuine but conditional security-control bypass rather than a mass-exploitable flaw, since certificate-bound tokens are a non-default opt-in configuration.
Ansible Automation Platform 2's gateway permits an authenticated gateway administrator (CVSS PR:H) to create a new service key for the Controller service cluster through the API, even though service-key creation is supposed to occur only via the installer-provisioned path; the resulting key is cryptographically indistinguishable from a legitimate one, so it can be used to mint a service-authentication token that impersonates the Controller service. When the non-default gateway OIDC workload-identity endpoint is enabled (FEATURE_OIDC_WORKLOAD_IDENTITY_ENABLED) and a downstream resource server such as HashiCorp Vault trusts the gateway's OIDC signing key, the attacker can induce the gateway to sign Workload Identity Tokens for arbitrary Controller workloads and retrieve the AAP credentials bound to that workload, crossing the administrator's authorization boundary to disclose secrets (C:H, no integrity or availability impact). Exploitation requires admin privileges plus that specific non-default trust configuration, and no public exploit has been identified at time of analysis; the defect is access-gated rather than broadly exploitable.
Information disclosure in the Keycloak Admin REST API lets an authenticated delegated administrator holding only basic group/role search privileges enumerate every group assigned to a given role, including groups they are supposed to be unable to see. The flaw (CWE-862, missing authorization) affects the Admin REST API endpoints that return role-to-group mappings in Keycloak, Red Hat Build of Keycloak, and Red Hat Single Sign-On 7, and is rated CVSS 3.1 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) - a read-only confidentiality impact with no integrity or availability effect. It requires valid, privileged-but-scoped credentials and is only meaningful where an organization actually partitions group visibility across delegated admins; there is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing).
Authenticated delegated administrators in Keycloak can reset other users' passwords and take over their accounts when Fine-Grained Admin Permissions (FGAP) are enabled, because the Admin REST API's general user-update path skips the password-reset authorization check that the dedicated credential-reset flow enforces. Red Hat Build of Keycloak and Red Hat Single Sign-On 7 are the affected downstream products, and the flaw is rated 6.6 (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H, CWE-862). Exploitation is conditionally gated rather than internet-facing: it requires a non-default FGAP configuration and an already-provisioned semi-trusted admin holding user-profile edit rights but deliberately denied password-reset rights, making this an insider or lateral privilege-escalation issue; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.
Keycloak's Level of Authentication (LoA) step-up enforcement can fail open: when a relying client requires a higher authentication level for a user who already holds an active session at a lower level, a logic error in session re-evaluation causes Keycloak to issue a token carrying the lower acr/LoA claim instead of forcing the required step-up authentication. The impact is a bounded assurance downgrade rather than unauthenticated access - the attacker must already be authenticated (CVSS PR:L) - but it may grant access to sensitive resources whose authorization decisions trust those claims, with low confidentiality and integrity impact and no availability impact (CVSS:3.1 4.2, AV:N/AC:H/UI:N/S:U/C:L/I:L/A:N). Exploitation depends on a deployment that actually configures per-client step-up/LoA and on a specific session-state and re-evaluation timing; no public exploit code has been identified at time of analysis and this CVE is not listed in CISA KEV.
Argument injection in Red Hat Ansible Automation Platform 2's automation-controller system-job subsystem allows an authenticated user with superuser privileges to inject arbitrary command-line arguments into the control-plane awx-manage process, gaining control of its argument vector and the first entry of its Python module search path. The root cause is that the system-job template launch endpoint stores a caller-supplied 'days' value without applying the integer validation used elsewhere for that field, and the dispatcher flattens the management-command argument list into a single space-delimited string that the job runner re-splits, so embedded spaces become additional arguments; system jobs run in-process on the control node without the container isolation applied to other job types. Confirmed remote code execution does not follow from the injected arguments alone - it would require an additional import gadget that is not present in the current management commands - so the demonstrated impact is argument injection and search-path control rather than code execution, and no public exploit was identified at time of analysis.
Server-side request forgery in Red Hat Ansible Automation Platform 2's automation-controller email notification backend lets an authenticated user holding organization notification-admin permission point an email notification template's SMTP host and port at arbitrary internal, loopback, link-local or reserved addresses; the controller task process then opens a raw TCP connection to that target when the notification test is triggered. Because the resulting connection error is surfaced through the notification record, an attacker gains a three-state internal port-scan oracle (open, closed, filtered) over the control-plane cluster network, including the in-cluster Kubernetes API, and if a shared organization template stores an SMTP password, redirecting the host can leak that credential to an attacker-controlled server. Impact is moderate (vendor CVSS 6.4, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) and requires a privileged, already-authenticated role rather than anonymous access; no public exploit code has been identified at time of analysis and CISA KEV does not list this CVE.
Secret values that playbook authors explicitly marked with no_log can be recovered from Red Hat Ansible Automation Platform 2 (automation-controller) through the REST filter backend, because the WorkflowJobNode.ancestor_artifacts column is not wrapped in prevent_search() and therefore remains queryable even though it is omitted from the API serializer. An authenticated user - one with only read access to a workflow, or any authenticated user with no roles at all by abusing a regular-expression lookup that bypasses the JSON cross-relation filter guard via the world-readable credential-types endpoint - can use the result count as a boolean/count oracle to extract secrets character by character, potentially across organizations. The issue is rated CVSS 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, CWE-639); no public exploit code or confirmed active exploitation was identified at time of analysis, and because recovery requires an account plus many incremental requests per character, the practical risk is a bounded confidentiality exposure rather than a top-tier emergency.
Source-IP spoofing in Ansible Automation Platform 2's automation-controller allows an authenticated remote attacker to forge the client IP recorded in audit and access logs when the application runs its shipped production reverse-proxy configuration and trusts the client-supplied X-Forwarded-For header. The flaw is CWE-348 and only affects log integrity (CVSS 3.1 4.3, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), with no access, confidentiality, or availability gain. No public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV).
Red Hat Ansible Automation Platform 2 (automation-controller) lets an unauthenticated remote attacker enumerate which Job Template and Workflow Job Template IDs have a Bitbucket Data Center webhook configured, by abusing an observable response discrepancy in the Bitbucket DC webhook receiver. For diagnostics:ping events the receiver performs the template lookup before HMAC signature verification is skipped, so the endpoint returns HTTP 200 for a template with a Bitbucket DC webhook and HTTP 403 otherwise - an oracle that requires neither authentication (PR:N in the assessed vector) nor knowledge of the secret webhook_key. Assessed at CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), this is a low-impact information-disclosure and enumeration issue: no secrets, code execution, or elevated access are exposed; no public exploit identified at time of analysis and no confirmed actively exploited status.
TLS peer impersonation in Red Hat Ansible Automation Platform 2's automation-controller instance install-bundle endpoint lets an authenticated controller System Administrator obtain a mesh-CA-signed X.509 certificate that TLS peers will accept as a different control node. The flaw arises because a caller-chosen instance hostname is copied verbatim into the certificate's Common Name, DNS SAN, and receptor node-id, and the hostname charset validator is case-insensitive while the uniqueness validator is case-sensitive, so a case variant of an existing control node's hostname passes registration and yields a hard-coded ten-year, non-revocable mesh peer credential. Realizing the impact additionally requires an on-path/man-in-the-middle position on the receptor mesh, and the scenario is most meaningful in managed or hosted deployments where a customer holds controller superuser while the platform operator runs the mesh; there is no public exploit identified at time of analysis, and the flaw does not grant direct remote code execution because receptor work submission is gated by a separate signing key absent from the bundle.
Authenticated users of any privilege level on Red Hat Ansible Automation Platform 2 automation-controller deployments can extract other tenants' notification secrets-PagerDuty service keys and Slack, Mattermost, RocketChat, and generic Webhook bearer-token URLs-by abusing the API filter backend as a boolean count-oracle. The attack requires only a low-privilege account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, base 6.5), is network-reachable and low in complexity, and yields high confidentiality impact with no integrity or availability effect. Impact is greatest in multi-tenant installations where recovered secrets break organization isolation and permit notification-channel impersonation; exploitation is inherently slow, requiring many iterative requests that may be visible in API logs. No public exploit code has been identified at time of analysis, and the flaw is not listed as confirmed actively exploited (CISA KEV).
Information disclosure in the automation-controller API of Red Hat Ansible Automation Platform 2 lets any remote unauthenticated party read the automation mesh topology from the health-check endpoint /api/v2/ping/ (CVSS 3.1: 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N). Because the ApiV2PingView view is declared with the AllowAny permission class and over-serializes RBAC-gated mesh data into its anonymous response, an attacker needs only network reachability to walk away with node hostnames, node types, UUIDs, heartbeats, capacities, exact software versions, instance-group names and membership, the deployment install UUID, and the identity of the active control node. The exposure is confidentiality-only - no secrets, credentials, or tenant data are involved - and there is no public exploit identified at time of analysis, so this is a genuine but modest reconnaissance-grade issue rather than an urgent one.
Opening a crafted uncompressed DDS image in GIMP triggers a one-byte heap out-of-bounds read in the file-dds plug-in, which can crash the plug-in process. The flaw requires a local user to open the malicious file (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L), and the crash is non-deterministic because it only occurs when the byte past the pixel buffer lands on an inaccessible memory page; no information disclosure or code execution has been demonstrated. No public exploit code has been identified at time of analysis, and while downstream tracking covers Red Hat Enterprise Linux 6 through 10, the availability-only impact keeps real-world risk low and the 'RCE', 'Buffer Overflow' and 'Information Disclosure' tags attached to this record are not supported by the assessed vector.
Argument injection in the ad hoc command builder of Red Hat Ansible Automation Platform 2 lets an authenticated user who is permitted to run ad hoc commands smuggle ansible CLI options by passing a host-restriction (`limit`) value beginning with a hyphen, which ansible-core then parses as an option flag. Impact today is minimal (CVSS 3.1, CWE-88): because the injected token displaces the required `pattern` positional argument, only short-circuit flags such as `--version` and `--help` are reachable, so integrity impact is limited to low and no arbitrary option or command control is achievable. There is no public exploit identified at time of analysis, and the issue would only escalate if a future ansible-core release were to default or make optional the `pattern` positional - a hypothetical, non-default upstream change rather than current behavior.
Red Hat Ansible Automation Platform 2 (AWX) accepts leading-dash values in the scm_branch field processed by LaunchConfigurationBaseSerializer, allowing an authenticated user who can create or edit a Schedule or Workflow Job Template node to supply a value such as --upload-pack=/bin/id. The gap is a latent argument-injection issue (CWE-88) that is currently neutralized at runtime by the ValueError guard at jobs.py:1502, so no command execution occurs in shipping code; it would escalate to remote code execution only if that task-layer guard were refactored or removed in a future release. No public exploit code has been identified at time of analysis, and impact today is limited to a low-severity hardening gap (CVSS 3.1, integrity-only).
Information disclosure in Red Hat Ansible Automation Platform 2 allows an authenticated administrator (PR:H per the CVSS vector) to leak controller-side implementation details, including install paths, Python version, and source line numbers, into notification payloads delivered to an attacker-controlled webhook URL. A crafted Jinja notification template using a dynamic subscript such as job['job'+'_env'] slips past the static-Getattr AST whitelist, while a conditional gate like {% if job.id > 100 %} prevents the branch from firing during the small-job.id stub test-render, so the payload executes only against a real job whose exception produces a full traceback in the notification body. Impact is confined to low confidentiality loss (C:L) with no integrity or availability effect, and no public exploit has been identified at time of analysis.
Out-of-bounds heap read in GIMP's TIM image loader is triggered when a user opens a crafted 4bpp TIM image that is promoted to an RGBA layer, causing the file-tim plug-in to allocate an undersized row buffer and then process it with the larger RGBA row size. The result is disclosure of adjacent heap memory into the decoded image and a possible plug-in crash, with exploitation requiring local access and victim user interaction (CVSS 4.4, CWE-125). No public exploit is identified at time of analysis, and impact is bounded to partial confidentiality loss and availability loss rather than code execution.
An authenticated tenant superuser on Red Hat Ansible Automation Platform 2 can use the automation-controller API to confirm the existence of arbitrary absolute filesystem paths inside the controller-web pod, because StringListPathField.to_internal_value() calls os.path.exists() on unbounded user-supplied input and the 200-versus-400 response difference acts as an existence oracle. The issue is rated CVSS 4.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N) and only reads existence, not content, but it lets a tenant admin probe paths such as /etc/tower/SECRET_KEY, Kubernetes service-account tokens, receptor sockets and ConfigMap mount points. It is materially impactful only in managed AAP deployments (ansiblecloud.com) where the tenant administrator is not the host administrator; there is no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis.
Information disclosure in the automation-controller component of Red Hat Ansible Automation Platform 2 lets any authenticated user of any privilege level extract internal database and ORM structure by sending crafted values through the host_filter query parameter of the Host list REST API. Because HostList.list() catches a bare Exception and returns str(e) verbatim, a malformed relation lookup such as credential__search=x raises a Django FieldError that exposes the complete Host model relation graph (including internal reverse accessors), while a malformed pattern such as name__regex=[bad raises a PostgreSQL DataError that reflects the raw database error string. The flaw is rated CVSS 4.3 (MEDIUM) with a vector of AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N; exploitation requires valid credentials but no user interaction, impact is limited to low-confidentiality schema and error-text leakage with no modification or code execution, and no public exploit was identified at time of analysis.
Authenticated users of Red Hat Ansible Automation Platform 2 can read sensitive commercial license metadata - account number, subscription ID, pool ID, SKU, support level, and instance counts - from the /api/v2/config/ endpoint, which is guarded only by Django REST Framework's IsAuthenticated permission class. The superuser/auditor gate that protects other configuration keys such as project_base_dir, project_local_paths, and custom_virtualenvs does not extend to the license_info block, so any logged-in account of any privilege level can retrieve it without user interaction or non-default configuration. Per the independent assessment this is a genuinely low-priority, information-disclosure issue (CVSS 4.3, PR:L) - no public exploit has been identified at time of analysis, and the practical risk is reconnaissance and social-engineering enablement against Red Hat support rather than direct compromise.
Authenticated but unprivileged users of Red Hat Ansible Automation Platform 2 can read platform-wide job event information through the JobJobEventsChildrenSummary endpoint, which performs no object-level authorization check. Because the view declares no model or parent_model, ModelAccessPermission.check_get_permissions() falls through and returns True for every authenticated principal, and the handler substitutes a raw get_object_or_404(Job, pk), exposing event tree structure, event_processing_finished status, and the existence of arbitrary Job IDs via a 200/404 oracle. Exploitation requires only a valid zero-privilege account on the controller and no user interaction, making this a confidentiality-only information disclosure (assessed CVSS 5.0, AV:N/AC:L/PR:L/UI:N); no public exploit code has been identified at time of analysis, and the sibling endpoint /jobs/{id}/job_events/ correctly returns 403, confirming the defect is endpoint-specific.
Information disclosure in Red Hat Ansible Automation Platform 2 allows an authenticated low-privilege user to enumerate named resources - organizations, credentials, inventories, and hosts - across tenants, including internal hostnames, by observing a response-discrepancy in the URLModificationMiddleware. The middleware resolves named-URL lookups against unfiltered Model.objects before RBAC enforcement, and its 403→404 shim only rewrites 403 responses, so the pk=0 miss path remains distinguishable via 'Not found.' versus 'No <Model> matches...'. Exploitation requires an authenticated account (PR:L per CVSS) and is only meaningful on multi-tenant deployments; it yields existence information only, with no modification or availability impact. No public exploit identified at time of analysis and no CISA KEV status is indicated (no EPSS score was provided).
An out-of-bounds read in BusyBox's built-in TLS handshake parser (get_client_hello()) lets unauthenticated remote attackers trigger a limited memory over-read by sending a malformed, truncated TLS ClientHello to a BusyBox process that parses inbound handshake data. Impact is confined to low confidentiality loss (CVSS 5.3, C:L) with no integrity or availability effect, and exploitation requires the atypical configuration of BusyBox acting as a TLS server or handshake receiver, since BusyBox's TLS code is most often used client-side for wget/https. There is no public exploit identified at time of analysis, the CVE is not listed in CISA KEV, and Red Hat tracks the issue for Red Hat Hardened Images (advisory: https://access.redhat.com/security/cve/CVE-2026-88840; Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2531354).
Out-of-bounds write in BusyBox's passwd and group applets allows an authenticated attacker with high privileges (PR:H) to corrupt heap memory via a stale endpoint pointer after field trimming. The vulnerability (CVSS 6.7, CWE-787) is local-only (AV:L), requires no user interaction (UI:N), and is confined to the host (S:U), meaning a would-be attacker must already hold root or equivalent privileges to supply the malformed passwd/group entry. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and no EPSS score was provided; the primary limiting factor is the PR:H requirement, which makes this a defense-in-depth hardening issue rather than a remotely reachable attack.
Authentication bypass in BusyBox httpd occurs when the server is configured with HTTP Basic Authentication backed by yescrypt ($y$-prefixed) password hashes, which the daemon fails to recognize as hashes and instead compares literally as plaintext - inverting the auth check so the stored hash string itself becomes a usable credential. The flaw is network-reachable and requires no prior authentication (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N, 6.5), with high attack complexity reflecting the dependency on the non-universal yescrypt configuration and the attacker's need to know or obtain the stored hash; impact skews to confidentiality (C:H) with limited integrity effect (I:L). Exposure is concentrated in Red Hat Hardened Images and other deployments where BusyBox httpd actually fronts authentication; there is no public exploit identified at time of analysis and no CISA KEV listing, so this is a configuration-gated weakness rather than a demonstrated in-the-wild attack.
An out-of-bounds heap read in BusyBox's dpkg applet (read_package_field()) allows a local attacker who supplies a malformed .deb package to crash the dpkg process and potentially expose a small amount of heap memory, since the assessed vector rates availability impact as High and confidentiality impact as Low (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H, 6.1 Medium). Exploitation is constrained: it requires a BusyBox build with the dpkg applet compiled in (a non-default option in many minimal configurations, though it is present in the Red Hat Hardened Images builds tracked under the associated CPE) and requires the victim or an automated pipeline to actively invoke BusyBox dpkg against the crafted package. No public exploit identified at time of analysis, and no EPSS data was provided for this CVE; Red Hat is tracking the defect for Red Hat Hardened Images.
IP-based deny rules in BusyBox httpd can be silently bypassed: when an administrator configures an access-control rule with an invalid CIDR prefix length, the parser zeroes the netmask so the rule matches no clients and the intended block never takes effect. The flaw is remotely reachable without authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3), but it only manifests under that administrator-side precondition, so exposure is limited to deployments whose httpd configuration contains malformed deny entries - Red Hat Hardened Images are identified as affected via the published CPE. Impact is confined to confidentiality loss through bypass of the intended IP restriction, and no public exploit identified at time of analysis.
Second-factor authentication bypass in Keycloak's Conditional OTP authenticator allows an attacker who already possesses a user's password to skip OTP verification by sending a crafted HTTP header, provided the realm is configured to evaluate headers for OTP-skipping without validating their source. This flaw affects Red Hat Build of Keycloak and Red Hat Single Sign-On 7, has a CVSS score of 6.8 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N), and requires a non-default configuration plus a compromised first factor, meaning it is an account-targeted MFA bypass rather than unauthenticated remote compromise. No public exploit has been identified at the time of analysis.
Keycloak's Pushed Authorization Request implementation can allow an authenticated OAuth client to reuse a previously pushed request_uri when the prompt=none silent-authentication path is used, resulting in multiple authorization codes for an already signed-in user. Exploitation requires a live victim session, PAR enabled, and an authenticated low-privilege client (PR:L), with high attack complexity and limited impact; CVSS is 4.2. No public exploit identified at time of analysis, and no CISA KEV confirmation was provided.
Deleted or deprovisioned users can retain authorization on hosts running SSSD with the LDAP access provider when ldap_access_order includes ppolicy or lockout, because a user lookup that returns zero results trips a fail-open path that reports success and caches an allow decision. A remote attacker who already holds valid account context on the SSSD-managed host (authenticated, PR:L) can exploit this after offboarding to keep reading information and make limited modifications, giving low confidentiality and integrity impact (CVSS 3.1 5.4 Medium). The flaw only affects non-default access configurations that explicitly enable ppolicy/lockout ordering, and no public exploit identified at time of analysis.
Authentication bypass in the Keycloak (Red Hat Build of Keycloak) Kerberos federation provider lets an attacker on the same or adjacent network impersonate the Key Distribution Center and bypass Kerberos password authentication, potentially gaining unauthorized access to user accounts. The flaw only manifests in the specific, non-default configuration where Kerberos PASSWORD authentication is used while SPNEGO is disabled, because that mode never requests a server ticket to verify the KDC's identity. Rated CVSS 3.1 6.8 (AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N), exploitation requires network adjacency and an active on-path spoofing operation; no public exploit code has been identified and the CVE has not been listed as confirmed actively exploited (CISA KEV).
A stack buffer overflow in libstoragemgmt's SCSI VPD page 0x80 serial-number parser lets an attacker who controls a local or virtual storage device crash or destabilize the host process that enumerates that device, yielding a denial of service with no confidentiality or integrity impact (CVSS 3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base 5.5). Exploitation requires low privileges on the host (PR:L, so an authenticated/local actor) plus the ability to attach or present a device, and it only triggers when the affected process actually queries the device's serial number - the vector is local, not remotely reachable over a network. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV); the practical risk is concentrated in environments that enumerate untrusted or attacker-attachable storage, such as multi-tenant virtualization or hosts that accept hostile removable, iSCSI, or hypervisor-presented disks.
Isochronous OUT stream handling in usbredir can leave a stream's single transfer buffer permanently unsubmitted when a transfer count of 1 is used, which defeats the bounds check in usbredirhost_iso_packet() and lets a usbredir peer write beyond the end of the packet descriptor array on every subsequent isochronous packet. The flaw is an out-of-bounds write (CWE-787) affecting usbredir as shipped in Red Hat Enterprise Linux 6 through 10, and the published CVSS:3.1 vector (AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H, score 4.1) reflects a local, high-complexity, privileged trigger path whose dominant impact is availability loss rather than code execution. No public exploit identified at time of analysis, and the bug is not listed as confirmed actively exploited (CISA KEV); the realistic risk is materially lower than the raw memory-corruption classification suggests.
Stack-based buffer overflow in fetchmail when built with NTLM support allows a malicious or compromised mail server to trigger memory corruption by sending a crafted NTLM Type 2 challenge, potentially leading to remote code execution, authentication failure, or process termination. Exploitation requires fetchmail to be built with NTLM and configured to authenticate via NTLM against an attacker-controlled or man-in-the-middle'd server; no public exploit code or active exploitation has been identified. The flaw carries a CVSS score of 8.1 with high confidentiality, integrity, and availability impact, though reliable RCE is limited by stack-frame layout and modern memory hardening (stack canaries, ASLR, FORTIFY_SOURCE) on RHEL builds.
Keycloak's Admin REST API allows authenticated administrators with delegated privileges over a realm to read or modify sensitive client configurations in the master realm by abusing a per-request in-memory cache that resolves clients by unique identifier without verifying realm ownership. The flaw affects Red Hat Build of Keycloak and Red Hat Single Sign-On 7, requires the attacker to hold privileged delegated administration rights and to know or reference a target client's unique ID, and is assessed as a moderate-priority authorization issue rather than a high-CVSS critical defect. No public exploit code was identified at time of analysis, and successful exploitation could expose client credentials or redirect administrative login attempts to malicious sites.
Missing authorization checks in the Keycloak Authorization Services policy evaluation endpoint allow an authenticated delegated administrator with limited viewing privileges to read the full profile and role information of any user in the realm, including email addresses and assigned security roles. This moderate-severity information-disclosure issue affects Red Hat Build of Keycloak and Red Hat Single Sign-On 7. No public exploit code has been identified at time of analysis.
Delegated administrators in Keycloak can bypass fine-grained reset-password restrictions through the Admin REST API's credential-deletion endpoint, deleting a targeted user's password credentials and locking that user out. The flaw (CWE-862) requires an authenticated, provisioned delegated admin who has user-management access but is specifically not granted the manage-credentials/reset-password permission; it is an insider/delegated-tenant privilege-boundary escalation within the admin's reachable user scope, not unauthenticated exploitation, account takeover, or data disclosure. No public exploit code has been identified at time of analysis, and exploitation depends on Keycloak's fine-grained admin permissions model being deployed.
Privilege escalation in the Keycloak Admin REST API allows an already-authenticated delegated administrator to add their own account to a group that carries administrative role mappings, turning scoped, fine-grained management rights into effective control of the entire realm. The group-membership endpoints do not verify whether the target group grants privileged roles (CWE-862, Missing Authorization), so the escalation is a single API call away for anyone holding manage-users or equivalent group-scoped permissions. Reachability is limited: anonymous users and ordinary end-users cannot trigger it, a high-privilege group must already exist in the same realm, and deployments that only use a single super-admin gain nothing new because those actors are already fully privileged. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV. Affected builds include Red Hat Build of Keycloak and Red Hat Single Sign-On 7.
Keycloak's OpenID Connect token refresh path can issue fresh access tokens on behalf of an OIDC client that an administrator has already disabled, because the server restores requested audiences from stored client IDs without re-checking whether that audience client is still enabled. An attacker who already possesses a valid, unexpired refresh token for the affected client can therefore keep obtaining usable access tokens after the client is turned off, but only against resource servers that validate the JWT locally (offline signature/claim checks) rather than calling Keycloak for introspection or userinfo. Scoring is low at CVSS 4.2 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N), no public exploit code was identified at time of analysis, and exploitation requires both a live refresh token and a client that was disabled after that token was issued.
HTTP request smuggling in Netty's HTTP/1 decoder lets remote, unauthenticated attackers bypass front-end security controls and reach resources they should not access by sending requests with malformed Transfer-Encoding headers. Netty is a widely embedded Java networking library, so the practical reach spans Red Hat products built on it - AMQ Broker 7, AMQ Clients, Red Hat Build of Keycloak, Red Hat Build of Quarkus, Red Hat Build of Apache Camel (Spring Boot 4 and Quarkus 3), Red Hat Build of Debezium 3, Red Hat Build of Apicurio Registry 3, Red Hat Data Grid 8 and Red Hat Fuse 7 - as well as JBoss EAP 7/8 and Red Hat Single Sign-On 7 per the associated advisory tags. CVSS 3.1 rates it 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N), consistent with smuggling-style control bypass rather than full compromise; no public exploit code or confirmed active exploitation was identified at time of analysis, though the flaw is trivially reachable on any exposed HTTP endpoint.
Sustained CPU consumption in m17n-lib allows an unauthenticated local attacker to hang applications that parse attacker-influenced text, because a crafted invalid UTF-8 byte sequence drives the library's text-parsing routine into a non-terminating loop (CWE-835) and pins a CPU core indefinitely, producing a denial of service (CVSS 6.2, AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Only systems where an application actually routes externally supplied text through m17n-lib's parsing path are exposed; hosts that never load the library are unaffected, and there is no code execution, data leakage, or integrity impact. There is no public exploit identified at time of analysis, and no vendor-released patch identified at time of analysis; Red Hat is tracking the issue under CVE-2026-107168 with Bugzilla 2547409.
Missing authentication in the smart_proxy_dynflow remote-execution callback handlers lets an unauthenticated network attacker forge progress and completion reports for a running job, causing the job to be recorded as a success or a failure with attacker-supplied output. The flaw (CWE-306) applies only when Red Hat Satellite 6 remote execution is configured in pull or pull-mqtt mode, and the attacker must already know the identifier of a live job and submit the forged report during that job's execution window, which is why the assessed severity is moderate (CVSS 5.9, AC:H, integrity-only). No public exploit code and no confirmed active exploitation were identified at time of analysis.
Keycloak's SMTP email configuration can silently fall back to unencrypted communication when STARTTLS is enabled, allowing an attacker who can intercept and tamper with traffic between the Keycloak server and its mail relay to capture SMTP credentials and email message content in cleartext. Affected deployments include Red Hat Build of Keycloak and Red Hat Single Sign-On 7 (CVSS 6.5, AV:N/AC:H/PR:N/UI:N), but exploitation is conditional: it requires a man-in-the-middle position on the SMTP path and an instance configured for opportunistic STARTTLS rather than implicit TLS. No public exploit code or confirmed active exploitation has been identified at time of analysis.
Path traversal in pulp-rpm's distribution tree publishing allows an authenticated user with sync or upload privileges to write files outside the intended task work area on the Pulp server. Crafted addon or variant ids in a .treeinfo file are used as directory names without sanitization, enabling the creation of new directories and writing of repository metadata and packages as the Pulp worker user. This is an integrity-only issue with no data disclosure or service disruption; no public exploit has been identified, and the practical risk is lower than the base CVSS 5.0 suggests due to the required privileges and the create-only constraint.
Pulp Ansible's bearer-token refresh for collection remotes can disclose access tokens to an authenticated attacker who can create or sync a remote and point it at a malicious server. The attacker must then reuse the token at the issuing service, and exploitation is only possible if another token download for a different remote has run on the same worker process, meaning shared, multi-tenant deployments are primarily at risk. No public exploit code exists, and the assessed attack complexity is high (AC:H), so this is a moderate-priority information disclosure issue rather than a top-tier emergency.
Authenticated users with permission to create and sync container remotes in Pulp can obtain upstream registry credentials-usernames, passwords, or bearer tokens-stored for other remotes because the pulp-container worker reuses authentication material across sync operations. This affects deployments built on Red Hat Ansible Automation Platform 2, Red Hat Satellite 6, and Red Hat Update Infrastructure 4/5, particularly multi-tenant environments where remotes share worker processes. No public exploit code or confirmed active exploitation has been identified; the flaw rates CVSS 6.5 (moderate) and requires no user interaction beyond the attacker's own sync, though it does require an authenticated user with remote-creation and sync privileges.
Out-of-bounds heap reads in GIMP's XMC (X cursor) thumbnail loader can crash the application or corrupt process memory when a victim opens a crafted XMC file, or when thumbnail generation is triggered for one by a file manager. The root cause is an integer overflow: the loader sizes a pixel buffer using width * height computed in 32-bit signed arithmetic, so an oversized product wraps to a small allocation that a later GEGL buffer read then indexes using the unwrapped dimensions. Exploitation is strictly local and user-interaction dependent (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H, 5.5), with no network attack surface and no confidentiality or integrity impact; no public exploit code and no confirmed active exploitation were identified at time of analysis, and Red Hat tracks the issue across RHEL 6 through 10.
Local denial of service in the SSSD autofs responder allows an authenticated user on an affected host to exhaust memory by repeatedly racing concurrent map enumeration requests against map invalidation requests. Per the assessed vector (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H), the attack requires local, valid credentials and depends on winning a narrow timing window, so successful sustained exploitation is non-deterministic; hosts that do not run the autofs responder are not exposed. Impact is confined to availability - leaked memory accumulates until the autofs service is degraded or crashes - with no confidentiality or integrity effect. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing), and the 4.7 base score reflects the local, high-complexity prerequisites rather than the broad enterprise presence of SSSD.
Memory exhaustion in the SSSD (System Security Services Daemon) can be triggered by an unauthenticated local attacker who repeatedly initiates Identity Provider (IdP) pre-authentication flows without completing them, causing uncleared in-memory state to accumulate until authentication services degrade or terminate (denial of service, CVSS 6.2). The flaw (CWE-770) affects SSSD on Red Hat Enterprise Linux 6, 7, 8, 9, and 10 as well as Red Hat OpenShift Container Platform 4, but only when IdP authentication is explicitly enabled, which is not the default configuration. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
DOM-based cross-site scripting in the Red Hat Ansible Automation Platform UI allows an attacker-crafted link to execute arbitrary JavaScript inside a logged-in user's session, because a specific redirect route takes the destination from the 'next' query parameter and assigns it straight to the browser's location.href while bypassing the platform's own URL and scheme validation. Exploitation is constrained by two concrete prerequisites: the victim must already be authenticated to the platform UI (PR:L) and must actively click the malicious link (UI:R), which is why the issue carries a moderate CVSS 3.1 base score of 5.4 rather than a critical rating. No public exploit code and no confirmed active exploitation were identified at the time of analysis, and the risk is best characterized as a moderate, not top-priority, issue that should be scheduled rather than emergency-patched.
A local, authenticated user on hosts running sssd (System Security Services Daemon) can stall the daemon's responder service by opening and holding a large number of concurrent connections to a responder socket while continuing to queue new connection attempts, driving the responder past its file-descriptor limit into an unthrottled retry loop. The result is a denial-of-service condition with high CPU consumption that blocks legitimate identity and authentication lookups (NSS/PAM) for other users. Exploitation requires local access and is rated high complexity (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H, base 4.7), so realistic exposure is concentrated on shared or multi-user systems rather than single-administrator hosts; there is no public exploit identified at time of analysis and no confirmed active exploitation (no CISA KEV listing).
Authentication bypass in Keycloak's OIDC Device Authorization Grant flow allows an attacker who already possesses a valid user password to evade a client's configured minimum authentication level, including mandatory multi-factor authentication, and gain unauthorized access to the Keycloak Admin REST API, according to Red Hat. The flaw is a missing enforcement check (CWE-287) affecting Red Hat Build of Keycloak and Red Hat Single Sign-On 7 deployments where the device authorization flow is enabled for a client that requires elevated authentication. Exploitation requires prior credential compromise (CVSS PR:L) and the targeted client must actually mandate MFA or another authentication level; no public exploit code or CISA KEV active exploitation is identified in the available data, and EPSS is not provided. The CVSS score is 5.4 (moderate), with limited confidentiality and integrity impact.
Denial of service in sssd passkey authentication handling allows any local user to crash the PAM responder by sending a crafted PAM request. The flaw, a missing state validation check leading to an uninitialized pointer dereference (CWE-476), affects sssd on Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 when passkey authentication is enabled-a non-default configuration. With a CVSS score of 6.2 (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), impact is limited to availability; no public exploit has been identified at time of analysis, and exploitation requires local access and the passkey feature to be active.
A local denial of service in SSSD's Name Service Switch (NSS) responder lets an attacker who can reach the responder's UNIX socket crash the name-resolution service by sending a crafted request containing an undersized packet header, which causes an integer underflow followed by an out-of-bounds read during packet parsing. Affected deployments are Red Hat Enterprise Linux 6, 7, 8, 9, and 10, plus Red Hat OpenShift Container Platform 4 nodes running SSSD. The impact is availability-only (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), exploitation requires prior local access and socket reachability, and no public exploit identified at time of analysis.
A local, low-privilege attacker can crash the SSSD PAM responder on Red Hat Enterprise Linux (versions 6 through 10) and Red Hat OpenShift Container Platform 4 by sending a crafted PAM request that contains a zero-length authentication token. The flaw, tracked as CVE-2026-104042 with a CVSS score of 5.5, stems from missing length validation that leads to an out-of-bounds read and a denial of service; it requires an existing local account and no user interaction. No public exploit code has been identified at time of analysis, and this is a moderate-severity local DoS rather than a remote or privilege-escalation issue.
Unprivileged local users can exhaust memory in the SSSD NSS responder by repeatedly requesting lookups for nonexistent entries, causing denial of service on Red Hat Enterprise Linux 6 through 10 and Red Hat OpenShift Container Platform 4. The negative cache in SSSD lacks a bound on total stored entries and only evicts expired records when an existing key is rechecked, so the cache grows until the responder becomes unresponsive or terminates. This is a local, availability-only issue requiring an authenticated account (CVSS 5.5, PR:L); no public exploit code or active exploitation is identified at time of analysis.
SSSD configured with the Microsoft Entra ID identity provider fails to neutralize single quotes in lookup names before embedding them into Microsoft Graph OData queries, enabling an authenticated local attacker to inject filter syntax. This can broaden user or group searches, leading to information disclosure of unintended directory objects and a denial of service through excessive processing and cache population. The CVSS vector (AV:L/PR:L) confirms the attack is local and requires low privileges, and exploitation is only possible when the non-default Entra ID backend is enabled; no public exploit or active exploitation is reported, and no EPSS score was provided.
Denial of service in SSSD allows a local, already-authenticated user who can reach the PAM responder and complete a GSSAPI authentication request to send a follow-up request over the same connection, dereferencing freed cached connection state and terminating the service, which disrupts system authentication. Per the authoritative assessment the issue is rated CVSS 4.7 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H): it is local-only, requires valid low-level credentials on the host, and is constrained by high attack complexity because the dangling-pointer dereference depends on request timing and sequencing over a reused connection. Impact is availability-only - no confidentiality or integrity effect - and no public exploit identified at time of analysis (no CISA KEV listing and no publicly available exploit code in the provided intelligence).
Denial of service in SSSD (the System Security Services Daemon) allows remote unauthenticated attackers to crash the daemon by presenting a certificate that is missing the expected Security Identifier (SID) extension during authentication or lookup operations. Only deployments explicitly configured with SID-based certificate mapping rules reach the vulnerable code path, since the certificate-to-user lookup logic dereferences the SID extension without first confirming it exists; standard installations that do not use SID-based certificate mapping are not affected. The flaw is rated CVSS 5.9 (AV:N/AC:H/PR:N/UI:N/C:N/I:N/A:H, availability-only) and, per available intelligence, no public exploit code exists and exploitation has not been confirmed as active - no public exploit identified at time of analysis.
Denial of service in SSSD's autofs responder allows a local attacker with an existing account on the host to crash the responder process by writing a specially crafted request containing an invalid packet length to its UNIX domain socket. The malformed length triggers an integer underflow that produces an out-of-bounds read (CWE-125), terminating the responder and disrupting automount map lookups; there is no confidentiality or integrity impact and no remote vector. Exploitation requires the autofs responder to be enabled in sssd.conf and local reachability of its socket (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 5.5); no public exploit code and no confirmed active exploitation were identified at time of analysis. Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 (via packaged SSSD) are listed as affected.
Access control bypass in SSSD when configured with non-default ordering that evaluates password-expiration warnings before restrictive access rules allows remote authenticated users with expired passwords to gain unauthorized access to protected systems via alternative authentication methods such as SSH public key authentication. This flaw (CWE-393) affects Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 deployments using LDAP access control. Exploitation requires a specific non-default configuration, an expired password, and a non-password authentication path, making it a moderate conditional risk; no public exploit identified at time of analysis.
SSSD's NFS idmap plugin contains an out-of-bounds write (CWE-787): when a cached user or group name is larger than the destination buffer it is copied into, the size check fires but the copy proceeds anyway. An authenticated, low-privileged local attacker can request identity lookups that resolve to such oversized cached entries, crashing the identity-mapping service (denial of service) and potentially corrupting adjacent process memory; the attack is local-only and depends on the oversized-cache precondition, giving it high attack complexity (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H, 5.8). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
Local denial of service in the SSSD Kerberos Credential Manager (KCM) responder allows an authenticated local user to exhaust host memory and make the service unresponsive by holding a persistent connection open while repeatedly storing and destroying Kerberos credentials. The flaw is a resource-lifecycle defect (CWE-772): cached objects are not released when credentials are removed, so memory grows monotonically until the responder stalls. Exploitation requires a valid local account and sustained store-then-destroy activity, yields availability impact only (CVSS 5.5, AV:L/PR:L/UI:N/A:H), and does not provide code execution or privilege escalation; no public exploit code or confirmed active exploitation was identified at time of analysis, and systems that do not use the KCM responder are not affected.
The SSSD Kerberos Credential Manager (KCM) responder can be crashed by an authenticated local user who holds a renewable Kerberos ticket-granting ticket, because a deferred callback in the TGT renewal path dereferences memory that has already been freed. Exploitation is conditional on the host being explicitly configured for KCM-based credential renewal (a non-default, feature-dependent prerequisite), and the assessed vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (4.7) reflects local access, high attack complexity, and an availability-only impact confined to the sssd-kcm service. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); overall this is a medium/low-priority denial-of-service issue rather than a high-CVSS/low-real-risk outlier.
Authentication bypass in SSSD permits a user with valid credentials for an already-expired account to authenticate to the system when SSSD is configured to enforce account expiration using LDAP shadow attributes and the expiration value is stored as zero. This moderate-severity logic flaw (CVSS 5.4, CWE-193) affects Red Hat Enterprise Linux 6, 7, 8, 9, and 10, as well as Red Hat OpenShift Container Platform 4; exploitation requires the non-default shadowExpire=0 configuration and valid credentials for the expired account. No public exploit code or active exploitation has been identified at time of analysis.
Denial of service in SSSD's autofs responder allows an authenticated local unprivileged user to repeatedly request master automount map updates, triggering global cache invalidation and forcing repeated backend directory lookups, which degrades automount availability and elevates resource consumption. Affects Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 when SSSD-backed automount maps are served from a backend directory provider such as LDAP or Active Directory. This is a moderate-priority local availability issue (CVSS 5.5) with no public exploit code identified at time of analysis.
Memory exhaustion in the SSSD autofs responder can let a local, authenticated unprivileged user deny service on affected hosts by holding an open client connection while repeatedly submitting valid requests, since per-request memory is only reclaimed when the connection closes. The flaw affects SSSD deployments on Red Hat Enterprise Linux 6 through 10 and Red Hat OpenShift Container Platform 4, but the vulnerable code path is only reachable when the autofs responder is explicitly enabled in sssd.conf - a non-default configuration. Exploitation is limited to local access (AV:L/PR:L) with no impact on confidentiality or integrity, so it is correctly rated medium (CVSS 5.5); no CISA KEV entry and no public exploit code have been identified at time of analysis, and a realistic impact generally requires a shared, multi-user host where one user's resource consumption degrades service for others.
Authentication bypass in the maestro gRPC broker shipped with Red Hat Multicluster Engine for Kubernetes lets a client that already holds a valid mTLS client certificate skip the broker's authentication check and then subscribe to other consumers' event streams or publish forged agent status messages. The consequence is unauthorized information disclosure and loss of data integrity inside the broker, with no availability impact and scope unchanged; the assessed CVSS 3.1 base score is 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N). There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis, and the valid-client-certificate prerequisite confines abuse to trusted-but-lower-privileged or already-compromised clients rather than anonymous remote attackers.
Crashing the SSSD autofs responder process via a crafted request to its UNIX socket allows a local, low-privileged attacker to cause a denial of service on affected Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 systems. The vulnerability stems from improper buffer offset calculation during request parsing, leading to an out-of-bounds read (CWE-125) that terminates the responder process; it carries a CVSS 3.3 (Low) score with no confidentiality or integrity impact. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and the autofs responder service must be enabled for the flaw to be exploitable.
A local, low-privileged user can crash the sssd authentication daemon by submitting a crafted passkey (FIDO2/WebAuthn) authentication token that omits expected null terminators, causing an out-of-bounds read and terminating the service, which disrupts authentication for all users relying on that host. Rated CVSS 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), the flaw is purely an availability issue confined to systems where sssd's passkey authentication path is configured and reachable; there is no confidentiality or integrity impact and no remote or unauthenticated route. At the time of analysis, no public exploit code has been identified and there is no confirmed active exploitation (not listed in CISA KEV), and no vendor-released patch has been identified.
Unauthenticated REST API write access in Maestro, the messaging and resourcing component shipped with Red Hat Multicluster Engine for Kubernetes, lets a remote attacker create, modify, or delete consumers and resource bundles without supplying any credentials, token, or session. Because the affected endpoints were registered without authentication middleware (CWE-306), preconditions reduce to network reachability of the Maestro API: deployments where the API is cluster-internal, gated by NetworkPolicy, or fronted by an authenticating gateway/service mesh are materially less exposed, while anything publishing those endpoints are directly exploitable with no user interaction. The exploitability posture is driven by impact rather than by observed activity - integrity is assessed as high and availability as low, and no public exploit code or confirmed in-the-wild exploitation (CISA KEV) was identified at time of analysis.
SQL injection in the maestro component of Red Hat Multicluster Engine for Kubernetes (MCE) allows remote attackers to perform read-only blind extraction of database contents through the orderBy parameter on REST API list endpoints. The vendor CVSS vector specifies PR:L, indicating a low-privileged authenticated account may be needed, while the description and independent assessment note that authentication may not be required; defenders should resolve this discrepancy because it changes exposure materially. At time of analysis there is no public exploit identified, and exploitation is constrained by blind, read-only extraction and the requirement for network reachability to the vulnerable MCE API; CVSS is 6.4 medium severity.
Argument injection in the OpenPrinting CUPS mailto notifier can let a low-privileged user or authorized subscription creator influence the configured sendmail command when CUPS email notifications are enabled. Exploitation requires a crafted notify-recipient-uri beginning with '-' and an MTA that interprets it as an option; the assessed risk is low because email notification is non-default, CUPS is typically local-only (AV:L), complexity is high, and impact is limited to low confidentiality and integrity in the assessed vector. No public exploit identified at time of analysis. Affected deployments include upstream OpenPrinting CUPS and CUPS in Red Hat Enterprise Linux 8, 9, 10, and Red Hat Hardened Images.
Cross-site scripting in Red Hat Quay 3 lets an unauthenticated remote attacker execute arbitrary script in a victim's authenticated browser session by tricking the user into completing login through a crafted URL, because the application does not validate the post-login redirect destination before navigating. Exploitation is tightly constrained: the deployment must be configured with direct database authentication (installs delegating to OIDC/LDAP/SSO are unaffected) and the victim must both click the malicious login link and finish authenticating through it. Severity is low-to-moderate (CVSS 4.2, AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N), impact is confined to the victim's own session, and no public exploit identified at time of analysis.
Cross-site scripting in the OAuth callback handler of Red Hat Quay 3 lets an unauthenticated remote attacker run arbitrary JavaScript in a logged-in user's browser session by luring that user to a crafted URL, with no attacker privileges required (PR:N) but mandatory victim interaction (UI:R), giving a CVSS 3.1 score of 5.4. Successful exploitation is scoped to the victim's Quay application session (S:U, low confidentiality and integrity impact, no availability impact), potentially exposing registry metadata or allowing actions to be performed as the victim, rather than yielding server-side compromise. The vulnerability class is CWE-79 improper neutralization of input during web page generation; no public exploit code was identified in the available intelligence at the time of analysis, and CISA KEV status was not indicated.
Denial of service in FreeType's CID-keyed font loader allows attackers to exhaust memory and CPU by supplying a crafted font that triggers repeated allocation and decryption of subroutine data across multiple font dictionaries, causing the consuming application or service to hang or terminate. The issue is rated CVSS 5.5 with availability-only impact (A:H, C:N/I:N) and is gated by user interaction - someone or some automated process must actually load and parse the malicious font, which can be delivered by embedding it in a document, web page, or other parsed content. No public exploit code and no confirmed active exploitation were identified at time of analysis, but the Red Hat advisory points to an upstream FreeType fix commit (f3ca71c9900fe860849b3163a6e2c1e765b291d9) and tracks the flaw under Bugzilla 2462295, so a patched release should be expected; the practical risk is highest for unattended font- or document-processing pipelines rather than interactive desktop use.
Information disclosure and denial of service in Keycloak's X.509 client certificate authenticator occur when CRL Distribution Point checking is enabled and an unauthenticated remote attacker submits a crafted client certificate. The server fails to properly validate file paths from the certificate, allowing limited local file reads and extreme memory consumption that can crash the system; exploitation requires the non-default combination of certificate-based client authentication and CRL checking, and no public exploit was identified at time of analysis.
An authorization bypass in Red Hat Satellite's Katello RegistryProxiesController allows an authenticated low-privilege attacker to enumerate valid Users, Organizations, and Products across the instance via differential responses. The flaw stems from a missing return statement in the registry_authorize filter, which flags unauthorized requests but fails to halt execution, letting the request proceed into database validation filters that leak internal state. No public exploit identified at time of analysis; the vendor has released an errata (RHSA-2026:74503).
An authenticated low-privileged user can inject SQL through the Katello Registry Proxy in Red Hat Satellite 6 by placing a crafted label in the request path, allowing them to read arbitrary data from the Satellite database. The vulnerable code paths (check_blob_push_org_label and get_matching_products_from_org) interpolate request-supplied labels straight into raw SQL, and the only prerequisite is an account holding the create_personal_access_tokens permission - even a heavily restricted account with no Organization or Location assigned, which makes the effective privilege bar unusually low. Impact is limited to confidentiality (CVSS 6.5, C:H/I:N/A:N); no public exploit code has been identified at time of analysis, and Red Hat has published erratum RHSA-2026:74503 to address the flaw. This is a genuine but moderate-priority issue, not a critical drop-everything vulnerability.
Command injection in Red Hat Satellite's Hammer CLI (rubygem-hammer_cli) allows a local authenticated user to run arbitrary shell commands by controlling the $EDITOR environment variable, which the application interpolates into a single-string Ruby system() call that is then interpreted by /bin/sh. The flaw affects Red Hat Satellite 6 and Satellite 6.19 for RHEL 9, and exploitation requires an attacker to already hold a valid local account, be able to set $EDITOR, and trigger a CLI operation that launches an external editor (such as editing a resource), meaning remote or unauthenticated exploitation is not possible. Public exploit code and confirmed active exploitation are not indicated in the available intelligence, and Red Hat has published an erratum (RHSA-2026:74503) to address the issue.
Path traversal and symlink-validation flaws in ansible-runner's unstream_dir() (CVE-2026-103754) let an authenticated, low-privilege actor who can inject crafted archive content into the transmit/worker protocol create files, create symlinks, or change permissions outside the intended extraction directory, which can be leveraged toward code execution. The issue affects ansible-runner as shipped in Red Hat Ansible Automation Platform 2 (and upstream/AWX deployments) prior to the PR #1550 fix and carries a vendor-assigned CVSS 3.1 base score of 5.9 (AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L). No public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation is constrained by the need to supply crafted archive members into this specific worker protocol path.
Post-login redirection in OpenShift's oauth-proxy fails to validate the `rd` destination parameter, so a remote unauthenticated attacker who convinces a user to follow a crafted link can send that user's browser to an arbitrary external website once authentication completes (CWE-601, CVSS 6.1). Red Hat OpenShift Container Platform 4 deployments that expose oauth-proxy login flows are affected, and exploitation depends on the victim clicking the attacker's link and authenticating through that proxy (UI:R); the resulting impact is a browser redirect rather than code execution or data compromise, with real risk arising when the victim is socially engineered into trusting the attacker-controlled landing page for phishing or credential harvesting. No public exploit identified at time of analysis, no CISA KEV listing, and no EPSS score was supplied with the source data.
GEGL's Radiance HDR loader reads past the end of a memory-mapped image when a crafted .hdr file declares a scanline width larger than the actual data present in an uncompressed scanline, crashing the application that consumes the library - most notably GIMP, which uses GEGL for image processing. Any local user who opens such a file is affected; no authentication is required to the library, but the attacker must convince a victim to open the crafted file (UI:R), and the impact is availability-only (CVSS 5.5, AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, consistent with a low-priority, local denial-of-service rather than a code-execution primitive.
HTTP request smuggling in libsoup's SoupServer - as shipped in Red Hat Enterprise Linux 6, 7, 8, 9, and 10 - allows remote, unauthenticated attackers to have an attacker-controlled HTTP request processed as an unintended subsequent request on a keep-alive connection. The issue triggers when an HTTP/1.x client sends 'Expect: 100-continue' with a declared body and the SoupServer-based application issues an early final (non-1xx) response before that body is read; SoupServer then neither drains the body bytes nor closes the connection, so the leftover bytes are parsed as the next request. Rated CVSS 3.1 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N), the flaw carries limited integrity impact on request handling while leaving confidentiality and availability unaffected, and it is inert unless the specific combination of keep-alive, a declared body, and an early final response is present. No public exploit code and no confirmed active exploitation were identified at time of analysis.
An out-of-bounds write in the printf builtin of the dash shell allows a local user to corrupt one or two bytes past a four-byte reservation when a crafted Unicode \u or \U escape expanding to a five- or six-byte token is processed, including via 'dash -c' with the escape passed as a positional argument to printf or 'echo %b'. The flaw affects dash as shipped in Red Hat Enterprise Linux 6 (CPE cpe:2.3:a:red_hat:red_hat_enterprise_linux_6) and is rated CVSS 4.0 (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N). No public exploit code was identified at time of analysis, and the bounded write stays within the caller's own shell process, so it provides no inherent privilege escalation.
Local denial of service in the dash shell affects builds compiled without libc fnmatch, where the internal pmatch() matcher handles the '*' wildcard by unbounded recursion over candidate positions. A local attacker who can plant filenames in a directory that later gets globbed - or otherwise feed the internal matcher - can supply a short multi-star pattern such as *.*.*.*.*.tar.gz and drive excessive CPU consumption in the affected shell process. The issue requires a non-default build configuration (PR:L, AV:L, no remote reachability, no privilege escalation or data disclosure), maps to CWE-1333 (inefficient regular expression complexity) with a CVSS 3.1 score of 5.5, and there is no public exploit identified at time of analysis and no confirmed actively exploited status (CISA KEV).
ServiceAccount token exfiltration in the StreamsHub Console for Apache Kafka lets a user who already holds RBAC permission to create or modify the Console custom resource point the console-api AdminClient at an attacker-controlled broker. Tenant-supplied Kafka client properties are copied into the AdminClient configuration without filtering security-sensitive keys, so setting config.providers and bootstrap.servers causes the console-api ServiceAccount token to be read and leaked off-cluster. The issue is rated CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, CWE-470) and is a moderate-severity, privilege-dependent information disclosure: it requires an authenticated, semi-trusted role with write access to Console CRs (PR:L), so clusters with tight RBAC on those resources are substantially less exposed, and unauthenticated external actors cannot trigger it. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV); no EPSS score was provided.
Keycloak's Micrometer user-event metrics listener can be forced to create unbounded metric time series by unauthenticated remote requests to the identity broker login endpoint with arbitrary provider aliases, leading to memory exhaustion and performance degradation. This is a low-priority issue because exploitation requires the non-default configuration of including the 'idp' tag in the listener, and the impact is limited to a gradual availability degradation (A:L). No public exploit code has been identified at the time of analysis.
Privilege escalation in the Fine-Grained Admin Permissions v2 (FGAP v2) feature of Keycloak lets an authenticated delegated administrator with role-assignment rights grant a composite role whose transitive contents are never inspected, silently conferring full realm administrative control. Exploitation requires that FGAP v2 be enabled for delegated administration, a limited-admin credential holding role-mapping permissions (CVSS vector PR:H), and the presence of a composite role that transitively contains realm-admin privileges within that administrator's assignable scope; the high attack complexity (AC:H) reflects these preconditions rather than any exploitation difficulty, and the resulting impact is a complete confidentiality, integrity, and availability compromise of the realm (CVSS 6.6). No public exploit code and no confirmed active exploitation have been identified at time of analysis, so this should be treated as a genuine but conditional authorization-logic flaw rather than a remotely exploitable takeover.
mTLS holder-of-key certificate binding is not enforced in Keycloak's Standard Token Exchange V2 flow, so an attacker who already holds valid confidential client credentials can obtain a standard, unrestricted token that escapes the certificate-binding protection the deployment believed was in place. Affected distributions include Red Hat Build of Keycloak and Red Hat Single Sign-On 7, and exploitation is conditional on three things being true at once: the attacker must already possess a stolen client secret or key (the CVSS vector rates this PR:L - a precondition the flaw itself does not grant), the deployment must have Standard Token Exchange V2 enabled and in active use, and the deployment must be relying on mTLS holder-of-key binding as a hardening control. No public exploit code has been identified at time of analysis and there is no CISA KEV listing; the assessed vector (AV:N/AC:H/PR:L/UI:N, C:H/I:H/A:N) reflects a genuine but conditional security-control bypass rather than a mass-exploitable flaw, since certificate-bound tokens are a non-default opt-in configuration.
Ansible Automation Platform 2's gateway permits an authenticated gateway administrator (CVSS PR:H) to create a new service key for the Controller service cluster through the API, even though service-key creation is supposed to occur only via the installer-provisioned path; the resulting key is cryptographically indistinguishable from a legitimate one, so it can be used to mint a service-authentication token that impersonates the Controller service. When the non-default gateway OIDC workload-identity endpoint is enabled (FEATURE_OIDC_WORKLOAD_IDENTITY_ENABLED) and a downstream resource server such as HashiCorp Vault trusts the gateway's OIDC signing key, the attacker can induce the gateway to sign Workload Identity Tokens for arbitrary Controller workloads and retrieve the AAP credentials bound to that workload, crossing the administrator's authorization boundary to disclose secrets (C:H, no integrity or availability impact). Exploitation requires admin privileges plus that specific non-default trust configuration, and no public exploit has been identified at time of analysis; the defect is access-gated rather than broadly exploitable.
Information disclosure in the Keycloak Admin REST API lets an authenticated delegated administrator holding only basic group/role search privileges enumerate every group assigned to a given role, including groups they are supposed to be unable to see. The flaw (CWE-862, missing authorization) affects the Admin REST API endpoints that return role-to-group mappings in Keycloak, Red Hat Build of Keycloak, and Red Hat Single Sign-On 7, and is rated CVSS 3.1 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) - a read-only confidentiality impact with no integrity or availability effect. It requires valid, privileged-but-scoped credentials and is only meaningful where an organization actually partitions group visibility across delegated admins; there is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing).
Authenticated delegated administrators in Keycloak can reset other users' passwords and take over their accounts when Fine-Grained Admin Permissions (FGAP) are enabled, because the Admin REST API's general user-update path skips the password-reset authorization check that the dedicated credential-reset flow enforces. Red Hat Build of Keycloak and Red Hat Single Sign-On 7 are the affected downstream products, and the flaw is rated 6.6 (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H, CWE-862). Exploitation is conditionally gated rather than internet-facing: it requires a non-default FGAP configuration and an already-provisioned semi-trusted admin holding user-profile edit rights but deliberately denied password-reset rights, making this an insider or lateral privilege-escalation issue; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.
Keycloak's Level of Authentication (LoA) step-up enforcement can fail open: when a relying client requires a higher authentication level for a user who already holds an active session at a lower level, a logic error in session re-evaluation causes Keycloak to issue a token carrying the lower acr/LoA claim instead of forcing the required step-up authentication. The impact is a bounded assurance downgrade rather than unauthenticated access - the attacker must already be authenticated (CVSS PR:L) - but it may grant access to sensitive resources whose authorization decisions trust those claims, with low confidentiality and integrity impact and no availability impact (CVSS:3.1 4.2, AV:N/AC:H/UI:N/S:U/C:L/I:L/A:N). Exploitation depends on a deployment that actually configures per-client step-up/LoA and on a specific session-state and re-evaluation timing; no public exploit code has been identified at time of analysis and this CVE is not listed in CISA KEV.
Argument injection in Red Hat Ansible Automation Platform 2's automation-controller system-job subsystem allows an authenticated user with superuser privileges to inject arbitrary command-line arguments into the control-plane awx-manage process, gaining control of its argument vector and the first entry of its Python module search path. The root cause is that the system-job template launch endpoint stores a caller-supplied 'days' value without applying the integer validation used elsewhere for that field, and the dispatcher flattens the management-command argument list into a single space-delimited string that the job runner re-splits, so embedded spaces become additional arguments; system jobs run in-process on the control node without the container isolation applied to other job types. Confirmed remote code execution does not follow from the injected arguments alone - it would require an additional import gadget that is not present in the current management commands - so the demonstrated impact is argument injection and search-path control rather than code execution, and no public exploit was identified at time of analysis.
Server-side request forgery in Red Hat Ansible Automation Platform 2's automation-controller email notification backend lets an authenticated user holding organization notification-admin permission point an email notification template's SMTP host and port at arbitrary internal, loopback, link-local or reserved addresses; the controller task process then opens a raw TCP connection to that target when the notification test is triggered. Because the resulting connection error is surfaced through the notification record, an attacker gains a three-state internal port-scan oracle (open, closed, filtered) over the control-plane cluster network, including the in-cluster Kubernetes API, and if a shared organization template stores an SMTP password, redirecting the host can leak that credential to an attacker-controlled server. Impact is moderate (vendor CVSS 6.4, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) and requires a privileged, already-authenticated role rather than anonymous access; no public exploit code has been identified at time of analysis and CISA KEV does not list this CVE.
Secret values that playbook authors explicitly marked with no_log can be recovered from Red Hat Ansible Automation Platform 2 (automation-controller) through the REST filter backend, because the WorkflowJobNode.ancestor_artifacts column is not wrapped in prevent_search() and therefore remains queryable even though it is omitted from the API serializer. An authenticated user - one with only read access to a workflow, or any authenticated user with no roles at all by abusing a regular-expression lookup that bypasses the JSON cross-relation filter guard via the world-readable credential-types endpoint - can use the result count as a boolean/count oracle to extract secrets character by character, potentially across organizations. The issue is rated CVSS 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, CWE-639); no public exploit code or confirmed active exploitation was identified at time of analysis, and because recovery requires an account plus many incremental requests per character, the practical risk is a bounded confidentiality exposure rather than a top-tier emergency.
Source-IP spoofing in Ansible Automation Platform 2's automation-controller allows an authenticated remote attacker to forge the client IP recorded in audit and access logs when the application runs its shipped production reverse-proxy configuration and trusts the client-supplied X-Forwarded-For header. The flaw is CWE-348 and only affects log integrity (CVSS 3.1 4.3, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), with no access, confidentiality, or availability gain. No public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV).
Red Hat Ansible Automation Platform 2 (automation-controller) lets an unauthenticated remote attacker enumerate which Job Template and Workflow Job Template IDs have a Bitbucket Data Center webhook configured, by abusing an observable response discrepancy in the Bitbucket DC webhook receiver. For diagnostics:ping events the receiver performs the template lookup before HMAC signature verification is skipped, so the endpoint returns HTTP 200 for a template with a Bitbucket DC webhook and HTTP 403 otherwise - an oracle that requires neither authentication (PR:N in the assessed vector) nor knowledge of the secret webhook_key. Assessed at CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), this is a low-impact information-disclosure and enumeration issue: no secrets, code execution, or elevated access are exposed; no public exploit identified at time of analysis and no confirmed actively exploited status.
TLS peer impersonation in Red Hat Ansible Automation Platform 2's automation-controller instance install-bundle endpoint lets an authenticated controller System Administrator obtain a mesh-CA-signed X.509 certificate that TLS peers will accept as a different control node. The flaw arises because a caller-chosen instance hostname is copied verbatim into the certificate's Common Name, DNS SAN, and receptor node-id, and the hostname charset validator is case-insensitive while the uniqueness validator is case-sensitive, so a case variant of an existing control node's hostname passes registration and yields a hard-coded ten-year, non-revocable mesh peer credential. Realizing the impact additionally requires an on-path/man-in-the-middle position on the receptor mesh, and the scenario is most meaningful in managed or hosted deployments where a customer holds controller superuser while the platform operator runs the mesh; there is no public exploit identified at time of analysis, and the flaw does not grant direct remote code execution because receptor work submission is gated by a separate signing key absent from the bundle.
Authenticated users of any privilege level on Red Hat Ansible Automation Platform 2 automation-controller deployments can extract other tenants' notification secrets-PagerDuty service keys and Slack, Mattermost, RocketChat, and generic Webhook bearer-token URLs-by abusing the API filter backend as a boolean count-oracle. The attack requires only a low-privilege account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, base 6.5), is network-reachable and low in complexity, and yields high confidentiality impact with no integrity or availability effect. Impact is greatest in multi-tenant installations where recovered secrets break organization isolation and permit notification-channel impersonation; exploitation is inherently slow, requiring many iterative requests that may be visible in API logs. No public exploit code has been identified at time of analysis, and the flaw is not listed as confirmed actively exploited (CISA KEV).
Information disclosure in the automation-controller API of Red Hat Ansible Automation Platform 2 lets any remote unauthenticated party read the automation mesh topology from the health-check endpoint /api/v2/ping/ (CVSS 3.1: 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N). Because the ApiV2PingView view is declared with the AllowAny permission class and over-serializes RBAC-gated mesh data into its anonymous response, an attacker needs only network reachability to walk away with node hostnames, node types, UUIDs, heartbeats, capacities, exact software versions, instance-group names and membership, the deployment install UUID, and the identity of the active control node. The exposure is confidentiality-only - no secrets, credentials, or tenant data are involved - and there is no public exploit identified at time of analysis, so this is a genuine but modest reconnaissance-grade issue rather than an urgent one.
Opening a crafted uncompressed DDS image in GIMP triggers a one-byte heap out-of-bounds read in the file-dds plug-in, which can crash the plug-in process. The flaw requires a local user to open the malicious file (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L), and the crash is non-deterministic because it only occurs when the byte past the pixel buffer lands on an inaccessible memory page; no information disclosure or code execution has been demonstrated. No public exploit code has been identified at time of analysis, and while downstream tracking covers Red Hat Enterprise Linux 6 through 10, the availability-only impact keeps real-world risk low and the 'RCE', 'Buffer Overflow' and 'Information Disclosure' tags attached to this record are not supported by the assessed vector.
Argument injection in the ad hoc command builder of Red Hat Ansible Automation Platform 2 lets an authenticated user who is permitted to run ad hoc commands smuggle ansible CLI options by passing a host-restriction (`limit`) value beginning with a hyphen, which ansible-core then parses as an option flag. Impact today is minimal (CVSS 3.1, CWE-88): because the injected token displaces the required `pattern` positional argument, only short-circuit flags such as `--version` and `--help` are reachable, so integrity impact is limited to low and no arbitrary option or command control is achievable. There is no public exploit identified at time of analysis, and the issue would only escalate if a future ansible-core release were to default or make optional the `pattern` positional - a hypothetical, non-default upstream change rather than current behavior.
Red Hat Ansible Automation Platform 2 (AWX) accepts leading-dash values in the scm_branch field processed by LaunchConfigurationBaseSerializer, allowing an authenticated user who can create or edit a Schedule or Workflow Job Template node to supply a value such as --upload-pack=/bin/id. The gap is a latent argument-injection issue (CWE-88) that is currently neutralized at runtime by the ValueError guard at jobs.py:1502, so no command execution occurs in shipping code; it would escalate to remote code execution only if that task-layer guard were refactored or removed in a future release. No public exploit code has been identified at time of analysis, and impact today is limited to a low-severity hardening gap (CVSS 3.1, integrity-only).
Information disclosure in Red Hat Ansible Automation Platform 2 allows an authenticated administrator (PR:H per the CVSS vector) to leak controller-side implementation details, including install paths, Python version, and source line numbers, into notification payloads delivered to an attacker-controlled webhook URL. A crafted Jinja notification template using a dynamic subscript such as job['job'+'_env'] slips past the static-Getattr AST whitelist, while a conditional gate like {% if job.id > 100 %} prevents the branch from firing during the small-job.id stub test-render, so the payload executes only against a real job whose exception produces a full traceback in the notification body. Impact is confined to low confidentiality loss (C:L) with no integrity or availability effect, and no public exploit has been identified at time of analysis.
Out-of-bounds heap read in GIMP's TIM image loader is triggered when a user opens a crafted 4bpp TIM image that is promoted to an RGBA layer, causing the file-tim plug-in to allocate an undersized row buffer and then process it with the larger RGBA row size. The result is disclosure of adjacent heap memory into the decoded image and a possible plug-in crash, with exploitation requiring local access and victim user interaction (CVSS 4.4, CWE-125). No public exploit is identified at time of analysis, and impact is bounded to partial confidentiality loss and availability loss rather than code execution.
An authenticated tenant superuser on Red Hat Ansible Automation Platform 2 can use the automation-controller API to confirm the existence of arbitrary absolute filesystem paths inside the controller-web pod, because StringListPathField.to_internal_value() calls os.path.exists() on unbounded user-supplied input and the 200-versus-400 response difference acts as an existence oracle. The issue is rated CVSS 4.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N) and only reads existence, not content, but it lets a tenant admin probe paths such as /etc/tower/SECRET_KEY, Kubernetes service-account tokens, receptor sockets and ConfigMap mount points. It is materially impactful only in managed AAP deployments (ansiblecloud.com) where the tenant administrator is not the host administrator; there is no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis.
Information disclosure in the automation-controller component of Red Hat Ansible Automation Platform 2 lets any authenticated user of any privilege level extract internal database and ORM structure by sending crafted values through the host_filter query parameter of the Host list REST API. Because HostList.list() catches a bare Exception and returns str(e) verbatim, a malformed relation lookup such as credential__search=x raises a Django FieldError that exposes the complete Host model relation graph (including internal reverse accessors), while a malformed pattern such as name__regex=[bad raises a PostgreSQL DataError that reflects the raw database error string. The flaw is rated CVSS 4.3 (MEDIUM) with a vector of AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N; exploitation requires valid credentials but no user interaction, impact is limited to low-confidentiality schema and error-text leakage with no modification or code execution, and no public exploit was identified at time of analysis.
Authenticated users of Red Hat Ansible Automation Platform 2 can read sensitive commercial license metadata - account number, subscription ID, pool ID, SKU, support level, and instance counts - from the /api/v2/config/ endpoint, which is guarded only by Django REST Framework's IsAuthenticated permission class. The superuser/auditor gate that protects other configuration keys such as project_base_dir, project_local_paths, and custom_virtualenvs does not extend to the license_info block, so any logged-in account of any privilege level can retrieve it without user interaction or non-default configuration. Per the independent assessment this is a genuinely low-priority, information-disclosure issue (CVSS 4.3, PR:L) - no public exploit has been identified at time of analysis, and the practical risk is reconnaissance and social-engineering enablement against Red Hat support rather than direct compromise.
Authenticated but unprivileged users of Red Hat Ansible Automation Platform 2 can read platform-wide job event information through the JobJobEventsChildrenSummary endpoint, which performs no object-level authorization check. Because the view declares no model or parent_model, ModelAccessPermission.check_get_permissions() falls through and returns True for every authenticated principal, and the handler substitutes a raw get_object_or_404(Job, pk), exposing event tree structure, event_processing_finished status, and the existence of arbitrary Job IDs via a 200/404 oracle. Exploitation requires only a valid zero-privilege account on the controller and no user interaction, making this a confidentiality-only information disclosure (assessed CVSS 5.0, AV:N/AC:L/PR:L/UI:N); no public exploit code has been identified at time of analysis, and the sibling endpoint /jobs/{id}/job_events/ correctly returns 403, confirming the defect is endpoint-specific.
Information disclosure in Red Hat Ansible Automation Platform 2 allows an authenticated low-privilege user to enumerate named resources - organizations, credentials, inventories, and hosts - across tenants, including internal hostnames, by observing a response-discrepancy in the URLModificationMiddleware. The middleware resolves named-URL lookups against unfiltered Model.objects before RBAC enforcement, and its 403→404 shim only rewrites 403 responses, so the pk=0 miss path remains distinguishable via 'Not found.' versus 'No <Model> matches...'. Exploitation requires an authenticated account (PR:L per CVSS) and is only meaningful on multi-tenant deployments; it yields existence information only, with no modification or availability impact. No public exploit identified at time of analysis and no CISA KEV status is indicated (no EPSS score was provided).
An out-of-bounds read in BusyBox's built-in TLS handshake parser (get_client_hello()) lets unauthenticated remote attackers trigger a limited memory over-read by sending a malformed, truncated TLS ClientHello to a BusyBox process that parses inbound handshake data. Impact is confined to low confidentiality loss (CVSS 5.3, C:L) with no integrity or availability effect, and exploitation requires the atypical configuration of BusyBox acting as a TLS server or handshake receiver, since BusyBox's TLS code is most often used client-side for wget/https. There is no public exploit identified at time of analysis, the CVE is not listed in CISA KEV, and Red Hat tracks the issue for Red Hat Hardened Images (advisory: https://access.redhat.com/security/cve/CVE-2026-88840; Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2531354).
Out-of-bounds write in BusyBox's passwd and group applets allows an authenticated attacker with high privileges (PR:H) to corrupt heap memory via a stale endpoint pointer after field trimming. The vulnerability (CVSS 6.7, CWE-787) is local-only (AV:L), requires no user interaction (UI:N), and is confined to the host (S:U), meaning a would-be attacker must already hold root or equivalent privileges to supply the malformed passwd/group entry. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and no EPSS score was provided; the primary limiting factor is the PR:H requirement, which makes this a defense-in-depth hardening issue rather than a remotely reachable attack.
Authentication bypass in BusyBox httpd occurs when the server is configured with HTTP Basic Authentication backed by yescrypt ($y$-prefixed) password hashes, which the daemon fails to recognize as hashes and instead compares literally as plaintext - inverting the auth check so the stored hash string itself becomes a usable credential. The flaw is network-reachable and requires no prior authentication (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N, 6.5), with high attack complexity reflecting the dependency on the non-universal yescrypt configuration and the attacker's need to know or obtain the stored hash; impact skews to confidentiality (C:H) with limited integrity effect (I:L). Exposure is concentrated in Red Hat Hardened Images and other deployments where BusyBox httpd actually fronts authentication; there is no public exploit identified at time of analysis and no CISA KEV listing, so this is a configuration-gated weakness rather than a demonstrated in-the-wild attack.
An out-of-bounds heap read in BusyBox's dpkg applet (read_package_field()) allows a local attacker who supplies a malformed .deb package to crash the dpkg process and potentially expose a small amount of heap memory, since the assessed vector rates availability impact as High and confidentiality impact as Low (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H, 6.1 Medium). Exploitation is constrained: it requires a BusyBox build with the dpkg applet compiled in (a non-default option in many minimal configurations, though it is present in the Red Hat Hardened Images builds tracked under the associated CPE) and requires the victim or an automated pipeline to actively invoke BusyBox dpkg against the crafted package. No public exploit identified at time of analysis, and no EPSS data was provided for this CVE; Red Hat is tracking the defect for Red Hat Hardened Images.
IP-based deny rules in BusyBox httpd can be silently bypassed: when an administrator configures an access-control rule with an invalid CIDR prefix length, the parser zeroes the netmask so the rule matches no clients and the intended block never takes effect. The flaw is remotely reachable without authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3), but it only manifests under that administrator-side precondition, so exposure is limited to deployments whose httpd configuration contains malformed deny entries - Red Hat Hardened Images are identified as affected via the published CPE. Impact is confined to confidentiality loss through bypass of the intended IP restriction, and no public exploit identified at time of analysis.
Second-factor authentication bypass in Keycloak's Conditional OTP authenticator allows an attacker who already possesses a user's password to skip OTP verification by sending a crafted HTTP header, provided the realm is configured to evaluate headers for OTP-skipping without validating their source. This flaw affects Red Hat Build of Keycloak and Red Hat Single Sign-On 7, has a CVSS score of 6.8 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N), and requires a non-default configuration plus a compromised first factor, meaning it is an account-targeted MFA bypass rather than unauthenticated remote compromise. No public exploit has been identified at the time of analysis.
Keycloak's Pushed Authorization Request implementation can allow an authenticated OAuth client to reuse a previously pushed request_uri when the prompt=none silent-authentication path is used, resulting in multiple authorization codes for an already signed-in user. Exploitation requires a live victim session, PAR enabled, and an authenticated low-privilege client (PR:L), with high attack complexity and limited impact; CVSS is 4.2. No public exploit identified at time of analysis, and no CISA KEV confirmation was provided.
Deleted or deprovisioned users can retain authorization on hosts running SSSD with the LDAP access provider when ldap_access_order includes ppolicy or lockout, because a user lookup that returns zero results trips a fail-open path that reports success and caches an allow decision. A remote attacker who already holds valid account context on the SSSD-managed host (authenticated, PR:L) can exploit this after offboarding to keep reading information and make limited modifications, giving low confidentiality and integrity impact (CVSS 3.1 5.4 Medium). The flaw only affects non-default access configurations that explicitly enable ppolicy/lockout ordering, and no public exploit identified at time of analysis.
Authentication bypass in the Keycloak (Red Hat Build of Keycloak) Kerberos federation provider lets an attacker on the same or adjacent network impersonate the Key Distribution Center and bypass Kerberos password authentication, potentially gaining unauthorized access to user accounts. The flaw only manifests in the specific, non-default configuration where Kerberos PASSWORD authentication is used while SPNEGO is disabled, because that mode never requests a server ticket to verify the KDC's identity. Rated CVSS 3.1 6.8 (AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N), exploitation requires network adjacency and an active on-path spoofing operation; no public exploit code has been identified and the CVE has not been listed as confirmed actively exploited (CISA KEV).
A stack buffer overflow in libstoragemgmt's SCSI VPD page 0x80 serial-number parser lets an attacker who controls a local or virtual storage device crash or destabilize the host process that enumerates that device, yielding a denial of service with no confidentiality or integrity impact (CVSS 3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base 5.5). Exploitation requires low privileges on the host (PR:L, so an authenticated/local actor) plus the ability to attach or present a device, and it only triggers when the affected process actually queries the device's serial number - the vector is local, not remotely reachable over a network. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV); the practical risk is concentrated in environments that enumerate untrusted or attacker-attachable storage, such as multi-tenant virtualization or hosts that accept hostile removable, iSCSI, or hypervisor-presented disks.
Isochronous OUT stream handling in usbredir can leave a stream's single transfer buffer permanently unsubmitted when a transfer count of 1 is used, which defeats the bounds check in usbredirhost_iso_packet() and lets a usbredir peer write beyond the end of the packet descriptor array on every subsequent isochronous packet. The flaw is an out-of-bounds write (CWE-787) affecting usbredir as shipped in Red Hat Enterprise Linux 6 through 10, and the published CVSS:3.1 vector (AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H, score 4.1) reflects a local, high-complexity, privileged trigger path whose dominant impact is availability loss rather than code execution. No public exploit identified at time of analysis, and the bug is not listed as confirmed actively exploited (CISA KEV); the realistic risk is materially lower than the raw memory-corruption classification suggests.
Stack-based buffer overflow in fetchmail when built with NTLM support allows a malicious or compromised mail server to trigger memory corruption by sending a crafted NTLM Type 2 challenge, potentially leading to remote code execution, authentication failure, or process termination. Exploitation requires fetchmail to be built with NTLM and configured to authenticate via NTLM against an attacker-controlled or man-in-the-middle'd server; no public exploit code or active exploitation has been identified. The flaw carries a CVSS score of 8.1 with high confidentiality, integrity, and availability impact, though reliable RCE is limited by stack-frame layout and modern memory hardening (stack canaries, ASLR, FORTIFY_SOURCE) on RHEL builds.
Keycloak's Admin REST API allows authenticated administrators with delegated privileges over a realm to read or modify sensitive client configurations in the master realm by abusing a per-request in-memory cache that resolves clients by unique identifier without verifying realm ownership. The flaw affects Red Hat Build of Keycloak and Red Hat Single Sign-On 7, requires the attacker to hold privileged delegated administration rights and to know or reference a target client's unique ID, and is assessed as a moderate-priority authorization issue rather than a high-CVSS critical defect. No public exploit code was identified at time of analysis, and successful exploitation could expose client credentials or redirect administrative login attempts to malicious sites.
Missing authorization checks in the Keycloak Authorization Services policy evaluation endpoint allow an authenticated delegated administrator with limited viewing privileges to read the full profile and role information of any user in the realm, including email addresses and assigned security roles. This moderate-severity information-disclosure issue affects Red Hat Build of Keycloak and Red Hat Single Sign-On 7. No public exploit code has been identified at time of analysis.
Delegated administrators in Keycloak can bypass fine-grained reset-password restrictions through the Admin REST API's credential-deletion endpoint, deleting a targeted user's password credentials and locking that user out. The flaw (CWE-862) requires an authenticated, provisioned delegated admin who has user-management access but is specifically not granted the manage-credentials/reset-password permission; it is an insider/delegated-tenant privilege-boundary escalation within the admin's reachable user scope, not unauthenticated exploitation, account takeover, or data disclosure. No public exploit code has been identified at time of analysis, and exploitation depends on Keycloak's fine-grained admin permissions model being deployed.
Privilege escalation in the Keycloak Admin REST API allows an already-authenticated delegated administrator to add their own account to a group that carries administrative role mappings, turning scoped, fine-grained management rights into effective control of the entire realm. The group-membership endpoints do not verify whether the target group grants privileged roles (CWE-862, Missing Authorization), so the escalation is a single API call away for anyone holding manage-users or equivalent group-scoped permissions. Reachability is limited: anonymous users and ordinary end-users cannot trigger it, a high-privilege group must already exist in the same realm, and deployments that only use a single super-admin gain nothing new because those actors are already fully privileged. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV. Affected builds include Red Hat Build of Keycloak and Red Hat Single Sign-On 7.
Keycloak's OpenID Connect token refresh path can issue fresh access tokens on behalf of an OIDC client that an administrator has already disabled, because the server restores requested audiences from stored client IDs without re-checking whether that audience client is still enabled. An attacker who already possesses a valid, unexpired refresh token for the affected client can therefore keep obtaining usable access tokens after the client is turned off, but only against resource servers that validate the JWT locally (offline signature/claim checks) rather than calling Keycloak for introspection or userinfo. Scoring is low at CVSS 4.2 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N), no public exploit code was identified at time of analysis, and exploitation requires both a live refresh token and a client that was disabled after that token was issued.
HTTP request smuggling in Netty's HTTP/1 decoder lets remote, unauthenticated attackers bypass front-end security controls and reach resources they should not access by sending requests with malformed Transfer-Encoding headers. Netty is a widely embedded Java networking library, so the practical reach spans Red Hat products built on it - AMQ Broker 7, AMQ Clients, Red Hat Build of Keycloak, Red Hat Build of Quarkus, Red Hat Build of Apache Camel (Spring Boot 4 and Quarkus 3), Red Hat Build of Debezium 3, Red Hat Build of Apicurio Registry 3, Red Hat Data Grid 8 and Red Hat Fuse 7 - as well as JBoss EAP 7/8 and Red Hat Single Sign-On 7 per the associated advisory tags. CVSS 3.1 rates it 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N), consistent with smuggling-style control bypass rather than full compromise; no public exploit code or confirmed active exploitation was identified at time of analysis, though the flaw is trivially reachable on any exposed HTTP endpoint.