Red Hat
Monthly
Token credential exposure in Red Hat insights-client causes the CCX_TOKEN bearer credential, used exclusively in disconnected cluster deployments, to be written in clear text to pod logs on every startup when glog verbosity is set to level 2 or higher. Any party with read access to pod logs or an aggregated logging backend can silently harvest this credential and use it to authenticate against the CCX API, extending access beyond the originating pod (CVSS scope change S:C). No public exploit is identified at time of analysis, and EPSS at 0.21% (11th percentile) combined with SSVC exploitation status of 'none' indicates this remains theoretical rather than actively targeted.
Sensitive credential leakage in Red Hat insights-client exposes cloud.openshift.com pull-secret tokens through application log files on Advanced Cluster Management hub clusters. When insights-client receives any non-200 HTTP response from the Red Hat cloud endpoint, it writes the full request headers - including the long-lived pull-secret bearer token - to pod logs readable by local cluster users. An attacker who harvests this token can authenticate against Red Hat cloud services without possessing their own credentials. No public exploit has been identified at time of analysis, and multiple vendor-released errata patch the behavior.
Heap and stack buffer overflow in CivetWeb's read_websocket() function (through commit 4a4f0c95) allows unauthenticated remote attackers to corrupt memory by sending crafted compressed WebSocket frames, but only against instances compiled with both USE_ZLIB and MG_EXPERIMENTAL_INTERFACES build flags. Attackers negotiate permessage-deflate during the WebSocket handshake and send an RSV1-flagged frame that triggers a 4-byte zlib sync trailer write past the allocated buffer boundary, corrupting heap metadata and enabling denial of service or potential code execution (per VulnCheck tagging). No public exploit code is confirmed and this CVE does not appear in CISA KEV at time of analysis, but the deterministic 4-byte overwrite primitive is a credible research target; the non-default build configuration substantially limits the real-world exploitable population.
Local code execution via out-of-bounds write in Microsoft .NET allows an unauthenticated local attacker to achieve full code execution upon successful exploitation, with high impact across confidentiality, integrity, and availability. The vulnerability requires user interaction - such as opening a malicious file or running a crafted application - making social engineering a likely delivery vector. No public exploit code or CISA KEV listing has been identified at time of analysis, though the Microsoft Security Response Center has acknowledged the issue.
Remote code execution in Microsoft Office SharePoint exploits unsafe deserialization of attacker-controlled data over the network. An authenticated attacker with low-level network access can submit a crafted serialized payload that SharePoint deserializes without sufficient validation, resulting in full compromise of confidentiality, integrity, and availability. No public exploit has been identified at time of analysis, but the low attack complexity and high impact across all three security properties make this a critical remediation priority.
Stack-based buffer overflow in Microsoft Office enables local arbitrary code execution when a user opens a specially crafted document. The CVSS vector (AV:L/AC:L/PR:N/UI:R) confirms exploitation is local and requires user interaction - most likely triggered by opening a maliciously crafted Office file delivered via phishing or other social engineering. No active exploitation has been confirmed (not listed in CISA KEV) and no public exploit code has been identified at time of analysis, though the high-impact triad (C:H/I:H/A:H) and Microsoft Office's ubiquitous deployment footprint make this a notable patching priority.
Remote code execution in Microsoft Office SharePoint enables any authenticated low-privileged user to execute arbitrary code on the server by submitting maliciously crafted serialized data over the network. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms the attack requires no user interaction, low complexity, and only a standard SharePoint account - making this straightforward to weaponize within any organization whose SharePoint is network-accessible to internal users or external authenticated parties. No public exploit code or CISA KEV listing is identified at time of analysis, though SharePoint deserialization vulnerabilities have historically attracted rapid weaponization.
Local privilege escalation in the Windows Cross Device Service (CVE-2026-66804) allows a low-privileged authenticated user to gain SYSTEM or elevated permissions on the local machine. The flaw stems from CWE-284 (Improper Access Control), meaning the service fails to adequately enforce authorization boundaries between user privilege levels. No public exploit or CISA KEV listing has been identified at time of analysis, but the low attack complexity and absence of required user interaction make this a straightforward target for post-compromise lateral movement or privilege escalation tooling.
Local privilege escalation in Windows Key Guard exposes any authenticated local user to full system compromise via a heap-based buffer overflow (CWE-122). The CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms low-complexity exploitation requiring only a standard local user session - no elevated rights, no user interaction. This class of vulnerability is a staple post-initial-access technique in ransomware and APT intrusion chains. No public exploit identified at time of analysis, and no CISA KEV listing is present in the provided data.
Local privilege escalation in Microsoft .NET Framework exploits a relative path traversal flaw (CWE-23), enabling an unprivileged local user to gain elevated system rights through user interaction. The vulnerability affects .NET Framework on Windows and is rated CVSS 7.8 (High), with full confidentiality, integrity, and availability impact upon successful exploitation. No public exploit code or CISA KEV listing has been identified at time of analysis.
Local privilege escalation in Microsoft .NET (versions 8.0, 9.0, and 10.0) and Microsoft Visual Studio 2022/2026 allows a low-privileged local attacker to elevate privileges by triggering an uncaught exception (CWE-248) within the runtime. The CVSS scope change (S:C) indicates impact extends beyond the .NET security boundary to the underlying host system. No public exploit identified at time of analysis, and Microsoft has released patched versions across all affected branches.
Denial-of-service in Microsoft .NET runtimes and Visual Studio allows unauthenticated remote attackers to crash or hang .NET applications by supplying crafted input that exploits an unchecked loop termination condition. Affected are .NET 8.0 (all releases through 8.0.29), .NET 9.0 (through 9.0.18), .NET 10.0 (through 10.0.10), and bundled Visual Studio 2022 and 2026 installations. No public exploit has been identified at time of analysis, but the low attack complexity and lack of authentication requirement make this a credible automated threat against any internet-exposed .NET service. Vendor-released patches are available and should be applied promptly, particularly for externally reachable endpoints. Note: the ENISA EUVD tags this as 'Authentication Bypass,' which conflicts with the description and CVSS impact metrics (C:N/I:N/A:H); this discrepancy should be verified with Microsoft's advisory.
Integer overflow in Microsoft .NET Framework and modern .NET runtimes enables local code execution with full process compromise (C:H/I:H/A:H) across a broad product surface spanning .NET Framework 3.5 through 4.8.1, .NET 8.0, 9.0, 10.0, and Visual Studio 2022 and 2026. An attacker who can deliver crafted input processed by a vulnerable .NET application can trigger arithmetic wraparound (CWE-190) to corrupt runtime memory and execute arbitrary code within the process context. Microsoft has released patches across all affected product lines; no public exploit identified at time of analysis, and no CISA KEV listing is present.
Privilege escalation in Microsoft .NET runtimes (8.0, 9.0, and 10.0) and Microsoft Visual Studio 2022 and 2026 results from a heap-based buffer overflow triggered by an integer overflow or wraparound condition in the runtime's memory handling. An unprivileged local user who interacts with a crafted input - such as a malicious file processed by a .NET application - can exploit the flaw to gain elevated privileges on the host system. No public exploit has been identified at time of analysis and this CVE is not listed in the CISA KEV catalog; however, a vendor-released patch is available from Microsoft.
Privilege escalation in Microsoft .NET Framework via incorrect authorization (CWE-863) allows network-authenticated low-privilege attackers to elevate their privileges, achieving full compromise of confidentiality, integrity, and availability on affected systems. Affected release families span .NET Framework 3.5 through 4.8.1, covering a broad swath of Windows enterprise deployments across multiple independently-installed runtime versions. No public exploit has been identified at time of analysis; a vendor-released patch with specific fix version thresholds is available through the Microsoft Security Response Center.
Heap-based buffer overflow (CWE-122) in Microsoft .NET enables local code execution across all actively supported .NET release streams (8.0, 9.0, 10.0) and associated Visual Studio tooling. The flaw requires user interaction - consistent with a file-processing or input-parsing trigger - but no elevated privileges, meaning an attacker can exploit it by inducing a user to open or process a maliciously crafted artifact within a vulnerable .NET context. Full confidentiality, integrity, and availability compromise of the affected process is possible on successful exploitation. No public exploit identified at time of analysis and no CISA KEV listing; Microsoft has released patches across all affected branches.
Local privilege escalation in Microsoft .NET runtimes (versions 8.0, 9.0, and 10.0) enables a local attacker to gain elevated system privileges by triggering an integer overflow condition, requiring only user interaction and no prior authentication. The flaw carries a CVSS 7.8 score with high impact across confidentiality, integrity, and availability. No public exploit or CISA KEV listing has been identified at time of analysis, but the broad deployment of .NET across enterprise Windows and Linux environments makes this a meaningful patching priority.
Code injection in the Perl DBI module as packaged for Red Hat Enterprise Linux allows a network-accessible, low-privileged attacker to execute arbitrary code, resulting in full confidentiality, integrity, and availability compromise. This CVE is a remediation of an incomplete fix for CVE-2026-14380, specifically targeting RHEL 9.8.z and 10.2.z patch levels where the prior partial fix left an exploitable residual path. No public exploit or CISA KEV listing is identified at time of analysis, but the CWE-94 classification and RCE tag indicate high potential impact if exploitation conditions are met.
Server-side authentication bypass in FreeRDP 3.x (confirmed through 3.27.1) allows an unauthenticated remote attacker to obtain a fully authenticated RDP session without supplying any credentials, GUID, or reconnect cookie when the server has RdstlsSecurity enabled. The flaw combines PDU-type confusion - the server routes inbound messages based solely on the client-supplied wire pduType without enforcing handshake state - with a calloc-zeroed result code that maps directly to RDSTLS_RESULT_SUCCESS, so sending a Capabilities PDU in place of the required Authentication Request PDU produces an unconditional authentication success response. No public exploit code or CISA KEV listing has been identified at time of analysis; the upstream fix commit is confirmed but a released patched version was not independently verified at advisory time.
Heap-based out-of-bounds read and write in FreeRDP before 3.30.0 can be triggered by a malicious peer during CredSSP/NLA Kerberos authentication, allowing information disclosure, heap memory corruption, or denial of service. The flaw exists in kerberos_DecryptMessage() where the peer-supplied 16-bit EC field of a GSS Wrap token is used directly in pointer arithmetic without bounds validation, enabling any RDP peer - rogue server or malicious client - to shift decrypt pointers up to 65535 bytes past the end of a ~60-byte token buffer. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Denial of service in ml-metadata (MLMD), a core metadata tracking component of Red Hat OpenShift AI (RHOAI), stems from an outdated statically-linked gRPC stack that retains known HTTP/2 resource exhaustion weaknesses. An in-cluster adversary with network reachability to the MLMD pod can crash it by sending specially crafted HTTP/2 requests, halting all ML pipeline runs within the affected namespace. No public exploit has been identified at time of analysis, and exploitation is constrained to actors already operating inside the Kubernetes cluster.
Privilege escalation in Red Hat OpenShift AI (RHOAI) training operator overlay allows any namespace editor to manage TrainJob resources beyond their intended authorization scope. The RHOAI overlay incorrectly injects trainjobs CRUD permissions into the native Kubernetes edit ClusterRole, violating the principle of least privilege. When chained with a companion flaw (TRN-01) that permits arbitrary pod configuration within TrainJobs, a remote attacker holding namespace editor credentials could escalate to arbitrary code execution - no public exploit is identified at time of analysis, and KEV listing has not been confirmed.
Privilege escalation in odh-dashboard (Red Hat OpenShift AI) allows an attacker who has obtained the dashboard's Service Account token to abuse overly broad SA permissions and elevate to cluster-administrator level. Exploitation grants full access to secrets, credentials, and keys across the entire OpenShift cluster, while also breaking multi-tenant isolation between workloads. No public exploit code has been identified at time of analysis, and this CVE is not in CISA KEV, but the CVSS score of 8.8 and cluster-wide blast radius make it a high-priority remediation target for RHOAI deployments.
Feast and feast-operator ship with a default 'no_auth' security configuration, leaving the feature-server, registry-server, and offline-server endpoints completely unauthenticated and accessible to any network-reachable attacker in Red Hat OpenShift AI (RHOAI) deployments. Exploitation enables three distinct high-impact outcomes: remote code execution via injection of a malicious User-Defined Function (UDF) onto the feature-server, denial of service by forcing full re-materialization of all tenant features, and unauthorized read access to cross-tenant feature data. No public exploit code has been identified at time of analysis and CISA KEV status is not confirmed, but the trivial exploitation conditions - no authentication, no interaction, default configuration - make this a realistic priority for any RHOAI operator.
The MaaS (Model-as-a-Service) Gateway component in Red Hat OpenShift AI (RHOAI) is improperly configured, enabling any low-privileged authenticated user within the platform to act as a man-in-the-middle against all model-serving traffic. Affected users can intercept, read, log, and modify requests and responses traversing the gateway, exposing highly sensitive artifacts including API access keys, user input prompts, and model outputs. No public exploit code has been identified at time of analysis, and the vulnerability has not been added to the CISA KEV catalog, but the CVSS 8.8 rating with high confidentiality, integrity, and availability impact reflects the severity of unrestricted traffic access within a shared AI serving environment.
Symlink escape in tar-rs versions 0.4.11 through 0.4.46 exposes arbitrary host filesystem files when a privileged process archives an attacker-controlled directory using the Builder::append_dir_all() function. The function resolves symbolic links during recursive directory traversal without verifying that resolved target paths remain within the specified source root, causing out-of-bounds files to be silently captured into the archive as regular file entries and disclosed to the attacker. A publicly available proof-of-concept exists; the CVE is not listed in CISA KEV, but low attack complexity combined with high confidentiality impact makes this a meaningful risk for affected Rust-based archiving pipelines.
Insufficient source identity validation in Red Hat Multicluster Global Hub's manager component allows a network-adjacent attacker who has compromised a managed hub to impersonate any other hub on the shared Kafka status bus. By presenting a legitimately obtained Kafka client certificate from the compromised hub while falsifying the CloudEvent source field, the attacker can overwrite or delete compliance records, inventory data, and cluster health telemetry belonging to sibling hubs in the shared database. No public exploit has been identified at time of analysis, but the scope-changed CVSS vector (S:C) reflects that the integrity impact extends beyond the initially compromised hub to the entire multi-hub management plane.
Arbitrary file read on the Jenkins controller affects Jenkins through LTS 2.555.3, where an authenticated attacker holding Item/Configure permission can exfiltrate any file readable by the Jenkins process user by uploading a crafted tar archive containing a symlink. This is an incomplete-fix bypass of CVE-2026-33001: the prior patch validated where a symlink is placed during extraction but not where it points, so a link staged inside the workspace can still resolve to paths outside it. There is no public exploit identified at time of analysis, and the flaw is not listed in CISA KEV, but it directly exposes secrets/master.key, credentials.xml, and other sensitive configuration.
Out-of-bounds read in Redis Cluster Bus PING message parsing affects Redis through version 8.8.1, enabling adjacent unauthenticated attackers to trigger denial of service or extract limited heap memory contents. The root cause is in the getPingExtLength() function, which fails to validate extension length fields against the actual remaining buffer size, allowing a crafted gossip-protocol PING packet to drive the parser past the allocated buffer boundary. No public exploit has been identified at time of analysis, and this vulnerability has not been confirmed in the CISA KEV catalog.
Heap-use-after-free in the Ruby json gem's native C extension (versions 2.20.0 through 2.21.1) allows an unauthenticated remote attacker to crash the Ruby process by supplying a crafted truncated JSON stream with duplicate object keys to any application using JSON::ResumableParser. The root cause is that the parser's input buffer is freed without resetting the state.start, state.cursor, and state.end pointers, which are subsequently dereferenced when partial_value processes the duplicate-key warning path via cursor_position, producing a heap-use-after-free confirmed by AddressSanitizer and a native SIGSEGV on official RubyGem releases. Impact is limited to availability - no code execution or information disclosure is claimed - and no public exploit code has been identified at time of analysis, though a private end-to-end TCP proof-of-concept was submitted with the advisory.
Sandbox escape in Google Chrome prior to 151.0.7922.109 enables a remote attacker who has already compromised the renderer process to break out of Chrome's OS-level security sandbox via a crafted HTML page. This is a second-stage, chained vulnerability - not directly exploitable in isolation - making it a high-value component in multi-step browser attacks that pair a renderer exploit with this UI input validation flaw to achieve full OS-level code execution. No public exploit has been identified and SSVC rates exploitation status as none at time of analysis, though the total technical impact and confirmed scope change (S:C) make this a critical priority when chained with any renderer compromise.
Use-after-free in Skia, Chrome's 2D graphics rendering engine, enables arbitrary code execution within the renderer sandbox in Google Chrome versions prior to 151.0.7922.109. Exploitation requires an attacker to have already achieved renderer process compromise, making this a second-stage chained payload rather than a standalone initial access vector - a prerequisite that materially constrains real-world exploit delivery. No public exploit code has been identified at time of analysis, and SSVC confirms Exploitation: none and Automatable: no, though C/I/A impacts are rated High within the sandboxed scope.
Sandbox escape in Google Chrome desktop versions prior to 151.0.7922.109 stems from a use-after-free in the Payments component, letting a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Rated High by Chromium and scored CVSS 9.6 due to a scope change, though exploitation requires user interaction (visiting a malicious page). There is no public exploit identified at time of analysis and no CISA KEV listing, but Chrome renderer/sandbox-escape bugs are historically high-value targets.
Remote code execution within the Chrome sandbox via an integer overflow in the V8 JavaScript engine affects Google Chrome prior to version 151.0.7922.109. An unauthenticated remote attacker can trigger the flaw by enticing a user to visit a specially crafted HTML page, resulting in full compromise of confidentiality, integrity, and availability within the renderer process. No public exploit code has been identified and CISA SSVC confirms exploitation status as none, though the total technical impact and low attack complexity elevate real-world priority for patching.
Out-of-bounds write in Skia enables sandbox escape in Google Chrome prior to 151.0.7922.109, allowing a remote attacker who has already compromised the renderer process to break out of Chrome's sandbox via a crafted HTML page. This is explicitly a second-stage chaining vulnerability - it does not independently achieve initial code execution but elevates a renderer-level compromise to full OS-level access. No public exploit code or active exploitation has been identified at time of analysis, though the scope-changing nature of this vulnerability makes it a high-value target for chained browser exploit chains.
Use-after-free in Chrome's Views component prior to version 151.0.7922.109 enables a sandbox escape for remote attackers who have already compromised the renderer process, via a crafted HTML page. The CVSS scope change (S:C) confirms the potential for OS-level code execution beyond Chrome's renderer sandbox, earning a Critical severity designation from the Chromium security team despite an NVD score of 8.3. No public exploit code or CISA KEV confirmation has been identified at time of analysis, though this vulnerability class is a high-value target frequently weaponized as the second stage of browser exploit chains by sophisticated threat actors.
Sandbox escape in Google Chrome's Media component on Windows (versions prior to 151.0.7922.109) lets a remote attacker break out of the renderer sandbox by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium and CVSS 9.6 because a successful escape yields full confidentiality, integrity, and availability impact beyond the sandboxed process. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though Chrome UAF media bugs are historically attractive targets.
Sandbox escape in Google Chrome for Android before 151.0.7922.109 stems from a use-after-free in the WebGL graphics component (CWE-416), letting a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Chromium rates this Critical and CVSS scores it 9.6 with a scope change (S:C), reflecting the cross-boundary sandbox escape. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but Chrome WebGL memory-corruption bugs are historically high-value exploitation targets.
Privilege escalation in Google Chrome's Contextual Tasks feature (prior to 151.0.7922.109) allows a remote attacker to escalate privileges by luring a victim to a crafted HTML page that delivers insufficiently validated untrusted input. The vulnerability carries a CVSS 8.8 score, reflecting high confidentiality, integrity, and availability impact with no prior authentication required from the attacker. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though the low attack complexity and Chrome's ubiquitous deployment surface make prompt patching a priority.
Remote code execution within the V8 JavaScript engine affects Google Chrome prior to 151.0.7922.109, allowing a remote attacker to execute arbitrary code inside the browser sandbox by luring a victim to a crafted HTML page. The flaw stems from an inappropriate implementation in V8 (CWE-693, Protection Mechanism Failure), carrying a CVSS 8.8 rating with high confidentiality, integrity, and availability impact. No public exploit code has been identified and CISA SSVC confirms no active exploitation at time of analysis, though the technical impact is rated total by SSVC, underscoring the severity if exploited.
Sandbox escape in Google Chrome's Web Authentication (WebAuthn) component before 151.0.7922.109 lets a remote attacker who lures a victim to a crafted HTML page corrupt memory via a use-after-free and potentially break out of the renderer sandbox. Rated High by Chromium and scored CVSS 9.6 (scope-changed), it affects the vast installed base of desktop Chrome; Google has shipped a fixed Stable-channel build. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Sandbox escape in Google Chrome's Codecs component (versions prior to 151.0.7922.109) allows a remote attacker to break out of the renderer sandbox when a victim views a crafted HTML page, via insufficient validation of untrusted input (CWE-20). Rated CVSS 9.6 with a changed scope, the flaw affects the desktop Stable channel across all platforms and is fixed in 151.0.7922.109. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Use-after-free exploitation in Google Chrome's Media component on Windows enables sandbox escape for attackers who have already compromised the renderer process. Chrome versions prior to 151.0.7922.109 on Windows are affected, with a crafted HTML page serving as the trigger mechanism to corrupt freed memory and break out of the renderer sandbox. SSVC rates current exploitation as none and non-automatable, though the total technical impact class reflects full OS-level compromise if the two-stage attack chain is completed successfully.
Remote code execution within the Chrome renderer sandbox is possible in Google Chrome versions prior to 151.0.7922.109 through an out-of-bounds write flaw in the V8 JavaScript engine, triggerable by a crafted HTML page. An unauthenticated remote attacker needs only to lure a victim to a malicious page, achieving code execution confined to the sandboxed renderer process. No public exploit or active exploitation has been identified at time of analysis; however, the CVSS 8.8 score and SSVC total technical impact classification indicate significant potential consequences if exploitation is developed.
Use-after-free in the Views UI rendering component of Google Chrome (all versions prior to 151.0.7922.109) enables a remote attacker to corrupt heap memory via a crafted HTML page, requiring the victim to perform specific UI gestures. The CVSS:3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects a fully network-delivered attack with no authentication barrier, though high attack complexity and mandatory user interaction substantially reduce opportunistic exploitation likelihood. No public exploit code or CISA KEV listing has been identified at time of analysis; Google rated this High severity internally and shipped a patch in the stable channel update.
Use-after-free in Google Chrome's Views UI framework on Windows, fixed in version 151.0.7922.109, exposes users to heap corruption with full confidentiality, integrity, and availability impact. Exploitation requires convincing a target to perform specific UI gestures while visiting a crafted HTML page, making this a social-engineering-dependent but high-consequence flaw. No public exploit code or CISA KEV listing has been identified at the time of analysis; however, the severity and platform breadth make patching urgent for Windows enterprise fleets.
Sandbox escape in Google Chrome for Android before 151.0.7922.109 stems from an out-of-bounds write in ANGLE, Chrome's OpenGL ES/GPU translation layer, allowing a remote attacker who lures a victim to a crafted HTML page to corrupt GPU-process memory and potentially break out of the renderer sandbox. Chromium rates the issue Critical and a vendor patch is available, but there is no public exploit identified at time of analysis and CISA SSVC records exploitation status as none. The high CVSS 9.6 reflects the scope-changing sandbox-escape potential rather than confirmed in-the-wild use.
Heap buffer overflow in Google Chrome's Base component (versions prior to 151.0.7922.109) enables potential heap corruption and arbitrary code execution when a user installs a malicious Chrome Extension crafted by an attacker. Exploitation requires social engineering to achieve extension installation, reflected in the AC:H/UI:R CVSS metrics, which meaningfully constrains real-world attack scale compared to the raw 7.5 score. No public exploit identified at time of analysis, and a vendor-released patch is available in 151.0.7922.109.
Use-after-free in the Payments component of Google Chrome prior to 151.0.7922.109 enables a sandbox escape when an attacker has already compromised the renderer process. Exploitation requires chaining a prior renderer compromise with delivery of a crafted HTML page, placing this firmly in the category of multi-stage browser exploitation. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and SSVC classifies exploitation status as none, though the technical impact is rated total due to the full sandbox escape capability.
Sandbox escape in Google Chrome on Android (prior to 151.0.7922.109) via a use-after-free vulnerability in the Skia graphics library allows a remote attacker who has already compromised the renderer process to break out of Chrome's sandbox through a crafted HTML page. The CVSS vector (S:C, C:H/I:H/A:H) confirms full cross-boundary compromise, elevating an attacker from renderer-level code execution to broader Android OS access. No active exploitation is confirmed at time of analysis (SSVC exploitation: none; not listed in CISA KEV), though Technical Impact is rated total by CISA's SSVC framework.
Site isolation bypass in Google Chrome Workers allows a remote attacker who has already compromised the renderer process to cross origin boundaries and access data from other sites via a crafted HTML page. All Chrome versions prior to 151.0.7922.109 are affected. EPSS sits at 0.26% (17th percentile) and SSVC confirms exploitation status as none, meaning no public exploit or active exploitation has been identified at time of analysis - the elevated CVSS of 8.1 reflects worst-case impact if this flaw is chained with a renderer exploit, rather than standalone exploitability.
Sandbox escape in Google Chrome prior to 151.0.7922.109 allows a remote attacker who has already compromised the renderer process to break out of Chrome's isolation boundary via a crafted HTML page exploiting insufficient Navigation policy enforcement (CWE-693). This is a second-stage exploit primitive: it elevates a sandboxed renderer breach into full host OS code execution at browser-process privilege, crossing Chrome's core security boundary as reflected in the CVSS Scope:Changed metric. No public exploit code or CISA KEV listing has been identified at time of analysis; the vendor-confirmed patch shipped in the 151.0.7922.109 stable channel update.
Remote code execution within the Chrome sandbox is possible in Google Chrome versions prior to 151.0.7922.109 due to a use-after-free vulnerability in the V8 JavaScript engine, triggerable by a remote attacker through a specially crafted HTML page. The attacker achieves arbitrary code execution confined to the Chrome renderer sandbox, requiring no privileges but necessitating user interaction to visit a malicious page. Google has released a fix in version 151.0.7922.109; SSVC assessment confirms no known active exploitation at time of analysis, and no public exploit code has been identified.
Remote code execution within Chrome's sandboxed renderer process is achievable in Google Chrome prior to 151.0.7922.109 through a crafted HTML page exploiting an inappropriate implementation in the V8 JavaScript engine. An unauthenticated remote attacker needs only to lure a victim to a malicious page - no credentials or special privileges are required on the attacker's side. Google has rated this High severity (Chromium classification); no public exploit has been identified at time of analysis, and CISA SSVC reports exploitation status as none, though technical impact is rated total within the sandbox boundary.
Sandbox escape in Google Chrome for Linux (versions before 151.0.7922.109) stems from a use-after-free in the Aura windowing subsystem, letting a remote attacker who lures a victim to a crafted HTML page corrupt memory and potentially break out of the renderer sandbox. Google rated the Chromium severity Critical (CVSS 9.6, scope-changed), but there is no public exploit identified at time of analysis and CISA's SSVC framework records exploitation status as 'none'. Because a full sandbox escape gives attacker code the privileges of the browser process on the host, this is a high-priority patch despite the absence of observed exploitation.
Out-of-bounds write in the GPU process of Google Chrome on Linux enables sandbox escape when an attacker has already compromised the renderer process. Specifically, an attacker controlling the renderer can deliver a crafted HTML page that triggers CWE-787 memory corruption in the GPU process, which operates with higher OS-level privileges than the sandboxed renderer, allowing full sandbox escape. Versions prior to 151.0.7922.109 on Linux are affected; no public exploit code and no CISA KEV listing have been identified at time of analysis, placing this in the category of no public exploit identified at time of analysis.
Sandbox escape in Google Chrome's Aura display layer on Linux allows a remote attacker with an already-compromised renderer process to break out of the Chrome sandbox via a crafted HTML page, achieving full system-level code execution. Affected versions are all Chrome builds prior to 151.0.7922.109 on Linux. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS scope-changed rating (S:C) and High across C/I/A reflect the severe post-exploitation impact of a successful sandbox escape in a privileged browser context.
Use-after-free in Google Chrome's Translate component (versions prior to 151.0.7922.109) enables remote attackers to execute arbitrary code within the browser's renderer sandbox by directing a user to a crafted HTML page. The CVSS 8.8 score reflects network-accessible, low-complexity exploitation gated only by a single user interaction - visiting an attacker-controlled page. No public exploit code or CISA KEV listing has been identified at time of analysis, though the RCE primitive within one of the world's most widely deployed browsers represents a materially significant attack surface.
Use-after-free in Google Chrome's HTML engine (all versions prior to 151.0.7922.109) exposes users to potential heap corruption and code execution when they visit a crafted HTML page. The CVSS 8.8 score reflects unauthenticated, network-reachable exploitation requiring only a single user interaction - consistent with Chromium's own 'High' severity classification. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor patch (151.0.7922.109) has been released and is the primary mitigation.
Sandbox escape in Google Chrome on Android prior to 151.0.7922.109 is achievable by a local attacker via a malicious file exploiting insufficient input validation in WebAPK processing. The CVSS scope change (S:C) with high confidentiality, integrity, and availability impacts reflects the potential for full breakout beyond Chrome's sandbox boundary into the broader Android process space. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor patch is available in the stable channel release.
Heap corruption via use-after-free in Google Chrome's Views UI framework (prior to 151.0.7922.109) can be triggered by a remote attacker who delivers a crafted HTML page and induces a user to perform specific UI gestures. Successful exploitation may lead to arbitrary code execution or denial of service within the browser process. No public exploit code or CISA KEV listing has been identified at time of analysis, and the CVSS AC:H rating signals non-trivial exploitation conditions that reduce real-world risk compared to the high severity label.
Use-after-free in Chrome's Resources component on Android enables sandbox escape for attackers who have already established a foothold in the renderer process. Affected versions are all Chrome for Android releases prior to 151.0.7922.109. The CVSS scope change (S:C) and High ratings across Confidentiality, Integrity, and Availability confirm that successful exploitation breaks out of the browser sandbox, exposing the underlying Android OS. No public exploit code or CISA KEV listing exists at time of analysis, though the chained exploit capability (renderer-to-sandbox-escape) represents a critical capability for advanced threat actors.
Sandbox escape via GPU use-after-free in Google Chrome prior to 151.0.7922.109 enables a remote attacker who has already compromised the renderer process to break out of the Chromium sandbox by delivering a crafted HTML page. The vulnerability resides in Chrome's GPU component and, if successfully chained after an initial renderer compromise, yields full confidentiality, integrity, and availability impact on the host system. No public exploit code has been identified at the time of analysis, and SSVC classifies exploitation status as none with automatable set to no, indicating no evidence of active or mass exploitation.
OS-level privilege escalation in Google Chrome's Windows CredentialProvider component allows a local attacker to gain elevated system privileges by winning a race condition triggered via a malicious file. Affected are all Chrome for Windows builds prior to 151.0.7922.109. No public exploit code has been identified and CISA has not added this to the Known Exploited Vulnerabilities catalog, but the SSVC assessment rates technical impact as total, meaning successful exploitation yields full system compromise.
Heap buffer overflow in the CrashReporting component of Google Chrome prior to 151.0.7922.109 enables sandbox escape when an attacker has already compromised the renderer process and can deliver a crafted HTML page. The CVSS scope change (S:C) and total technical impact rating confirm full host system compromise is achievable as the second stage of a chained exploit. No public exploit code or active exploitation has been identified at time of analysis, per SSVC exploitation status of 'none' and absence from CISA KEV.
Use-after-free in the WebGL subsystem of Google Chrome for Android (prior to 151.0.7922.109) enables sandbox escape for an attacker who has already achieved renderer-process compromise. By directing a victim to a crafted HTML page, an adversary with existing renderer access can exploit freed memory corruption in WebGL to break out of Chrome's sandbox and reach OS-level execution on the Android device. No public exploit code or active exploitation has been identified; SSVC rates exploitation as none and automatable as no, though technical impact is assessed as total given the full scope change.
Arbitrary file write via Zip-Slip in Nx's self-hosted HTTP remote cache extractor allows a malicious or MITM-positioned cache server to overwrite files anywhere on the developer's machine, escalating to remote code execution. Affected are Nx workspaces using self-hosted remote cache (NX_SELF_HOSTED_REMOTE_CACHE_SERVER, @nx/s3-cache, @nx/gcs-cache, @nx/azure-cache, @nx/shared-fs-cache) running nx >= 20.8.0 and < 22.7.7; Nx Cloud and the default local cache are confirmed unaffected. No public exploit code has been identified and this vulnerability is not listed in CISA KEV at time of analysis, but the CVSS 4.0 score of 8.7 and trivial exploitability once positioned reflect significant real-world risk for teams using self-hosted caching.
Denial of service (and possibly information disclosure) in the Apache Portable Runtime Utility (APR-util) library through version 1.6.3 lets remote attackers crash any consumer that parses attacker-supplied XML via apr_xml_quote_elem(). The flaw is an uncontrolled stack recursion (CWE-674) triggered by deeply nested or malicious XML; no authentication or user interaction is required. There is no public exploit identified at time of analysis and it is not in CISA KEV, but the CISA SSVC framework rates it automatable, so scanning-driven abuse is plausible.
SQL injection in the Apache Portable Runtime Utility (APR-util) affects the apr_dbd_oracle database provider in versions 1.6.0 through 1.6.3, letting remote attackers inject arbitrary SQL through an application that relies on this DBD backend for query construction or escaping. Rated CVSS 9.1 with high confidentiality and integrity impact but no availability impact, it allows unauthorized reading and modification of Oracle-backed data. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Heap-based buffer overflow in Apache Portable Runtime Utility's redis client component allows remote unauthenticated attackers to crash applications that use the library, resulting in a denial of service. Affected versions span APR-util 1.6.0 through 1.6.3; version 1.6.4 resolves the issue per Apache's advisory on the oss-security mailing list. No public exploit code and no CISA KEV listing have been identified at time of analysis, though SSVC classifies the flaw as automatable with partial technical impact, indicating it could be scripted for broad scanning.
Heap-based buffer overflow in Apache Portable Runtime Utility's memcached client component (versions 1.3.0 through 1.6.3) allows remote unauthenticated attackers to crash affected applications, causing denial of service. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms full availability impact with no confidentiality or integrity exposure. No public exploit identified at time of analysis, but SSVC marks this as automatable, meaning scripted mass scanning is feasible once attack primitives are established.
Double-spending of OAuth2 authorization codes in Apache CXF's JCacheCodeDataProvider enables issuance of multiple valid access tokens from a single code. Concurrent requests to the token endpoint during the brief window between code validation and invalidation exploit the TOCTOU race condition (CWE-367), allowing an attacker in possession of a valid authorization code to obtain additional access tokens beyond the one they are entitled to. No public exploit has been identified at time of analysis, and fixed versions are available across all maintained branches.
Authorization scope escalation in Apache CXF's OAuth2 Dynamic Client Registration endpoint allows any registering client to self-assign privileged scopes by supplying arbitrary `scope` values in the registration request, which the authorization server stores verbatim without validating against a server-defined allowlist. Affected versions span the 3.x, 4.1.x, and 4.2.x release lines; patched releases 3.6.12, 4.1.8, and 4.2.3 are available per the Apache advisory. No public exploit or active exploitation has been identified at time of analysis, but the straightforward exploitation path - crafting a single registration request - makes this a meaningful authorization bypass risk for any deployment exposing CXF's OAuth2 AS with Dynamic Client Registration enabled.
Apache CXF's JwtRequestCodeFilter blindly copies all claims from a validly-signed JWT request object into the OAuth2 authorization parameter map, including security-sensitive fields that must not be client-controlled: code_challenge, code_challenge_method, nonce, and state. Affected are all Apache CXF deployments using this filter for OAuth2/OIDC authorization code flows prior to versions 4.2.3, 4.1.8, and 3.6.12. An OAuth2 client with a known or compromised client_secret can craft a signed request JWT that overrides the PKCE parameters established in the outer HTTP request, effectively nullifying PKCE authorization code binding and OIDC replay protection. No public exploit code or CISA KEV listing has been identified at time of analysis.
Apache CXF's DefaultEncryptingCodeDataProvider allows captured OAuth 2.0 authorization codes to be redeemed an unlimited number of times, violating RFC 6749's single-use requirement. The removeCodeGrant() method that should invalidate a code after first exchange fails to do so, meaning any attacker who intercepts or obtains a legitimate authorization code can replay it repeatedly to obtain additional access tokens. No public exploit has been identified at time of analysis, and the issue is addressed in patched releases 4.2.3, 4.1.8, and 3.6.12.
Token revocation bypass in Apache CXF's DefaultEncryptingOAuthDataProvider allows revoked OAuth access and refresh tokens to remain functionally valid indefinitely - the provider continues to decrypt them successfully and TokenIntrospectionService returns active:true in direct violation of RFC 7009 and RFC 7662 mandates. All Apache CXF deployments using this built-in OAuth data provider and relying on token revocation as a security control are affected across the 3.6.x, 4.1.x, and 4.2.x branches. An attacker or suspended user who retains a revoked token can continue accessing protected resources as though revocation never occurred, bypassing intended authorization boundaries. No public exploit has been identified at time of analysis, though the attack requires no tooling beyond a standard HTTP client.
Authorization Code Substitution in Apache CXF's OpenID Connect Relying Party implementation allows remote attackers to hijack authenticated sessions when CXF is deployed in Hybrid Flow mode with a non-compliant or misconfigured Identity Provider that omits the c_hash parameter. Successful exploitation yields full authenticated access equivalent to account takeover, with high confidentiality and integrity impact. No public exploit has been identified at time of analysis, but SSVC classifies the attack as automatable with total technical impact once the prerequisite IdP condition is present.
Unsafe deserialization in Apache CXF's JMS transport allows any party able to publish to the service's JMS destination to achieve denial of service or, where a compatible deserialization gadget chain is present on the application classpath, remote code execution within the CXF process. All Apache CXF versions prior to 4.2.3, 4.1.8, and 3.6.12 are affected when the JMS transport is in use. No public exploit code or CISA KEV listing has been identified at time of analysis, though the vulnerability class (CWE-502 with unrestricted ObjectInputStream) is well-understood and tooling such as ysoserial makes it routinely exploitable wherever gadget libraries are present.
SSRF protection bypass in Gitea prior to 1.27.0 exposes internal services, cloud instance-metadata endpoints (e.g., AWS IMDSv1 at 169.254.169.254), and local files - including the application configuration containing database credentials and signing secrets - to authenticated attackers. Three HTTP fetch code paths in the migration and OAuth avatar subsystems use Go's raw http.Get() rather than the hardened hostmatcher.NewDialContext() transport used elsewhere, completely circumventing Gitea's built-in SSRF defenses. A publicly available proof-of-concept is included in the GHSA advisory; no confirmed active exploitation (CISA KEV) has been identified at time of analysis.
Unsafe class loading in the ORB (Object Request Broker) component of IBM WebSphere Application Server 8.5, 9.0, and Liberty Continuous Delivery allows a malicious or attacker-controlled IIOP server to force a WebSphere client/server to load and instantiate arbitrary Java classes over the network. Exploitation requires no authentication or user interaction (CVSS 9.8), and successful abuse can lead to loss of confidentiality, integrity, and availability, potentially culminating in remote code execution via dangerous class instantiation. There is no public exploit identified at time of analysis, and EPSS estimates only a 0.44% probability of exploitation in the next 30 days.
Memory exhaustion denial-of-service in OpenSSL 3.6.0-3.6.3 and 4.0.0-4.0.1 allows a malicious TLS server to leak attacker-tunable amounts of heap memory per handshake in connecting client applications that have explicitly enabled OCSP staple verification. By delivering a syntactically valid BasicOCSPResponse containing an empty SingleResponse sequence - optionally padded with bogus certificates to amplify each allocation - the server causes the internal OCSP_BASICRESP structure to be allocated but never freed, bypassing the cleanup path. No public exploit has been identified at time of analysis and no CISA KEV listing exists; risk is bounded by the non-default OCSP flag requirement.
Authentication bypass in Red Hat Build of Keycloak (and Red Hat Single Sign-On 7) lets an unauthenticated attacker forge SAML responses to hijack accounts when a SAML identity-provider's metadata was imported without explicit key-usage attributes, causing the keycloak-services identity-brokering engine to silently disable signature validation despite a signing certificate being present. Rated CVSS 9.1 with total technical impact per CISA SSVC, an attacker who knows a victim's external identifier can log in as that user. No public exploit identified at time of analysis, and EPSS is low (0.14%, 4th percentile), indicating the risk is currently theoretical/targeted rather than mass-exploited.
Privilege escalation to cluster-admin in Red Hat Advanced Cluster Management for Kubernetes (ACM) lets a user holding only namespace-scoped 'edit' rights on an ACM hub namespace take over the entire cluster. By creating a Channel pointing to an attacker-controlled Helm repository and a Subscription referencing it, the app-subscription controller (multicluster-operators-subscription) applies the chart with its own elevated authority and without enforcing the subscription-admin role or namespace confinement, letting the chart install cluster-scoped objects such as a ClusterRoleBinding to cluster-admin. No public exploit identified at time of analysis, and EPSS is low (0.25%), but the technical impact is total and the flaw directly contradicts ACM's documented namespace-confinement guarantee.
MLflow's AI Gateway proxy exposes internal network services - including cloud-instance metadata endpoints - to any authenticated user, including read-only accounts, via an unvalidated api_base field in the CreateGatewaySecret endpoint. All MLflow releases through 3.14.0 are affected; the attack requires only basic credentials and no special configuration, making IAM credential theft a realistic outcome for cloud-hosted deployments. No public exploit has been identified at time of analysis, but the two-step attack (create secret, invoke proxy) involves only standard HTTP requests and no technical barrier beyond holding a valid account.
Denial of service in Apache Qpid Proton-J through 0.34.1 allows unauthenticated remote attackers to crash the service by sending AMQP messages with deeply nested type structures that exhaust the JVM call stack via a StackOverflowError. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivial, unauthenticated network exploitation with no user interaction required, targeting availability exclusively. No active exploitation has been confirmed - this vulnerability is absent from CISA KEV and carries a low EPSS score of 0.21% (11th percentile) - but the zero-prerequisite attack path warrants prompt patching for any internet-facing AMQP deployment.
Incorrect buffer size calculation (CWE-131) in an unidentified Linux distribution package tracked by both Ubuntu and Red Hat enables local, user-interaction-triggered exploitation with high confidentiality, integrity, and availability impact, yielding a CVSS base score of 7.8. The local attack vector combined with a user-interaction requirement (AV:L/UI:R/PR:N) is consistent with a malicious file parsing scenario, where a user opens a crafted input triggering the buffer miscalculation. No public exploit has been identified at time of analysis, and no KEV listing is present; however, the full C:H/I:H/A:H impact triad indicates potential for memory corruption leading to arbitrary code execution.
Uncontrolled resource consumption in Apache Qpid ProtonJ2 through version 1.1.0 allows authenticated AMQP clients to cause denial of service by sending deliveries composed of an unbounded number of transfer frames. Because the library imposed no upper limit on how many AMQP transfer frames could constitute a single incoming delivery, a malicious but authenticated client can force unbounded heap accumulation, leading to excessive memory usage and potential JVM failure. No public exploit code and no active exploitation have been identified at time of analysis; vendor-released patch version 1.2.0 is available.
Denial of service in Apache Qpid ProtonJ2 through version 1.1.0 allows a remote unauthenticated attacker to crash the messaging service by sending AMQP messages with maliciously crafted type nesting that triggers an uncontrolled recursive call stack, resulting in a StackOverflowError. The flaw (CWE-674) is exploitable without authentication over the network with low attack complexity, making it trivially reachable against any exposed ProtonJ2 endpoint. No active exploitation has been confirmed (not in CISA KEV) and EPSS sits at 0.21% (11th percentile), suggesting minimal observed exploitation activity at time of analysis despite the ease of triggering the condition.
Remote unauthenticated denial of service in Apache Qpid ProtonJ2 through version 1.1.0 allows a network attacker to exhaust server memory by sending AMQP messages with maliciously crafted type size or count fields, triggering uncontrolled allocation. The vulnerability (CWE-789) requires no authentication or user interaction and is exploitable directly over the network with low complexity, making it trivially reachable in any exposed deployment. No active exploitation has been confirmed in CISA KEV, and the EPSS score of 0.21% (11th percentile) suggests limited real-world exploitation interest at time of analysis; a vendor-released fix is available in version 1.2.0.
Denial of service in Apache Qpid ProtonJ2 through 1.1.0 allows unauthenticated remote attackers to exhaust server resources by exploiting unbounded caching of AMQP symbol values during pre-authentication message processing. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms no credentials or user interaction are required, and the attack can be executed at low complexity from any network-accessible position. No public exploit or CISA KEV listing exists at time of analysis, though the trivial exploitation conditions make this a realistic threat against any Qpid ProtonJ2 endpoint exposed to untrusted networks.
Token credential exposure in Red Hat insights-client causes the CCX_TOKEN bearer credential, used exclusively in disconnected cluster deployments, to be written in clear text to pod logs on every startup when glog verbosity is set to level 2 or higher. Any party with read access to pod logs or an aggregated logging backend can silently harvest this credential and use it to authenticate against the CCX API, extending access beyond the originating pod (CVSS scope change S:C). No public exploit is identified at time of analysis, and EPSS at 0.21% (11th percentile) combined with SSVC exploitation status of 'none' indicates this remains theoretical rather than actively targeted.
Sensitive credential leakage in Red Hat insights-client exposes cloud.openshift.com pull-secret tokens through application log files on Advanced Cluster Management hub clusters. When insights-client receives any non-200 HTTP response from the Red Hat cloud endpoint, it writes the full request headers - including the long-lived pull-secret bearer token - to pod logs readable by local cluster users. An attacker who harvests this token can authenticate against Red Hat cloud services without possessing their own credentials. No public exploit has been identified at time of analysis, and multiple vendor-released errata patch the behavior.
Heap and stack buffer overflow in CivetWeb's read_websocket() function (through commit 4a4f0c95) allows unauthenticated remote attackers to corrupt memory by sending crafted compressed WebSocket frames, but only against instances compiled with both USE_ZLIB and MG_EXPERIMENTAL_INTERFACES build flags. Attackers negotiate permessage-deflate during the WebSocket handshake and send an RSV1-flagged frame that triggers a 4-byte zlib sync trailer write past the allocated buffer boundary, corrupting heap metadata and enabling denial of service or potential code execution (per VulnCheck tagging). No public exploit code is confirmed and this CVE does not appear in CISA KEV at time of analysis, but the deterministic 4-byte overwrite primitive is a credible research target; the non-default build configuration substantially limits the real-world exploitable population.
Local code execution via out-of-bounds write in Microsoft .NET allows an unauthenticated local attacker to achieve full code execution upon successful exploitation, with high impact across confidentiality, integrity, and availability. The vulnerability requires user interaction - such as opening a malicious file or running a crafted application - making social engineering a likely delivery vector. No public exploit code or CISA KEV listing has been identified at time of analysis, though the Microsoft Security Response Center has acknowledged the issue.
Remote code execution in Microsoft Office SharePoint exploits unsafe deserialization of attacker-controlled data over the network. An authenticated attacker with low-level network access can submit a crafted serialized payload that SharePoint deserializes without sufficient validation, resulting in full compromise of confidentiality, integrity, and availability. No public exploit has been identified at time of analysis, but the low attack complexity and high impact across all three security properties make this a critical remediation priority.
Stack-based buffer overflow in Microsoft Office enables local arbitrary code execution when a user opens a specially crafted document. The CVSS vector (AV:L/AC:L/PR:N/UI:R) confirms exploitation is local and requires user interaction - most likely triggered by opening a maliciously crafted Office file delivered via phishing or other social engineering. No active exploitation has been confirmed (not listed in CISA KEV) and no public exploit code has been identified at time of analysis, though the high-impact triad (C:H/I:H/A:H) and Microsoft Office's ubiquitous deployment footprint make this a notable patching priority.
Remote code execution in Microsoft Office SharePoint enables any authenticated low-privileged user to execute arbitrary code on the server by submitting maliciously crafted serialized data over the network. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms the attack requires no user interaction, low complexity, and only a standard SharePoint account - making this straightforward to weaponize within any organization whose SharePoint is network-accessible to internal users or external authenticated parties. No public exploit code or CISA KEV listing is identified at time of analysis, though SharePoint deserialization vulnerabilities have historically attracted rapid weaponization.
Local privilege escalation in the Windows Cross Device Service (CVE-2026-66804) allows a low-privileged authenticated user to gain SYSTEM or elevated permissions on the local machine. The flaw stems from CWE-284 (Improper Access Control), meaning the service fails to adequately enforce authorization boundaries between user privilege levels. No public exploit or CISA KEV listing has been identified at time of analysis, but the low attack complexity and absence of required user interaction make this a straightforward target for post-compromise lateral movement or privilege escalation tooling.
Local privilege escalation in Windows Key Guard exposes any authenticated local user to full system compromise via a heap-based buffer overflow (CWE-122). The CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms low-complexity exploitation requiring only a standard local user session - no elevated rights, no user interaction. This class of vulnerability is a staple post-initial-access technique in ransomware and APT intrusion chains. No public exploit identified at time of analysis, and no CISA KEV listing is present in the provided data.
Local privilege escalation in Microsoft .NET Framework exploits a relative path traversal flaw (CWE-23), enabling an unprivileged local user to gain elevated system rights through user interaction. The vulnerability affects .NET Framework on Windows and is rated CVSS 7.8 (High), with full confidentiality, integrity, and availability impact upon successful exploitation. No public exploit code or CISA KEV listing has been identified at time of analysis.
Local privilege escalation in Microsoft .NET (versions 8.0, 9.0, and 10.0) and Microsoft Visual Studio 2022/2026 allows a low-privileged local attacker to elevate privileges by triggering an uncaught exception (CWE-248) within the runtime. The CVSS scope change (S:C) indicates impact extends beyond the .NET security boundary to the underlying host system. No public exploit identified at time of analysis, and Microsoft has released patched versions across all affected branches.
Denial-of-service in Microsoft .NET runtimes and Visual Studio allows unauthenticated remote attackers to crash or hang .NET applications by supplying crafted input that exploits an unchecked loop termination condition. Affected are .NET 8.0 (all releases through 8.0.29), .NET 9.0 (through 9.0.18), .NET 10.0 (through 10.0.10), and bundled Visual Studio 2022 and 2026 installations. No public exploit has been identified at time of analysis, but the low attack complexity and lack of authentication requirement make this a credible automated threat against any internet-exposed .NET service. Vendor-released patches are available and should be applied promptly, particularly for externally reachable endpoints. Note: the ENISA EUVD tags this as 'Authentication Bypass,' which conflicts with the description and CVSS impact metrics (C:N/I:N/A:H); this discrepancy should be verified with Microsoft's advisory.
Integer overflow in Microsoft .NET Framework and modern .NET runtimes enables local code execution with full process compromise (C:H/I:H/A:H) across a broad product surface spanning .NET Framework 3.5 through 4.8.1, .NET 8.0, 9.0, 10.0, and Visual Studio 2022 and 2026. An attacker who can deliver crafted input processed by a vulnerable .NET application can trigger arithmetic wraparound (CWE-190) to corrupt runtime memory and execute arbitrary code within the process context. Microsoft has released patches across all affected product lines; no public exploit identified at time of analysis, and no CISA KEV listing is present.
Privilege escalation in Microsoft .NET runtimes (8.0, 9.0, and 10.0) and Microsoft Visual Studio 2022 and 2026 results from a heap-based buffer overflow triggered by an integer overflow or wraparound condition in the runtime's memory handling. An unprivileged local user who interacts with a crafted input - such as a malicious file processed by a .NET application - can exploit the flaw to gain elevated privileges on the host system. No public exploit has been identified at time of analysis and this CVE is not listed in the CISA KEV catalog; however, a vendor-released patch is available from Microsoft.
Privilege escalation in Microsoft .NET Framework via incorrect authorization (CWE-863) allows network-authenticated low-privilege attackers to elevate their privileges, achieving full compromise of confidentiality, integrity, and availability on affected systems. Affected release families span .NET Framework 3.5 through 4.8.1, covering a broad swath of Windows enterprise deployments across multiple independently-installed runtime versions. No public exploit has been identified at time of analysis; a vendor-released patch with specific fix version thresholds is available through the Microsoft Security Response Center.
Heap-based buffer overflow (CWE-122) in Microsoft .NET enables local code execution across all actively supported .NET release streams (8.0, 9.0, 10.0) and associated Visual Studio tooling. The flaw requires user interaction - consistent with a file-processing or input-parsing trigger - but no elevated privileges, meaning an attacker can exploit it by inducing a user to open or process a maliciously crafted artifact within a vulnerable .NET context. Full confidentiality, integrity, and availability compromise of the affected process is possible on successful exploitation. No public exploit identified at time of analysis and no CISA KEV listing; Microsoft has released patches across all affected branches.
Local privilege escalation in Microsoft .NET runtimes (versions 8.0, 9.0, and 10.0) enables a local attacker to gain elevated system privileges by triggering an integer overflow condition, requiring only user interaction and no prior authentication. The flaw carries a CVSS 7.8 score with high impact across confidentiality, integrity, and availability. No public exploit or CISA KEV listing has been identified at time of analysis, but the broad deployment of .NET across enterprise Windows and Linux environments makes this a meaningful patching priority.
Code injection in the Perl DBI module as packaged for Red Hat Enterprise Linux allows a network-accessible, low-privileged attacker to execute arbitrary code, resulting in full confidentiality, integrity, and availability compromise. This CVE is a remediation of an incomplete fix for CVE-2026-14380, specifically targeting RHEL 9.8.z and 10.2.z patch levels where the prior partial fix left an exploitable residual path. No public exploit or CISA KEV listing is identified at time of analysis, but the CWE-94 classification and RCE tag indicate high potential impact if exploitation conditions are met.
Server-side authentication bypass in FreeRDP 3.x (confirmed through 3.27.1) allows an unauthenticated remote attacker to obtain a fully authenticated RDP session without supplying any credentials, GUID, or reconnect cookie when the server has RdstlsSecurity enabled. The flaw combines PDU-type confusion - the server routes inbound messages based solely on the client-supplied wire pduType without enforcing handshake state - with a calloc-zeroed result code that maps directly to RDSTLS_RESULT_SUCCESS, so sending a Capabilities PDU in place of the required Authentication Request PDU produces an unconditional authentication success response. No public exploit code or CISA KEV listing has been identified at time of analysis; the upstream fix commit is confirmed but a released patched version was not independently verified at advisory time.
Heap-based out-of-bounds read and write in FreeRDP before 3.30.0 can be triggered by a malicious peer during CredSSP/NLA Kerberos authentication, allowing information disclosure, heap memory corruption, or denial of service. The flaw exists in kerberos_DecryptMessage() where the peer-supplied 16-bit EC field of a GSS Wrap token is used directly in pointer arithmetic without bounds validation, enabling any RDP peer - rogue server or malicious client - to shift decrypt pointers up to 65535 bytes past the end of a ~60-byte token buffer. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Denial of service in ml-metadata (MLMD), a core metadata tracking component of Red Hat OpenShift AI (RHOAI), stems from an outdated statically-linked gRPC stack that retains known HTTP/2 resource exhaustion weaknesses. An in-cluster adversary with network reachability to the MLMD pod can crash it by sending specially crafted HTTP/2 requests, halting all ML pipeline runs within the affected namespace. No public exploit has been identified at time of analysis, and exploitation is constrained to actors already operating inside the Kubernetes cluster.
Privilege escalation in Red Hat OpenShift AI (RHOAI) training operator overlay allows any namespace editor to manage TrainJob resources beyond their intended authorization scope. The RHOAI overlay incorrectly injects trainjobs CRUD permissions into the native Kubernetes edit ClusterRole, violating the principle of least privilege. When chained with a companion flaw (TRN-01) that permits arbitrary pod configuration within TrainJobs, a remote attacker holding namespace editor credentials could escalate to arbitrary code execution - no public exploit is identified at time of analysis, and KEV listing has not been confirmed.
Privilege escalation in odh-dashboard (Red Hat OpenShift AI) allows an attacker who has obtained the dashboard's Service Account token to abuse overly broad SA permissions and elevate to cluster-administrator level. Exploitation grants full access to secrets, credentials, and keys across the entire OpenShift cluster, while also breaking multi-tenant isolation between workloads. No public exploit code has been identified at time of analysis, and this CVE is not in CISA KEV, but the CVSS score of 8.8 and cluster-wide blast radius make it a high-priority remediation target for RHOAI deployments.
Feast and feast-operator ship with a default 'no_auth' security configuration, leaving the feature-server, registry-server, and offline-server endpoints completely unauthenticated and accessible to any network-reachable attacker in Red Hat OpenShift AI (RHOAI) deployments. Exploitation enables three distinct high-impact outcomes: remote code execution via injection of a malicious User-Defined Function (UDF) onto the feature-server, denial of service by forcing full re-materialization of all tenant features, and unauthorized read access to cross-tenant feature data. No public exploit code has been identified at time of analysis and CISA KEV status is not confirmed, but the trivial exploitation conditions - no authentication, no interaction, default configuration - make this a realistic priority for any RHOAI operator.
The MaaS (Model-as-a-Service) Gateway component in Red Hat OpenShift AI (RHOAI) is improperly configured, enabling any low-privileged authenticated user within the platform to act as a man-in-the-middle against all model-serving traffic. Affected users can intercept, read, log, and modify requests and responses traversing the gateway, exposing highly sensitive artifacts including API access keys, user input prompts, and model outputs. No public exploit code has been identified at time of analysis, and the vulnerability has not been added to the CISA KEV catalog, but the CVSS 8.8 rating with high confidentiality, integrity, and availability impact reflects the severity of unrestricted traffic access within a shared AI serving environment.
Symlink escape in tar-rs versions 0.4.11 through 0.4.46 exposes arbitrary host filesystem files when a privileged process archives an attacker-controlled directory using the Builder::append_dir_all() function. The function resolves symbolic links during recursive directory traversal without verifying that resolved target paths remain within the specified source root, causing out-of-bounds files to be silently captured into the archive as regular file entries and disclosed to the attacker. A publicly available proof-of-concept exists; the CVE is not listed in CISA KEV, but low attack complexity combined with high confidentiality impact makes this a meaningful risk for affected Rust-based archiving pipelines.
Insufficient source identity validation in Red Hat Multicluster Global Hub's manager component allows a network-adjacent attacker who has compromised a managed hub to impersonate any other hub on the shared Kafka status bus. By presenting a legitimately obtained Kafka client certificate from the compromised hub while falsifying the CloudEvent source field, the attacker can overwrite or delete compliance records, inventory data, and cluster health telemetry belonging to sibling hubs in the shared database. No public exploit has been identified at time of analysis, but the scope-changed CVSS vector (S:C) reflects that the integrity impact extends beyond the initially compromised hub to the entire multi-hub management plane.
Arbitrary file read on the Jenkins controller affects Jenkins through LTS 2.555.3, where an authenticated attacker holding Item/Configure permission can exfiltrate any file readable by the Jenkins process user by uploading a crafted tar archive containing a symlink. This is an incomplete-fix bypass of CVE-2026-33001: the prior patch validated where a symlink is placed during extraction but not where it points, so a link staged inside the workspace can still resolve to paths outside it. There is no public exploit identified at time of analysis, and the flaw is not listed in CISA KEV, but it directly exposes secrets/master.key, credentials.xml, and other sensitive configuration.
Out-of-bounds read in Redis Cluster Bus PING message parsing affects Redis through version 8.8.1, enabling adjacent unauthenticated attackers to trigger denial of service or extract limited heap memory contents. The root cause is in the getPingExtLength() function, which fails to validate extension length fields against the actual remaining buffer size, allowing a crafted gossip-protocol PING packet to drive the parser past the allocated buffer boundary. No public exploit has been identified at time of analysis, and this vulnerability has not been confirmed in the CISA KEV catalog.
Heap-use-after-free in the Ruby json gem's native C extension (versions 2.20.0 through 2.21.1) allows an unauthenticated remote attacker to crash the Ruby process by supplying a crafted truncated JSON stream with duplicate object keys to any application using JSON::ResumableParser. The root cause is that the parser's input buffer is freed without resetting the state.start, state.cursor, and state.end pointers, which are subsequently dereferenced when partial_value processes the duplicate-key warning path via cursor_position, producing a heap-use-after-free confirmed by AddressSanitizer and a native SIGSEGV on official RubyGem releases. Impact is limited to availability - no code execution or information disclosure is claimed - and no public exploit code has been identified at time of analysis, though a private end-to-end TCP proof-of-concept was submitted with the advisory.
Sandbox escape in Google Chrome prior to 151.0.7922.109 enables a remote attacker who has already compromised the renderer process to break out of Chrome's OS-level security sandbox via a crafted HTML page. This is a second-stage, chained vulnerability - not directly exploitable in isolation - making it a high-value component in multi-step browser attacks that pair a renderer exploit with this UI input validation flaw to achieve full OS-level code execution. No public exploit has been identified and SSVC rates exploitation status as none at time of analysis, though the total technical impact and confirmed scope change (S:C) make this a critical priority when chained with any renderer compromise.
Use-after-free in Skia, Chrome's 2D graphics rendering engine, enables arbitrary code execution within the renderer sandbox in Google Chrome versions prior to 151.0.7922.109. Exploitation requires an attacker to have already achieved renderer process compromise, making this a second-stage chained payload rather than a standalone initial access vector - a prerequisite that materially constrains real-world exploit delivery. No public exploit code has been identified at time of analysis, and SSVC confirms Exploitation: none and Automatable: no, though C/I/A impacts are rated High within the sandboxed scope.
Sandbox escape in Google Chrome desktop versions prior to 151.0.7922.109 stems from a use-after-free in the Payments component, letting a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Rated High by Chromium and scored CVSS 9.6 due to a scope change, though exploitation requires user interaction (visiting a malicious page). There is no public exploit identified at time of analysis and no CISA KEV listing, but Chrome renderer/sandbox-escape bugs are historically high-value targets.
Remote code execution within the Chrome sandbox via an integer overflow in the V8 JavaScript engine affects Google Chrome prior to version 151.0.7922.109. An unauthenticated remote attacker can trigger the flaw by enticing a user to visit a specially crafted HTML page, resulting in full compromise of confidentiality, integrity, and availability within the renderer process. No public exploit code has been identified and CISA SSVC confirms exploitation status as none, though the total technical impact and low attack complexity elevate real-world priority for patching.
Out-of-bounds write in Skia enables sandbox escape in Google Chrome prior to 151.0.7922.109, allowing a remote attacker who has already compromised the renderer process to break out of Chrome's sandbox via a crafted HTML page. This is explicitly a second-stage chaining vulnerability - it does not independently achieve initial code execution but elevates a renderer-level compromise to full OS-level access. No public exploit code or active exploitation has been identified at time of analysis, though the scope-changing nature of this vulnerability makes it a high-value target for chained browser exploit chains.
Use-after-free in Chrome's Views component prior to version 151.0.7922.109 enables a sandbox escape for remote attackers who have already compromised the renderer process, via a crafted HTML page. The CVSS scope change (S:C) confirms the potential for OS-level code execution beyond Chrome's renderer sandbox, earning a Critical severity designation from the Chromium security team despite an NVD score of 8.3. No public exploit code or CISA KEV confirmation has been identified at time of analysis, though this vulnerability class is a high-value target frequently weaponized as the second stage of browser exploit chains by sophisticated threat actors.
Sandbox escape in Google Chrome's Media component on Windows (versions prior to 151.0.7922.109) lets a remote attacker break out of the renderer sandbox by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium and CVSS 9.6 because a successful escape yields full confidentiality, integrity, and availability impact beyond the sandboxed process. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though Chrome UAF media bugs are historically attractive targets.
Sandbox escape in Google Chrome for Android before 151.0.7922.109 stems from a use-after-free in the WebGL graphics component (CWE-416), letting a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Chromium rates this Critical and CVSS scores it 9.6 with a scope change (S:C), reflecting the cross-boundary sandbox escape. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but Chrome WebGL memory-corruption bugs are historically high-value exploitation targets.
Privilege escalation in Google Chrome's Contextual Tasks feature (prior to 151.0.7922.109) allows a remote attacker to escalate privileges by luring a victim to a crafted HTML page that delivers insufficiently validated untrusted input. The vulnerability carries a CVSS 8.8 score, reflecting high confidentiality, integrity, and availability impact with no prior authentication required from the attacker. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though the low attack complexity and Chrome's ubiquitous deployment surface make prompt patching a priority.
Remote code execution within the V8 JavaScript engine affects Google Chrome prior to 151.0.7922.109, allowing a remote attacker to execute arbitrary code inside the browser sandbox by luring a victim to a crafted HTML page. The flaw stems from an inappropriate implementation in V8 (CWE-693, Protection Mechanism Failure), carrying a CVSS 8.8 rating with high confidentiality, integrity, and availability impact. No public exploit code has been identified and CISA SSVC confirms no active exploitation at time of analysis, though the technical impact is rated total by SSVC, underscoring the severity if exploited.
Sandbox escape in Google Chrome's Web Authentication (WebAuthn) component before 151.0.7922.109 lets a remote attacker who lures a victim to a crafted HTML page corrupt memory via a use-after-free and potentially break out of the renderer sandbox. Rated High by Chromium and scored CVSS 9.6 (scope-changed), it affects the vast installed base of desktop Chrome; Google has shipped a fixed Stable-channel build. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Sandbox escape in Google Chrome's Codecs component (versions prior to 151.0.7922.109) allows a remote attacker to break out of the renderer sandbox when a victim views a crafted HTML page, via insufficient validation of untrusted input (CWE-20). Rated CVSS 9.6 with a changed scope, the flaw affects the desktop Stable channel across all platforms and is fixed in 151.0.7922.109. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Use-after-free exploitation in Google Chrome's Media component on Windows enables sandbox escape for attackers who have already compromised the renderer process. Chrome versions prior to 151.0.7922.109 on Windows are affected, with a crafted HTML page serving as the trigger mechanism to corrupt freed memory and break out of the renderer sandbox. SSVC rates current exploitation as none and non-automatable, though the total technical impact class reflects full OS-level compromise if the two-stage attack chain is completed successfully.
Remote code execution within the Chrome renderer sandbox is possible in Google Chrome versions prior to 151.0.7922.109 through an out-of-bounds write flaw in the V8 JavaScript engine, triggerable by a crafted HTML page. An unauthenticated remote attacker needs only to lure a victim to a malicious page, achieving code execution confined to the sandboxed renderer process. No public exploit or active exploitation has been identified at time of analysis; however, the CVSS 8.8 score and SSVC total technical impact classification indicate significant potential consequences if exploitation is developed.
Use-after-free in the Views UI rendering component of Google Chrome (all versions prior to 151.0.7922.109) enables a remote attacker to corrupt heap memory via a crafted HTML page, requiring the victim to perform specific UI gestures. The CVSS:3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects a fully network-delivered attack with no authentication barrier, though high attack complexity and mandatory user interaction substantially reduce opportunistic exploitation likelihood. No public exploit code or CISA KEV listing has been identified at time of analysis; Google rated this High severity internally and shipped a patch in the stable channel update.
Use-after-free in Google Chrome's Views UI framework on Windows, fixed in version 151.0.7922.109, exposes users to heap corruption with full confidentiality, integrity, and availability impact. Exploitation requires convincing a target to perform specific UI gestures while visiting a crafted HTML page, making this a social-engineering-dependent but high-consequence flaw. No public exploit code or CISA KEV listing has been identified at the time of analysis; however, the severity and platform breadth make patching urgent for Windows enterprise fleets.
Sandbox escape in Google Chrome for Android before 151.0.7922.109 stems from an out-of-bounds write in ANGLE, Chrome's OpenGL ES/GPU translation layer, allowing a remote attacker who lures a victim to a crafted HTML page to corrupt GPU-process memory and potentially break out of the renderer sandbox. Chromium rates the issue Critical and a vendor patch is available, but there is no public exploit identified at time of analysis and CISA SSVC records exploitation status as none. The high CVSS 9.6 reflects the scope-changing sandbox-escape potential rather than confirmed in-the-wild use.
Heap buffer overflow in Google Chrome's Base component (versions prior to 151.0.7922.109) enables potential heap corruption and arbitrary code execution when a user installs a malicious Chrome Extension crafted by an attacker. Exploitation requires social engineering to achieve extension installation, reflected in the AC:H/UI:R CVSS metrics, which meaningfully constrains real-world attack scale compared to the raw 7.5 score. No public exploit identified at time of analysis, and a vendor-released patch is available in 151.0.7922.109.
Use-after-free in the Payments component of Google Chrome prior to 151.0.7922.109 enables a sandbox escape when an attacker has already compromised the renderer process. Exploitation requires chaining a prior renderer compromise with delivery of a crafted HTML page, placing this firmly in the category of multi-stage browser exploitation. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and SSVC classifies exploitation status as none, though the technical impact is rated total due to the full sandbox escape capability.
Sandbox escape in Google Chrome on Android (prior to 151.0.7922.109) via a use-after-free vulnerability in the Skia graphics library allows a remote attacker who has already compromised the renderer process to break out of Chrome's sandbox through a crafted HTML page. The CVSS vector (S:C, C:H/I:H/A:H) confirms full cross-boundary compromise, elevating an attacker from renderer-level code execution to broader Android OS access. No active exploitation is confirmed at time of analysis (SSVC exploitation: none; not listed in CISA KEV), though Technical Impact is rated total by CISA's SSVC framework.
Site isolation bypass in Google Chrome Workers allows a remote attacker who has already compromised the renderer process to cross origin boundaries and access data from other sites via a crafted HTML page. All Chrome versions prior to 151.0.7922.109 are affected. EPSS sits at 0.26% (17th percentile) and SSVC confirms exploitation status as none, meaning no public exploit or active exploitation has been identified at time of analysis - the elevated CVSS of 8.1 reflects worst-case impact if this flaw is chained with a renderer exploit, rather than standalone exploitability.
Sandbox escape in Google Chrome prior to 151.0.7922.109 allows a remote attacker who has already compromised the renderer process to break out of Chrome's isolation boundary via a crafted HTML page exploiting insufficient Navigation policy enforcement (CWE-693). This is a second-stage exploit primitive: it elevates a sandboxed renderer breach into full host OS code execution at browser-process privilege, crossing Chrome's core security boundary as reflected in the CVSS Scope:Changed metric. No public exploit code or CISA KEV listing has been identified at time of analysis; the vendor-confirmed patch shipped in the 151.0.7922.109 stable channel update.
Remote code execution within the Chrome sandbox is possible in Google Chrome versions prior to 151.0.7922.109 due to a use-after-free vulnerability in the V8 JavaScript engine, triggerable by a remote attacker through a specially crafted HTML page. The attacker achieves arbitrary code execution confined to the Chrome renderer sandbox, requiring no privileges but necessitating user interaction to visit a malicious page. Google has released a fix in version 151.0.7922.109; SSVC assessment confirms no known active exploitation at time of analysis, and no public exploit code has been identified.
Remote code execution within Chrome's sandboxed renderer process is achievable in Google Chrome prior to 151.0.7922.109 through a crafted HTML page exploiting an inappropriate implementation in the V8 JavaScript engine. An unauthenticated remote attacker needs only to lure a victim to a malicious page - no credentials or special privileges are required on the attacker's side. Google has rated this High severity (Chromium classification); no public exploit has been identified at time of analysis, and CISA SSVC reports exploitation status as none, though technical impact is rated total within the sandbox boundary.
Sandbox escape in Google Chrome for Linux (versions before 151.0.7922.109) stems from a use-after-free in the Aura windowing subsystem, letting a remote attacker who lures a victim to a crafted HTML page corrupt memory and potentially break out of the renderer sandbox. Google rated the Chromium severity Critical (CVSS 9.6, scope-changed), but there is no public exploit identified at time of analysis and CISA's SSVC framework records exploitation status as 'none'. Because a full sandbox escape gives attacker code the privileges of the browser process on the host, this is a high-priority patch despite the absence of observed exploitation.
Out-of-bounds write in the GPU process of Google Chrome on Linux enables sandbox escape when an attacker has already compromised the renderer process. Specifically, an attacker controlling the renderer can deliver a crafted HTML page that triggers CWE-787 memory corruption in the GPU process, which operates with higher OS-level privileges than the sandboxed renderer, allowing full sandbox escape. Versions prior to 151.0.7922.109 on Linux are affected; no public exploit code and no CISA KEV listing have been identified at time of analysis, placing this in the category of no public exploit identified at time of analysis.
Sandbox escape in Google Chrome's Aura display layer on Linux allows a remote attacker with an already-compromised renderer process to break out of the Chrome sandbox via a crafted HTML page, achieving full system-level code execution. Affected versions are all Chrome builds prior to 151.0.7922.109 on Linux. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS scope-changed rating (S:C) and High across C/I/A reflect the severe post-exploitation impact of a successful sandbox escape in a privileged browser context.
Use-after-free in Google Chrome's Translate component (versions prior to 151.0.7922.109) enables remote attackers to execute arbitrary code within the browser's renderer sandbox by directing a user to a crafted HTML page. The CVSS 8.8 score reflects network-accessible, low-complexity exploitation gated only by a single user interaction - visiting an attacker-controlled page. No public exploit code or CISA KEV listing has been identified at time of analysis, though the RCE primitive within one of the world's most widely deployed browsers represents a materially significant attack surface.
Use-after-free in Google Chrome's HTML engine (all versions prior to 151.0.7922.109) exposes users to potential heap corruption and code execution when they visit a crafted HTML page. The CVSS 8.8 score reflects unauthenticated, network-reachable exploitation requiring only a single user interaction - consistent with Chromium's own 'High' severity classification. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor patch (151.0.7922.109) has been released and is the primary mitigation.
Sandbox escape in Google Chrome on Android prior to 151.0.7922.109 is achievable by a local attacker via a malicious file exploiting insufficient input validation in WebAPK processing. The CVSS scope change (S:C) with high confidentiality, integrity, and availability impacts reflects the potential for full breakout beyond Chrome's sandbox boundary into the broader Android process space. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor patch is available in the stable channel release.
Heap corruption via use-after-free in Google Chrome's Views UI framework (prior to 151.0.7922.109) can be triggered by a remote attacker who delivers a crafted HTML page and induces a user to perform specific UI gestures. Successful exploitation may lead to arbitrary code execution or denial of service within the browser process. No public exploit code or CISA KEV listing has been identified at time of analysis, and the CVSS AC:H rating signals non-trivial exploitation conditions that reduce real-world risk compared to the high severity label.
Use-after-free in Chrome's Resources component on Android enables sandbox escape for attackers who have already established a foothold in the renderer process. Affected versions are all Chrome for Android releases prior to 151.0.7922.109. The CVSS scope change (S:C) and High ratings across Confidentiality, Integrity, and Availability confirm that successful exploitation breaks out of the browser sandbox, exposing the underlying Android OS. No public exploit code or CISA KEV listing exists at time of analysis, though the chained exploit capability (renderer-to-sandbox-escape) represents a critical capability for advanced threat actors.
Sandbox escape via GPU use-after-free in Google Chrome prior to 151.0.7922.109 enables a remote attacker who has already compromised the renderer process to break out of the Chromium sandbox by delivering a crafted HTML page. The vulnerability resides in Chrome's GPU component and, if successfully chained after an initial renderer compromise, yields full confidentiality, integrity, and availability impact on the host system. No public exploit code has been identified at the time of analysis, and SSVC classifies exploitation status as none with automatable set to no, indicating no evidence of active or mass exploitation.
OS-level privilege escalation in Google Chrome's Windows CredentialProvider component allows a local attacker to gain elevated system privileges by winning a race condition triggered via a malicious file. Affected are all Chrome for Windows builds prior to 151.0.7922.109. No public exploit code has been identified and CISA has not added this to the Known Exploited Vulnerabilities catalog, but the SSVC assessment rates technical impact as total, meaning successful exploitation yields full system compromise.
Heap buffer overflow in the CrashReporting component of Google Chrome prior to 151.0.7922.109 enables sandbox escape when an attacker has already compromised the renderer process and can deliver a crafted HTML page. The CVSS scope change (S:C) and total technical impact rating confirm full host system compromise is achievable as the second stage of a chained exploit. No public exploit code or active exploitation has been identified at time of analysis, per SSVC exploitation status of 'none' and absence from CISA KEV.
Use-after-free in the WebGL subsystem of Google Chrome for Android (prior to 151.0.7922.109) enables sandbox escape for an attacker who has already achieved renderer-process compromise. By directing a victim to a crafted HTML page, an adversary with existing renderer access can exploit freed memory corruption in WebGL to break out of Chrome's sandbox and reach OS-level execution on the Android device. No public exploit code or active exploitation has been identified; SSVC rates exploitation as none and automatable as no, though technical impact is assessed as total given the full scope change.
Arbitrary file write via Zip-Slip in Nx's self-hosted HTTP remote cache extractor allows a malicious or MITM-positioned cache server to overwrite files anywhere on the developer's machine, escalating to remote code execution. Affected are Nx workspaces using self-hosted remote cache (NX_SELF_HOSTED_REMOTE_CACHE_SERVER, @nx/s3-cache, @nx/gcs-cache, @nx/azure-cache, @nx/shared-fs-cache) running nx >= 20.8.0 and < 22.7.7; Nx Cloud and the default local cache are confirmed unaffected. No public exploit code has been identified and this vulnerability is not listed in CISA KEV at time of analysis, but the CVSS 4.0 score of 8.7 and trivial exploitability once positioned reflect significant real-world risk for teams using self-hosted caching.
Denial of service (and possibly information disclosure) in the Apache Portable Runtime Utility (APR-util) library through version 1.6.3 lets remote attackers crash any consumer that parses attacker-supplied XML via apr_xml_quote_elem(). The flaw is an uncontrolled stack recursion (CWE-674) triggered by deeply nested or malicious XML; no authentication or user interaction is required. There is no public exploit identified at time of analysis and it is not in CISA KEV, but the CISA SSVC framework rates it automatable, so scanning-driven abuse is plausible.
SQL injection in the Apache Portable Runtime Utility (APR-util) affects the apr_dbd_oracle database provider in versions 1.6.0 through 1.6.3, letting remote attackers inject arbitrary SQL through an application that relies on this DBD backend for query construction or escaping. Rated CVSS 9.1 with high confidentiality and integrity impact but no availability impact, it allows unauthorized reading and modification of Oracle-backed data. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Heap-based buffer overflow in Apache Portable Runtime Utility's redis client component allows remote unauthenticated attackers to crash applications that use the library, resulting in a denial of service. Affected versions span APR-util 1.6.0 through 1.6.3; version 1.6.4 resolves the issue per Apache's advisory on the oss-security mailing list. No public exploit code and no CISA KEV listing have been identified at time of analysis, though SSVC classifies the flaw as automatable with partial technical impact, indicating it could be scripted for broad scanning.
Heap-based buffer overflow in Apache Portable Runtime Utility's memcached client component (versions 1.3.0 through 1.6.3) allows remote unauthenticated attackers to crash affected applications, causing denial of service. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms full availability impact with no confidentiality or integrity exposure. No public exploit identified at time of analysis, but SSVC marks this as automatable, meaning scripted mass scanning is feasible once attack primitives are established.
Double-spending of OAuth2 authorization codes in Apache CXF's JCacheCodeDataProvider enables issuance of multiple valid access tokens from a single code. Concurrent requests to the token endpoint during the brief window between code validation and invalidation exploit the TOCTOU race condition (CWE-367), allowing an attacker in possession of a valid authorization code to obtain additional access tokens beyond the one they are entitled to. No public exploit has been identified at time of analysis, and fixed versions are available across all maintained branches.
Authorization scope escalation in Apache CXF's OAuth2 Dynamic Client Registration endpoint allows any registering client to self-assign privileged scopes by supplying arbitrary `scope` values in the registration request, which the authorization server stores verbatim without validating against a server-defined allowlist. Affected versions span the 3.x, 4.1.x, and 4.2.x release lines; patched releases 3.6.12, 4.1.8, and 4.2.3 are available per the Apache advisory. No public exploit or active exploitation has been identified at time of analysis, but the straightforward exploitation path - crafting a single registration request - makes this a meaningful authorization bypass risk for any deployment exposing CXF's OAuth2 AS with Dynamic Client Registration enabled.
Apache CXF's JwtRequestCodeFilter blindly copies all claims from a validly-signed JWT request object into the OAuth2 authorization parameter map, including security-sensitive fields that must not be client-controlled: code_challenge, code_challenge_method, nonce, and state. Affected are all Apache CXF deployments using this filter for OAuth2/OIDC authorization code flows prior to versions 4.2.3, 4.1.8, and 3.6.12. An OAuth2 client with a known or compromised client_secret can craft a signed request JWT that overrides the PKCE parameters established in the outer HTTP request, effectively nullifying PKCE authorization code binding and OIDC replay protection. No public exploit code or CISA KEV listing has been identified at time of analysis.
Apache CXF's DefaultEncryptingCodeDataProvider allows captured OAuth 2.0 authorization codes to be redeemed an unlimited number of times, violating RFC 6749's single-use requirement. The removeCodeGrant() method that should invalidate a code after first exchange fails to do so, meaning any attacker who intercepts or obtains a legitimate authorization code can replay it repeatedly to obtain additional access tokens. No public exploit has been identified at time of analysis, and the issue is addressed in patched releases 4.2.3, 4.1.8, and 3.6.12.
Token revocation bypass in Apache CXF's DefaultEncryptingOAuthDataProvider allows revoked OAuth access and refresh tokens to remain functionally valid indefinitely - the provider continues to decrypt them successfully and TokenIntrospectionService returns active:true in direct violation of RFC 7009 and RFC 7662 mandates. All Apache CXF deployments using this built-in OAuth data provider and relying on token revocation as a security control are affected across the 3.6.x, 4.1.x, and 4.2.x branches. An attacker or suspended user who retains a revoked token can continue accessing protected resources as though revocation never occurred, bypassing intended authorization boundaries. No public exploit has been identified at time of analysis, though the attack requires no tooling beyond a standard HTTP client.
Authorization Code Substitution in Apache CXF's OpenID Connect Relying Party implementation allows remote attackers to hijack authenticated sessions when CXF is deployed in Hybrid Flow mode with a non-compliant or misconfigured Identity Provider that omits the c_hash parameter. Successful exploitation yields full authenticated access equivalent to account takeover, with high confidentiality and integrity impact. No public exploit has been identified at time of analysis, but SSVC classifies the attack as automatable with total technical impact once the prerequisite IdP condition is present.
Unsafe deserialization in Apache CXF's JMS transport allows any party able to publish to the service's JMS destination to achieve denial of service or, where a compatible deserialization gadget chain is present on the application classpath, remote code execution within the CXF process. All Apache CXF versions prior to 4.2.3, 4.1.8, and 3.6.12 are affected when the JMS transport is in use. No public exploit code or CISA KEV listing has been identified at time of analysis, though the vulnerability class (CWE-502 with unrestricted ObjectInputStream) is well-understood and tooling such as ysoserial makes it routinely exploitable wherever gadget libraries are present.
SSRF protection bypass in Gitea prior to 1.27.0 exposes internal services, cloud instance-metadata endpoints (e.g., AWS IMDSv1 at 169.254.169.254), and local files - including the application configuration containing database credentials and signing secrets - to authenticated attackers. Three HTTP fetch code paths in the migration and OAuth avatar subsystems use Go's raw http.Get() rather than the hardened hostmatcher.NewDialContext() transport used elsewhere, completely circumventing Gitea's built-in SSRF defenses. A publicly available proof-of-concept is included in the GHSA advisory; no confirmed active exploitation (CISA KEV) has been identified at time of analysis.
Unsafe class loading in the ORB (Object Request Broker) component of IBM WebSphere Application Server 8.5, 9.0, and Liberty Continuous Delivery allows a malicious or attacker-controlled IIOP server to force a WebSphere client/server to load and instantiate arbitrary Java classes over the network. Exploitation requires no authentication or user interaction (CVSS 9.8), and successful abuse can lead to loss of confidentiality, integrity, and availability, potentially culminating in remote code execution via dangerous class instantiation. There is no public exploit identified at time of analysis, and EPSS estimates only a 0.44% probability of exploitation in the next 30 days.
Memory exhaustion denial-of-service in OpenSSL 3.6.0-3.6.3 and 4.0.0-4.0.1 allows a malicious TLS server to leak attacker-tunable amounts of heap memory per handshake in connecting client applications that have explicitly enabled OCSP staple verification. By delivering a syntactically valid BasicOCSPResponse containing an empty SingleResponse sequence - optionally padded with bogus certificates to amplify each allocation - the server causes the internal OCSP_BASICRESP structure to be allocated but never freed, bypassing the cleanup path. No public exploit has been identified at time of analysis and no CISA KEV listing exists; risk is bounded by the non-default OCSP flag requirement.
Authentication bypass in Red Hat Build of Keycloak (and Red Hat Single Sign-On 7) lets an unauthenticated attacker forge SAML responses to hijack accounts when a SAML identity-provider's metadata was imported without explicit key-usage attributes, causing the keycloak-services identity-brokering engine to silently disable signature validation despite a signing certificate being present. Rated CVSS 9.1 with total technical impact per CISA SSVC, an attacker who knows a victim's external identifier can log in as that user. No public exploit identified at time of analysis, and EPSS is low (0.14%, 4th percentile), indicating the risk is currently theoretical/targeted rather than mass-exploited.
Privilege escalation to cluster-admin in Red Hat Advanced Cluster Management for Kubernetes (ACM) lets a user holding only namespace-scoped 'edit' rights on an ACM hub namespace take over the entire cluster. By creating a Channel pointing to an attacker-controlled Helm repository and a Subscription referencing it, the app-subscription controller (multicluster-operators-subscription) applies the chart with its own elevated authority and without enforcing the subscription-admin role or namespace confinement, letting the chart install cluster-scoped objects such as a ClusterRoleBinding to cluster-admin. No public exploit identified at time of analysis, and EPSS is low (0.25%), but the technical impact is total and the flaw directly contradicts ACM's documented namespace-confinement guarantee.
MLflow's AI Gateway proxy exposes internal network services - including cloud-instance metadata endpoints - to any authenticated user, including read-only accounts, via an unvalidated api_base field in the CreateGatewaySecret endpoint. All MLflow releases through 3.14.0 are affected; the attack requires only basic credentials and no special configuration, making IAM credential theft a realistic outcome for cloud-hosted deployments. No public exploit has been identified at time of analysis, but the two-step attack (create secret, invoke proxy) involves only standard HTTP requests and no technical barrier beyond holding a valid account.
Denial of service in Apache Qpid Proton-J through 0.34.1 allows unauthenticated remote attackers to crash the service by sending AMQP messages with deeply nested type structures that exhaust the JVM call stack via a StackOverflowError. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivial, unauthenticated network exploitation with no user interaction required, targeting availability exclusively. No active exploitation has been confirmed - this vulnerability is absent from CISA KEV and carries a low EPSS score of 0.21% (11th percentile) - but the zero-prerequisite attack path warrants prompt patching for any internet-facing AMQP deployment.
Incorrect buffer size calculation (CWE-131) in an unidentified Linux distribution package tracked by both Ubuntu and Red Hat enables local, user-interaction-triggered exploitation with high confidentiality, integrity, and availability impact, yielding a CVSS base score of 7.8. The local attack vector combined with a user-interaction requirement (AV:L/UI:R/PR:N) is consistent with a malicious file parsing scenario, where a user opens a crafted input triggering the buffer miscalculation. No public exploit has been identified at time of analysis, and no KEV listing is present; however, the full C:H/I:H/A:H impact triad indicates potential for memory corruption leading to arbitrary code execution.
Uncontrolled resource consumption in Apache Qpid ProtonJ2 through version 1.1.0 allows authenticated AMQP clients to cause denial of service by sending deliveries composed of an unbounded number of transfer frames. Because the library imposed no upper limit on how many AMQP transfer frames could constitute a single incoming delivery, a malicious but authenticated client can force unbounded heap accumulation, leading to excessive memory usage and potential JVM failure. No public exploit code and no active exploitation have been identified at time of analysis; vendor-released patch version 1.2.0 is available.
Denial of service in Apache Qpid ProtonJ2 through version 1.1.0 allows a remote unauthenticated attacker to crash the messaging service by sending AMQP messages with maliciously crafted type nesting that triggers an uncontrolled recursive call stack, resulting in a StackOverflowError. The flaw (CWE-674) is exploitable without authentication over the network with low attack complexity, making it trivially reachable against any exposed ProtonJ2 endpoint. No active exploitation has been confirmed (not in CISA KEV) and EPSS sits at 0.21% (11th percentile), suggesting minimal observed exploitation activity at time of analysis despite the ease of triggering the condition.
Remote unauthenticated denial of service in Apache Qpid ProtonJ2 through version 1.1.0 allows a network attacker to exhaust server memory by sending AMQP messages with maliciously crafted type size or count fields, triggering uncontrolled allocation. The vulnerability (CWE-789) requires no authentication or user interaction and is exploitable directly over the network with low complexity, making it trivially reachable in any exposed deployment. No active exploitation has been confirmed in CISA KEV, and the EPSS score of 0.21% (11th percentile) suggests limited real-world exploitation interest at time of analysis; a vendor-released fix is available in version 1.2.0.
Denial of service in Apache Qpid ProtonJ2 through 1.1.0 allows unauthenticated remote attackers to exhaust server resources by exploiting unbounded caching of AMQP symbol values during pre-authentication message processing. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms no credentials or user interaction are required, and the attack can be executed at low complexity from any network-accessible position. No public exploit or CISA KEV listing exists at time of analysis, though the trivial exploitation conditions make this a realistic threat against any Qpid ProtonJ2 endpoint exposed to untrusted networks.