Suse
Monthly
Remote code execution in Google Chrome on Windows (versions prior to 153.0.8010.36) arises from a heap buffer overflow in ANGLE, Chrome's graphics abstraction layer. A remote attacker who lures a victim to a crafted HTML page can corrupt heap memory and execute arbitrary code outside the renderer sandbox, gaining full compromise of the host. No public exploit is identified at time of analysis and EPSS is low (0.33%), but the sandbox-escape scope and Chrome's near-universal footprint make prompt patching essential.
Out-of-bounds read in the WebGL component of Google Chrome before 153.0.8010.36 lets a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the browser sandbox. Chromium rates the security severity as High, and a vendor patch is available; no public exploit has been identified and CISA SSVC records exploitation as none, with EPSS at a low 0.28% (20th percentile).
Use-after-free in Chrome's Views UI framework enables local attackers to escape the browser sandbox and execute arbitrary code at browser-process privilege level. The vulnerability affects all Google Chrome desktop versions prior to 153.0.8010.36. No public exploit code or active exploitation has been identified; EPSS at 0.17% (7th percentile) reflects low near-term exploitation probability.
Sandbox-escape remote code execution in Google Chrome on Android (versions prior to 153.0.8010.36) stems from a use-after-free in Dawn, Chromium's WebGPU implementation. A remote attacker who lures a victim to a crafted HTML page can trigger the freed-object reuse to execute arbitrary code outside the renderer sandbox. Chromium rates this 'High'; there is no public exploit or CISA KEV listing, and EPSS is low (0.30%), indicating no evidence of active or widespread exploitation at time of analysis.
Sandbox-escape remote code execution in Google Chrome (Chromium-based desktop) before 153.0.8010.36 stems from an incorrect authorization flaw in the DevTools component. A remote attacker who lures a victim to a crafted HTML page can potentially execute arbitrary code outside the renderer sandbox, achieving full compromise of the browser process. No public exploit identified at time of analysis; EPSS is low (0.21%, 11th percentile) and the issue is not in CISA KEV, but Google rates the Chromium security severity as High.
Sandbox-escape code execution via a race condition in the Google Chrome Updater component on Windows allows a local attacker to execute arbitrary code outside the Chrome sandbox. Affected builds are all Chrome versions prior to 153.0.8010.36 on Windows. The Chrome Updater's elevated-privilege execution context makes winning the race condition particularly impactful, as successful exploitation bypasses sandbox containment entirely.
Sandbox escape in Google Chrome's Chromoting (Chrome Remote Desktop) component on Windows allows a local unprivileged attacker to execute arbitrary code outside the Chrome renderer sandbox by exploiting a race condition. All Chrome for Windows releases prior to 153.0.8010.36 are affected. No public exploit has been identified at time of analysis; EPSS places exploitation probability at the 3rd percentile, though SSVC rates technical impact as 'total,' reflecting full system compromise potential if the race condition is successfully won.
Missing authorization in the Views UI framework of Google Chrome prior to 153.0.8010.36 allows remote attackers to bypass system access restrictions via a crafted HTML page requiring social engineering. The vulnerability (CWE-862) resides in Chrome's cross-platform UI layer rather than web content rendering, with full confidentiality, integrity, and availability impact per CVSS C:H/I:H/A:H. No public exploit code or active exploitation has been identified at time of analysis; EPSS of 0.18% (7th percentile) corroborates low current weaponization despite the 8.8 CVSS score.
Use-after-free in Google Chrome's Core component on Windows prior to 153.0.8010.36 enables a renderer-compromised attacker to escape the browser sandbox and execute arbitrary code on the host OS. The vulnerability is platform-specific to Windows and functions as the second stage of a chained exploit: an attacker must first achieve renderer-level compromise before triggering this UAF to pivot into the privileged browser process. No public exploit code or active exploitation has been identified at time of analysis; vendor patch 153.0.8010.36 is available.
Use-after-free in Chrome's Receiver component allows an adjacent, unauthenticated attacker to execute arbitrary code outside the renderer sandbox via crafted network traffic, affecting all Chrome versions prior to 153.0.8010.36. The scope change in the CVSS vector confirms this is a full sandbox escape - successful exploitation yields OS-level code execution on the victim machine without requiring any user interaction. No public exploit has been identified at time of analysis, and EPSS at 0.13% (3rd percentile) indicates low observed exploitation activity.
Sandbox-escape remote code execution in Google Chrome's Views UI framework prior to 153.0.8010.36 allows a local attacker to execute arbitrary code outside the browser sandbox by inducing a specific UI interaction that triggers a use-after-free condition. The CVSS scope change (S:C) confirms the vulnerability crosses the renderer sandbox boundary into the broader OS context, with full confidentiality, integrity, and availability impact. No public exploit or CISA KEV listing has been identified at time of analysis; EPSS of 0.20% (10th percentile) reflects low automated exploitation probability, though sandbox escapes are high-value for privilege escalation chains.
Out-of-bounds read in Google Chrome's Media component (versions prior to 153.0.8010.36) enables remote code execution confined within the browser sandbox when a user visits a specially crafted HTML page. The vulnerability stems from improper bounds checking during media processing, allowing a remote attacker to read memory beyond intended buffer limits and leverage the resulting data to achieve arbitrary code execution. No public exploit has been identified at time of analysis and EPSS is low (0.35%), but the attack surface is broad given Chrome's ubiquity.
Memory corruption in the Codecs component of Google Chrome prior to 153.0.8010.36 enables remote unauthenticated attackers to execute arbitrary code inside the browser sandbox by delivering a crafted HTML page containing malformed media content. The flaw is classified CWE-119 (improper bounds restriction), rated 'High' by Chromium Security, and carries a CVSS 8.8 base score with a network attack vector requiring only passive user interaction. No public exploit code or CISA KEV listing has been identified at time of analysis, and EPSS stands at a low 0.35% (29th percentile), indicating theoretical rather than observed exploitation.
Double-free memory corruption in PDFium (Chrome's PDF rendering engine) on Windows allows remote code execution within the Chrome renderer sandbox when a user opens a crafted PDF file. Affected versions are all Chrome releases on Windows prior to 153.0.8010.36, where CWE-415 double-free in the PDFium component enables an attacker-controlled allocation state. No public exploit or CISA KEV listing is confirmed at time of analysis, and EPSS remains low at 0.20% (10th percentile), suggesting exploitation is not yet widespread despite the network-reachable vector.
Remote code execution in Google Chrome on Windows (versions prior to 153.0.8010.36) arises from a use-after-free in ANGLE, Chrome's graphics abstraction layer that translates OpenGL ES calls to Direct3D. A remote attacker who lures a victim to a crafted HTML page can corrupt memory and execute arbitrary code outside the browser sandbox, giving full compromise of the renderer host process. No public exploit identified at time of analysis, and EPSS is modest (0.35%), but the sandbox-escape impact and one-click delivery make this a high-priority browser patch.
Use-after-free in Chrome's Cast (Chromecast streaming) component allows an adjacent unauthenticated attacker to potentially escape the browser sandbox and execute arbitrary code by delivering crafted network traffic over a local or Wi-Fi network. All Chrome desktop versions prior to 153.0.8010.36 are affected, with Chromium rating this Critical due to the full-CIA, scope-changed impact. No public exploit has been identified at time of analysis, and the EPSS score of 0.17% (6th percentile) indicates minimal observed exploitation activity despite the high severity classification.
Remote code execution in Google Chrome prior to 153.0.8010.36 allows a remote attacker to escape the renderer sandbox and run arbitrary code on the host by luring a victim to a crafted HTML page that triggers a heap buffer overflow in the WebGL implementation. Chromium rates this Critical and the CVSS 9.6 score reflects a scope-changing sandbox escape; no public exploit is identified at time of analysis, and EPSS is low at 0.29% (21st percentile). Patched in the September 2026 stable-channel desktop release.
Remote code execution in Google Chrome for Android prior to 153.0.8010.36 arises from an out-of-bounds write in the WebGL graphics subsystem, letting a remote attacker who lures a user to a crafted HTML page execute arbitrary code outside the renderer sandbox. Rated Critical by Chromium and CVSS 9.6, the scope-changed vector reflects a full sandbox escape. No public exploit is identified at time of analysis and EPSS is low (0.39%), but WebGL memory-corruption bugs are historically high-value targets.
Remote code execution in Google Chrome for Android prior to 153.0.8010.36 stems from a use-after-free in the WebGL implementation that a remote attacker can trigger with a crafted HTML page to execute arbitrary code outside the browser sandbox. Chromium rates this Critical and the CVSS is 9.6, reflecting a full renderer-to-sandbox-escape chain requiring only that a victim visit a malicious page. No public exploit is identified at time of analysis and EPSS is low (0.36%), but the sandbox-escape impact makes it a priority patch.
Remote code execution in Google Chrome desktop prior to 153.0.8010.36 arises from a use-after-free in the WebGL implementation, allowing a remote attacker to run arbitrary code outside the browser sandbox by luring a victim to a crafted HTML page. Google rates the Chromium severity as Critical and the CVSS is 9.6, reflecting a full renderer-to-host sandbox escape. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; EPSS is low at 0.28% (20th percentile).
Integer overflow in FreeType's COLR color-layer blending function (tt_face_colr_blend_layer in ttcolr.c) enables local privilege escalation across Android 14 through 17. A low-privileged app can deliver a maliciously crafted TrueType font containing a corrupted COLR table, triggering arithmetic overflow that corrupts heap memory and enables code execution in a higher-privileged system context. No active exploitation has been identified (EPSS 0.15%, SSVC Exploitation: none), and no user interaction beyond app execution is required.
Out-of-bounds memory corruption in Tapdisk, the XAPI toolstack's userspace xen-blkback implementation, allows a malicious guest VM to achieve code execution inside the tapdisk process, which normally runs as root in dom0. CVE-2026-79606 specifically concerns the gcopy_segs[] array: the bounds check incorrectly permits nr_segments values between 12 and 32, causing out-of-bounds writes that corrupt adjacent process memory. All versions of tapdisk are confirmed vulnerable, no mitigations exist, and patches are available via XSA-513.
Out-of-bounds memory corruption in Xen's Tapdisk (userspace xen-blkback) enables a malicious guest VM to achieve code execution within the tapdisk process, which runs as root in Dom0, constituting a full guest-to-host escape. CVE-2026-79605 specifically covers the absent upper bounds check on blkif->last_sect: guest-supplied values greater than 7 trigger reads or writes beyond the mapped grant region. All versions of tapdisk are confirmed vulnerable per XSA-513, no mitigations exist, and patch application is the sole remediation path. No public exploit or CISA KEV listing is identified at time of analysis.
Unbounded memory exhaustion in Xen's OCaml xenstore daemon (oxenstored) allows a malicious or compromised guest VM to trigger a system-wide denial of service by repeatedly sending xenbus reconnect requests without clearing the global watch trie. Each reconnect cycle purges only the per-domain hashtable, leaving stale watch entries to accumulate indefinitely in the global trie. All Xen deployments from 4.6 onwards using the OCaml oxenstored implementation are affected; no public exploit has been identified, but the attack surface is accessible to any guest with standard xenbus connectivity and no mitigations exist.
HTTP/2 thread-exhaustion denial-of-service in Eclipse Jetty allows unauthenticated remote clients to permanently block all server threads by exploiting a race condition in RST_STREAM and GOAWAY frame handling. The race incorrectly resets the `HTTP2Flusher.terminated` field from a non-null terminal state back to null, allowing new write-queue entries to be enqueued in a flusher that will never drain them; the write-blocked threads waiting on those entries hang indefinitely. Across five affected Jetty major branches (9.4, 10.0, 11.0, 12.0, 12.1), any internet-exposed HTTP/2 endpoint is reachable without authentication. No public exploit has been identified at time of analysis.
Guest-to-hypervisor privilege escalation in Xen allows a VM guest with a PCI device assigned - where the device exposes at least one Base Address Register (BAR) mapped to IO port space - to trigger a BUG() assertion in the Xen hypervisor, crashing or potentially compromising the host. The CVSS scope-changed vector (S:C, C:H/I:H/A:H) reflects cross-boundary impact: the attack originates inside a guest VM but affects the host hypervisor. Tracked as XSA-510, no public exploit is identified at time of analysis, and EPSS sits at 0.17% (7th percentile), consistent with a targeted-environment issue rather than mass exploitation.
HTTP/1.1 request smuggling in Eclipse Jetty allows unauthenticated remote attackers to desynchronize request boundary parsing between Jetty and an upstream proxy, enabling manipulation of other users' HTTP sessions. The root cause is Jetty's acceptance of a bare LF character (\n) as a line terminator during chunked transfer encoding parsing - specifically in chunk extensions, chunk data termination, or trailer termination - where RFC 7230 mandates CRLF (\r\n). Depending on the Jetty version and configured HTTP compliance mode, a crafted request can cause the proxy and Jetty to disagree on where one request ends and the next begins, enabling request injection against co-located tenants. No public exploit has been identified at time of analysis.
Stack exhaustion via uncontrolled recursion in Qt's QDomDocument XML serialization allows a remote attacker to crash any Qt application that processes untrusted XML input, resulting in a denial-of-service condition. Affected applications using the QtXml module parse attacker-supplied deeply nested XML documents, triggering recursive descent without a depth guard until the call stack is exhausted. No code execution is possible; impact is limited to application availability. No public exploit or CISA KEV listing has been identified at time of analysis.
Authenticated OS command injection in Dogtag PKI's certificate profile import mechanism allows a CA Administrator to achieve code execution as the pkiuser account on RHEL 6-10 and Red Hat Certificate System 9. By uploading a crafted certificate profile that exploits the ExternalProcessConstraint mechanism with attacker-controlled environment variables, a privileged attacker can bypass the limited profile ID validation and execute arbitrary system commands. No public exploit or active exploitation is known at time of analysis, but the CVSS 7.2 / PR:H rating reflects that CA Administrator access is a prerequisite.
Use-after-free in strongSwan's IKEv2 Multi-Key Exchange (Multi-KE, RFC 9370) implementation is triggered when two authenticated IKE peers simultaneously initiate a rekey operation, causing a race condition that corrupts heap memory and can result in remote code execution within the IKE daemon. The attack requires an established IKE session and high-complexity timing to induce the collision, reflected in the CVSS AC:H/PR:L vector. Fixed in strongSwan 6.1.0, released September 7, 2026, alongside six other CVEs disclosed in the same advisory batch. No public exploit identified at time of analysis.
Denial of service via infinite loop in strongSwan's x509 plugin affects all deployments that process X.509 attribute certificates. An unauthenticated remote attacker can craft a malformed attribute certificate that triggers CWE-835 (infinite loop) during parsing, causing the IKE daemon to hang indefinitely and disrupting all VPN connectivity. The vendor fixed this in strongSwan 6.1.0 alongside six other vulnerabilities disclosed on 2026-09-07; no public exploit has been identified at time of analysis.
Denial of service via NULL-pointer dereference in strongSwan's x509 plugin affects versions 4.2.0 through 6.0.x, triggered during verification of X.509 attribute certificates. An unauthenticated remote attacker can crash the charon IKE daemon by presenting a crafted attribute certificate during VPN handshake negotiation, taking the gateway offline. Vendor-released fix is strongSwan 6.1.0, published September 7, 2026, as part of a coordinated batch of six CVE patches; no public exploit has been identified at time of analysis.
Tunneled EAP authentication in strongSwan before 6.1.0 can be bypassed when the IKEv2 responder fails to properly enforce inner EAP method authentication details, enabling a network attacker with a low-privilege outer-tunnel identity to obtain an authorized VPN session without completing the inner credential exchange. The flaw (CWE-863, Incorrect Authorization) is limited to deployments using tunneled EAP methods such as EAP-TTLS or EAP-PEAP; certificate-only or non-tunneled EAP configurations are not affected. Vendor-released patch strongSwan 6.1.0 is available; no public exploit identified at time of analysis.
strongSwan 5.9.7 through versions prior to 6.1.0 lets unauthenticated network attackers drive an IKEv2 responder running charon/libcharon into creating a Child Security Association before the IKE authentication exchange has completed, giving low-level impacts to confidentiality, integrity and availability (CVSS 3.1 base 7.3, AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L). Reachability over UDP 500/4500 is what drives the score rather than severe impact, and there is a public advisory but no public exploit identified at time of analysis; EPSS is 0.34% (27th percentile), indicating low near-term exploitation likelihood. The vendor-released patch is strongSwan 6.1.0, published alongside a September 2026 batch of unrelated strongSwan fixes (CVE-2026-78123, -78124, -78126, -78127, -78129 through -78131).
Relative path traversal in Apache Ant's built-in `ftp` and `scp` tasks (versions 1.2 through 1.10.17) permits a malicious or MITM-intercepted remote server to supply server-controlled paths that escape the configured download directory, overwriting arbitrary files with the filesystem permissions of the Ant process. For FTP tasks not using FTPS, no server identity check is enforced, making a network MITM attacker sufficient to trigger the write primitive without needing a valid certificate. The vulnerability is fixed in Ant 1.10.18, which validates destination paths by default; no public exploit code has been identified and EPSS is low at 0.19%.
Authentication bypass via response replay affects the DIGEST-MD5 server implementation in the Perl Authen::SASL distribution (Authen::SASL::Perl::DIGEST_MD5) before version 2.2100. The server generates a fresh nonce in its challenge but never compares it against the nonce returned by the client, so an attacker who passively captures one successful qop=auth exchange can replay that exact response against a later session for the same service, host, realm and user and authenticate as that user without knowing the password. An upstream fix is available (2.2100, commit 9433736); no public exploit identified at time of analysis, and EPSS is low at 0.22%.
Path traversal in h3's serveStatic() function on Node.js allows unauthenticated remote attackers to read arbitrary files outside the configured static root directory. The root cause is that h3 uses srvx's FastURL class, which skips WHATWG URL normalization for performance - percent-encoded dot segments (%2e%2e) survive raw into decodeURI(), are decoded to ../, and are passed unsanitized to filesystem callbacks. A detailed proof-of-concept exploit chain is publicly documented in GHSA-wr4h-v87w-p3r7; no active exploitation confirmed in CISA KEV at time of analysis. Fixed in versions 1.15.6 and 2.0.1-rc.15.
Path traversal in h3's serveStatic utility (versions before 1.15.9) enables unauthenticated remote attackers to read arbitrary files from URL-based storage backends (S3, CDN, object storage) by exploiting a double-decoding flaw that bypasses dot-segment normalization. A request crafted with double-encoded dot sequences (%252e%252e) survives the resolveDotSegments() guard - which only matches literal '.' characters - and is then interpreted as '..' by RFC 3986-compliant URL backends. No public exploit code or active exploitation has been confirmed, though the GHSA advisory provides source-level analysis sufficient to guide exploit development.
Unvalidated BPF scratch-register array index in libpcap's user-space BPF interpreter allows a local attacker with low privileges to craft a filter program that reads or writes OS process memory beyond the intended 16-entry M[] scratch array. On 64-bit architectures the accessible range is up to 16GiB starting at the current stack frame; on 32-bit architectures the entire process address space is reachable. The Tcpdump Group has issued a fix (commit 48e8960a) that adds bounds checks before every M[] access, rejecting filters referencing register index ≥ BPF_MEMWORDS (16). No public exploit or CISA KEV listing is identified at time of analysis.
Out-of-bounds heap write in PCRE2 before 10.48 allows memory corruption via the DFA matching engine when a cached workspace block is reused in a recursive context without the size check that guards a freshly allocated block of the same type. Applications that pass attacker-controlled regular expressions to pcre2_dfa_match, or that configure a small heap limit via the PCRE2 API while processing recursive patterns, are exploitable. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog; however, PCRE2 10.48 ships a confirmed vendor fix alongside four other security patches in the same release.
Infinite-loop denial-of-service in smol-toml (npm, squirrelchat) before version 1.7.1 allows remote unauthenticated attackers to permanently hang any Node.js service that parses attacker-controlled TOML. The trigger is a crafted value inside a TOML array or inline table followed by a comment character with no trailing newline - when this input reaches the parser, skipUntil() in src/util.ts receives -1 from indexOfNewline() and resets the cursor to position zero instead of terminating, spinning indefinitely and consuming all processing capacity. No public exploit has been identified at time of analysis, but the CVSS 4.0 score of 8.2 and the trivially constructible trigger make this straightforward to weaponize against any exposed TOML-parsing endpoint.
Arbitrary command execution in goose v1.37.0 allows an attacker to embed shell commands inside recipe stdio extension definitions and retry.check fields that are silently executed under the victim user's OS privileges. The built-in recipe security scanner does not inspect these fields, providing a false safety guarantee and a clear bypass path. No public exploit is identified at time of analysis, but exploitation is low-complexity once a target user loads a malicious recipe.
Improper OCSP response validation across the Snowflake Python, Go, JDBC, and Node.js drivers allowed a revoked TLS certificate to be treated as valid, enabling a man-in-the-middle attacker to intercept and tamper with driver-to-Snowflake TLS sessions. The root flaw is twofold: OCSP stapled or fetched responses were not reliably bound to the specific certificate under validation, and definitive OCSP verification failures were treated as transient errors (soft-fail), causing the driver to proceed with a connection rather than abort it. Exploitation requires a network-adjacent or on-path position combined with possession of a revoked certificate and its corresponding private key for a Snowflake or storage-stage hostname; no public exploit is identified at time of analysis and EPSS data was not provided, but the CVSS AC:H reflects these steep prerequisites.
Done. The analysis is above as the JSON object. Key points of the synthesis: - **Same FreeIPMI 1.6.19 cluster** as CVEs 85504/85507/85508 already tracked — all client-side stack overflows (CWE-121) triggered by a malicious/compromised BMC returning oversized responses. - **CVSS 9.8 is overstated**: this is a client-side/rogue-BMC flaw, not an internet-facing service. I assessed it down to `AC:H/UI:R` (needs attacker control of a BMC plus an operator/job initiating the FRU read). - **Metadata is clean** — vendor tag, CPE, and CWE all correct, and no embedded injection note this time — so `data_quality_flags` is `[]`. - Fix confirmed as 1.6.19; no EPSS/KEV/POC signal, so exploitation status is unknown. Memory updated with the new CVE note and index entry.
Stack-based buffer overflow in GNU FreeIPMI's ipmi-oem tool (before 1.6.19) affects the _output_dell_system_info_cmc_ipv6_info routine reached through the 'dell get-system-info cmc-ipv6-info' subcommand. Because the flaw lies in code that parses the response returned by a Dell CMC/BMC, an attacker who controls (or can MITM) the IPMI device an operator queries can corrupt the client's stack and potentially execute code on the management host. This is one of several FreeIPMI OEM-parser overflows fixed together in 1.6.19 (disclosed on oss-security 2026-08-28); no public exploit identified at time of analysis.
Stack-based buffer overflow in FreeIPMI's ipmi-oem utility (versions before 1.6.19) lets a malicious or compromised Dell iDRAC BMC corrupt the memory of the client host running the 'dell get-system-info idrac-info' subcommand, potentially achieving code execution in the context of the operator (often root). The flaw sits in _get_dell_system_info_idrac_info in ipmi-oem/ipmi-oem-dell.c, which copies attacker-influenced OEM response data into a fixed-size stack buffer without bounds checking. No public exploit identified at time of analysis; disclosed via oss-security and fixed in FreeIPMI 1.6.19.
Stack-based buffer over-read in FreeIPMI's ipmi-oem Fujitsu OEM module crashes the client process when a Fujitsu BMC returns a shorter-than-expected response to a System Event Log query. All FreeIPMI versions before 1.6.19 are affected; this is a distinct vulnerability from CVE-2026-50031, which covers different version ranges. No public exploit code or active exploitation has been identified at time of analysis.
Stack-based buffer overflow in GNU FreeIPMI before 1.6.19 lets a malicious or compromised Fujitsu iRMC BMC corrupt client memory when the FreeIPMI tooling parses malformed Fujitsu SEL 'long text' responses in _ipmi_sel_oem_fujitsu_get_sel_entry_long_text. Successful exploitation can crash the client or execute arbitrary code in the context of the process reading the System Event Log (typically ipmi-sel or libfreeipmi consumers). No public exploit is identified at time of analysis, and the flaw is fixed in FreeIPMI 1.6.19.
Prototype pollution in toml-node (npm package `toml` by BinaryMuse) prior to 4.1.2 allows unauthenticated remote attackers to write arbitrary keys onto Object.prototype by supplying a crafted TOML document to `toml.parse()`. The vulnerability exploits a path desynchronization bug in the compiler's duplicate-key guard - comma-joined tracking paths diverge from dot-joined traversal paths, allowing `__proto__` traversal through scalar values into the real JavaScript prototype chain. Injected properties propagate process-wide in Node.js and can enable denial of service, authorization bypass, or code execution via application gadget chains; the GHSA advisory includes working proof-of-concept code, and a fix is available in version 4.1.2.
Sandbox-escape remote code execution affects Google Chrome on iOS prior to 152.0.7977.82, where improper input validation (CWE-20) in the browser's Transactions Platform component lets a remote attacker potentially run arbitrary code outside the renderer sandbox when a victim loads a crafted HTML page. Google shipped a fix in the stable channel and Chromium rated the underlying issue Medium severity, though the supplied CVSS vector scores it 9.6. There is no public exploit identified and CISA's SSVC framework records exploitation status as none.
Type confusion (CWE-843) in the Compositing subsystem of Google Chrome prior to 152.0.7977.82 enables unauthenticated remote attackers to execute arbitrary code within the renderer sandbox by delivering a crafted HTML page to a victim. Execution is confined to Chrome's renderer process rather than the underlying OS - a full host compromise would require chaining with a separate sandbox escape primitive. No public exploit or active exploitation (KEV) has been identified at time of analysis; SSVC rates Exploitation: none and Automatable: no.
Use-after-free in Skia, Chrome's 2D graphics rendering engine, allows remote attackers to execute arbitrary code within the Chrome renderer sandbox by luring a user to a crafted HTML page. Affected versions are all Chrome releases prior to 152.0.7977.82 across desktop platforms. The sandbox confinement means this vulnerability alone does not yield full system compromise - a chained sandbox escape would be required for that - but the renderer-process code execution is rated high impact by Chromium's internal severity team. No public exploit or CISA KEV listing is present at time of analysis; SSVC labels exploitation as none and the attack as non-automatable due to the required user interaction.
Remote code execution in Google Chrome's DevTools component before 152.0.7977.82 lets a remote attacker escape the renderer sandbox and run arbitrary code by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium and carries a CVSS 9.6 with scope change, reflecting sandbox escape. Google has shipped a fix; per CISA's SSVC assessment there is no evidence of active exploitation and no public exploit identified at time of analysis.
Sandboxed remote code execution in Google Chrome's CacheStorage API (prior to 152.0.7977.82) allows a remote attacker to execute arbitrary code inside the Chrome renderer sandbox by luring a user to visit a specially crafted HTML page. The root cause is CWE-668 (Exposure of Resource to Wrong Sphere), where CacheStorage improperly exposes resources to an unintended security context. No public exploit code has been identified and SSVC reports exploitation status as none, though the patch is available and update is strongly recommended.
Remote code execution in Google Chrome for Android before 152.0.7977.82 stems from an out-of-bounds write in the WebGL implementation, letting a remote attacker escape the browser sandbox and run arbitrary code simply by luring a victim to a crafted HTML page. Rated Chromium severity High and CVSS 9.6, the flaw is notable because exploitation breaks out of the renderer sandbox rather than being contained by it. There is no public exploit identified at time of analysis, and CISA SSVC lists exploitation status as none.
In-sandbox arbitrary code execution in Google Chrome's V8 JavaScript engine (all versions prior to 152.0.7977.82) is achievable by a remote unauthenticated attacker who tricks a user into visiting a specially crafted HTML page. The underlying flaw is a CWE-367 Time-of-Check Time-of-Use (TOCTOU) race condition within V8, allowing the attacker to win a memory-access race and redirect execution flow inside the Chrome renderer sandbox. No public exploit code has been identified and CISA SSVC rates exploitation as 'none' at time of analysis, though the technical impact is rated 'total' within the sandbox boundary.
Use-after-free in Chrome's Compositing component (versions prior to 152.0.7977.82) enables a sandbox escape when chained with a renderer-process compromise - an attacker who has already gained control of the renderer can corrupt memory in the Compositing layer and execute arbitrary code outside Chrome's sandbox boundary on the host operating system. The CVSS S:C (scope changed) metric confirms this is a privilege-escalation-across-boundary primitive, delivering full C:H/I:H/A:H impact against the underlying OS. A vendor patch is available in Chrome 152.0.7977.82, and no public exploit has been identified at time of analysis.
System access-restriction bypass in Google Chrome's Network component (versions prior to 152.0.7977.82) lets a remote attacker use crafted network traffic to circumvent enforced access controls, stemming from incomplete resource cleanup (CWE-459). The flaw carries a Chromium-rated High severity and a CVSS of 9.1 reflecting high confidentiality and availability impact; no public exploit is identified at time of analysis and EPSS is low (0.22%). Google fixed it in the 2026-09 stable desktop channel update.
Remote denial of service in OpenVPN's reliability layer - the custom reliable-delivery sublayer underpinning the TLS control channel - allows unauthenticated network attackers to crash or hang OpenVPN daemons on versions up to 2.7.6 and 2.6.22 by triggering an unbounded TLS retransmission timeout or forcing acknowledgment of packets that cannot be outstanding. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VA:H) confirms full availability impact with no authentication, complexity, or user-interaction requirements, and downstream VPN clients lose connectivity when the concentrator is taken offline. No public exploit code or active exploitation (KEV) has been identified at time of analysis; vendor-released fix is available as OpenVPN v2.7.7.
Untrusted search path (CWE-426) in OpenVPN's Windows tapctl utility allows a local low-privileged attacker to substitute a malicious netsh.exe executable when tapctl invokes it without a fully-qualified path. Affected versions span OpenVPN 2.5.0-2.6.22 and 2.7_alpha1-2.7.6 on Windows; the fix was released in v2.7.7. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis.
Cross-cluster secret exfiltration in Rancher Manager before 2.15.1 allows any authenticated user with namespace-creation rights on one downstream cluster to read Project Secrets belonging to a completely separate downstream cluster. The secretsController propagates secrets based solely on the user-writable `field.cattle.io/projectId` annotation, skipping validation that the referenced project belongs to the same cluster - a classic CWE-639 insecure direct object reference pattern. No public exploit or CISA KEV listing has been identified at time of analysis; the vendor-confirmed fix is v2.15.1.
Token store authorization bypass in Rancher Manager before 2.15.1 allows any authenticated user to enumerate every other user's session tokens by supplying a crafted label selector to the ext.cattle.io/v1 Token API. The owner-scoped filter that restricts results to the calling user's own tokens is silently dropped when the caller supplies a label selector naming a different user, instead of returning an empty result set as intended. Exposed data includes token metadata and salted bearer-token hashes, creating an offline cracking risk. No public exploit is identified at time of analysis; a vendor-released patch is available in v2.15.1.
SAML assertion replay bypass in Rancher Manager before v2.15.1 allows unauthenticated network attackers to obtain additional authenticated management sessions as a victim user in high-availability deployments. The per-process in-memory cache that tracks consumed SAML assertion IDs - introduced by the CVE-2026-44946 fix - is not shared across pod replicas, so a captured assertion can be replayed once against each replica that has not yet seen it, yielding one unauthorized session per targeted replica. All SAML identity providers supported by Rancher are affected, and a vendor-released patch is available in v2.15.1. No public exploit code or CISA KEV listing has been identified at time of analysis.
Privilege escalation in Rancher Manager before 2.15.1 allows any user with delegated GlobalRole create or update permission to permanently destroy cluster-wide Kubernetes RBAC policies by hijacking arbitrary ClusterRoles. The GlobalRole controller resolved its target ClusterRole by reading the user-settable `authz.management.cattle.io/cr-name` annotation rather than deriving the name from the GlobalRole's own identity, enabling an authenticated attacker to redirect the controller at any ClusterRole - including `cluster-admin` - and overwrite its rules. The corrupted permissions persist in the Kubernetes object store even after the malicious GlobalRole is deleted, making this a durable, stealthy integrity attack. No public exploit has been identified at time of analysis.
Server-Side Request Forgery in Ollama versions 0.30.0 through 0.33.2 allows unauthenticated remote attackers to redirect the Ollama server's blob-download requests to arbitrary internal hosts, including cloud metadata endpoints such as the AWS instance metadata service. The flaw exists in the tensor-layer model pulling code path (x/transfer/download.go), where HTTP redirect destinations are not validated against an allowlist or the originating registry host. With no public exploit identified at time of analysis, the primary real-world impact is credential theft from cloud metadata services when Ollama runs on cloud-hosted infrastructure.
Race condition in the Linux kernel's ovpn (kernel-native OpenVPN) module allows a workqueue callback to continue executing within module text after that text has been freed during module teardown, creating a use-after-free condition in kernel space. The flaw exists because ovpn queues work items on the global system workqueue rather than a module-owned queue, leaving no driver-controlled drain point to guarantee all callbacks have exited before the module's code segment is released. Systems actively using the kernel-native ovpn module are at risk of kernel memory corruption or crash during module unload; no public exploit has been identified at time of analysis and EPSS is 0.20%.
NULL pointer dereference in the Linux kernel's psxpad-spi driver crashes the kernel when system suspend is triggered on hardware using SPI-connected PlayStation controllers. The probe() function in drivers/input/joystick/psxpad-spi.c omits the spi_set_drvdata() call that stores per-device state, so psxpad_spi_suspend() unconditionally dereferences a NULL pointer on suspend entry, causing a kernel panic. Patches are available across all active stable kernel branches (5.10 through 7.2); EPSS is 0.21% and no active exploitation has been identified.
Uninitialized pointer dereference in the Linux kernel's MediaTek GPU power-domain driver (`pmdomain/mediatek/mfg`) can trigger a kernel fault or incorrect OPP (Operating Performance Point) configuration on first device attachment. The `prev_o` variable in `mtk_mfg_attach_dev()` is read in a conditional branch on the first loop iteration before ever being assigned, meaning it holds an indeterminate stack value; if that value is non-NULL, the kernel dereferences a stale or garbage pointer. Affected versions span stable kernel trees from commit f08e7a4e8d6a through the fixed points in 7.1.10, 7.2, and 6.19. No public exploit code and no CISA KEV listing are present; EPSS at 0.19% (9th percentile) reflects minimal real-world exploitation interest.
Use-after-free in the Linux kernel's MediaTek power domain driver exposes kernel memory to potential corruption via a dangling device-tree node pointer. In scpsys_get_bus_protection_legacy(), two error paths call of_node_put() to release infracfg and SMI device-tree node references before those nodes are passed to dev_err_probe() with the %pOF format specifier; if the put drops the last reference, the formatter dereferences freed memory. Vendor patches are available for Linux 6.18.46, 7.1.10, and 7.2, and EPSS exploitation probability sits at 0.20% (10th percentile) with no confirmed active exploitation.
Out-of-bounds memory read in the Linux kernel's DRM HDMI connector subsystem allows a local, low-privileged user to potentially leak up to 32 bytes of adjacent kernel heap memory or trigger a page fault leading to kernel crash. The flaw exists in a helper function that copies audio infoframe data using the destination buffer size (60 bytes) rather than the source structure size (28 bytes), reading 32 bytes beyond the source allocation. No public exploit code exists, and EPSS sits at the 10th percentile; however, the availability impact is real - the overread can cross a page boundary and cause an access violation.
Out-of-bounds memory access in the Linux kernel's Loongson2 MMC driver allows a local authenticated user to corrupt kernel memory through incorrect scatterlist indexing in the mmc: loongson2 subsystem. The functions `ls2k0500_mmc_reorder_cmd_data()` and `ls2k2000_mmc_reorder_cmd_data()` use `for_each_sg()` to iterate a scatterlist but then incorrectly re-index the current `sg` pointer as if it were an array base (using `&sg[i]`), causing access to wrong or out-of-bounds scatterlist entries. This memory corruption can lead to full kernel compromise - confidentiality, integrity, and availability loss - on systems using Loongson LS2K0500 or LS2K2000 SoCs equipped with MMC storage. No public exploit has been identified at time of analysis.
Out-of-bounds table access in the Linux kernel fp9931 regulator driver exposes kernel memory to corruption via a malformed VPOS/VNEG voltage selector lookup table. The fp9931 driver's VPOSNEG_table[] contains two defects: a duplicate 7.04V entry that shifts all subsequent selector mappings by one, and a truncated table of only 41 entries instead of the required 64, meaning any selector value above 0x28 triggers an out-of-bounds access in kernel memory. Devices incorporating the FP9931 PMIC (a display-panel power regulator) running affected kernel versions are vulnerable; exploitation probability is very low (EPSS 0.20%, 10th percentile) with no public exploit and no confirmed active exploitation.
Out-of-bounds kernel memory read in the Linux kernel DRM log subsystem allows a local low-privileged user to potentially disclose kernel memory contents or crash the system. The flaw resides in drm_log_draw_kmsg_record(), where an unsigned integer underflow on a zero-length message causes an array access at offset UINT_MAX (0xFFFFFFFF) rather than a valid buffer position. No public exploit exists and EPSS sits at 0.20% (10th percentile), indicating low observed exploitation interest, though the kernel DRM panic-display path is reachable on any system with a GPU using the DRM framework.
Out-of-bounds array access in the Linux kernel's Thunderbolt driver exposes local low-privileged users to potential kernel memory corruption and privilege escalation. The flaw in tb_consumed_dp_bandwidth() sizes the group_reserved[] array at MAX_GROUPS entries (indices 0 through MAX_GROUPS-1) but uses Group IDs directly as indices, where valid IDs run from 1 through MAX_GROUPS - causing an off-by-one that reads and writes one element past the array boundary when the highest bandwidth group is processed. Patches are available across multiple stable kernel branches (6.12.x, 6.18.x, 7.1.x, 7.2), and no public exploit code has been identified at time of analysis.
Out-of-bounds kernel memory reads in the Linux kernel's ovpn (in-kernel OpenVPN) driver allow a local attacker with low privileges to leak kernel memory by abusing a missing ownership check on the sk_user_data socket field. The driver dereferences sk_user_data as an ovpn-internal structure without first confirming that encap_type identifies the socket as ovpn-owned, so when BPF SOCKMAP or another subsystem has populated sk_user_data with a different pointer type, ovpn misinterprets that memory and reads out of bounds. Affected kernels span 6.16 through pre-patch stable releases; no public exploit has been identified and EPSS sits at 0.21% (11th percentile), but kernel memory disclosure can seed further privilege escalation.
Use-after-free in the Linux kernel's pata_sl82c105 PATA bridge driver allows a local low-privileged user to potentially achieve kernel memory corruption leading to privilege escalation on systems equipped with the SL82C105 PCI bridge chip. The defect was introduced by commit 44c10138fd4b, which replaced a PCI configuration-space read with direct access to the cached revision field of a PCI device struct - but left that access after the reference was dropped via pci_dev_put(), creating a window where the bridge struct may be freed before the read occurs. Patches have been backported across multiple long-term stable kernel branches; no public exploit code or active exploitation has been identified at time of analysis.
Heap buffer overflow in zlib 1.3.1.2 through 1.3.2 allows remote attackers to corrupt memory via crafted input to applications using the non-blocking gzwrite API. The gz_vacate() function fails to bounds-check a memmove() when stale external buffer pointers are present after a write stall, reachable by calling gzprintf() or gzvprintf() in that state. A publicly available proof-of-concept exploit exists; no vendor-released patch has been identified at time of analysis.
Uninitialized heap memory disclosure in FreeRDP 3.0.0-3.30.0 exposes up to 576 bytes of stale server or proxy heap contents - potentially including cleartext credentials from prior RDP sessions - to any authenticated downstream RDP client. Three PDU-serialization functions in libfreerdp/core/info.c advance the stream write pointer with Stream_Seek over reserved padding bytes instead of zeroing them with Stream_Zero, leaving prior malloc heap contents in Save Session Info PDUs transmitted to clients. FreeRDP-based server deployments and freerdp-proxy instances are the affected roles; a vendor-confirmed fix ships in version 3.31.0, and no public exploit or active exploitation has been identified at time of analysis.
Host-parsing ambiguity in fast-uri allows attackers to silently bypass SSRF denylists, redirect allowlists, and proxy routing rules by submitting URLs containing unbalanced authority brackets. Affected versions 2.4.5, 3.1.6, and 4.1.3 of the Fastify ecosystem URI parsing library return the malformed bracket-containing string as the host without raising an error, while Node.js's URL implementation and downstream HTTP clients resolve the same string to an entirely different host. Any application that reads the fast-uri-parsed host to enforce a security policy, then passes the original URL to an HTTP client, evaluates its controls against a string that is never the host the request actually reaches.
Denial-of-service in the Go extended cryptography library's SSH package allows a malicious peer to deadlock an entire SSH connection by sending crafted RFC 4254 channel messages after a channel is established. All versions of golang.org/x/crypto/ssh below 0.56.0 are affected; the flaw manifests because unrecognized channel messages were buffered and allowed to block rather than being rejected as protocol errors. No public exploit or active exploitation has been identified, but the attack requires no privileges in the worst-case client scenario where a malicious SSH server targets a connecting client.
Connection deadlock in golang.org/x/crypto/ssh (all versions before 0.56.0) allows a malicious remote SSH peer to permanently freeze an SSH connection by flooding the incomingRequests queue of a channel that has been registered in the mux's chanList but not yet established. The attack exploits the absence of any established-state guard in the packet handler, causing a deadlock that renders the entire connection unresponsive without triggering an explicit teardown. No public exploit has been identified and no CISA KEV listing exists, but the network-accessible, no-authentication CVSS vector makes this straightforward to trigger against any Go application using this library for SSH.
Memory exhaustion via unbounded decompression in HTTPX2 (all versions before 2.12.0) allows any HTTP server the client contacts to cause severe memory pressure or out-of-memory process termination by returning a crafted compressed response body. The content decoders in `_decoders.py` call `decompress()` without a size cap, so a single 64 KiB compressed chunk can inflate to approximately 64 MiB in one allocation across gzip, deflate, brotli, and zstd encodings - all enabled by default. No active exploitation is confirmed in CISA KEV, and no public proof-of-concept is referenced, but the decompression-bomb technique is well understood and trivially reproducible.
HTTPX2's SOCKS5 proxy implementation omits TLS negotiation for WebSocket Secure (wss://) origins, exposing the full WebSocket session - opening handshake, query parameters, Authorization headers, cookies, and message frames - in plaintext to anyone who can observe or control the proxy path. Affected are applications using Client.websocket() or AsyncClient.websocket() in HTTPX2 versions 2.6.0 through 2.9.1 when routing through a SOCKS5 proxy. An adjacent-network attacker can passively eavesdrop on or actively modify traffic, and can impersonate the WebSocket server due to the missing certificate verification step. No public exploit code has been identified at time of analysis and this CVE does not appear in the CISA KEV catalog.
NULL pointer dereference in NGINX JavaScript (njs) crashes NGINX worker processes when an njs script calls ngx.fetch() against a server that returns a malformed HTTP response and subsequently reads Response.statusText on the result. All versions of F5's NGINX JavaScript module are listed as affected per the wildcard CPE, and the impact is confined entirely to the data plane - worker availability - with no control-plane, confidentiality, or integrity exposure. No public exploit code exists and the CVE is not listed in CISA KEV at time of analysis, but the network-accessible path and zero-privilege requirement make this a credible service-disruption risk for any NGINX deployment using njs-based outbound HTTP fetching.
NGINX JavaScript (njs) and QuickJS (qjs) fail open during the js_access phase when an exception is thrown inside an asynchronous request-body processing handler before an explicit access-denial is returned. The flaw (CWE-636, Not Failing Securely) allows unauthenticated remote attackers to bypass js_access controls entirely and reach protected backend resources. No public exploit code or CISA KEV listing has been identified at time of analysis; exploitation is bounded by the requirement for a specific async access-handler pattern.
Symlink traversal in util-linux's X-mount.subdir mount option allows a local unprivileged user with an fstab-authorized entry to redirect mount resolution to arbitrary host paths, achieving privilege escalation or container escape on Linux 6.15+ kernels. The root cause is that AT_SYMLINK_NOFOLLOW, passed to open_tree() in the detached-tree fast path, only blocks final-component symlinks - not intermediate path components - leaving an attacker who can plant a symlink in a middle directory able to substitute the intended subdirectory with any host path. Affected platforms include Red Hat Enterprise Linux 7-10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4; no public exploit has been identified at time of analysis.
Local privilege escalation in util-linux's SUID mount(8) binary exposes all major Red Hat Enterprise Linux versions (7-10), Red Hat Hardened Images, and OpenShift Container Platform 4 to root-level file ownership and permission manipulation by low-privileged local users. The flaw stems from a time-of-check to time-of-use (TOCTOU) race: mount(8) reads the bind-mount source from fstab but does not pin the resolved inode before issuing the privileged syscall, allowing an attacker with write access to the source path or a writable ancestor to substitute an arbitrary host directory. When fstab entries additionally specify X-mount.owner, X-mount.group, or X-mount.mode, root subsequently applies chown or chmod to the attacker-redirected path, completing the privilege escalation. No public exploit code or CISA KEV listing is identified at time of analysis.
Privilege escalation in util-linux's nsenter --join-cgroup option allows an unprivileged local user to move and terminate root-owned host processes by exploiting a persistent file descriptor opened as root that survives across namespace and credential changes. The kernel evaluates cgroup migration requests against the credentials held at fd-open time rather than the current caller's credentials, so any program that inherits the still-open cgroup.procs fd effectively retains root's cgroup management authority. Red Hat Enterprise Linux 7-10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4 are confirmed affected; no public exploit has been identified at time of analysis.
Path traversal in wcurl for Windows allows a crafted URL containing percent-encoded backslashes to redirect a downloaded file to an attacker-controlled directory outside the user's intended destination. Affecting wcurl shipped with curl 8.14.0 through 8.21.0 and standalone wcurl 2024.12.08 through 2026.01.05, the flaw exploits Windows path-separator semantics: wcurl decodes %5C to a backslash, which Windows treats as a directory separator, causing file placement at an unintended filesystem path. No public exploit code and no active exploitation have been identified at time of analysis; vendor-released patches are available as of September 2, 2026.
Unauthenticated remote denial of service in Libreswan's pluto IKE daemon allows any network attacker to repeatedly crash and restart the VPN service by sending a malformed X.509 certificate in a CERT payload during IKE handshake negotiation. The crash is triggered by a reachable assertion in `add_decoded_cert()`: when NSS's `CERT_ExtractPublicKey()` receives a certificate with an invalid RSA exponent (e.g., zero), it returns NULL, which the FIPS-mode code path does not handle, causing the daemon to abort. The vendor explicitly confirms no remote code execution is possible; impact is limited to availability. No CISA KEV listing and no public exploit code have been identified at time of analysis.
Remote code execution in Google Chrome on Windows (versions prior to 153.0.8010.36) arises from a heap buffer overflow in ANGLE, Chrome's graphics abstraction layer. A remote attacker who lures a victim to a crafted HTML page can corrupt heap memory and execute arbitrary code outside the renderer sandbox, gaining full compromise of the host. No public exploit is identified at time of analysis and EPSS is low (0.33%), but the sandbox-escape scope and Chrome's near-universal footprint make prompt patching essential.
Out-of-bounds read in the WebGL component of Google Chrome before 153.0.8010.36 lets a remote attacker who lures a victim to a crafted HTML page potentially execute arbitrary code outside the browser sandbox. Chromium rates the security severity as High, and a vendor patch is available; no public exploit has been identified and CISA SSVC records exploitation as none, with EPSS at a low 0.28% (20th percentile).
Use-after-free in Chrome's Views UI framework enables local attackers to escape the browser sandbox and execute arbitrary code at browser-process privilege level. The vulnerability affects all Google Chrome desktop versions prior to 153.0.8010.36. No public exploit code or active exploitation has been identified; EPSS at 0.17% (7th percentile) reflects low near-term exploitation probability.
Sandbox-escape remote code execution in Google Chrome on Android (versions prior to 153.0.8010.36) stems from a use-after-free in Dawn, Chromium's WebGPU implementation. A remote attacker who lures a victim to a crafted HTML page can trigger the freed-object reuse to execute arbitrary code outside the renderer sandbox. Chromium rates this 'High'; there is no public exploit or CISA KEV listing, and EPSS is low (0.30%), indicating no evidence of active or widespread exploitation at time of analysis.
Sandbox-escape remote code execution in Google Chrome (Chromium-based desktop) before 153.0.8010.36 stems from an incorrect authorization flaw in the DevTools component. A remote attacker who lures a victim to a crafted HTML page can potentially execute arbitrary code outside the renderer sandbox, achieving full compromise of the browser process. No public exploit identified at time of analysis; EPSS is low (0.21%, 11th percentile) and the issue is not in CISA KEV, but Google rates the Chromium security severity as High.
Sandbox-escape code execution via a race condition in the Google Chrome Updater component on Windows allows a local attacker to execute arbitrary code outside the Chrome sandbox. Affected builds are all Chrome versions prior to 153.0.8010.36 on Windows. The Chrome Updater's elevated-privilege execution context makes winning the race condition particularly impactful, as successful exploitation bypasses sandbox containment entirely.
Sandbox escape in Google Chrome's Chromoting (Chrome Remote Desktop) component on Windows allows a local unprivileged attacker to execute arbitrary code outside the Chrome renderer sandbox by exploiting a race condition. All Chrome for Windows releases prior to 153.0.8010.36 are affected. No public exploit has been identified at time of analysis; EPSS places exploitation probability at the 3rd percentile, though SSVC rates technical impact as 'total,' reflecting full system compromise potential if the race condition is successfully won.
Missing authorization in the Views UI framework of Google Chrome prior to 153.0.8010.36 allows remote attackers to bypass system access restrictions via a crafted HTML page requiring social engineering. The vulnerability (CWE-862) resides in Chrome's cross-platform UI layer rather than web content rendering, with full confidentiality, integrity, and availability impact per CVSS C:H/I:H/A:H. No public exploit code or active exploitation has been identified at time of analysis; EPSS of 0.18% (7th percentile) corroborates low current weaponization despite the 8.8 CVSS score.
Use-after-free in Google Chrome's Core component on Windows prior to 153.0.8010.36 enables a renderer-compromised attacker to escape the browser sandbox and execute arbitrary code on the host OS. The vulnerability is platform-specific to Windows and functions as the second stage of a chained exploit: an attacker must first achieve renderer-level compromise before triggering this UAF to pivot into the privileged browser process. No public exploit code or active exploitation has been identified at time of analysis; vendor patch 153.0.8010.36 is available.
Use-after-free in Chrome's Receiver component allows an adjacent, unauthenticated attacker to execute arbitrary code outside the renderer sandbox via crafted network traffic, affecting all Chrome versions prior to 153.0.8010.36. The scope change in the CVSS vector confirms this is a full sandbox escape - successful exploitation yields OS-level code execution on the victim machine without requiring any user interaction. No public exploit has been identified at time of analysis, and EPSS at 0.13% (3rd percentile) indicates low observed exploitation activity.
Sandbox-escape remote code execution in Google Chrome's Views UI framework prior to 153.0.8010.36 allows a local attacker to execute arbitrary code outside the browser sandbox by inducing a specific UI interaction that triggers a use-after-free condition. The CVSS scope change (S:C) confirms the vulnerability crosses the renderer sandbox boundary into the broader OS context, with full confidentiality, integrity, and availability impact. No public exploit or CISA KEV listing has been identified at time of analysis; EPSS of 0.20% (10th percentile) reflects low automated exploitation probability, though sandbox escapes are high-value for privilege escalation chains.
Out-of-bounds read in Google Chrome's Media component (versions prior to 153.0.8010.36) enables remote code execution confined within the browser sandbox when a user visits a specially crafted HTML page. The vulnerability stems from improper bounds checking during media processing, allowing a remote attacker to read memory beyond intended buffer limits and leverage the resulting data to achieve arbitrary code execution. No public exploit has been identified at time of analysis and EPSS is low (0.35%), but the attack surface is broad given Chrome's ubiquity.
Memory corruption in the Codecs component of Google Chrome prior to 153.0.8010.36 enables remote unauthenticated attackers to execute arbitrary code inside the browser sandbox by delivering a crafted HTML page containing malformed media content. The flaw is classified CWE-119 (improper bounds restriction), rated 'High' by Chromium Security, and carries a CVSS 8.8 base score with a network attack vector requiring only passive user interaction. No public exploit code or CISA KEV listing has been identified at time of analysis, and EPSS stands at a low 0.35% (29th percentile), indicating theoretical rather than observed exploitation.
Double-free memory corruption in PDFium (Chrome's PDF rendering engine) on Windows allows remote code execution within the Chrome renderer sandbox when a user opens a crafted PDF file. Affected versions are all Chrome releases on Windows prior to 153.0.8010.36, where CWE-415 double-free in the PDFium component enables an attacker-controlled allocation state. No public exploit or CISA KEV listing is confirmed at time of analysis, and EPSS remains low at 0.20% (10th percentile), suggesting exploitation is not yet widespread despite the network-reachable vector.
Remote code execution in Google Chrome on Windows (versions prior to 153.0.8010.36) arises from a use-after-free in ANGLE, Chrome's graphics abstraction layer that translates OpenGL ES calls to Direct3D. A remote attacker who lures a victim to a crafted HTML page can corrupt memory and execute arbitrary code outside the browser sandbox, giving full compromise of the renderer host process. No public exploit identified at time of analysis, and EPSS is modest (0.35%), but the sandbox-escape impact and one-click delivery make this a high-priority browser patch.
Use-after-free in Chrome's Cast (Chromecast streaming) component allows an adjacent unauthenticated attacker to potentially escape the browser sandbox and execute arbitrary code by delivering crafted network traffic over a local or Wi-Fi network. All Chrome desktop versions prior to 153.0.8010.36 are affected, with Chromium rating this Critical due to the full-CIA, scope-changed impact. No public exploit has been identified at time of analysis, and the EPSS score of 0.17% (6th percentile) indicates minimal observed exploitation activity despite the high severity classification.
Remote code execution in Google Chrome prior to 153.0.8010.36 allows a remote attacker to escape the renderer sandbox and run arbitrary code on the host by luring a victim to a crafted HTML page that triggers a heap buffer overflow in the WebGL implementation. Chromium rates this Critical and the CVSS 9.6 score reflects a scope-changing sandbox escape; no public exploit is identified at time of analysis, and EPSS is low at 0.29% (21st percentile). Patched in the September 2026 stable-channel desktop release.
Remote code execution in Google Chrome for Android prior to 153.0.8010.36 arises from an out-of-bounds write in the WebGL graphics subsystem, letting a remote attacker who lures a user to a crafted HTML page execute arbitrary code outside the renderer sandbox. Rated Critical by Chromium and CVSS 9.6, the scope-changed vector reflects a full sandbox escape. No public exploit is identified at time of analysis and EPSS is low (0.39%), but WebGL memory-corruption bugs are historically high-value targets.
Remote code execution in Google Chrome for Android prior to 153.0.8010.36 stems from a use-after-free in the WebGL implementation that a remote attacker can trigger with a crafted HTML page to execute arbitrary code outside the browser sandbox. Chromium rates this Critical and the CVSS is 9.6, reflecting a full renderer-to-sandbox-escape chain requiring only that a victim visit a malicious page. No public exploit is identified at time of analysis and EPSS is low (0.36%), but the sandbox-escape impact makes it a priority patch.
Remote code execution in Google Chrome desktop prior to 153.0.8010.36 arises from a use-after-free in the WebGL implementation, allowing a remote attacker to run arbitrary code outside the browser sandbox by luring a victim to a crafted HTML page. Google rates the Chromium severity as Critical and the CVSS is 9.6, reflecting a full renderer-to-host sandbox escape. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; EPSS is low at 0.28% (20th percentile).
Integer overflow in FreeType's COLR color-layer blending function (tt_face_colr_blend_layer in ttcolr.c) enables local privilege escalation across Android 14 through 17. A low-privileged app can deliver a maliciously crafted TrueType font containing a corrupted COLR table, triggering arithmetic overflow that corrupts heap memory and enables code execution in a higher-privileged system context. No active exploitation has been identified (EPSS 0.15%, SSVC Exploitation: none), and no user interaction beyond app execution is required.
Out-of-bounds memory corruption in Tapdisk, the XAPI toolstack's userspace xen-blkback implementation, allows a malicious guest VM to achieve code execution inside the tapdisk process, which normally runs as root in dom0. CVE-2026-79606 specifically concerns the gcopy_segs[] array: the bounds check incorrectly permits nr_segments values between 12 and 32, causing out-of-bounds writes that corrupt adjacent process memory. All versions of tapdisk are confirmed vulnerable, no mitigations exist, and patches are available via XSA-513.
Out-of-bounds memory corruption in Xen's Tapdisk (userspace xen-blkback) enables a malicious guest VM to achieve code execution within the tapdisk process, which runs as root in Dom0, constituting a full guest-to-host escape. CVE-2026-79605 specifically covers the absent upper bounds check on blkif->last_sect: guest-supplied values greater than 7 trigger reads or writes beyond the mapped grant region. All versions of tapdisk are confirmed vulnerable per XSA-513, no mitigations exist, and patch application is the sole remediation path. No public exploit or CISA KEV listing is identified at time of analysis.
Unbounded memory exhaustion in Xen's OCaml xenstore daemon (oxenstored) allows a malicious or compromised guest VM to trigger a system-wide denial of service by repeatedly sending xenbus reconnect requests without clearing the global watch trie. Each reconnect cycle purges only the per-domain hashtable, leaving stale watch entries to accumulate indefinitely in the global trie. All Xen deployments from 4.6 onwards using the OCaml oxenstored implementation are affected; no public exploit has been identified, but the attack surface is accessible to any guest with standard xenbus connectivity and no mitigations exist.
HTTP/2 thread-exhaustion denial-of-service in Eclipse Jetty allows unauthenticated remote clients to permanently block all server threads by exploiting a race condition in RST_STREAM and GOAWAY frame handling. The race incorrectly resets the `HTTP2Flusher.terminated` field from a non-null terminal state back to null, allowing new write-queue entries to be enqueued in a flusher that will never drain them; the write-blocked threads waiting on those entries hang indefinitely. Across five affected Jetty major branches (9.4, 10.0, 11.0, 12.0, 12.1), any internet-exposed HTTP/2 endpoint is reachable without authentication. No public exploit has been identified at time of analysis.
Guest-to-hypervisor privilege escalation in Xen allows a VM guest with a PCI device assigned - where the device exposes at least one Base Address Register (BAR) mapped to IO port space - to trigger a BUG() assertion in the Xen hypervisor, crashing or potentially compromising the host. The CVSS scope-changed vector (S:C, C:H/I:H/A:H) reflects cross-boundary impact: the attack originates inside a guest VM but affects the host hypervisor. Tracked as XSA-510, no public exploit is identified at time of analysis, and EPSS sits at 0.17% (7th percentile), consistent with a targeted-environment issue rather than mass exploitation.
HTTP/1.1 request smuggling in Eclipse Jetty allows unauthenticated remote attackers to desynchronize request boundary parsing between Jetty and an upstream proxy, enabling manipulation of other users' HTTP sessions. The root cause is Jetty's acceptance of a bare LF character (\n) as a line terminator during chunked transfer encoding parsing - specifically in chunk extensions, chunk data termination, or trailer termination - where RFC 7230 mandates CRLF (\r\n). Depending on the Jetty version and configured HTTP compliance mode, a crafted request can cause the proxy and Jetty to disagree on where one request ends and the next begins, enabling request injection against co-located tenants. No public exploit has been identified at time of analysis.
Stack exhaustion via uncontrolled recursion in Qt's QDomDocument XML serialization allows a remote attacker to crash any Qt application that processes untrusted XML input, resulting in a denial-of-service condition. Affected applications using the QtXml module parse attacker-supplied deeply nested XML documents, triggering recursive descent without a depth guard until the call stack is exhausted. No code execution is possible; impact is limited to application availability. No public exploit or CISA KEV listing has been identified at time of analysis.
Authenticated OS command injection in Dogtag PKI's certificate profile import mechanism allows a CA Administrator to achieve code execution as the pkiuser account on RHEL 6-10 and Red Hat Certificate System 9. By uploading a crafted certificate profile that exploits the ExternalProcessConstraint mechanism with attacker-controlled environment variables, a privileged attacker can bypass the limited profile ID validation and execute arbitrary system commands. No public exploit or active exploitation is known at time of analysis, but the CVSS 7.2 / PR:H rating reflects that CA Administrator access is a prerequisite.
Use-after-free in strongSwan's IKEv2 Multi-Key Exchange (Multi-KE, RFC 9370) implementation is triggered when two authenticated IKE peers simultaneously initiate a rekey operation, causing a race condition that corrupts heap memory and can result in remote code execution within the IKE daemon. The attack requires an established IKE session and high-complexity timing to induce the collision, reflected in the CVSS AC:H/PR:L vector. Fixed in strongSwan 6.1.0, released September 7, 2026, alongside six other CVEs disclosed in the same advisory batch. No public exploit identified at time of analysis.
Denial of service via infinite loop in strongSwan's x509 plugin affects all deployments that process X.509 attribute certificates. An unauthenticated remote attacker can craft a malformed attribute certificate that triggers CWE-835 (infinite loop) during parsing, causing the IKE daemon to hang indefinitely and disrupting all VPN connectivity. The vendor fixed this in strongSwan 6.1.0 alongside six other vulnerabilities disclosed on 2026-09-07; no public exploit has been identified at time of analysis.
Denial of service via NULL-pointer dereference in strongSwan's x509 plugin affects versions 4.2.0 through 6.0.x, triggered during verification of X.509 attribute certificates. An unauthenticated remote attacker can crash the charon IKE daemon by presenting a crafted attribute certificate during VPN handshake negotiation, taking the gateway offline. Vendor-released fix is strongSwan 6.1.0, published September 7, 2026, as part of a coordinated batch of six CVE patches; no public exploit has been identified at time of analysis.
Tunneled EAP authentication in strongSwan before 6.1.0 can be bypassed when the IKEv2 responder fails to properly enforce inner EAP method authentication details, enabling a network attacker with a low-privilege outer-tunnel identity to obtain an authorized VPN session without completing the inner credential exchange. The flaw (CWE-863, Incorrect Authorization) is limited to deployments using tunneled EAP methods such as EAP-TTLS or EAP-PEAP; certificate-only or non-tunneled EAP configurations are not affected. Vendor-released patch strongSwan 6.1.0 is available; no public exploit identified at time of analysis.
strongSwan 5.9.7 through versions prior to 6.1.0 lets unauthenticated network attackers drive an IKEv2 responder running charon/libcharon into creating a Child Security Association before the IKE authentication exchange has completed, giving low-level impacts to confidentiality, integrity and availability (CVSS 3.1 base 7.3, AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L). Reachability over UDP 500/4500 is what drives the score rather than severe impact, and there is a public advisory but no public exploit identified at time of analysis; EPSS is 0.34% (27th percentile), indicating low near-term exploitation likelihood. The vendor-released patch is strongSwan 6.1.0, published alongside a September 2026 batch of unrelated strongSwan fixes (CVE-2026-78123, -78124, -78126, -78127, -78129 through -78131).
Relative path traversal in Apache Ant's built-in `ftp` and `scp` tasks (versions 1.2 through 1.10.17) permits a malicious or MITM-intercepted remote server to supply server-controlled paths that escape the configured download directory, overwriting arbitrary files with the filesystem permissions of the Ant process. For FTP tasks not using FTPS, no server identity check is enforced, making a network MITM attacker sufficient to trigger the write primitive without needing a valid certificate. The vulnerability is fixed in Ant 1.10.18, which validates destination paths by default; no public exploit code has been identified and EPSS is low at 0.19%.
Authentication bypass via response replay affects the DIGEST-MD5 server implementation in the Perl Authen::SASL distribution (Authen::SASL::Perl::DIGEST_MD5) before version 2.2100. The server generates a fresh nonce in its challenge but never compares it against the nonce returned by the client, so an attacker who passively captures one successful qop=auth exchange can replay that exact response against a later session for the same service, host, realm and user and authenticate as that user without knowing the password. An upstream fix is available (2.2100, commit 9433736); no public exploit identified at time of analysis, and EPSS is low at 0.22%.
Path traversal in h3's serveStatic() function on Node.js allows unauthenticated remote attackers to read arbitrary files outside the configured static root directory. The root cause is that h3 uses srvx's FastURL class, which skips WHATWG URL normalization for performance - percent-encoded dot segments (%2e%2e) survive raw into decodeURI(), are decoded to ../, and are passed unsanitized to filesystem callbacks. A detailed proof-of-concept exploit chain is publicly documented in GHSA-wr4h-v87w-p3r7; no active exploitation confirmed in CISA KEV at time of analysis. Fixed in versions 1.15.6 and 2.0.1-rc.15.
Path traversal in h3's serveStatic utility (versions before 1.15.9) enables unauthenticated remote attackers to read arbitrary files from URL-based storage backends (S3, CDN, object storage) by exploiting a double-decoding flaw that bypasses dot-segment normalization. A request crafted with double-encoded dot sequences (%252e%252e) survives the resolveDotSegments() guard - which only matches literal '.' characters - and is then interpreted as '..' by RFC 3986-compliant URL backends. No public exploit code or active exploitation has been confirmed, though the GHSA advisory provides source-level analysis sufficient to guide exploit development.
Unvalidated BPF scratch-register array index in libpcap's user-space BPF interpreter allows a local attacker with low privileges to craft a filter program that reads or writes OS process memory beyond the intended 16-entry M[] scratch array. On 64-bit architectures the accessible range is up to 16GiB starting at the current stack frame; on 32-bit architectures the entire process address space is reachable. The Tcpdump Group has issued a fix (commit 48e8960a) that adds bounds checks before every M[] access, rejecting filters referencing register index ≥ BPF_MEMWORDS (16). No public exploit or CISA KEV listing is identified at time of analysis.
Out-of-bounds heap write in PCRE2 before 10.48 allows memory corruption via the DFA matching engine when a cached workspace block is reused in a recursive context without the size check that guards a freshly allocated block of the same type. Applications that pass attacker-controlled regular expressions to pcre2_dfa_match, or that configure a small heap limit via the PCRE2 API while processing recursive patterns, are exploitable. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog; however, PCRE2 10.48 ships a confirmed vendor fix alongside four other security patches in the same release.
Infinite-loop denial-of-service in smol-toml (npm, squirrelchat) before version 1.7.1 allows remote unauthenticated attackers to permanently hang any Node.js service that parses attacker-controlled TOML. The trigger is a crafted value inside a TOML array or inline table followed by a comment character with no trailing newline - when this input reaches the parser, skipUntil() in src/util.ts receives -1 from indexOfNewline() and resets the cursor to position zero instead of terminating, spinning indefinitely and consuming all processing capacity. No public exploit has been identified at time of analysis, but the CVSS 4.0 score of 8.2 and the trivially constructible trigger make this straightforward to weaponize against any exposed TOML-parsing endpoint.
Arbitrary command execution in goose v1.37.0 allows an attacker to embed shell commands inside recipe stdio extension definitions and retry.check fields that are silently executed under the victim user's OS privileges. The built-in recipe security scanner does not inspect these fields, providing a false safety guarantee and a clear bypass path. No public exploit is identified at time of analysis, but exploitation is low-complexity once a target user loads a malicious recipe.
Improper OCSP response validation across the Snowflake Python, Go, JDBC, and Node.js drivers allowed a revoked TLS certificate to be treated as valid, enabling a man-in-the-middle attacker to intercept and tamper with driver-to-Snowflake TLS sessions. The root flaw is twofold: OCSP stapled or fetched responses were not reliably bound to the specific certificate under validation, and definitive OCSP verification failures were treated as transient errors (soft-fail), causing the driver to proceed with a connection rather than abort it. Exploitation requires a network-adjacent or on-path position combined with possession of a revoked certificate and its corresponding private key for a Snowflake or storage-stage hostname; no public exploit is identified at time of analysis and EPSS data was not provided, but the CVSS AC:H reflects these steep prerequisites.
Done. The analysis is above as the JSON object. Key points of the synthesis: - **Same FreeIPMI 1.6.19 cluster** as CVEs 85504/85507/85508 already tracked — all client-side stack overflows (CWE-121) triggered by a malicious/compromised BMC returning oversized responses. - **CVSS 9.8 is overstated**: this is a client-side/rogue-BMC flaw, not an internet-facing service. I assessed it down to `AC:H/UI:R` (needs attacker control of a BMC plus an operator/job initiating the FRU read). - **Metadata is clean** — vendor tag, CPE, and CWE all correct, and no embedded injection note this time — so `data_quality_flags` is `[]`. - Fix confirmed as 1.6.19; no EPSS/KEV/POC signal, so exploitation status is unknown. Memory updated with the new CVE note and index entry.
Stack-based buffer overflow in GNU FreeIPMI's ipmi-oem tool (before 1.6.19) affects the _output_dell_system_info_cmc_ipv6_info routine reached through the 'dell get-system-info cmc-ipv6-info' subcommand. Because the flaw lies in code that parses the response returned by a Dell CMC/BMC, an attacker who controls (or can MITM) the IPMI device an operator queries can corrupt the client's stack and potentially execute code on the management host. This is one of several FreeIPMI OEM-parser overflows fixed together in 1.6.19 (disclosed on oss-security 2026-08-28); no public exploit identified at time of analysis.
Stack-based buffer overflow in FreeIPMI's ipmi-oem utility (versions before 1.6.19) lets a malicious or compromised Dell iDRAC BMC corrupt the memory of the client host running the 'dell get-system-info idrac-info' subcommand, potentially achieving code execution in the context of the operator (often root). The flaw sits in _get_dell_system_info_idrac_info in ipmi-oem/ipmi-oem-dell.c, which copies attacker-influenced OEM response data into a fixed-size stack buffer without bounds checking. No public exploit identified at time of analysis; disclosed via oss-security and fixed in FreeIPMI 1.6.19.
Stack-based buffer over-read in FreeIPMI's ipmi-oem Fujitsu OEM module crashes the client process when a Fujitsu BMC returns a shorter-than-expected response to a System Event Log query. All FreeIPMI versions before 1.6.19 are affected; this is a distinct vulnerability from CVE-2026-50031, which covers different version ranges. No public exploit code or active exploitation has been identified at time of analysis.
Stack-based buffer overflow in GNU FreeIPMI before 1.6.19 lets a malicious or compromised Fujitsu iRMC BMC corrupt client memory when the FreeIPMI tooling parses malformed Fujitsu SEL 'long text' responses in _ipmi_sel_oem_fujitsu_get_sel_entry_long_text. Successful exploitation can crash the client or execute arbitrary code in the context of the process reading the System Event Log (typically ipmi-sel or libfreeipmi consumers). No public exploit is identified at time of analysis, and the flaw is fixed in FreeIPMI 1.6.19.
Prototype pollution in toml-node (npm package `toml` by BinaryMuse) prior to 4.1.2 allows unauthenticated remote attackers to write arbitrary keys onto Object.prototype by supplying a crafted TOML document to `toml.parse()`. The vulnerability exploits a path desynchronization bug in the compiler's duplicate-key guard - comma-joined tracking paths diverge from dot-joined traversal paths, allowing `__proto__` traversal through scalar values into the real JavaScript prototype chain. Injected properties propagate process-wide in Node.js and can enable denial of service, authorization bypass, or code execution via application gadget chains; the GHSA advisory includes working proof-of-concept code, and a fix is available in version 4.1.2.
Sandbox-escape remote code execution affects Google Chrome on iOS prior to 152.0.7977.82, where improper input validation (CWE-20) in the browser's Transactions Platform component lets a remote attacker potentially run arbitrary code outside the renderer sandbox when a victim loads a crafted HTML page. Google shipped a fix in the stable channel and Chromium rated the underlying issue Medium severity, though the supplied CVSS vector scores it 9.6. There is no public exploit identified and CISA's SSVC framework records exploitation status as none.
Type confusion (CWE-843) in the Compositing subsystem of Google Chrome prior to 152.0.7977.82 enables unauthenticated remote attackers to execute arbitrary code within the renderer sandbox by delivering a crafted HTML page to a victim. Execution is confined to Chrome's renderer process rather than the underlying OS - a full host compromise would require chaining with a separate sandbox escape primitive. No public exploit or active exploitation (KEV) has been identified at time of analysis; SSVC rates Exploitation: none and Automatable: no.
Use-after-free in Skia, Chrome's 2D graphics rendering engine, allows remote attackers to execute arbitrary code within the Chrome renderer sandbox by luring a user to a crafted HTML page. Affected versions are all Chrome releases prior to 152.0.7977.82 across desktop platforms. The sandbox confinement means this vulnerability alone does not yield full system compromise - a chained sandbox escape would be required for that - but the renderer-process code execution is rated high impact by Chromium's internal severity team. No public exploit or CISA KEV listing is present at time of analysis; SSVC labels exploitation as none and the attack as non-automatable due to the required user interaction.
Remote code execution in Google Chrome's DevTools component before 152.0.7977.82 lets a remote attacker escape the renderer sandbox and run arbitrary code by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium and carries a CVSS 9.6 with scope change, reflecting sandbox escape. Google has shipped a fix; per CISA's SSVC assessment there is no evidence of active exploitation and no public exploit identified at time of analysis.
Sandboxed remote code execution in Google Chrome's CacheStorage API (prior to 152.0.7977.82) allows a remote attacker to execute arbitrary code inside the Chrome renderer sandbox by luring a user to visit a specially crafted HTML page. The root cause is CWE-668 (Exposure of Resource to Wrong Sphere), where CacheStorage improperly exposes resources to an unintended security context. No public exploit code has been identified and SSVC reports exploitation status as none, though the patch is available and update is strongly recommended.
Remote code execution in Google Chrome for Android before 152.0.7977.82 stems from an out-of-bounds write in the WebGL implementation, letting a remote attacker escape the browser sandbox and run arbitrary code simply by luring a victim to a crafted HTML page. Rated Chromium severity High and CVSS 9.6, the flaw is notable because exploitation breaks out of the renderer sandbox rather than being contained by it. There is no public exploit identified at time of analysis, and CISA SSVC lists exploitation status as none.
In-sandbox arbitrary code execution in Google Chrome's V8 JavaScript engine (all versions prior to 152.0.7977.82) is achievable by a remote unauthenticated attacker who tricks a user into visiting a specially crafted HTML page. The underlying flaw is a CWE-367 Time-of-Check Time-of-Use (TOCTOU) race condition within V8, allowing the attacker to win a memory-access race and redirect execution flow inside the Chrome renderer sandbox. No public exploit code has been identified and CISA SSVC rates exploitation as 'none' at time of analysis, though the technical impact is rated 'total' within the sandbox boundary.
Use-after-free in Chrome's Compositing component (versions prior to 152.0.7977.82) enables a sandbox escape when chained with a renderer-process compromise - an attacker who has already gained control of the renderer can corrupt memory in the Compositing layer and execute arbitrary code outside Chrome's sandbox boundary on the host operating system. The CVSS S:C (scope changed) metric confirms this is a privilege-escalation-across-boundary primitive, delivering full C:H/I:H/A:H impact against the underlying OS. A vendor patch is available in Chrome 152.0.7977.82, and no public exploit has been identified at time of analysis.
System access-restriction bypass in Google Chrome's Network component (versions prior to 152.0.7977.82) lets a remote attacker use crafted network traffic to circumvent enforced access controls, stemming from incomplete resource cleanup (CWE-459). The flaw carries a Chromium-rated High severity and a CVSS of 9.1 reflecting high confidentiality and availability impact; no public exploit is identified at time of analysis and EPSS is low (0.22%). Google fixed it in the 2026-09 stable desktop channel update.
Remote denial of service in OpenVPN's reliability layer - the custom reliable-delivery sublayer underpinning the TLS control channel - allows unauthenticated network attackers to crash or hang OpenVPN daemons on versions up to 2.7.6 and 2.6.22 by triggering an unbounded TLS retransmission timeout or forcing acknowledgment of packets that cannot be outstanding. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VA:H) confirms full availability impact with no authentication, complexity, or user-interaction requirements, and downstream VPN clients lose connectivity when the concentrator is taken offline. No public exploit code or active exploitation (KEV) has been identified at time of analysis; vendor-released fix is available as OpenVPN v2.7.7.
Untrusted search path (CWE-426) in OpenVPN's Windows tapctl utility allows a local low-privileged attacker to substitute a malicious netsh.exe executable when tapctl invokes it without a fully-qualified path. Affected versions span OpenVPN 2.5.0-2.6.22 and 2.7_alpha1-2.7.6 on Windows; the fix was released in v2.7.7. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis.
Cross-cluster secret exfiltration in Rancher Manager before 2.15.1 allows any authenticated user with namespace-creation rights on one downstream cluster to read Project Secrets belonging to a completely separate downstream cluster. The secretsController propagates secrets based solely on the user-writable `field.cattle.io/projectId` annotation, skipping validation that the referenced project belongs to the same cluster - a classic CWE-639 insecure direct object reference pattern. No public exploit or CISA KEV listing has been identified at time of analysis; the vendor-confirmed fix is v2.15.1.
Token store authorization bypass in Rancher Manager before 2.15.1 allows any authenticated user to enumerate every other user's session tokens by supplying a crafted label selector to the ext.cattle.io/v1 Token API. The owner-scoped filter that restricts results to the calling user's own tokens is silently dropped when the caller supplies a label selector naming a different user, instead of returning an empty result set as intended. Exposed data includes token metadata and salted bearer-token hashes, creating an offline cracking risk. No public exploit is identified at time of analysis; a vendor-released patch is available in v2.15.1.
SAML assertion replay bypass in Rancher Manager before v2.15.1 allows unauthenticated network attackers to obtain additional authenticated management sessions as a victim user in high-availability deployments. The per-process in-memory cache that tracks consumed SAML assertion IDs - introduced by the CVE-2026-44946 fix - is not shared across pod replicas, so a captured assertion can be replayed once against each replica that has not yet seen it, yielding one unauthorized session per targeted replica. All SAML identity providers supported by Rancher are affected, and a vendor-released patch is available in v2.15.1. No public exploit code or CISA KEV listing has been identified at time of analysis.
Privilege escalation in Rancher Manager before 2.15.1 allows any user with delegated GlobalRole create or update permission to permanently destroy cluster-wide Kubernetes RBAC policies by hijacking arbitrary ClusterRoles. The GlobalRole controller resolved its target ClusterRole by reading the user-settable `authz.management.cattle.io/cr-name` annotation rather than deriving the name from the GlobalRole's own identity, enabling an authenticated attacker to redirect the controller at any ClusterRole - including `cluster-admin` - and overwrite its rules. The corrupted permissions persist in the Kubernetes object store even after the malicious GlobalRole is deleted, making this a durable, stealthy integrity attack. No public exploit has been identified at time of analysis.
Server-Side Request Forgery in Ollama versions 0.30.0 through 0.33.2 allows unauthenticated remote attackers to redirect the Ollama server's blob-download requests to arbitrary internal hosts, including cloud metadata endpoints such as the AWS instance metadata service. The flaw exists in the tensor-layer model pulling code path (x/transfer/download.go), where HTTP redirect destinations are not validated against an allowlist or the originating registry host. With no public exploit identified at time of analysis, the primary real-world impact is credential theft from cloud metadata services when Ollama runs on cloud-hosted infrastructure.
Race condition in the Linux kernel's ovpn (kernel-native OpenVPN) module allows a workqueue callback to continue executing within module text after that text has been freed during module teardown, creating a use-after-free condition in kernel space. The flaw exists because ovpn queues work items on the global system workqueue rather than a module-owned queue, leaving no driver-controlled drain point to guarantee all callbacks have exited before the module's code segment is released. Systems actively using the kernel-native ovpn module are at risk of kernel memory corruption or crash during module unload; no public exploit has been identified at time of analysis and EPSS is 0.20%.
NULL pointer dereference in the Linux kernel's psxpad-spi driver crashes the kernel when system suspend is triggered on hardware using SPI-connected PlayStation controllers. The probe() function in drivers/input/joystick/psxpad-spi.c omits the spi_set_drvdata() call that stores per-device state, so psxpad_spi_suspend() unconditionally dereferences a NULL pointer on suspend entry, causing a kernel panic. Patches are available across all active stable kernel branches (5.10 through 7.2); EPSS is 0.21% and no active exploitation has been identified.
Uninitialized pointer dereference in the Linux kernel's MediaTek GPU power-domain driver (`pmdomain/mediatek/mfg`) can trigger a kernel fault or incorrect OPP (Operating Performance Point) configuration on first device attachment. The `prev_o` variable in `mtk_mfg_attach_dev()` is read in a conditional branch on the first loop iteration before ever being assigned, meaning it holds an indeterminate stack value; if that value is non-NULL, the kernel dereferences a stale or garbage pointer. Affected versions span stable kernel trees from commit f08e7a4e8d6a through the fixed points in 7.1.10, 7.2, and 6.19. No public exploit code and no CISA KEV listing are present; EPSS at 0.19% (9th percentile) reflects minimal real-world exploitation interest.
Use-after-free in the Linux kernel's MediaTek power domain driver exposes kernel memory to potential corruption via a dangling device-tree node pointer. In scpsys_get_bus_protection_legacy(), two error paths call of_node_put() to release infracfg and SMI device-tree node references before those nodes are passed to dev_err_probe() with the %pOF format specifier; if the put drops the last reference, the formatter dereferences freed memory. Vendor patches are available for Linux 6.18.46, 7.1.10, and 7.2, and EPSS exploitation probability sits at 0.20% (10th percentile) with no confirmed active exploitation.
Out-of-bounds memory read in the Linux kernel's DRM HDMI connector subsystem allows a local, low-privileged user to potentially leak up to 32 bytes of adjacent kernel heap memory or trigger a page fault leading to kernel crash. The flaw exists in a helper function that copies audio infoframe data using the destination buffer size (60 bytes) rather than the source structure size (28 bytes), reading 32 bytes beyond the source allocation. No public exploit code exists, and EPSS sits at the 10th percentile; however, the availability impact is real - the overread can cross a page boundary and cause an access violation.
Out-of-bounds memory access in the Linux kernel's Loongson2 MMC driver allows a local authenticated user to corrupt kernel memory through incorrect scatterlist indexing in the mmc: loongson2 subsystem. The functions `ls2k0500_mmc_reorder_cmd_data()` and `ls2k2000_mmc_reorder_cmd_data()` use `for_each_sg()` to iterate a scatterlist but then incorrectly re-index the current `sg` pointer as if it were an array base (using `&sg[i]`), causing access to wrong or out-of-bounds scatterlist entries. This memory corruption can lead to full kernel compromise - confidentiality, integrity, and availability loss - on systems using Loongson LS2K0500 or LS2K2000 SoCs equipped with MMC storage. No public exploit has been identified at time of analysis.
Out-of-bounds table access in the Linux kernel fp9931 regulator driver exposes kernel memory to corruption via a malformed VPOS/VNEG voltage selector lookup table. The fp9931 driver's VPOSNEG_table[] contains two defects: a duplicate 7.04V entry that shifts all subsequent selector mappings by one, and a truncated table of only 41 entries instead of the required 64, meaning any selector value above 0x28 triggers an out-of-bounds access in kernel memory. Devices incorporating the FP9931 PMIC (a display-panel power regulator) running affected kernel versions are vulnerable; exploitation probability is very low (EPSS 0.20%, 10th percentile) with no public exploit and no confirmed active exploitation.
Out-of-bounds kernel memory read in the Linux kernel DRM log subsystem allows a local low-privileged user to potentially disclose kernel memory contents or crash the system. The flaw resides in drm_log_draw_kmsg_record(), where an unsigned integer underflow on a zero-length message causes an array access at offset UINT_MAX (0xFFFFFFFF) rather than a valid buffer position. No public exploit exists and EPSS sits at 0.20% (10th percentile), indicating low observed exploitation interest, though the kernel DRM panic-display path is reachable on any system with a GPU using the DRM framework.
Out-of-bounds array access in the Linux kernel's Thunderbolt driver exposes local low-privileged users to potential kernel memory corruption and privilege escalation. The flaw in tb_consumed_dp_bandwidth() sizes the group_reserved[] array at MAX_GROUPS entries (indices 0 through MAX_GROUPS-1) but uses Group IDs directly as indices, where valid IDs run from 1 through MAX_GROUPS - causing an off-by-one that reads and writes one element past the array boundary when the highest bandwidth group is processed. Patches are available across multiple stable kernel branches (6.12.x, 6.18.x, 7.1.x, 7.2), and no public exploit code has been identified at time of analysis.
Out-of-bounds kernel memory reads in the Linux kernel's ovpn (in-kernel OpenVPN) driver allow a local attacker with low privileges to leak kernel memory by abusing a missing ownership check on the sk_user_data socket field. The driver dereferences sk_user_data as an ovpn-internal structure without first confirming that encap_type identifies the socket as ovpn-owned, so when BPF SOCKMAP or another subsystem has populated sk_user_data with a different pointer type, ovpn misinterprets that memory and reads out of bounds. Affected kernels span 6.16 through pre-patch stable releases; no public exploit has been identified and EPSS sits at 0.21% (11th percentile), but kernel memory disclosure can seed further privilege escalation.
Use-after-free in the Linux kernel's pata_sl82c105 PATA bridge driver allows a local low-privileged user to potentially achieve kernel memory corruption leading to privilege escalation on systems equipped with the SL82C105 PCI bridge chip. The defect was introduced by commit 44c10138fd4b, which replaced a PCI configuration-space read with direct access to the cached revision field of a PCI device struct - but left that access after the reference was dropped via pci_dev_put(), creating a window where the bridge struct may be freed before the read occurs. Patches have been backported across multiple long-term stable kernel branches; no public exploit code or active exploitation has been identified at time of analysis.
Heap buffer overflow in zlib 1.3.1.2 through 1.3.2 allows remote attackers to corrupt memory via crafted input to applications using the non-blocking gzwrite API. The gz_vacate() function fails to bounds-check a memmove() when stale external buffer pointers are present after a write stall, reachable by calling gzprintf() or gzvprintf() in that state. A publicly available proof-of-concept exploit exists; no vendor-released patch has been identified at time of analysis.
Uninitialized heap memory disclosure in FreeRDP 3.0.0-3.30.0 exposes up to 576 bytes of stale server or proxy heap contents - potentially including cleartext credentials from prior RDP sessions - to any authenticated downstream RDP client. Three PDU-serialization functions in libfreerdp/core/info.c advance the stream write pointer with Stream_Seek over reserved padding bytes instead of zeroing them with Stream_Zero, leaving prior malloc heap contents in Save Session Info PDUs transmitted to clients. FreeRDP-based server deployments and freerdp-proxy instances are the affected roles; a vendor-confirmed fix ships in version 3.31.0, and no public exploit or active exploitation has been identified at time of analysis.
Host-parsing ambiguity in fast-uri allows attackers to silently bypass SSRF denylists, redirect allowlists, and proxy routing rules by submitting URLs containing unbalanced authority brackets. Affected versions 2.4.5, 3.1.6, and 4.1.3 of the Fastify ecosystem URI parsing library return the malformed bracket-containing string as the host without raising an error, while Node.js's URL implementation and downstream HTTP clients resolve the same string to an entirely different host. Any application that reads the fast-uri-parsed host to enforce a security policy, then passes the original URL to an HTTP client, evaluates its controls against a string that is never the host the request actually reaches.
Denial-of-service in the Go extended cryptography library's SSH package allows a malicious peer to deadlock an entire SSH connection by sending crafted RFC 4254 channel messages after a channel is established. All versions of golang.org/x/crypto/ssh below 0.56.0 are affected; the flaw manifests because unrecognized channel messages were buffered and allowed to block rather than being rejected as protocol errors. No public exploit or active exploitation has been identified, but the attack requires no privileges in the worst-case client scenario where a malicious SSH server targets a connecting client.
Connection deadlock in golang.org/x/crypto/ssh (all versions before 0.56.0) allows a malicious remote SSH peer to permanently freeze an SSH connection by flooding the incomingRequests queue of a channel that has been registered in the mux's chanList but not yet established. The attack exploits the absence of any established-state guard in the packet handler, causing a deadlock that renders the entire connection unresponsive without triggering an explicit teardown. No public exploit has been identified and no CISA KEV listing exists, but the network-accessible, no-authentication CVSS vector makes this straightforward to trigger against any Go application using this library for SSH.
Memory exhaustion via unbounded decompression in HTTPX2 (all versions before 2.12.0) allows any HTTP server the client contacts to cause severe memory pressure or out-of-memory process termination by returning a crafted compressed response body. The content decoders in `_decoders.py` call `decompress()` without a size cap, so a single 64 KiB compressed chunk can inflate to approximately 64 MiB in one allocation across gzip, deflate, brotli, and zstd encodings - all enabled by default. No active exploitation is confirmed in CISA KEV, and no public proof-of-concept is referenced, but the decompression-bomb technique is well understood and trivially reproducible.
HTTPX2's SOCKS5 proxy implementation omits TLS negotiation for WebSocket Secure (wss://) origins, exposing the full WebSocket session - opening handshake, query parameters, Authorization headers, cookies, and message frames - in plaintext to anyone who can observe or control the proxy path. Affected are applications using Client.websocket() or AsyncClient.websocket() in HTTPX2 versions 2.6.0 through 2.9.1 when routing through a SOCKS5 proxy. An adjacent-network attacker can passively eavesdrop on or actively modify traffic, and can impersonate the WebSocket server due to the missing certificate verification step. No public exploit code has been identified at time of analysis and this CVE does not appear in the CISA KEV catalog.
NULL pointer dereference in NGINX JavaScript (njs) crashes NGINX worker processes when an njs script calls ngx.fetch() against a server that returns a malformed HTTP response and subsequently reads Response.statusText on the result. All versions of F5's NGINX JavaScript module are listed as affected per the wildcard CPE, and the impact is confined entirely to the data plane - worker availability - with no control-plane, confidentiality, or integrity exposure. No public exploit code exists and the CVE is not listed in CISA KEV at time of analysis, but the network-accessible path and zero-privilege requirement make this a credible service-disruption risk for any NGINX deployment using njs-based outbound HTTP fetching.
NGINX JavaScript (njs) and QuickJS (qjs) fail open during the js_access phase when an exception is thrown inside an asynchronous request-body processing handler before an explicit access-denial is returned. The flaw (CWE-636, Not Failing Securely) allows unauthenticated remote attackers to bypass js_access controls entirely and reach protected backend resources. No public exploit code or CISA KEV listing has been identified at time of analysis; exploitation is bounded by the requirement for a specific async access-handler pattern.
Symlink traversal in util-linux's X-mount.subdir mount option allows a local unprivileged user with an fstab-authorized entry to redirect mount resolution to arbitrary host paths, achieving privilege escalation or container escape on Linux 6.15+ kernels. The root cause is that AT_SYMLINK_NOFOLLOW, passed to open_tree() in the detached-tree fast path, only blocks final-component symlinks - not intermediate path components - leaving an attacker who can plant a symlink in a middle directory able to substitute the intended subdirectory with any host path. Affected platforms include Red Hat Enterprise Linux 7-10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4; no public exploit has been identified at time of analysis.
Local privilege escalation in util-linux's SUID mount(8) binary exposes all major Red Hat Enterprise Linux versions (7-10), Red Hat Hardened Images, and OpenShift Container Platform 4 to root-level file ownership and permission manipulation by low-privileged local users. The flaw stems from a time-of-check to time-of-use (TOCTOU) race: mount(8) reads the bind-mount source from fstab but does not pin the resolved inode before issuing the privileged syscall, allowing an attacker with write access to the source path or a writable ancestor to substitute an arbitrary host directory. When fstab entries additionally specify X-mount.owner, X-mount.group, or X-mount.mode, root subsequently applies chown or chmod to the attacker-redirected path, completing the privilege escalation. No public exploit code or CISA KEV listing is identified at time of analysis.
Privilege escalation in util-linux's nsenter --join-cgroup option allows an unprivileged local user to move and terminate root-owned host processes by exploiting a persistent file descriptor opened as root that survives across namespace and credential changes. The kernel evaluates cgroup migration requests against the credentials held at fd-open time rather than the current caller's credentials, so any program that inherits the still-open cgroup.procs fd effectively retains root's cgroup management authority. Red Hat Enterprise Linux 7-10, Red Hat Hardened Images, and Red Hat OpenShift Container Platform 4 are confirmed affected; no public exploit has been identified at time of analysis.
Path traversal in wcurl for Windows allows a crafted URL containing percent-encoded backslashes to redirect a downloaded file to an attacker-controlled directory outside the user's intended destination. Affecting wcurl shipped with curl 8.14.0 through 8.21.0 and standalone wcurl 2024.12.08 through 2026.01.05, the flaw exploits Windows path-separator semantics: wcurl decodes %5C to a backslash, which Windows treats as a directory separator, causing file placement at an unintended filesystem path. No public exploit code and no active exploitation have been identified at time of analysis; vendor-released patches are available as of September 2, 2026.
Unauthenticated remote denial of service in Libreswan's pluto IKE daemon allows any network attacker to repeatedly crash and restart the VPN service by sending a malformed X.509 certificate in a CERT payload during IKE handshake negotiation. The crash is triggered by a reachable assertion in `add_decoded_cert()`: when NSS's `CERT_ExtractPublicKey()` receives a certificate with an invalid RSA exponent (e.g., zero), it returns NULL, which the FIPS-mode code path does not handle, causing the daemon to abort. The vendor explicitly confirms no remote code execution is possible; impact is limited to availability. No CISA KEV listing and no public exploit code have been identified at time of analysis.