Suse
Monthly
Cleartext transmission of sensitive information via the HttpsUpgrades component in Google Chrome on iOS (versions prior to 153.0.8010.36) exposes user data to network-positioned attackers through crafted traffic. The HttpsUpgrades mechanism, which is responsible for automatically promoting HTTP requests to HTTPS, fails under certain conditions on iOS, leaving sensitive request content unencrypted in transit. With no public exploit identified and high attack complexity required (network positioning), the real-world risk is moderate despite the C:H confidentiality impact.
Incorrect authorization in the WebAppInstalls subsystem of Google Chrome before 153.0.8010.36 enables a remote attacker who has already compromised the renderer process to bypass Chrome's site isolation via a crafted HTML page combined with social engineering. This is a chained, second-stage exploit - not a standalone vulnerability - requiring a prior renderer compromise before the WebAppInstalls flaw can be weaponized. Chromium rates it 'Medium' and EPSS sits at 0.19%, consistent with the high exploitation prerequisite; no public exploit code or CISA KEV listing exists.
Improper input validation in Chrome's built-in Passwords component (all versions prior to 153.0.8010.36) enables a remote, unauthenticated attacker to potentially leak sensitive stored credential data via crafted network traffic. The flaw is rated CVSS 5.9 (AC:H), with Chromium assigning a 'Medium' severity consistent with the meaningful exploitation complexity required. No public exploits or active exploitation have been identified at time of analysis.
Integer overflow in Chrome's WebRTC subsystem (prior to 153.0.8010.36) enables remote unauthenticated attackers to read memory within the browser's renderer sandbox by directing a victim to a crafted HTML page. The impact is confined to a partial confidentiality breach inside the sandbox - no integrity or availability compromise results. No public exploit code or CISA KEV listing exists at time of analysis, and EPSS at 0.24% places this in the bottom quartile of near-term exploitation likelihood.
Missing authorization in the Actor component of Google Chrome before 153.0.8010.36 allows remote attackers to read sensitive browser information by inducing a victim to visit a crafted HTML page. The flaw (CWE-862) reflects a failure to enforce access control checks in an internal Chromium IPC/actor abstraction, exposing confidential data without requiring credentials. With CVSS 6.5 (Medium), EPSS at 0.28% (20th percentile), no KEV listing, and no public exploit identified at time of analysis, this is a real but lower-priority information disclosure fixed in the September 2026 stable channel update.
Safebrowsing in Google Chrome prior to 153.0.8010.36 contains improper state validation (CWE-754) that allows a remote, unauthenticated attacker to bypass system access restrictions enforced by the Safe Browsing subsystem via a specially crafted HTML page. The bypass yields partial confidentiality and integrity impact (C:L/I:L) but no availability impact, consistent with circumventing protective filtering rather than achieving code execution. No active exploitation has been confirmed - EPSS is 0.24% (15th percentile) and the CVE is absent from CISA KEV - and Chromium's own severity assessment of 'Medium' aligns with the CVSS 5.4 score.
Cross-site request forgery in Chrome's DeviceBoundSessionCredentials (DBSC) subsystem allows a remote, unauthenticated attacker to bypass the web origin policy by luring a victim to a crafted HTML page. DeviceBoundSessionCredentials is Chrome's mechanism for cryptographically binding session tokens to a specific device, and the CSRF flaw undermines that origin-isolation guarantee, potentially allowing limited credential scope leakage (C:L). No public exploit code exists and no active exploitation has been confirmed; the EPSS score of 0.17% (7th percentile) and Chromium's own 'Medium' severity rating align with the modest real-world risk.
Origin-policy bypass in Google Chrome's Isolated component (prior to 153.0.8010.36) enables unauthenticated remote attackers to cross into privileged page contexts via a crafted HTML page requiring one click from the victim. Chromium rates this Medium severity, consistent with the CVSS 4.3 score and its limited confidentiality-only impact. No public exploit or active exploitation has been identified; EPSS at 0.19% (9th percentile) confirms very low near-term exploitation probability.
Cross-origin data disclosure in Google Chrome's WebGL subsystem (all versions prior to 153.0.8010.36) enables remote attackers to read residual GPU memory belonging to other origins by serving a crafted HTML page to an unpatched user. The root cause is CWE-908 (use of uninitialized resource): Chrome's WebGL implementation exposed GPU-side buffers to JavaScript before zeroing them, allowing fragments of prior rendering operations from cross-origin contexts to be read back. No active exploitation is confirmed (not in CISA KEV) and EPSS is low at 0.29%, consistent with the Medium Chromium severity rating and the limited, read-only impact.
Race condition in the Payments component of Google Chrome prior to 153.0.8010.36 enables remote attackers to spoof payment UI elements by delivering a crafted HTML page combined with social engineering, requiring user interaction to trigger the vulnerable timing window. The CWE-362 race condition in Chrome's Payment Request handling allows the attacker to substitute or overlay legitimate payment dialogs with fraudulent ones during the race window, potentially tricking victims into submitting payment credentials to attacker-controlled endpoints. No public exploit code exists and EPSS of 0.14% (4th percentile) reflects very low exploitation probability; Chromium rates this Medium severity.
Missing authorization in Chrome's FileSystem API allows a remote unauthenticated attacker to bypass system-level file access restrictions by luring a user to a crafted HTML page. Affected versions are all Chrome releases prior to 153.0.8010.36. The CVSS vector (I:H, C:N) indicates high integrity impact with no confidentiality exposure, meaning the attacker can write or modify files accessible through the FileSystem API without reading them. No public exploit has been identified and EPSS sits at 0.18% (7th percentile), consistent with Chromium's own 'Medium' severity rating.
Incorrect authorization in Chrome's Web Workers component enables remote unauthenticated attackers to bypass the browser's same-origin policy (web origin isolation) by inducing a victim to visit a crafted HTML page. All Google Chrome desktop versions prior to 153.0.8010.36 are affected. The impact is confined to partial cross-origin data read (C:L), with no integrity or availability consequences; no public exploit code and no active exploitation have been identified at time of analysis.
Google Chrome's Downloads subsystem on Android prior to 153.0.8010.36 improperly enforces its behavioral workflow (CWE-841), allowing a remote attacker to bypass Android system access restrictions via a crafted HTML page combined with social engineering. The attacker achieves high integrity impact - likely the ability to write files or trigger downloads that circumvent Android's permission and access control model - without any confidentiality or availability exposure. No public exploit exists and EPSS sits at 0.22% (13th percentile), placing real-world exploitation risk low despite the network-accessible attack vector.
LocalNetworkAccess missing authorization in Google Chrome before 153.0.8010.36 allows a renderer-compromised attacker to bypass Chrome's Private Network Access (PNA) restrictions via a crafted HTML page, enabling unauthorized requests to private network resources. This is a chained second-stage capability (CWE-862): the attacker must already control the renderer process before this bypass is reachable. No public exploits have been identified and EPSS sits at 0.25% (16th percentile), consistent with the significant chained-attack prerequisite; Chromium's own 'Medium' severity rating aligns with the CVSS 4.3 score.
Incorrect authorization in Chrome's FileAPI implementation allows remote attackers to bypass system-level file access restrictions, resulting in high-integrity impact against the vulnerable system. Exploitation requires social engineering - a user must visit a crafted HTML page - making it a targeted rather than opportunistic threat. No public exploit code or active exploitation has been identified; the Chromium team assigned a 'Medium' severity rating consistent with the CVSS 6.5 score, and a patch is available in Chrome 153.0.8010.36.
Chrome's Downloads subsystem in versions prior to 153.0.8010.36 contains an incorrect authorization check (CWE-863) that allows an attacker who has already compromised the renderer process to spoof download-related UI elements via a crafted HTML page. This vulnerability is a post-renderer-compromise chaining primitive - it cannot be exploited independently and must be paired with a separate renderer exploit. Chromium rates this 'Medium' and the CVSS score of 4.2 aligns with that assessment; EPSS at 0.17% (6th percentile) and absence from CISA KEV confirm low real-world exploitation probability.
Cross-origin data disclosure in Google Chrome's Extensions subsystem before version 153.0.8010.36 allows a remote attacker to obtain data from origins other than those the victim is currently browsing, contingent on successfully social-engineering the victim into installing a crafted malicious extension. The Chromium security team rated this Medium severity, consistent with the CVSS 4.3 score, and the EPSS probability of 0.23% confirms minimal current exploitation interest. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Sensitive information disclosure in Google Chrome's BackgroundFetch API allows a remote attacker who has already compromised the renderer process to leverage the BackgroundFetch service worker mechanism as a confused deputy, leaking sensitive data via a crafted HTML page. Affected versions are all Chrome releases prior to 153.0.8010.36; Chromium rates this Medium, consistent with the CVSS 5.3 score that reflects the high-complexity prerequisite of a compromised renderer. No public exploit code or active exploitation (CISA KEV) has been identified, and EPSS places exploitation probability at 0.20% (10th percentile).
Incomplete cleanup in Google Chrome's Extensions subsystem (versions prior to 153.0.8010.36) allows a remote attacker to bypass system access restrictions by delivering a crafted Chrome extension through social engineering. The flaw (CWE-459) leaves residual access state after extension processing, which a specially crafted extension exploits to obtain capabilities beyond its declared permissions - yielding a high integrity impact with no confidentiality or availability consequence. No active exploitation has been confirmed, and EPSS stands at 0.28%, placing this squarely in routine patch priority territory.
Observable discrepancy in Google Chrome's Autofill subsystem prior to version 153.0.8010.36 enables remote information disclosure through a crafted HTML page. An unauthenticated remote attacker who tricks a user into visiting a malicious page can exploit timing or behavioral side-channel differences (CWE-203) in Autofill's response to form field probes to infer sensitive data stored in Chrome's Autofill database - potentially including names, addresses, and saved form values. No public exploit code or active exploitation has been identified; EPSS stands at 0.29% (21st percentile), indicating low current exploitation pressure.
Out-of-bounds memory read in the WebView component of Google Chrome on Android allows an attacker who has already compromised the renderer process to escape the sandbox and read arbitrary memory via a crafted HTML page. The vulnerability is fixed in Chrome 153.0.8010.36; all prior Android Chrome versions are affected. No public exploit code has been identified and EPSS probability is low at 0.22%, though the scope-changed confidentiality impact is significant if renderer compromise is already achieved.
Type confusion in V8, Chrome's JavaScript engine, enables remote attackers to read memory within the Chrome sandbox by directing a user to a crafted HTML page. All Chrome desktop builds prior to 153.0.8010.36 are affected. The demonstrated impact is limited to partial in-sandbox memory disclosure - no integrity loss, no availability impact, and no sandbox escape is described. No public exploit is identified at time of analysis, and EPSS sits at 0.23%, reflecting low current real-world exploitation pressure.
Incorrect authorization in Chrome's Paint rendering component (versions prior to 153.0.8010.36) allows a remote attacker to read cross-origin data by directing a user to a crafted HTML page. The flaw (CWE-863) bypasses same-origin policy enforcement within the Paint subsystem, exposing rendered or pixel-level data from other origins to the attacking script. No public exploit has been identified and EPSS is low (0.22%), though Chromium's own 'High' severity rating substantially exceeds the NVD-assigned CVSS 4.3, signaling that the vendor considers the cross-origin data exposure more consequential than the base score reflects.
Missing authorization in Google Chrome's TrustedWebActivities (TWA) component on Android prior to version 153.0.8010.36 allows a local attacker to obtain sensitive information through a co-installed malicious application. The vulnerability stems from CWE-862 (Missing Authorization), where the TWA implementation fails to enforce adequate access controls between co-installed apps and Chrome's protected data. No public exploit code has been identified and the EPSS score places this at the 5th percentile, but the confidentiality impact is rated high given Chrome's potential access to session data, credentials, and browsing context.
Out-of-bounds read in ANGLE (Chrome's graphics translation layer) affects Google Chrome prior to 153.0.8010.36, enabling a remote attacker to read memory from the renderer process when a victim visits a crafted HTML page. The impact is limited to partial confidentiality disclosure (C:L) with no integrity or availability consequence, and the vulnerability is contained within the renderer sandbox (S:U). No public exploit code and no CISA KEV entry have been identified at time of analysis; vendor-released patch 153.0.8010.36 is available.
Web origin policy bypass in Google Chrome's Network component prior to 153.0.8010.36 allows remote attackers to violate cross-origin resource isolation by socially engineering victims into interacting with a crafted Chrome extension. The Same-Origin Policy (SOP) is a foundational browser security boundary; its bypass enables unauthorized cross-origin writes (I:H), potentially allowing attackers to tamper with resources on other origins. No public exploit code exists and EPSS is low (0.29%), though Chromium's own severity rating is 'High.'
Out-of-bounds memory read in the stb library's stbsp_vsnprintf function (stb_sprintf.h) at commit 31c1ad3 enables a denial-of-service condition when a consuming application passes attacker-controlled input to the function. The nothings/stb project is Sean Barrett's widely-vendored, public-domain, single-file C library suite embedded across game engines, imaging tools, and embedded systems. No public exploit code and no CISA KEV listing exist at time of analysis; the local attack vector and high attack complexity in the CVSS vector further limit practical exploitability.
Out-of-bounds read in stb_truetype's stbtt_GetGlyphShape function enables denial of service against any application that parses attacker-supplied TrueType font files using the nothings/stb library at commit 31c1ad3. The affected function reads glyph outline data from a crafted TTF without sufficient bounds validation, causing an abnormal read that crashes the host application. No public exploit code or CISA KEV listing was identified at time of analysis; CVSS 4.3 with UI:R reflects the realistic, user-triggered exposure.
Cross-site scripting in HTML::FormHandler before 0.410002 for Perl allows unauthenticated remote attackers to inject JavaScript into rendered pages when application field attributes are derived from user-controlled data. The root cause is the `process_attrs` method in `HTML/FormHandler/Render/Util.pm`, which formats attribute key-value pairs via `sprintf('%s="%s"', $attr, $value)` without encoding, letting a double-quote character break out of the attribute context and inject event handlers. The fix - encoding double quotes and ampersands via `HTML::Entities::encode_entities` - is confirmed merged and released as version 0.410002 on CPAN.
Reflected XSS in HTML::FormHandler before 0.410002 allows unauthenticated network attackers to inject JavaScript into rendered Perl web application pages by submitting form input containing script content. The Table form layout and Bootstrap 2 and 3 wrappers interpolated error strings - including rejected field values - directly into HTML without HTML-entity encoding, an incomplete fix relative to CVE-2026-19872 (which patched equivalent paths in other layouts in version 0.410000). No public exploit is identified and EPSS is 0.19%; risk is limited to applications using the three affected widget modules.
Stored and reflected cross-site scripting in HTML::FormHandler before 0.410002 (Perl/CPAN) allows attacker-influenced text in form option labels to execute arbitrary JavaScript in victims' browsers. The Select, RadioGroup, CheckboxGroup, and HorizCheckboxGroup widgets passed group labels and individual option labels directly into rendered HTML without applying HTML encoding, meaning any application that builds option lists from database records, user submissions, or dynamic sources exposes those label values as live markup. No public exploit code has been identified, but the patch commit and oss-security disclosure provide full technical detail on the affected rendering paths.
Cross-site scripting in HTML::FormHandler before 0.410000 (Perl/CPAN) allows unauthenticated network attackers to inject arbitrary JavaScript by submitting markup to any form field that triggers a validation error message embedding the submitted value. The library's rendering roles - Render::Simple, Render::Table, and Widget::Form::Simple - interpolate error strings directly into HTML error spans without entity encoding, so fields using check regexps, check lists, or type constraints expose the reflected XSS path. A stored XSS variant is also possible when applications persist and later re-render rejected form values. No public exploit is identified; vendor-released patch 0.410000 is available.
Xen hypervisor on x86 PV (paravirtualized) guest configurations contains a race condition in memory page lifecycle management that allows a guest to write to pages already scrubbed by Xen. When a PV guest frees a memory page, Xen defers the TLB flush until the page is re-used - but scrubbing occurs before that flush, creating a window in which the guest's stale TLB entry remains valid for a page now considered clean. This permits the attacking PV guest to inject arbitrary data into a scrubbed page, which may subsequently be allocated to another guest, undermining Xen's inter-VM memory isolation guarantee. No public exploit has been identified at time of analysis, and SSVC assessment rates exploitation as none and non-automatable.
Xen hypervisor contains a race condition (XSA-509) during guest termination that allows a guest to induce its device model to re-establish IRQ tracking structures for PCI devices after those structures have already been torn down in the cleanup sequence. At least one of the re-established tracking structures is never subsequently freed, resulting in a resource leak that can impact hypervisor availability. With a CVSS S:C/A:H impact and PR:L, a low-privileged guest user can affect the hypervisor domain - making this a guest-to-hypervisor containment issue, not merely a local self-DoS. EPSS is low at 0.17% and no public exploit or CISA KEV listing exists at time of analysis.
XML External Entity (XXE) injection in NanoXML 2.2.3 allows low-privileged network attackers to trigger unauthorized interaction with external systems or read internal resources, because the library enables external entity processing by default with no opt-out enforced at the API level. The affected product is identified under CPE cpe:2.3:a:cyberelf:nanoxml:*:*:*:*:*:*:*:* and was reported by TCS-CERT with an ENISA EUVD entry (EUVD-2026-72683). No public exploit code or active exploitation has been identified at time of analysis, and the CVSS 4.0 score of 5.3 reflects a moderate, subsequent-system confidentiality impact rather than direct system compromise.
Path traversal in the gnome-tweaks shell theme installer allows a local attacker who can persuade a user to install a crafted ZIP-packaged theme to write arbitrary files outside the intended ~/.themes directory. The flaw - a classic "zip slip" pattern (CWE-22) - exploits the absence of archive-member-path validation: malicious archives can embed ../ sequences, absolute paths, or symlink entries to redirect file writes anywhere the victim user can write. With user-level write access this can overwrite shell startup scripts, SSH authorized_keys, or desktop autostart entries, escalating to persistent code execution under the victim's account. No public exploit code or KEV listing exists at time of analysis; EPSS data was not provided.
Symlink-following race condition in GLib2's g_file_replace() allows a local attacker with write access to the destination directory to redirect privileged file writes to arbitrary files. When the G_FILE_CREATE_REPLACE_DESTINATION flag is set and creation of the .goutputstream-XXXXXX temporary file fails, GLib2 unlinks the destination and then recreates it without O_EXCL (exclusive creation) or symlink-safe open semantics, opening a TOCTOU race window. An attacker who wins this race by placing a symlink at the destination path can cause any process using this code path - potentially running with elevated privileges - to overwrite files the attacker cannot directly modify. No public exploit has been identified at time of analysis.
Heap-use-after-free in ImageMagick's PerlMagick Layer method allows an attacker supplying a crafted list of images to trigger memory access after deallocation, causing a crash. Affected versions include ImageMagick before 7.1.2-30 and the 6.9.x branch before 6.9.13-55. Impact is limited to denial of service (crash); no confidentiality or integrity compromise is possible from this flaw. No public exploit code or active exploitation has been identified at time of analysis.
Heap-use-after-free in ImageMagick's PerlMagick Perl binding crashes the host process via a crafted call to the GetList method. Affected versions span the 6.9.x branch before 6.9.13-55 and the 7.x branch before 7.1.2-30. Impact is limited to denial of service (process crash); no confidentiality or integrity compromise has been demonstrated. No public exploit code or active exploitation is identified at time of analysis.
Memory exhaustion in ImageMagick's MSL image decoder affects versions before 7.1.2-30 (v7 branch) and 6.9.13-55 (v6 branch), enabling unauthenticated network attackers to degrade or crash image-processing services by submitting crafted MSL files that trigger unbounded heap allocation without deallocation. The root cause (CWE-400, Uncontrolled Resource Consumption) lies in the MSL decoder's failure to free allocated memory on certain code paths, allowing cumulative heap exhaustion across repeated requests. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis; the CVSS 4.0 score of 6.3 (Medium) reflects limited availability-only impact with elevated attack complexity.
Memory budget exhaustion in ImageMagick's OpenPixelCache allows remote unauthenticated attackers to cause a process-level denial of service by repeatedly triggering internal cache operation failures. Affected versions span both the 7.x branch (before 7.1.2-30) and the legacy 6.x branch (before 6.9.13-55), covering a large installed base of web services that process user-supplied images. The vulnerability stems from improper cleanup of memory accounting state on error paths, making the failure accumulative rather than self-correcting. No public exploit or CISA KEV listing has been identified at time of analysis.
Use-after-free (CWE-415/416) in the OpenVPN ovpn-dco-win Windows kernel Data Channel Offload driver versions 2.5.0 through 2.8.6 enables a local authenticated user to trigger a system crash by sending crafted control messages to the driver. Because the flaw resides in a kernel-mode driver, successful exploitation causes a full system crash (BSOD), affecting availability of the entire host. No public exploit code or active exploitation has been identified at time of analysis.
The Windows interactive service in OpenVPN 2.4.0 through 2.6.22 allows local authenticated users to bypass the trusted configuration directory constraint by exploiting incorrect file path validation logic (CWE-73), causing the privileged service to load attacker-controlled VPN configurations. The impact is integrity-focused: a successful bypass enables substitution of legitimate VPN configuration with a malicious one, potentially redirecting traffic, disabling certificate validation, or weakening encryption enforced by an administrator. No public exploit code or CISA KEV listing has been identified at time of analysis, and exploitation is limited to the local Windows context.
CVE-2026-85218 is attributed to Ubuntu per the vendor intelligence source, but no public description, CVSS score, CWE classification, or technical detail has been released at the time of this analysis. The vulnerability type, affected component, attack vector, and impact are all unknown. No meaningful synthesis of exploitation conditions or attacker capability is possible from available data alone.
Stack buffer underflow in polkit's read_cookie() function, introduced as a regression by the fix for CVE-2026-4897, exposes Linux systems to potential memory corruption and privilege escalation via polkit's D-Bus authentication path. Systems that applied the CVE-2026-4897 patch are specifically affected, meaning the remediation for a prior vulnerability created new exposure. No public exploit code has been identified at time of analysis, but the target (polkit, a setuid/privileged authorization daemon) makes this class of memory corruption high-consequence.
Undefined memory access in PKCS#7 container parsing affects an Ubuntu-packaged cryptographic library, potentially enabling denial of service or information disclosure when processing malformed PKCS#7 input. The specific library (OpenSSL, GnuTLS, NSS, or Linux kernel PKCS#7 module) is not identified in available data. No patch version, CVSS score, or CWE classification was provided, leaving severity and exploitability largely unquantified at time of analysis.
NULL-pointer dereference in code handling Authentication and Key Agreement (AKA) Synchronization-Failure messages causes a process crash when a malformed or unexpected AKA-Synchronization-Failure response is processed. The vulnerability affects software that implements 3GPP AKA authentication - a protocol used in mobile network authentication (3G/4G/5G) and EAP-AKA for Wi-Fi/IMS - as packaged by Ubuntu. No public exploit or CISA KEV listing has been identified at time of analysis, and the primary real-world impact is denial of service via crash of the authentication handling daemon.
Unbounded iteration during PKCS#7 container decryption exposes affected systems to a denial-of-service condition where a crafted cryptographic payload causes a parsing loop to run without termination bounds. The specific library or package is not identified in the available intelligence - Ubuntu is the reporting source, suggesting this affects a cryptographic library they distribute (candidates include OpenSSL, GnuTLS, NSS, or similar). An attacker able to supply a malformed PKCS#7 container to a vulnerable parsing routine can exhaust CPU resources and halt service availability. No public exploit has been identified at time of analysis, and no CVSS score or severity rating has been assigned.
CVE-2026-71223 is reported via Ubuntu's security channels, but no description, CVSS score, CWE classification, or affected product detail is available in the current dataset. The vulnerability cannot be characterized beyond its Ubuntu vendor attribution. Security teams should consult Ubuntu Security Notices (USN) or the Ubuntu CVE tracker directly for authoritative details before assessing exposure or priority.
SSE event injection in the h3 JavaScript HTTP framework (npm package h3js/h3, versions before 1.15.9 stable and before 2.0.1-rc.17 beta) allows remote attackers to inject arbitrary Server-Sent Events by embedding carriage return (`\r`) characters in `data` or `comment` fields that are reflected into the EventStream. Because the HTML SSE specification treats `\r` as a valid line terminator, browsers parse injected `\r` sequences as field boundaries - enabling attackers to spoof event types, split a single push call into multiple distinct browser-parsed events, or escape comment fields to deliver fake data. This is a confirmed incomplete-fix bypass: the prior commit `7791538` sanitized `\n` and `\r` only for `id` and `event` fields while leaving `data` and `comment` unprotected. No public exploit has been confirmed in CISA KEV; however, the GHSA advisory (GHSA-4hxc-9384-m385) includes a proof-of-concept server setup demonstrating the bypass.
Open redirect in h3 (h3js) before 2.0.1-rc.18 allows unauthenticated remote attackers to redirect victims to arbitrary external domains by crafting a Referer header containing a same-origin URL with a double-slash path segment (e.g., http://target.com//evil.com/phish). The redirectBack() utility passes the WHATWG origin check - because the parsed origin is correctly identified as the target domain - but emits the raw pathname //evil.com/phish as the Location header, which browsers interpret as a protocol-relative redirect to an attacker-controlled site. A proof-of-concept is included in the GHSA advisory; no active exploitation (CISA KEV) has been identified at time of analysis.
Remote memory disclosure in libpcap's rpcap client allows a malicious or compromised rpcap server to cause a connected client to read up to 20 bytes beyond the end of its receive buffer and treat that data as captured packet content. All libpcap versions with rpcap support are affected per CPE cpe:2.3:a:the_tcpdump_group:libpcap:*:*:*:*:*:*:*:*. The root cause is an incorrect boundary check in pcap_read_nocb_remote(): the RPCAP_MSG_PACKET caplen field was validated against the full payload length rather than against the payload length minus the fixed-size RPCAP_MSG_PACKET header, creating a window of up to sizeof(struct rpcap_pkthdr) bytes that could be read beyond the buffer. No public exploit or CISA KEV listing is identified at time of analysis.
Memory exhaustion in libpcap's rpcapd remote capture daemon allows an authenticated remote client to degrade or crash the service by triggering unreleased heap allocations. The daemon allocates up to 65536 bytes per RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message processed in daemon_unpackapplyfilter(), but the bf_insns BPF filter instruction array is never freed on any code path - success or error - under the pre-patch logic. A malicious rpcap client can accelerate memory exhaustion by rapidly submitting filter-update or capture-start requests. No active exploitation is confirmed and no public exploit code exists at time of analysis.
Infinite-loop denial of service in libpcap's BPF interpreter allows a local low-privileged attacker to hang any process that evaluates a crafted BPF filter program via pcap_offline_filter(). The 'ja L' (jump always) instruction stores its target offset as a signed integer, enabling backward jumps that implement looping, but the interpreter imposed no cap on iterations, so a self-referential or backward-looping filter causes unbounded CPU consumption. The upstream fix (commit ff3c83475a) introduces a MAX_BACKWARD_JUMPS limit of 64 per packet and adds validator rejection of self-jumps; no active exploitation or public exploit code has been identified at time of analysis.
Division by zero in libpcap's BPF interpreter can crash any application using the library when processing a crafted filter program containing 'div #k' or 'mod #k' ALU instructions with k=0. The flaw, reported by The Tcpdump Group, affects all versions of libpcap (cpe:2.3:a:the_tcpdump_group:libpcap) and requires a locally-supplied malicious BPF filter - typically via an application that accepts user-controlled filter expressions and calls pcap_offline_filter(). No public exploit or active exploitation has been identified; the vendor has released a patch via GitHub commit.
Process termination via crafted BPF filter in libpcap allows a local attacker with low privileges to crash any application linked against the library by supplying a filter program containing an invalid BPF opcode. The BPF interpreter in bpf_filter.c calls abort() on encountering an unrecognized opcode - a reachable assertion (CWE-617) that converts a defensive check into a denial-of-service vector. No public exploit or active exploitation has been identified; the Tcpdump Group has released a patch replacing abort() with a safe return 0.
Out-of-bounds memory reads in libpcap's userland BPF interpreter allow a local attacker who can supply a crafted filter program to drive the interpreter's program counter past the end of the filter buffer, reading up to 32 GiB of surrounding process memory on 64-bit systems or the entire address space on 32-bit systems. All libpcap versions tracked under CPE cpe:2.3:a:the_tcpdump_group:libpcap are affected; The Tcpdump Group has published a fix via commit d3f358d3. No active exploitation has been confirmed and no public exploit exists; the vulnerability is restricted to uncommon application patterns that pass raw BPF bytecode directly to the interpreter without prior validation.
Out-of-bounds read in libxml2's XML regular expression parser exposes all versions before 2.15.4 to a limited availability impact when processing malformed character group patterns. The NXT(index) macro in xmlregexp.c performed a direct array dereference without verifying the index stays within the parsed string's length, allowing a specially crafted regexp pattern to read one byte past the allocated buffer. The vendor-released fix in v2.15.4 adds a bounds guard returning 0 for out-of-bounds accesses; no public exploit is identified at time of analysis.
Flatpak's `org.freedesktop.Flatpak.SystemHelper` D-Bus service contains a TOCTOU race condition in the `Deploy()` function where a privileged `chmod` executes before OSTree repository validation completes, allowing a local low-privileged attacker to redirect symlinks to arbitrary system files within that timing window. A successful exploit can yield high-confidentiality impact (reading privileged files) and limited integrity and availability impact (CVSS C:H/I:L/A:L), as the unguarded chmod can be inherited by attacker-controlled symlink targets. No public exploit code or CISA KEV listing has been identified at time of analysis, and the High attack complexity (AC:H) reflects the precision timing required to win the race.
Heap out-of-bounds read in libtpms during TPM 2.0 state restoration allows an adjacent unauthenticated attacker to crash the swtpm process and deny TPM services to dependent virtual machines. The flaw arises in the state-blob parser: an attacker-controlled oversized skip-block length drives the internal INT32 size counter negative; subsequent bounds checks cast that counter to UINT32, wrapping it to a large positive value and bypassing the check, which then drives the parser to read memory outside the heap buffer. Vendor and upstream commit confirm the impact is denial of service only - no data corruption or information disclosure was confirmed. No public exploit or CISA KEV listing has been identified.
Memory exhaustion via compression bomb in undici's decompress interceptor (versions 7.15.0-<7.29.1 and 8.0.0-<8.10.2) allows a malicious or compromised upstream HTTP server to crash a Node.js process by returning a small compressed payload that expands to hundreds of megabytes in client heap memory. The interceptor respects the untrusted Content-Encoding header and enforces no ceiling on total decompressed output size, making the attack purely asymmetric - a kilobyte-scale upstream payload can trigger unbounded client-side allocation. No public exploit has been identified and the vulnerability is not in the CISA KEV catalog; fixed versions 7.29.1 and 8.10.2 are available.
Chunked-body handling in undici's dump interceptor triggers a double-completion assertion that tears down the underlying TCP connection while returning a misleading success status to the application. Affected are undici versions 7.1.0 through 7.29.0 and 8.0.0 through 8.10.1; fixed releases 7.29.1 and 8.10.2 are available. No public exploit or active exploitation has been identified; the CVSS 3.7 score reflects the high attack complexity and limited real-world impact relative to the narrow exploitation path.
undici's cache interceptor incorrectly permits responses to unsafe HTTP methods - POST, PUT, DELETE, and PATCH - to be stored and later replayed, because the skip-list that gates caching is built by subtracting configured methods from the safe-method set rather than by positively excluding all non-safe methods, leaving unsafe methods unguarded. A remote origin that returns a heuristically cacheable status code or an explicit Cache-Control directive in response to a state-changing request causes undici to store that response; all subsequent client requests to the same path using the same method are then served from the stale cache entry without ever reaching the origin. Affected versions span undici 7.0.0 through 7.29.0 and 8.0.0 through 8.10.1; no public exploit has been identified at time of analysis.
Out-of-bounds read in Valkey's cluster slot-migration RDB loader allows a network-positioned attacker to crash affected servers by supplying a crafted RDB file with a truncated `job_name` field in an `RDB_OPCODE_SLOT_IMPORT` record. Valkey versions up to 9.0.4 and 9.1.0 running in cluster mode are affected; the vulnerable `createSlotImportJob()` function in `src/cluster_migrateslots.c` performs a fixed 40-byte `memcpy` without first validating that the loaded `job_name` is exactly `CLUSTER_NAMELEN` bytes, triggering CWE-125 on undersized input. A public proof-of-concept is available via GitHub issue #4207, and patched releases 9.0.5 and 9.1.1 are confirmed available.
HTTP/2 flow-control window mismanagement in libsoup (GNOME's HTTP client/server library) allows a malicious HTTP/2 server to abort a connecting client process or crash its HTTP/2 session. When the client sends a request body sourced from a non-pollable GInputStream, libsoup buffers the data before transmission; a server that then shrinks SETTINGS_INITIAL_WINDOW_SIZE causes the client to copy the full pre-buffered payload into a now-undersized DATA callback without a runtime bounds check, triggering a reachable assertion abort (CWE-617). No public exploit has been identified at time of analysis, and the high-complexity timing requirement constrains practical exploitation.
Integer overflow in Corosync's membership commit token processing crashes the daemon on 32-bit cluster nodes, enabling a denial-of-service attack from any adjacent network host. The CWE-190 flaw causes the length validation to be bypassed on 32-bit systems where arithmetic wraps before the bounds check is applied, resulting in an out-of-bounds memory access that kills the Corosync process. Modern 64-bit deployments of the same packages are explicitly not affected, substantially narrowing real-world exposure despite the CVSS 6.5 rating; no public exploit code or CISA KEV listing exists at time of analysis.
Key-ID (kid) bypass in the jwcrypto Python JOSE library allows an attacker who holds any valid key within a JWK set to forge a General JSON Serialization JWS that satisfies verification for a different kid, effectively impersonating another tenant, user, or service. Affected deployments include Red Hat Ansible Automation Platform 2, RHEL 7-10, Red Hat OpenShift AI (RHOAI), and Red Hat OpenStack Platform 16.2, wherever jwcrypto performs JWS signature verification with kid-based authorization. No public exploit or CISA KEV listing has been identified at time of analysis, and the EPSS score is not provided, but the integrity impact is high for multi-tenant architectures.
Web origin policy bypass in Google Chrome for Android (prior to 152.0.7977.82) exploits a use-of-released-resource flaw (CWE-672) in the browser's mobile implementation, allowing cross-origin content manipulation via a crafted HTML page. An attacker must socially engineer a victim into visiting the malicious page, after which Chrome's Same-Origin Policy enforcement can be circumvented, resulting in high integrity impact against targeted origins. No public exploit code or CISA KEV listing exists at time of analysis; Google issued a fix in stable channel release 152.0.7977.82.
Buffer overread in OpenVPN's Windows service component (`openvpnserv`) through version 2.7.6 exposes adjacent service process memory or crashes the service when NRPT domain entries containing Internationalized Domain Names (IDN) with UTF-8 encoding trigger an incorrect buffer size calculation (CWE-131). The flaw is Windows-specific and confined to split-DNS configurations that include non-ASCII domain names; Linux and macOS deployments are unaffected. The issue was discovered by BreachX Zero Day Labs and fixed in OpenVPN v2.7.7, co-released with four other security patches. No public exploit code or CISA KEV listing has been identified at time of analysis.
Windows openvpnserv path-validation bypass in OpenVPN 2.7_alpha1 through 2.7.6 allows a low-privileged local user to circumvent administrative config-path restrictions by using '/' instead of '\' as a directory separator. Windows path-validation APIs do not recognize '/' as a separator while file-open APIs do, creating a mismatch exploitable to load a user-controlled OpenVPN config file that administrators have explicitly prohibited. Fixed in v2.7.7; no public exploit identified at time of analysis.
Path traversal in OpenList prior to v4.2.3 allows any authenticated user holding the PermAddOfflineDownload permission to write, truncate, or overwrite arbitrary files accessible to the OpenList process via the SimpleHttp offline-download tool. The attacker controls a remote HTTP server that returns a crafted Content-Disposition header containing path-traversal sequences; OpenList uses the attacker-supplied filename without containment validation to construct a file path via filepath.Join relative to a per-task temporary directory, allowing traversal outside that directory. No public exploit has been identified at time of analysis, though the GHSA advisory details the exact vulnerable function and the fix commit is publicly accessible, significantly lowering the effort required to develop one.
Heap buffer out-of-bounds write in the MongoDB C Driver's BSON-to-JSON conversion helpers allows an unauthenticated party who supplies document content to corrupt a small number of bytes past the end of a heap-allocated buffer. The overflow is triggered specifically when a binary BSON field is being encoded and the caller has configured a maximum output length that causes the conversion to be cut short. Impact is limited to a low-integrity write of a few bytes adjacent to the buffer - no confidentiality loss and no confirmed availability impact - but heap corruption in native C applications can have unpredictable downstream effects depending on allocator layout. No public exploit code and no CISA KEV listing exist at time of analysis.
Fleet controller's Helm template preprocessing exposes cluster metadata and internal DNS topology to any user with write access to a GitRepo-tracked repository, via a server-side request forgery path that abuses name resolution. Affected releases span all active branches from 0.12.0 through 0.16.0, with patched builds released across each branch. The DNS-based exfiltration channel is notable because it can remain effective in environments where outbound TCP/UDP egress is otherwise restricted, making standard network perimeter controls insufficient as a compensating measure.
Identity injection in Rancher Manager before 2.15.1 allows a privileged Rancher user to hijack any other user's account by overwriting immutable identity provider fields. The /v3/users update API failed to strip principalIds and username from update payloads, so a user holding the update verb on users.management.cattle.io could inject an external IdP principal they control into any target account. The next time the attacker authenticates via that injected IdP principal, Rancher binds the session to the victim's account and the attacker inherits all its role bindings. No public exploit is identified at time of analysis, and a vendor patch is available in version 2.15.1.
Heap out-of-bounds read in FreeRDP before 3.31.0 allows a malicious RDP server to trigger adjacent heap memory disclosure and potential client instability by sending a crafted RFX_AVC444_BITMAP_STREAM during AVC444 chroma reconstruction. The root cause is a missing row-index bounds check in `general_ChromaV1ToYUV444` (and its ARM NEON and x86 SSE4.1 counterparts), causing `memcpy` to read past the end of the allocated luma plane when the server specifies specific frame geometry. No public exploit or CISA KEV listing exists at time of analysis; a confirmed fix is available in the 3.31.0 release.
HTTP request smuggling in pydantic's HTTPX2 Python client library, all versions prior to 2.11.0, arises because Request._prepare() in _models.py appends a Content-Length header even when a caller-supplied Transfer-Encoding header is already present, producing HTTP/1.1 requests with two conflicting framing headers simultaneously. Downstream intermediaries such as reverse proxies or API gateways that resolve the Content-Length vs. Transfer-Encoding ambiguity differently from the upstream server can misparse request boundaries, enabling request smuggling or connection desynchronization affecting co-located sessions. No public exploit code or active exploitation has been identified at time of analysis; a vendor-released patch is available in v2.11.0.
CRLF injection in httpx2 (pydantic's next-generation Python HTTP client) before v2.11.0 allows manipulation of multipart/form-data part headers when attacker-controlled data reaches the `content_type` or custom headers fields of the `files=` parameter. `FileField.render_headers()` in `_multipart.py` interpolates these values directly into raw header bytes without stripping CR or LF characters, enabling injection of fabricated headers into multipart parts. No public exploit is identified at time of analysis; the vendor-released patch is v2.11.0.
Credential exfiltration via SSRF in LiteLLM proxy (AI Gateway) prior to versions 1.88.6 and 1.96.2 allows any authenticated proxy user to redirect outbound LLM provider calls to an attacker-controlled endpoint, causing the proxy to transmit its operator-configured API keys and other secrets to that destination. Vulnerable routing parameters - api_base, base_url, model_list, fallbacks, and litellm_credential_name - could be injected through nested request fields, path values, and bracket-notation form data that incomplete validation across five proxy modules failed to intercept. No public exploit code has been identified at time of analysis; vendor-released patches are confirmed at versions 1.88.6 and 1.96.2.
Uncontrolled memory consumption in Grafana's SQL macro evaluator allows authenticated users with query permissions to crash the Grafana server process via a bypass of the prior CVE-2026-33375 fix. By injecting the timeGroup macro into a WHERE clause rather than the positions blocked by the original regex-based patch, attackers cause the macro evaluator to consume unbounded memory, terminating the server. Microsoft SQL Server, PostgreSQL, and MySQL data source integrations are all confirmed affected, and no public exploit has been identified at time of analysis.
SAML assertion replay in Grafana Enterprise allows an attacker who obtains a valid signed SAML response to authenticate as the victim user without re-authenticating. When the non-default `allow_idp_initiated` setting is enabled, the SAML library globally suppresses InResponseTo field validation - a field that normally binds each response to a specific originating request - across all SAML flows, including SP-initiated ones that should still enforce it. This anti-replay failure is limited to Grafana Enterprise with an explicit opt-in configuration change; Grafana OSS is unaffected. No public exploit code has been identified and the vulnerability is not in CISA KEV.
Address bar spoofing in Google Chrome's Downloads component (versions prior to 152.0.7977.75) is reachable only after an attacker has already achieved code execution within the renderer process, enabling display of a falsified URL via a crafted HTML page. The flaw stems from improper privilege management (CWE-269) in the Downloads subsystem, which fails to enforce the privilege boundary between the sandboxed renderer and the trusted browser UI. No public exploit identified at time of analysis; a vendor-released patch is available in Chrome 152.0.7977.75.
Origin policy bypass in Google Chrome's Omnibox (address bar) prior to version 152.0.7977.75 allows remote attackers using social engineering and crafted network traffic to circumvent the web same-origin policy, enabling high-integrity cross-origin manipulation. The CVSS vector confirms user interaction is required, meaning the attack cannot be fully automated and depends on deceiving the victim. No public exploit code or active exploitation has been identified; EPSS of 0.16% (5th percentile) reflects low near-term exploitation probability.
Address bar spoofing in Google Chrome prior to version 152.0.7977.75 allows remote attackers to visually deceive users by manipulating the browser's fullscreen UI state through a crafted HTML page, causing the displayed origin to misrepresent the actual site being visited. The vulnerability (CWE-451) carries no confidentiality or availability impact - the risk is exclusively to integrity through phishing enablement, consistent with Google's own 'Low' severity designation. No public exploit code has been identified, and exploitation probability is negligible at EPSS 0.16% (6th percentile).
Information leakage via the MediaCapture component in Google Chrome prior to 152.0.7977.75 enables a remote attacker to exfiltrate sensitive browser-side data by directing a user to a specially crafted HTML page. The flaw (CWE-200) resides in Chrome's implementation of the W3C Media Capture API, which handles camera, microphone, and display-capture device access, and may expose captured media content or associated metadata beyond the intended same-origin boundary. Google has released a fix in the 152.0.7977.75 stable channel update; no public exploit has been identified at time of analysis.
Incorrect authorization in Chrome's SiteSettings component (versions prior to 152.0.7977.75) allows an unauthenticated remote attacker to bypass system-level site access restrictions via a crafted HTML page. The attack requires user interaction - the victim must visit the attacker-controlled page - and the primary impact is a high-integrity authorization bypass, potentially allowing a malicious page to access system resources (e.g., geolocation, camera) that should be gated behind permission prompts. No public exploit code or CISA KEV listing exists at time of analysis, and the EPSS score of 0.17% reflects low near-term exploitation probability despite Chrome's massive global deployment footprint.
Address bar spoofing in Google Chrome on Android prior to version 152.0.7977.75 allows an unauthenticated remote attacker to deceive users about their true browsing origin by triggering fullscreen mode via a crafted HTML page. The flaw (CWE-451: UI Misrepresentation of Critical Information) causes the address bar to be suppressed or misrepresented during fullscreen transitions, creating a reliable phishing surface on Android devices. Google has released a fix in Chrome 152.0.7977.75; no public exploit code has been identified and CISA SSVC rates exploitation as none at time of analysis.
Confused deputy vulnerability in Chrome's CredentialProvider component on Windows allows a remote attacker who has already established renderer process compromise to leak sensitive credential information via a crafted HTML page. Affected versions are Chrome for Windows prior to 152.0.7977.75. Google rates this Low severity internally, though the CVSS Confidentiality impact is scored High due to the potential for credential disclosure; the AC:H vector reflects the significant prerequisite of prior renderer compromise. No public exploit code or CISA KEV listing has been identified at time of analysis.
Incorrect authorization in Chrome's Autofill component on Android (prior to 152.0.7977.75) exposes sensitive Autofill-stored data - potentially including saved credentials, addresses, or payment details - to a remote attacker who can socially engineer a victim into visiting a crafted HTML page. The flaw is platform-specific to Chrome on Android and requires active user interaction via social engineering, which limits real-world exploitation friction somewhat. Google has released a patch and no public exploit code has been identified at time of analysis.
Missing FileSystem authorization in Google Chrome prior to 152.0.7977.75 enables sensitive information disclosure through a two-stage attack chain requiring a pre-compromised renderer process and social engineering. The CVSS vector (AC:H/UI:R) accurately reflects the chained nature of exploitation: an attacker must first compromise the renderer, then induce user interaction with a crafted HTML page to bypass FileSystem access controls. No public exploit or CISA KEV listing has been identified at time of analysis; the vendor patch was released in the September 2026 stable channel update.
CVE-2026-80220 is attributed to Ubuntu but carries no description, CVSS score, CWE classification, or technical details in the available intelligence data. Without a vulnerability description or affected component, no characterization of attacker capability, impact type, or affected user population is possible. Security teams should monitor Ubuntu Security Notices directly at ubuntu.com/security/notices for authoritative details as they become available.
Cleartext transmission of sensitive information via the HttpsUpgrades component in Google Chrome on iOS (versions prior to 153.0.8010.36) exposes user data to network-positioned attackers through crafted traffic. The HttpsUpgrades mechanism, which is responsible for automatically promoting HTTP requests to HTTPS, fails under certain conditions on iOS, leaving sensitive request content unencrypted in transit. With no public exploit identified and high attack complexity required (network positioning), the real-world risk is moderate despite the C:H confidentiality impact.
Incorrect authorization in the WebAppInstalls subsystem of Google Chrome before 153.0.8010.36 enables a remote attacker who has already compromised the renderer process to bypass Chrome's site isolation via a crafted HTML page combined with social engineering. This is a chained, second-stage exploit - not a standalone vulnerability - requiring a prior renderer compromise before the WebAppInstalls flaw can be weaponized. Chromium rates it 'Medium' and EPSS sits at 0.19%, consistent with the high exploitation prerequisite; no public exploit code or CISA KEV listing exists.
Improper input validation in Chrome's built-in Passwords component (all versions prior to 153.0.8010.36) enables a remote, unauthenticated attacker to potentially leak sensitive stored credential data via crafted network traffic. The flaw is rated CVSS 5.9 (AC:H), with Chromium assigning a 'Medium' severity consistent with the meaningful exploitation complexity required. No public exploits or active exploitation have been identified at time of analysis.
Integer overflow in Chrome's WebRTC subsystem (prior to 153.0.8010.36) enables remote unauthenticated attackers to read memory within the browser's renderer sandbox by directing a victim to a crafted HTML page. The impact is confined to a partial confidentiality breach inside the sandbox - no integrity or availability compromise results. No public exploit code or CISA KEV listing exists at time of analysis, and EPSS at 0.24% places this in the bottom quartile of near-term exploitation likelihood.
Missing authorization in the Actor component of Google Chrome before 153.0.8010.36 allows remote attackers to read sensitive browser information by inducing a victim to visit a crafted HTML page. The flaw (CWE-862) reflects a failure to enforce access control checks in an internal Chromium IPC/actor abstraction, exposing confidential data without requiring credentials. With CVSS 6.5 (Medium), EPSS at 0.28% (20th percentile), no KEV listing, and no public exploit identified at time of analysis, this is a real but lower-priority information disclosure fixed in the September 2026 stable channel update.
Safebrowsing in Google Chrome prior to 153.0.8010.36 contains improper state validation (CWE-754) that allows a remote, unauthenticated attacker to bypass system access restrictions enforced by the Safe Browsing subsystem via a specially crafted HTML page. The bypass yields partial confidentiality and integrity impact (C:L/I:L) but no availability impact, consistent with circumventing protective filtering rather than achieving code execution. No active exploitation has been confirmed - EPSS is 0.24% (15th percentile) and the CVE is absent from CISA KEV - and Chromium's own severity assessment of 'Medium' aligns with the CVSS 5.4 score.
Cross-site request forgery in Chrome's DeviceBoundSessionCredentials (DBSC) subsystem allows a remote, unauthenticated attacker to bypass the web origin policy by luring a victim to a crafted HTML page. DeviceBoundSessionCredentials is Chrome's mechanism for cryptographically binding session tokens to a specific device, and the CSRF flaw undermines that origin-isolation guarantee, potentially allowing limited credential scope leakage (C:L). No public exploit code exists and no active exploitation has been confirmed; the EPSS score of 0.17% (7th percentile) and Chromium's own 'Medium' severity rating align with the modest real-world risk.
Origin-policy bypass in Google Chrome's Isolated component (prior to 153.0.8010.36) enables unauthenticated remote attackers to cross into privileged page contexts via a crafted HTML page requiring one click from the victim. Chromium rates this Medium severity, consistent with the CVSS 4.3 score and its limited confidentiality-only impact. No public exploit or active exploitation has been identified; EPSS at 0.19% (9th percentile) confirms very low near-term exploitation probability.
Cross-origin data disclosure in Google Chrome's WebGL subsystem (all versions prior to 153.0.8010.36) enables remote attackers to read residual GPU memory belonging to other origins by serving a crafted HTML page to an unpatched user. The root cause is CWE-908 (use of uninitialized resource): Chrome's WebGL implementation exposed GPU-side buffers to JavaScript before zeroing them, allowing fragments of prior rendering operations from cross-origin contexts to be read back. No active exploitation is confirmed (not in CISA KEV) and EPSS is low at 0.29%, consistent with the Medium Chromium severity rating and the limited, read-only impact.
Race condition in the Payments component of Google Chrome prior to 153.0.8010.36 enables remote attackers to spoof payment UI elements by delivering a crafted HTML page combined with social engineering, requiring user interaction to trigger the vulnerable timing window. The CWE-362 race condition in Chrome's Payment Request handling allows the attacker to substitute or overlay legitimate payment dialogs with fraudulent ones during the race window, potentially tricking victims into submitting payment credentials to attacker-controlled endpoints. No public exploit code exists and EPSS of 0.14% (4th percentile) reflects very low exploitation probability; Chromium rates this Medium severity.
Missing authorization in Chrome's FileSystem API allows a remote unauthenticated attacker to bypass system-level file access restrictions by luring a user to a crafted HTML page. Affected versions are all Chrome releases prior to 153.0.8010.36. The CVSS vector (I:H, C:N) indicates high integrity impact with no confidentiality exposure, meaning the attacker can write or modify files accessible through the FileSystem API without reading them. No public exploit has been identified and EPSS sits at 0.18% (7th percentile), consistent with Chromium's own 'Medium' severity rating.
Incorrect authorization in Chrome's Web Workers component enables remote unauthenticated attackers to bypass the browser's same-origin policy (web origin isolation) by inducing a victim to visit a crafted HTML page. All Google Chrome desktop versions prior to 153.0.8010.36 are affected. The impact is confined to partial cross-origin data read (C:L), with no integrity or availability consequences; no public exploit code and no active exploitation have been identified at time of analysis.
Google Chrome's Downloads subsystem on Android prior to 153.0.8010.36 improperly enforces its behavioral workflow (CWE-841), allowing a remote attacker to bypass Android system access restrictions via a crafted HTML page combined with social engineering. The attacker achieves high integrity impact - likely the ability to write files or trigger downloads that circumvent Android's permission and access control model - without any confidentiality or availability exposure. No public exploit exists and EPSS sits at 0.22% (13th percentile), placing real-world exploitation risk low despite the network-accessible attack vector.
LocalNetworkAccess missing authorization in Google Chrome before 153.0.8010.36 allows a renderer-compromised attacker to bypass Chrome's Private Network Access (PNA) restrictions via a crafted HTML page, enabling unauthorized requests to private network resources. This is a chained second-stage capability (CWE-862): the attacker must already control the renderer process before this bypass is reachable. No public exploits have been identified and EPSS sits at 0.25% (16th percentile), consistent with the significant chained-attack prerequisite; Chromium's own 'Medium' severity rating aligns with the CVSS 4.3 score.
Incorrect authorization in Chrome's FileAPI implementation allows remote attackers to bypass system-level file access restrictions, resulting in high-integrity impact against the vulnerable system. Exploitation requires social engineering - a user must visit a crafted HTML page - making it a targeted rather than opportunistic threat. No public exploit code or active exploitation has been identified; the Chromium team assigned a 'Medium' severity rating consistent with the CVSS 6.5 score, and a patch is available in Chrome 153.0.8010.36.
Chrome's Downloads subsystem in versions prior to 153.0.8010.36 contains an incorrect authorization check (CWE-863) that allows an attacker who has already compromised the renderer process to spoof download-related UI elements via a crafted HTML page. This vulnerability is a post-renderer-compromise chaining primitive - it cannot be exploited independently and must be paired with a separate renderer exploit. Chromium rates this 'Medium' and the CVSS score of 4.2 aligns with that assessment; EPSS at 0.17% (6th percentile) and absence from CISA KEV confirm low real-world exploitation probability.
Cross-origin data disclosure in Google Chrome's Extensions subsystem before version 153.0.8010.36 allows a remote attacker to obtain data from origins other than those the victim is currently browsing, contingent on successfully social-engineering the victim into installing a crafted malicious extension. The Chromium security team rated this Medium severity, consistent with the CVSS 4.3 score, and the EPSS probability of 0.23% confirms minimal current exploitation interest. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Sensitive information disclosure in Google Chrome's BackgroundFetch API allows a remote attacker who has already compromised the renderer process to leverage the BackgroundFetch service worker mechanism as a confused deputy, leaking sensitive data via a crafted HTML page. Affected versions are all Chrome releases prior to 153.0.8010.36; Chromium rates this Medium, consistent with the CVSS 5.3 score that reflects the high-complexity prerequisite of a compromised renderer. No public exploit code or active exploitation (CISA KEV) has been identified, and EPSS places exploitation probability at 0.20% (10th percentile).
Incomplete cleanup in Google Chrome's Extensions subsystem (versions prior to 153.0.8010.36) allows a remote attacker to bypass system access restrictions by delivering a crafted Chrome extension through social engineering. The flaw (CWE-459) leaves residual access state after extension processing, which a specially crafted extension exploits to obtain capabilities beyond its declared permissions - yielding a high integrity impact with no confidentiality or availability consequence. No active exploitation has been confirmed, and EPSS stands at 0.28%, placing this squarely in routine patch priority territory.
Observable discrepancy in Google Chrome's Autofill subsystem prior to version 153.0.8010.36 enables remote information disclosure through a crafted HTML page. An unauthenticated remote attacker who tricks a user into visiting a malicious page can exploit timing or behavioral side-channel differences (CWE-203) in Autofill's response to form field probes to infer sensitive data stored in Chrome's Autofill database - potentially including names, addresses, and saved form values. No public exploit code or active exploitation has been identified; EPSS stands at 0.29% (21st percentile), indicating low current exploitation pressure.
Out-of-bounds memory read in the WebView component of Google Chrome on Android allows an attacker who has already compromised the renderer process to escape the sandbox and read arbitrary memory via a crafted HTML page. The vulnerability is fixed in Chrome 153.0.8010.36; all prior Android Chrome versions are affected. No public exploit code has been identified and EPSS probability is low at 0.22%, though the scope-changed confidentiality impact is significant if renderer compromise is already achieved.
Type confusion in V8, Chrome's JavaScript engine, enables remote attackers to read memory within the Chrome sandbox by directing a user to a crafted HTML page. All Chrome desktop builds prior to 153.0.8010.36 are affected. The demonstrated impact is limited to partial in-sandbox memory disclosure - no integrity loss, no availability impact, and no sandbox escape is described. No public exploit is identified at time of analysis, and EPSS sits at 0.23%, reflecting low current real-world exploitation pressure.
Incorrect authorization in Chrome's Paint rendering component (versions prior to 153.0.8010.36) allows a remote attacker to read cross-origin data by directing a user to a crafted HTML page. The flaw (CWE-863) bypasses same-origin policy enforcement within the Paint subsystem, exposing rendered or pixel-level data from other origins to the attacking script. No public exploit has been identified and EPSS is low (0.22%), though Chromium's own 'High' severity rating substantially exceeds the NVD-assigned CVSS 4.3, signaling that the vendor considers the cross-origin data exposure more consequential than the base score reflects.
Missing authorization in Google Chrome's TrustedWebActivities (TWA) component on Android prior to version 153.0.8010.36 allows a local attacker to obtain sensitive information through a co-installed malicious application. The vulnerability stems from CWE-862 (Missing Authorization), where the TWA implementation fails to enforce adequate access controls between co-installed apps and Chrome's protected data. No public exploit code has been identified and the EPSS score places this at the 5th percentile, but the confidentiality impact is rated high given Chrome's potential access to session data, credentials, and browsing context.
Out-of-bounds read in ANGLE (Chrome's graphics translation layer) affects Google Chrome prior to 153.0.8010.36, enabling a remote attacker to read memory from the renderer process when a victim visits a crafted HTML page. The impact is limited to partial confidentiality disclosure (C:L) with no integrity or availability consequence, and the vulnerability is contained within the renderer sandbox (S:U). No public exploit code and no CISA KEV entry have been identified at time of analysis; vendor-released patch 153.0.8010.36 is available.
Web origin policy bypass in Google Chrome's Network component prior to 153.0.8010.36 allows remote attackers to violate cross-origin resource isolation by socially engineering victims into interacting with a crafted Chrome extension. The Same-Origin Policy (SOP) is a foundational browser security boundary; its bypass enables unauthorized cross-origin writes (I:H), potentially allowing attackers to tamper with resources on other origins. No public exploit code exists and EPSS is low (0.29%), though Chromium's own severity rating is 'High.'
Out-of-bounds memory read in the stb library's stbsp_vsnprintf function (stb_sprintf.h) at commit 31c1ad3 enables a denial-of-service condition when a consuming application passes attacker-controlled input to the function. The nothings/stb project is Sean Barrett's widely-vendored, public-domain, single-file C library suite embedded across game engines, imaging tools, and embedded systems. No public exploit code and no CISA KEV listing exist at time of analysis; the local attack vector and high attack complexity in the CVSS vector further limit practical exploitability.
Out-of-bounds read in stb_truetype's stbtt_GetGlyphShape function enables denial of service against any application that parses attacker-supplied TrueType font files using the nothings/stb library at commit 31c1ad3. The affected function reads glyph outline data from a crafted TTF without sufficient bounds validation, causing an abnormal read that crashes the host application. No public exploit code or CISA KEV listing was identified at time of analysis; CVSS 4.3 with UI:R reflects the realistic, user-triggered exposure.
Cross-site scripting in HTML::FormHandler before 0.410002 for Perl allows unauthenticated remote attackers to inject JavaScript into rendered pages when application field attributes are derived from user-controlled data. The root cause is the `process_attrs` method in `HTML/FormHandler/Render/Util.pm`, which formats attribute key-value pairs via `sprintf('%s="%s"', $attr, $value)` without encoding, letting a double-quote character break out of the attribute context and inject event handlers. The fix - encoding double quotes and ampersands via `HTML::Entities::encode_entities` - is confirmed merged and released as version 0.410002 on CPAN.
Reflected XSS in HTML::FormHandler before 0.410002 allows unauthenticated network attackers to inject JavaScript into rendered Perl web application pages by submitting form input containing script content. The Table form layout and Bootstrap 2 and 3 wrappers interpolated error strings - including rejected field values - directly into HTML without HTML-entity encoding, an incomplete fix relative to CVE-2026-19872 (which patched equivalent paths in other layouts in version 0.410000). No public exploit is identified and EPSS is 0.19%; risk is limited to applications using the three affected widget modules.
Stored and reflected cross-site scripting in HTML::FormHandler before 0.410002 (Perl/CPAN) allows attacker-influenced text in form option labels to execute arbitrary JavaScript in victims' browsers. The Select, RadioGroup, CheckboxGroup, and HorizCheckboxGroup widgets passed group labels and individual option labels directly into rendered HTML without applying HTML encoding, meaning any application that builds option lists from database records, user submissions, or dynamic sources exposes those label values as live markup. No public exploit code has been identified, but the patch commit and oss-security disclosure provide full technical detail on the affected rendering paths.
Cross-site scripting in HTML::FormHandler before 0.410000 (Perl/CPAN) allows unauthenticated network attackers to inject arbitrary JavaScript by submitting markup to any form field that triggers a validation error message embedding the submitted value. The library's rendering roles - Render::Simple, Render::Table, and Widget::Form::Simple - interpolate error strings directly into HTML error spans without entity encoding, so fields using check regexps, check lists, or type constraints expose the reflected XSS path. A stored XSS variant is also possible when applications persist and later re-render rejected form values. No public exploit is identified; vendor-released patch 0.410000 is available.
Xen hypervisor on x86 PV (paravirtualized) guest configurations contains a race condition in memory page lifecycle management that allows a guest to write to pages already scrubbed by Xen. When a PV guest frees a memory page, Xen defers the TLB flush until the page is re-used - but scrubbing occurs before that flush, creating a window in which the guest's stale TLB entry remains valid for a page now considered clean. This permits the attacking PV guest to inject arbitrary data into a scrubbed page, which may subsequently be allocated to another guest, undermining Xen's inter-VM memory isolation guarantee. No public exploit has been identified at time of analysis, and SSVC assessment rates exploitation as none and non-automatable.
Xen hypervisor contains a race condition (XSA-509) during guest termination that allows a guest to induce its device model to re-establish IRQ tracking structures for PCI devices after those structures have already been torn down in the cleanup sequence. At least one of the re-established tracking structures is never subsequently freed, resulting in a resource leak that can impact hypervisor availability. With a CVSS S:C/A:H impact and PR:L, a low-privileged guest user can affect the hypervisor domain - making this a guest-to-hypervisor containment issue, not merely a local self-DoS. EPSS is low at 0.17% and no public exploit or CISA KEV listing exists at time of analysis.
XML External Entity (XXE) injection in NanoXML 2.2.3 allows low-privileged network attackers to trigger unauthorized interaction with external systems or read internal resources, because the library enables external entity processing by default with no opt-out enforced at the API level. The affected product is identified under CPE cpe:2.3:a:cyberelf:nanoxml:*:*:*:*:*:*:*:* and was reported by TCS-CERT with an ENISA EUVD entry (EUVD-2026-72683). No public exploit code or active exploitation has been identified at time of analysis, and the CVSS 4.0 score of 5.3 reflects a moderate, subsequent-system confidentiality impact rather than direct system compromise.
Path traversal in the gnome-tweaks shell theme installer allows a local attacker who can persuade a user to install a crafted ZIP-packaged theme to write arbitrary files outside the intended ~/.themes directory. The flaw - a classic "zip slip" pattern (CWE-22) - exploits the absence of archive-member-path validation: malicious archives can embed ../ sequences, absolute paths, or symlink entries to redirect file writes anywhere the victim user can write. With user-level write access this can overwrite shell startup scripts, SSH authorized_keys, or desktop autostart entries, escalating to persistent code execution under the victim's account. No public exploit code or KEV listing exists at time of analysis; EPSS data was not provided.
Symlink-following race condition in GLib2's g_file_replace() allows a local attacker with write access to the destination directory to redirect privileged file writes to arbitrary files. When the G_FILE_CREATE_REPLACE_DESTINATION flag is set and creation of the .goutputstream-XXXXXX temporary file fails, GLib2 unlinks the destination and then recreates it without O_EXCL (exclusive creation) or symlink-safe open semantics, opening a TOCTOU race window. An attacker who wins this race by placing a symlink at the destination path can cause any process using this code path - potentially running with elevated privileges - to overwrite files the attacker cannot directly modify. No public exploit has been identified at time of analysis.
Heap-use-after-free in ImageMagick's PerlMagick Layer method allows an attacker supplying a crafted list of images to trigger memory access after deallocation, causing a crash. Affected versions include ImageMagick before 7.1.2-30 and the 6.9.x branch before 6.9.13-55. Impact is limited to denial of service (crash); no confidentiality or integrity compromise is possible from this flaw. No public exploit code or active exploitation has been identified at time of analysis.
Heap-use-after-free in ImageMagick's PerlMagick Perl binding crashes the host process via a crafted call to the GetList method. Affected versions span the 6.9.x branch before 6.9.13-55 and the 7.x branch before 7.1.2-30. Impact is limited to denial of service (process crash); no confidentiality or integrity compromise has been demonstrated. No public exploit code or active exploitation is identified at time of analysis.
Memory exhaustion in ImageMagick's MSL image decoder affects versions before 7.1.2-30 (v7 branch) and 6.9.13-55 (v6 branch), enabling unauthenticated network attackers to degrade or crash image-processing services by submitting crafted MSL files that trigger unbounded heap allocation without deallocation. The root cause (CWE-400, Uncontrolled Resource Consumption) lies in the MSL decoder's failure to free allocated memory on certain code paths, allowing cumulative heap exhaustion across repeated requests. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis; the CVSS 4.0 score of 6.3 (Medium) reflects limited availability-only impact with elevated attack complexity.
Memory budget exhaustion in ImageMagick's OpenPixelCache allows remote unauthenticated attackers to cause a process-level denial of service by repeatedly triggering internal cache operation failures. Affected versions span both the 7.x branch (before 7.1.2-30) and the legacy 6.x branch (before 6.9.13-55), covering a large installed base of web services that process user-supplied images. The vulnerability stems from improper cleanup of memory accounting state on error paths, making the failure accumulative rather than self-correcting. No public exploit or CISA KEV listing has been identified at time of analysis.
Use-after-free (CWE-415/416) in the OpenVPN ovpn-dco-win Windows kernel Data Channel Offload driver versions 2.5.0 through 2.8.6 enables a local authenticated user to trigger a system crash by sending crafted control messages to the driver. Because the flaw resides in a kernel-mode driver, successful exploitation causes a full system crash (BSOD), affecting availability of the entire host. No public exploit code or active exploitation has been identified at time of analysis.
The Windows interactive service in OpenVPN 2.4.0 through 2.6.22 allows local authenticated users to bypass the trusted configuration directory constraint by exploiting incorrect file path validation logic (CWE-73), causing the privileged service to load attacker-controlled VPN configurations. The impact is integrity-focused: a successful bypass enables substitution of legitimate VPN configuration with a malicious one, potentially redirecting traffic, disabling certificate validation, or weakening encryption enforced by an administrator. No public exploit code or CISA KEV listing has been identified at time of analysis, and exploitation is limited to the local Windows context.
CVE-2026-85218 is attributed to Ubuntu per the vendor intelligence source, but no public description, CVSS score, CWE classification, or technical detail has been released at the time of this analysis. The vulnerability type, affected component, attack vector, and impact are all unknown. No meaningful synthesis of exploitation conditions or attacker capability is possible from available data alone.
Stack buffer underflow in polkit's read_cookie() function, introduced as a regression by the fix for CVE-2026-4897, exposes Linux systems to potential memory corruption and privilege escalation via polkit's D-Bus authentication path. Systems that applied the CVE-2026-4897 patch are specifically affected, meaning the remediation for a prior vulnerability created new exposure. No public exploit code has been identified at time of analysis, but the target (polkit, a setuid/privileged authorization daemon) makes this class of memory corruption high-consequence.
Undefined memory access in PKCS#7 container parsing affects an Ubuntu-packaged cryptographic library, potentially enabling denial of service or information disclosure when processing malformed PKCS#7 input. The specific library (OpenSSL, GnuTLS, NSS, or Linux kernel PKCS#7 module) is not identified in available data. No patch version, CVSS score, or CWE classification was provided, leaving severity and exploitability largely unquantified at time of analysis.
NULL-pointer dereference in code handling Authentication and Key Agreement (AKA) Synchronization-Failure messages causes a process crash when a malformed or unexpected AKA-Synchronization-Failure response is processed. The vulnerability affects software that implements 3GPP AKA authentication - a protocol used in mobile network authentication (3G/4G/5G) and EAP-AKA for Wi-Fi/IMS - as packaged by Ubuntu. No public exploit or CISA KEV listing has been identified at time of analysis, and the primary real-world impact is denial of service via crash of the authentication handling daemon.
Unbounded iteration during PKCS#7 container decryption exposes affected systems to a denial-of-service condition where a crafted cryptographic payload causes a parsing loop to run without termination bounds. The specific library or package is not identified in the available intelligence - Ubuntu is the reporting source, suggesting this affects a cryptographic library they distribute (candidates include OpenSSL, GnuTLS, NSS, or similar). An attacker able to supply a malformed PKCS#7 container to a vulnerable parsing routine can exhaust CPU resources and halt service availability. No public exploit has been identified at time of analysis, and no CVSS score or severity rating has been assigned.
CVE-2026-71223 is reported via Ubuntu's security channels, but no description, CVSS score, CWE classification, or affected product detail is available in the current dataset. The vulnerability cannot be characterized beyond its Ubuntu vendor attribution. Security teams should consult Ubuntu Security Notices (USN) or the Ubuntu CVE tracker directly for authoritative details before assessing exposure or priority.
SSE event injection in the h3 JavaScript HTTP framework (npm package h3js/h3, versions before 1.15.9 stable and before 2.0.1-rc.17 beta) allows remote attackers to inject arbitrary Server-Sent Events by embedding carriage return (`\r`) characters in `data` or `comment` fields that are reflected into the EventStream. Because the HTML SSE specification treats `\r` as a valid line terminator, browsers parse injected `\r` sequences as field boundaries - enabling attackers to spoof event types, split a single push call into multiple distinct browser-parsed events, or escape comment fields to deliver fake data. This is a confirmed incomplete-fix bypass: the prior commit `7791538` sanitized `\n` and `\r` only for `id` and `event` fields while leaving `data` and `comment` unprotected. No public exploit has been confirmed in CISA KEV; however, the GHSA advisory (GHSA-4hxc-9384-m385) includes a proof-of-concept server setup demonstrating the bypass.
Open redirect in h3 (h3js) before 2.0.1-rc.18 allows unauthenticated remote attackers to redirect victims to arbitrary external domains by crafting a Referer header containing a same-origin URL with a double-slash path segment (e.g., http://target.com//evil.com/phish). The redirectBack() utility passes the WHATWG origin check - because the parsed origin is correctly identified as the target domain - but emits the raw pathname //evil.com/phish as the Location header, which browsers interpret as a protocol-relative redirect to an attacker-controlled site. A proof-of-concept is included in the GHSA advisory; no active exploitation (CISA KEV) has been identified at time of analysis.
Remote memory disclosure in libpcap's rpcap client allows a malicious or compromised rpcap server to cause a connected client to read up to 20 bytes beyond the end of its receive buffer and treat that data as captured packet content. All libpcap versions with rpcap support are affected per CPE cpe:2.3:a:the_tcpdump_group:libpcap:*:*:*:*:*:*:*:*. The root cause is an incorrect boundary check in pcap_read_nocb_remote(): the RPCAP_MSG_PACKET caplen field was validated against the full payload length rather than against the payload length minus the fixed-size RPCAP_MSG_PACKET header, creating a window of up to sizeof(struct rpcap_pkthdr) bytes that could be read beyond the buffer. No public exploit or CISA KEV listing is identified at time of analysis.
Memory exhaustion in libpcap's rpcapd remote capture daemon allows an authenticated remote client to degrade or crash the service by triggering unreleased heap allocations. The daemon allocates up to 65536 bytes per RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message processed in daemon_unpackapplyfilter(), but the bf_insns BPF filter instruction array is never freed on any code path - success or error - under the pre-patch logic. A malicious rpcap client can accelerate memory exhaustion by rapidly submitting filter-update or capture-start requests. No active exploitation is confirmed and no public exploit code exists at time of analysis.
Infinite-loop denial of service in libpcap's BPF interpreter allows a local low-privileged attacker to hang any process that evaluates a crafted BPF filter program via pcap_offline_filter(). The 'ja L' (jump always) instruction stores its target offset as a signed integer, enabling backward jumps that implement looping, but the interpreter imposed no cap on iterations, so a self-referential or backward-looping filter causes unbounded CPU consumption. The upstream fix (commit ff3c83475a) introduces a MAX_BACKWARD_JUMPS limit of 64 per packet and adds validator rejection of self-jumps; no active exploitation or public exploit code has been identified at time of analysis.
Division by zero in libpcap's BPF interpreter can crash any application using the library when processing a crafted filter program containing 'div #k' or 'mod #k' ALU instructions with k=0. The flaw, reported by The Tcpdump Group, affects all versions of libpcap (cpe:2.3:a:the_tcpdump_group:libpcap) and requires a locally-supplied malicious BPF filter - typically via an application that accepts user-controlled filter expressions and calls pcap_offline_filter(). No public exploit or active exploitation has been identified; the vendor has released a patch via GitHub commit.
Process termination via crafted BPF filter in libpcap allows a local attacker with low privileges to crash any application linked against the library by supplying a filter program containing an invalid BPF opcode. The BPF interpreter in bpf_filter.c calls abort() on encountering an unrecognized opcode - a reachable assertion (CWE-617) that converts a defensive check into a denial-of-service vector. No public exploit or active exploitation has been identified; the Tcpdump Group has released a patch replacing abort() with a safe return 0.
Out-of-bounds memory reads in libpcap's userland BPF interpreter allow a local attacker who can supply a crafted filter program to drive the interpreter's program counter past the end of the filter buffer, reading up to 32 GiB of surrounding process memory on 64-bit systems or the entire address space on 32-bit systems. All libpcap versions tracked under CPE cpe:2.3:a:the_tcpdump_group:libpcap are affected; The Tcpdump Group has published a fix via commit d3f358d3. No active exploitation has been confirmed and no public exploit exists; the vulnerability is restricted to uncommon application patterns that pass raw BPF bytecode directly to the interpreter without prior validation.
Out-of-bounds read in libxml2's XML regular expression parser exposes all versions before 2.15.4 to a limited availability impact when processing malformed character group patterns. The NXT(index) macro in xmlregexp.c performed a direct array dereference without verifying the index stays within the parsed string's length, allowing a specially crafted regexp pattern to read one byte past the allocated buffer. The vendor-released fix in v2.15.4 adds a bounds guard returning 0 for out-of-bounds accesses; no public exploit is identified at time of analysis.
Flatpak's `org.freedesktop.Flatpak.SystemHelper` D-Bus service contains a TOCTOU race condition in the `Deploy()` function where a privileged `chmod` executes before OSTree repository validation completes, allowing a local low-privileged attacker to redirect symlinks to arbitrary system files within that timing window. A successful exploit can yield high-confidentiality impact (reading privileged files) and limited integrity and availability impact (CVSS C:H/I:L/A:L), as the unguarded chmod can be inherited by attacker-controlled symlink targets. No public exploit code or CISA KEV listing has been identified at time of analysis, and the High attack complexity (AC:H) reflects the precision timing required to win the race.
Heap out-of-bounds read in libtpms during TPM 2.0 state restoration allows an adjacent unauthenticated attacker to crash the swtpm process and deny TPM services to dependent virtual machines. The flaw arises in the state-blob parser: an attacker-controlled oversized skip-block length drives the internal INT32 size counter negative; subsequent bounds checks cast that counter to UINT32, wrapping it to a large positive value and bypassing the check, which then drives the parser to read memory outside the heap buffer. Vendor and upstream commit confirm the impact is denial of service only - no data corruption or information disclosure was confirmed. No public exploit or CISA KEV listing has been identified.
Memory exhaustion via compression bomb in undici's decompress interceptor (versions 7.15.0-<7.29.1 and 8.0.0-<8.10.2) allows a malicious or compromised upstream HTTP server to crash a Node.js process by returning a small compressed payload that expands to hundreds of megabytes in client heap memory. The interceptor respects the untrusted Content-Encoding header and enforces no ceiling on total decompressed output size, making the attack purely asymmetric - a kilobyte-scale upstream payload can trigger unbounded client-side allocation. No public exploit has been identified and the vulnerability is not in the CISA KEV catalog; fixed versions 7.29.1 and 8.10.2 are available.
Chunked-body handling in undici's dump interceptor triggers a double-completion assertion that tears down the underlying TCP connection while returning a misleading success status to the application. Affected are undici versions 7.1.0 through 7.29.0 and 8.0.0 through 8.10.1; fixed releases 7.29.1 and 8.10.2 are available. No public exploit or active exploitation has been identified; the CVSS 3.7 score reflects the high attack complexity and limited real-world impact relative to the narrow exploitation path.
undici's cache interceptor incorrectly permits responses to unsafe HTTP methods - POST, PUT, DELETE, and PATCH - to be stored and later replayed, because the skip-list that gates caching is built by subtracting configured methods from the safe-method set rather than by positively excluding all non-safe methods, leaving unsafe methods unguarded. A remote origin that returns a heuristically cacheable status code or an explicit Cache-Control directive in response to a state-changing request causes undici to store that response; all subsequent client requests to the same path using the same method are then served from the stale cache entry without ever reaching the origin. Affected versions span undici 7.0.0 through 7.29.0 and 8.0.0 through 8.10.1; no public exploit has been identified at time of analysis.
Out-of-bounds read in Valkey's cluster slot-migration RDB loader allows a network-positioned attacker to crash affected servers by supplying a crafted RDB file with a truncated `job_name` field in an `RDB_OPCODE_SLOT_IMPORT` record. Valkey versions up to 9.0.4 and 9.1.0 running in cluster mode are affected; the vulnerable `createSlotImportJob()` function in `src/cluster_migrateslots.c` performs a fixed 40-byte `memcpy` without first validating that the loaded `job_name` is exactly `CLUSTER_NAMELEN` bytes, triggering CWE-125 on undersized input. A public proof-of-concept is available via GitHub issue #4207, and patched releases 9.0.5 and 9.1.1 are confirmed available.
HTTP/2 flow-control window mismanagement in libsoup (GNOME's HTTP client/server library) allows a malicious HTTP/2 server to abort a connecting client process or crash its HTTP/2 session. When the client sends a request body sourced from a non-pollable GInputStream, libsoup buffers the data before transmission; a server that then shrinks SETTINGS_INITIAL_WINDOW_SIZE causes the client to copy the full pre-buffered payload into a now-undersized DATA callback without a runtime bounds check, triggering a reachable assertion abort (CWE-617). No public exploit has been identified at time of analysis, and the high-complexity timing requirement constrains practical exploitation.
Integer overflow in Corosync's membership commit token processing crashes the daemon on 32-bit cluster nodes, enabling a denial-of-service attack from any adjacent network host. The CWE-190 flaw causes the length validation to be bypassed on 32-bit systems where arithmetic wraps before the bounds check is applied, resulting in an out-of-bounds memory access that kills the Corosync process. Modern 64-bit deployments of the same packages are explicitly not affected, substantially narrowing real-world exposure despite the CVSS 6.5 rating; no public exploit code or CISA KEV listing exists at time of analysis.
Key-ID (kid) bypass in the jwcrypto Python JOSE library allows an attacker who holds any valid key within a JWK set to forge a General JSON Serialization JWS that satisfies verification for a different kid, effectively impersonating another tenant, user, or service. Affected deployments include Red Hat Ansible Automation Platform 2, RHEL 7-10, Red Hat OpenShift AI (RHOAI), and Red Hat OpenStack Platform 16.2, wherever jwcrypto performs JWS signature verification with kid-based authorization. No public exploit or CISA KEV listing has been identified at time of analysis, and the EPSS score is not provided, but the integrity impact is high for multi-tenant architectures.
Web origin policy bypass in Google Chrome for Android (prior to 152.0.7977.82) exploits a use-of-released-resource flaw (CWE-672) in the browser's mobile implementation, allowing cross-origin content manipulation via a crafted HTML page. An attacker must socially engineer a victim into visiting the malicious page, after which Chrome's Same-Origin Policy enforcement can be circumvented, resulting in high integrity impact against targeted origins. No public exploit code or CISA KEV listing exists at time of analysis; Google issued a fix in stable channel release 152.0.7977.82.
Buffer overread in OpenVPN's Windows service component (`openvpnserv`) through version 2.7.6 exposes adjacent service process memory or crashes the service when NRPT domain entries containing Internationalized Domain Names (IDN) with UTF-8 encoding trigger an incorrect buffer size calculation (CWE-131). The flaw is Windows-specific and confined to split-DNS configurations that include non-ASCII domain names; Linux and macOS deployments are unaffected. The issue was discovered by BreachX Zero Day Labs and fixed in OpenVPN v2.7.7, co-released with four other security patches. No public exploit code or CISA KEV listing has been identified at time of analysis.
Windows openvpnserv path-validation bypass in OpenVPN 2.7_alpha1 through 2.7.6 allows a low-privileged local user to circumvent administrative config-path restrictions by using '/' instead of '\' as a directory separator. Windows path-validation APIs do not recognize '/' as a separator while file-open APIs do, creating a mismatch exploitable to load a user-controlled OpenVPN config file that administrators have explicitly prohibited. Fixed in v2.7.7; no public exploit identified at time of analysis.
Path traversal in OpenList prior to v4.2.3 allows any authenticated user holding the PermAddOfflineDownload permission to write, truncate, or overwrite arbitrary files accessible to the OpenList process via the SimpleHttp offline-download tool. The attacker controls a remote HTTP server that returns a crafted Content-Disposition header containing path-traversal sequences; OpenList uses the attacker-supplied filename without containment validation to construct a file path via filepath.Join relative to a per-task temporary directory, allowing traversal outside that directory. No public exploit has been identified at time of analysis, though the GHSA advisory details the exact vulnerable function and the fix commit is publicly accessible, significantly lowering the effort required to develop one.
Heap buffer out-of-bounds write in the MongoDB C Driver's BSON-to-JSON conversion helpers allows an unauthenticated party who supplies document content to corrupt a small number of bytes past the end of a heap-allocated buffer. The overflow is triggered specifically when a binary BSON field is being encoded and the caller has configured a maximum output length that causes the conversion to be cut short. Impact is limited to a low-integrity write of a few bytes adjacent to the buffer - no confidentiality loss and no confirmed availability impact - but heap corruption in native C applications can have unpredictable downstream effects depending on allocator layout. No public exploit code and no CISA KEV listing exist at time of analysis.
Fleet controller's Helm template preprocessing exposes cluster metadata and internal DNS topology to any user with write access to a GitRepo-tracked repository, via a server-side request forgery path that abuses name resolution. Affected releases span all active branches from 0.12.0 through 0.16.0, with patched builds released across each branch. The DNS-based exfiltration channel is notable because it can remain effective in environments where outbound TCP/UDP egress is otherwise restricted, making standard network perimeter controls insufficient as a compensating measure.
Identity injection in Rancher Manager before 2.15.1 allows a privileged Rancher user to hijack any other user's account by overwriting immutable identity provider fields. The /v3/users update API failed to strip principalIds and username from update payloads, so a user holding the update verb on users.management.cattle.io could inject an external IdP principal they control into any target account. The next time the attacker authenticates via that injected IdP principal, Rancher binds the session to the victim's account and the attacker inherits all its role bindings. No public exploit is identified at time of analysis, and a vendor patch is available in version 2.15.1.
Heap out-of-bounds read in FreeRDP before 3.31.0 allows a malicious RDP server to trigger adjacent heap memory disclosure and potential client instability by sending a crafted RFX_AVC444_BITMAP_STREAM during AVC444 chroma reconstruction. The root cause is a missing row-index bounds check in `general_ChromaV1ToYUV444` (and its ARM NEON and x86 SSE4.1 counterparts), causing `memcpy` to read past the end of the allocated luma plane when the server specifies specific frame geometry. No public exploit or CISA KEV listing exists at time of analysis; a confirmed fix is available in the 3.31.0 release.
HTTP request smuggling in pydantic's HTTPX2 Python client library, all versions prior to 2.11.0, arises because Request._prepare() in _models.py appends a Content-Length header even when a caller-supplied Transfer-Encoding header is already present, producing HTTP/1.1 requests with two conflicting framing headers simultaneously. Downstream intermediaries such as reverse proxies or API gateways that resolve the Content-Length vs. Transfer-Encoding ambiguity differently from the upstream server can misparse request boundaries, enabling request smuggling or connection desynchronization affecting co-located sessions. No public exploit code or active exploitation has been identified at time of analysis; a vendor-released patch is available in v2.11.0.
CRLF injection in httpx2 (pydantic's next-generation Python HTTP client) before v2.11.0 allows manipulation of multipart/form-data part headers when attacker-controlled data reaches the `content_type` or custom headers fields of the `files=` parameter. `FileField.render_headers()` in `_multipart.py` interpolates these values directly into raw header bytes without stripping CR or LF characters, enabling injection of fabricated headers into multipart parts. No public exploit is identified at time of analysis; the vendor-released patch is v2.11.0.
Credential exfiltration via SSRF in LiteLLM proxy (AI Gateway) prior to versions 1.88.6 and 1.96.2 allows any authenticated proxy user to redirect outbound LLM provider calls to an attacker-controlled endpoint, causing the proxy to transmit its operator-configured API keys and other secrets to that destination. Vulnerable routing parameters - api_base, base_url, model_list, fallbacks, and litellm_credential_name - could be injected through nested request fields, path values, and bracket-notation form data that incomplete validation across five proxy modules failed to intercept. No public exploit code has been identified at time of analysis; vendor-released patches are confirmed at versions 1.88.6 and 1.96.2.
Uncontrolled memory consumption in Grafana's SQL macro evaluator allows authenticated users with query permissions to crash the Grafana server process via a bypass of the prior CVE-2026-33375 fix. By injecting the timeGroup macro into a WHERE clause rather than the positions blocked by the original regex-based patch, attackers cause the macro evaluator to consume unbounded memory, terminating the server. Microsoft SQL Server, PostgreSQL, and MySQL data source integrations are all confirmed affected, and no public exploit has been identified at time of analysis.
SAML assertion replay in Grafana Enterprise allows an attacker who obtains a valid signed SAML response to authenticate as the victim user without re-authenticating. When the non-default `allow_idp_initiated` setting is enabled, the SAML library globally suppresses InResponseTo field validation - a field that normally binds each response to a specific originating request - across all SAML flows, including SP-initiated ones that should still enforce it. This anti-replay failure is limited to Grafana Enterprise with an explicit opt-in configuration change; Grafana OSS is unaffected. No public exploit code has been identified and the vulnerability is not in CISA KEV.
Address bar spoofing in Google Chrome's Downloads component (versions prior to 152.0.7977.75) is reachable only after an attacker has already achieved code execution within the renderer process, enabling display of a falsified URL via a crafted HTML page. The flaw stems from improper privilege management (CWE-269) in the Downloads subsystem, which fails to enforce the privilege boundary between the sandboxed renderer and the trusted browser UI. No public exploit identified at time of analysis; a vendor-released patch is available in Chrome 152.0.7977.75.
Origin policy bypass in Google Chrome's Omnibox (address bar) prior to version 152.0.7977.75 allows remote attackers using social engineering and crafted network traffic to circumvent the web same-origin policy, enabling high-integrity cross-origin manipulation. The CVSS vector confirms user interaction is required, meaning the attack cannot be fully automated and depends on deceiving the victim. No public exploit code or active exploitation has been identified; EPSS of 0.16% (5th percentile) reflects low near-term exploitation probability.
Address bar spoofing in Google Chrome prior to version 152.0.7977.75 allows remote attackers to visually deceive users by manipulating the browser's fullscreen UI state through a crafted HTML page, causing the displayed origin to misrepresent the actual site being visited. The vulnerability (CWE-451) carries no confidentiality or availability impact - the risk is exclusively to integrity through phishing enablement, consistent with Google's own 'Low' severity designation. No public exploit code has been identified, and exploitation probability is negligible at EPSS 0.16% (6th percentile).
Information leakage via the MediaCapture component in Google Chrome prior to 152.0.7977.75 enables a remote attacker to exfiltrate sensitive browser-side data by directing a user to a specially crafted HTML page. The flaw (CWE-200) resides in Chrome's implementation of the W3C Media Capture API, which handles camera, microphone, and display-capture device access, and may expose captured media content or associated metadata beyond the intended same-origin boundary. Google has released a fix in the 152.0.7977.75 stable channel update; no public exploit has been identified at time of analysis.
Incorrect authorization in Chrome's SiteSettings component (versions prior to 152.0.7977.75) allows an unauthenticated remote attacker to bypass system-level site access restrictions via a crafted HTML page. The attack requires user interaction - the victim must visit the attacker-controlled page - and the primary impact is a high-integrity authorization bypass, potentially allowing a malicious page to access system resources (e.g., geolocation, camera) that should be gated behind permission prompts. No public exploit code or CISA KEV listing exists at time of analysis, and the EPSS score of 0.17% reflects low near-term exploitation probability despite Chrome's massive global deployment footprint.
Address bar spoofing in Google Chrome on Android prior to version 152.0.7977.75 allows an unauthenticated remote attacker to deceive users about their true browsing origin by triggering fullscreen mode via a crafted HTML page. The flaw (CWE-451: UI Misrepresentation of Critical Information) causes the address bar to be suppressed or misrepresented during fullscreen transitions, creating a reliable phishing surface on Android devices. Google has released a fix in Chrome 152.0.7977.75; no public exploit code has been identified and CISA SSVC rates exploitation as none at time of analysis.
Confused deputy vulnerability in Chrome's CredentialProvider component on Windows allows a remote attacker who has already established renderer process compromise to leak sensitive credential information via a crafted HTML page. Affected versions are Chrome for Windows prior to 152.0.7977.75. Google rates this Low severity internally, though the CVSS Confidentiality impact is scored High due to the potential for credential disclosure; the AC:H vector reflects the significant prerequisite of prior renderer compromise. No public exploit code or CISA KEV listing has been identified at time of analysis.
Incorrect authorization in Chrome's Autofill component on Android (prior to 152.0.7977.75) exposes sensitive Autofill-stored data - potentially including saved credentials, addresses, or payment details - to a remote attacker who can socially engineer a victim into visiting a crafted HTML page. The flaw is platform-specific to Chrome on Android and requires active user interaction via social engineering, which limits real-world exploitation friction somewhat. Google has released a patch and no public exploit code has been identified at time of analysis.
Missing FileSystem authorization in Google Chrome prior to 152.0.7977.75 enables sensitive information disclosure through a two-stage attack chain requiring a pre-compromised renderer process and social engineering. The CVSS vector (AC:H/UI:R) accurately reflects the chained nature of exploitation: an attacker must first compromise the renderer, then induce user interaction with a crafted HTML page to bypass FileSystem access controls. No public exploit or CISA KEV listing has been identified at time of analysis; the vendor patch was released in the September 2026 stable channel update.
CVE-2026-80220 is attributed to Ubuntu but carries no description, CVSS score, CWE classification, or technical details in the available intelligence data. Without a vulnerability description or affected component, no characterization of attacker capability, impact type, or affected user population is possible. Security teams should monitor Ubuntu Security Notices directly at ubuntu.com/security/notices for authoritative details as they become available.