Information Disclosure

Cross-origin data leakage in Google Chrome's CustomTabs feature on Android (versions prior to 152.0.7977.65) enables a local attacker to infer cross-origin information via a co-installed malicious application. The vulnerability stems from an observable discrepancy (CWE-203) - a measurable side-channel difference in Chrome's behavior that a co-resident app can detect and use to reconstruct protected web content. Impact is confined to limited confidentiality loss; no public exploit has been identified at time of analysis, and EPSS at 0.15% (4th percentile) signals very low real-world exploitation probability.

Cross-origin data leakage through the CustomTabs component in Google Chrome for Android (versions prior to 152.0.7977.65) enables a local attacker to extract sensitive browsing data belonging to other origins via a co-installed application. The flaw is classified CWE-200 and carries a CVSS Medium score of 5.5, reflecting meaningful confidentiality impact constrained by a local-only attack vector and required user interaction. No public exploit code or active exploitation via CISA KEV has been identified; the vendor-released patch is available in Chrome 152.0.7977.65.

Information leak in the Animation component of Google Chrome prior to 152.0.7977.65 allows remote unauthenticated attackers to obtain sensitive browser data by inducing a user to visit a crafted HTML page. The flaw is classified CWE-200 (Exposure of Sensitive Information) and carries a CVSS confidentiality impact of High, though Chromium's internal team rated it Medium severity. No public exploit or CISA KEV listing exists at time of analysis, and EPSS of 0.22% (13th percentile) confirms very low observed exploitation probability, making this a normal patch-cycle priority rather than an emergency.

CustomTabs UI spoofing in Google Chrome for Android (prior to 152.0.7977.65) allows a remote attacker using social engineering to misrepresent browser UI elements through a crafted HTML page, enabling phishing-grade deception of users who believe they are interacting with a trusted interface. The flaw is classified under CWE-451 (UI Misrepresentation of Critical Information) and is limited to the Android platform's CustomTabs feature. No active exploitation is confirmed via CISA KEV, and EPSS sits at 0.22% (13th percentile), indicating negligible current exploitation activity.

Observable discrepancy in HTML rendering in Google Chrome prior to 152.0.7977.65 enables a remote attacker to extract sensitive information when a victim visits a crafted HTML page. The root cause is CWE-203 (Observable Discrepancy), where Chrome's handling of specific HTML constructs produces measurable behavioral differences - such as timing variations or rendering side-channels - that leak protected state. No active exploitation is confirmed in CISA KEV, and EPSS sits at 0.22% (13th percentile), indicating low opportunistic risk despite the High confidentiality impact rating in the CVSS vector.

Cross-origin data leakage in Google Chrome's Canvas API (versions prior to 152.0.7977.65) allows a remote, unauthenticated attacker to read pixel-level data from cross-origin resources rendered in a canvas element via a crafted HTML page. Exploitation requires user interaction - the victim must visit an attacker-controlled page - and impact is limited to partial confidentiality loss (C:L), with no integrity or availability consequences. No public exploit code has been identified and EPSS sits at 0.27% (18th percentile), indicating low real-world exploitation probability; vendor-released patch is available.

ServiceWorker in Google Chrome versions prior to 152.0.7977.65 leaks sensitive information to remote attackers via a crafted HTML page, exploiting CWE-200 (Exposure of Sensitive Information to Unauthorized Actor). The vulnerability requires no attacker-side authentication (PR:N per CVSS) but does require user interaction - a victim must visit the malicious page. With CVSS C:H and no integrity or availability impact, the primary threat is data exfiltration; no public exploit has been identified at time of analysis and EPSS sits at a low 0.27%.

UI misrepresentation in Chrome's WebAppInstalls component allows remote attackers to spoof browser UI elements by serving a crafted HTML page to a user who visits it. All Chrome releases prior to 152.0.7977.65 are affected across desktop platforms. Exploitation requires user interaction (visiting a malicious page) but no authentication, and could be used to deceive users into believing they are interacting with a trusted installation prompt - for example, tricking a user into approving a Progressive Web App install from an attacker-controlled origin. No public exploit code has been identified and EPSS is low (0.22%, 13th percentile), placing this firmly in the 'patch on schedule' tier rather than emergency response.

Observable discrepancy in the Forms component of Google Chrome prior to 152.0.7977.65 enables remote attackers to extract sensitive information by serving a crafted HTML page that induces measurable behavioral side-channel differences. The CVSS vector (AC:H/UI:R) confirms exploitation requires both high attack complexity - precise timing or environmental control to reliably observe the discrepancy - and active user interaction to visit the malicious page. No public exploit has been identified at time of analysis, and an EPSS of 0.22% (13th percentile) signals limited automated exploitation interest despite the high confidentiality impact designation.

CustomTabs in Google Chrome on Android before version 152.0.7977.65 leaks cross-origin data through an observable discrepancy (CWE-203) exploitable by a co-installed malicious application. The information disclosure is constrained to local attack scenarios where an adversary controls a second app on the same Android device, limiting real-world exposure significantly. EPSS stands at 0.18% (7th percentile), no public exploit code has been identified, and the vulnerability is not listed in the CISA KEV catalog.

Cross-origin data leakage in Google Chrome's FindInPage component affects all versions prior to 152.0.7977.65. Exploitation requires a remote attacker to have already compromised the renderer process and then deliver a crafted HTML page that triggers improper input validation, exposing data from a different origin accessible in the browser session. No public exploit code has been identified; EPSS scores this at 0.22% (13th percentile), consistent with the compound, chained nature of exploitation required.

Memory read outside Chrome's sandbox via an uninitialized resource in ANGLE affects Google Chrome prior to 152.0.7977.65, enabling an attacker who has already compromised the renderer process to exfiltrate memory beyond sandbox boundaries using a crafted HTML page. This is a chained exploit component - it does not enable initial access but extends an attacker's reach post-renderer-compromise, making it a meaningful escalation primitive in a multi-stage browser exploit chain. No public exploit code or CISA KEV listing has been identified at time of analysis; EPSS is low at 0.29% (21st percentile), consistent with its role as a secondary exploit stage.

Out-of-bounds memory read in the GPU component of Google Chrome on Android (prior to 152.0.7977.65) exposes process memory outside the renderer sandbox when a victim visits a crafted HTML page. The flaw targets Android-specific GPU code paths in Chrome's rendering pipeline, producing a high confidentiality impact limited to the GPU process memory space, with no integrity or availability consequence. No public exploit has been identified at time of analysis, and an EPSS probability of 0.24% at the 15th percentile indicates low near-term opportunistic exploitation likelihood.

Cross-origin data leakage in Google Chrome's Performance API implementation prior to version 152.0.7977.65 enables remote information disclosure via observable timing discrepancies. By serving a crafted HTML page, a remote unauthenticated attacker can exploit CWE-203 side-channel behavior to infer or extract data belonging to other web origins, violating the browser Same-Origin Policy. No active exploitation is confirmed (not in CISA KEV), and EPSS sits at 0.37% (30th percentile), indicating low near-term exploitation probability despite the high confidentiality impact rating in CVSS.

UI misrepresentation in Google Chrome prior to 152.0.7977.65 enables remote attackers to spoof browser interface elements via a crafted HTML page, potentially deceiving users about the identity or security state of a site they are visiting. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L) confirms network delivery with no attacker authentication required, though user interaction is a hard prerequisite. No public exploit code and no active exploitation have been identified; the EPSS score of 0.22% at the 13th percentile reflects very low near-term exploitation probability.

UI spoofing in Google Chrome on macOS prior to version 152.0.7977.65 enables a remote attacker to misrepresent input UI elements by serving a crafted HTML page, classified under CWE-451 (UI Misrepresentation of Critical Information). Victims who visit the malicious page may be deceived by falsified browser UI elements - such as address bar content, form fields, or security indicators - potentially leading to credential theft or other social engineering outcomes. No active exploitation is confirmed (not in CISA KEV), and EPSS is very low at 0.22%; a vendor patch is available at 152.0.7977.65.

Address bar spoofing in Google Chrome prior to version 152.0.7977.65 enables remote attackers to deceive users about the true origin of a page they are visiting via a crafted HTML page, exploiting CWE-451 (UI Misrepresentation of Critical Information) in the browser's navigation subsystem. The practical impact is phishing amplification: a victim visiting the attacker's page may see a trusted domain displayed in the address bar and submit credentials or sensitive information to an attacker-controlled site. No public exploit code and no CISA KEV listing have been identified at time of analysis; EPSS at 0.22% (13th percentile) confirms low automated exploitation probability, though the social-engineering utility of address bar spoofing makes targeted abuse plausible.

Cross-origin data disclosure in Google Chrome's ANGLE graphics layer on Windows allows a remote unauthenticated attacker to read data from other origins by serving a crafted HTML page to a victim user. The flaw is rooted in an uninitialized resource (CWE-908) within ANGLE, Chrome's graphics abstraction layer, affecting all Chrome versions on Windows prior to 152.0.7977.65. No public exploit code has been identified and the vulnerability is absent from CISA KEV; EPSS of 0.29% (21st percentile) corroborates low observed exploitation activity, though the C:H confidentiality rating reflects the severity of cross-origin data leakage if exploited.

Network-layer information disclosure in Google Chrome prior to 152.0.7977.65 enables a remote attacker who has already compromised the renderer process to exfiltrate sensitive network-layer data by delivering a crafted HTML page to a victim. The CVSS score of 5.3 reflects constrained real-world risk: high confidentiality impact is offset by the requirement for a prior renderer compromise and active user interaction. No public exploit code or CISA KEV listing exists at time of analysis, and the EPSS score of 0.22% (13th percentile) indicates low anticipated exploitation activity.

Sensitive information disclosure in Google Chrome's Sync component (versions prior to 152.0.7977.65) allows remote unauthenticated attackers to extract synchronized user data via crafted network traffic. The flaw stems from improper input validation (CWE-20) in the Sync subsystem, which handles cross-device synchronization of browser data including passwords, history, and tokens. No public exploit code or CISA KEV listing exists; EPSS of 0.34% (27th percentile) reflects low real-world exploitation probability, though CVSS C:H signals potentially severe data exposure if exploited.

Information disclosure in Google Chrome's SignIn component (versions prior to 152.0.7977.65) allows remote, unauthenticated attackers to obtain sensitive user information by sending crafted network traffic during the sign-in flow. The CVSS vector assigns High complexity (AC:H), indicating exploitation is not straightforward and requires specific network conditions to be met. No public exploit code has been identified, and EPSS places exploitation probability at just 0.21%, reinforcing that real-world opportunistic exploitation is unlikely at this time.

Memory disclosure in Google Chrome's ANGLE graphics subsystem (prior to 152.0.7977.65) exposes out-of-sandbox memory contents when a user visits a crafted HTML page. The uninitialized resource flaw (CWE-908) in ANGLE - Chrome's cross-platform graphics abstraction layer - allows a remote attacker to read memory that should be isolated within the renderer sandbox, leading to high-confidence confidentiality impact. No public exploit has been identified at time of analysis, and EPSS at 0.29% reflects currently low exploitation probability despite the high CVSS confidentiality rating.

Cross-origin data disclosure in Google Chrome's ANGLE graphics translation layer affects all desktop versions prior to 152.0.7977.65. The uninitialized GPU resource (CWE-908) can be triggered by a crafted HTML page, allowing a remote attacker to read residual data across origin boundaries - a direct violation of browser isolation guarantees. No public exploit code or active exploitation is identified at the time of analysis; the 0.24% EPSS score (15th percentile) places real-world exploitation probability in low-priority territory despite the High confidentiality sub-score in the CVSS rating.

Cross-origin data leakage in Google Chrome's Payments subsystem, affecting all versions prior to 152.0.7977.65, stems from a TOCTOU race condition exploitable by an attacker who has already compromised the renderer process. By delivering a crafted HTML page, the attacker can race the Payments component to read data across origin boundaries, violating the Same-Origin Policy. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog; the EPSS score of 0.25% (16th percentile) reflects low real-world exploitation probability.

Memory disclosure in Google Chrome's Video component (versions prior to 152.0.7977.65) allows a remote attacker to read memory contents from within the Chrome sandbox by directing a victim to a specially crafted HTML page. The uninitialized resource flaw (CWE-908) means the Video subsystem may expose stale memory - potentially including session tokens, credentials, or other sensitive browser data - without requiring any authentication from the attacker. No public exploit code or active exploitation has been identified at time of analysis; the EPSS score of 0.34% (26th percentile) confirms low automated exploitation probability.

Improper resource exposure in Google Chrome's Preload mechanism prior to version 152.0.7977.65 enables remote attackers to bypass Site Isolation by luring a user to a crafted HTML page. The flaw (CWE-668) allows cross-origin resource data to leak across security boundaries, undermining Chrome's core renderer isolation architecture and potentially exposing sensitive information from other origins loaded in the browser. No public exploit has been identified at time of analysis; EPSS at 0.39% (32nd percentile) and the absence of a CISA KEV listing indicate low but non-zero exploitation probability.

WebProtect race condition in Google Chrome prior to 152.0.7977.65 exposes sensitive information to attackers who have already achieved renderer process compromise. The flaw (CWE-367 TOCTOU) enables a second-stage information disclosure step within a broader browser exploitation chain, requiring a victim to interact with a crafted HTML page. No public exploit code has been identified and EPSS sits at 0.29% (22nd percentile), indicating limited real-world exploitation pressure at this time; a vendor patch is available.

Cross-origin data leakage in Google Chrome's Payments subsystem (prior to 152.0.7977.65) exposes information from other origins when a user visits a crafted HTML page. The vulnerability stems from improper isolation within the Payments component, allowing a remote unauthenticated attacker to read data across origin boundaries - a violation of the Same-Origin Policy that underpins browser security. No public exploit code has been identified at time of analysis, and EPSS of 0.22% (13th percentile) indicates low observed exploitation probability in the wild.

Cross-origin data exfiltration via Skia, Chrome's graphics rendering engine, affects all Google Chrome versions prior to 152.0.7977.65, enabling remote unauthenticated attackers to read pixel-level cross-origin data from a victim's browser session. Exploitation requires user interaction - the victim must visit a crafted HTML page - and impact is limited to partial confidentiality loss with no integrity or availability consequence. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.22% (13th percentile) indicates minimal observed exploitation pressure.

DOM information leak in Google Chrome prior to 152.0.7977.65 enables remote attackers to extract sensitive browser data by inducing a victim to visit a crafted HTML page via social engineering. The vulnerability (CWE-200) reflects improper information exposure within Chrome's Document Object Model, with high confidentiality impact per CVSS. No active exploitation is confirmed (not in CISA KEV), EPSS sits at the 13th percentile (0.22%), and a vendor-released patch is available in stable channel 152.0.7977.65.

Canvas API information leak in Google Chrome prior to 152.0.7977.65 enables remote attackers to bypass the Same-Origin Policy and read cross-origin pixel data via a crafted HTML page. Exploitation requires user interaction (visiting the malicious page) and results in low confidentiality impact - pixel-level canvas data leakage rather than credential or file system exposure. No public exploit has been identified and EPSS at 0.39% (32nd percentile) confirms low real-world exploitation probability; no CISA KEV listing exists.

Observable discrepancy (CWE-203) in Google Chrome's network stack prior to version 152.0.7977.65 enables remote attackers to extract sensitive information by exploiting behavioral differences observable from a crafted HTML page. Exploitation requires high attack complexity and user interaction - the victim must visit a malicious page - constraining real-world impact despite the high confidentiality rating in the CVSS vector. No public exploit code exists and no active exploitation has been reported; Google has released a patch in Chrome 152.0.7977.65.

Site isolation bypass in Google Chrome prior to 152.0.7977.65 enables cross-origin information disclosure via a crafted HTML page, but only when an attacker has already achieved renderer process compromise through a separate, chained exploit. The flaw, tracked internally as Chromium issue 498327743, carries a CVSS score of 3.1 reflecting the high-complexity, multi-stage attack prerequisite. No public exploit code or active exploitation has been identified; EPSS exploitation probability stands at 0.33% (25th percentile), consistent with no observed widespread abuse.

Cross-origin data leakage in Google Chrome's SVG rendering engine (prior to 152.0.7977.65) allows a remote attacker to bypass same-origin policy boundaries through observable behavioral discrepancies. Exploitation requires the victim to interact with a crafted HTML page (UI:R), limiting opportunistic mass exploitation. No public exploit code exists and no CISA KEV listing is present; EPSS of 0.37% (30th percentile) confirms low current exploitation probability.

UI misrepresentation in the Chrome Extensions subsystem (CWE-451) enables remote attackers to use social engineering and a crafted extension to deceive users into disclosing sensitive information. All Google Chrome desktop installations prior to version 152.0.7977.65 are affected. No public exploit has been identified at time of analysis, and no active exploitation has been confirmed by CISA KEV; however, the high confidentiality impact in the CVSS vector reflects the potential for credential or sensitive-data theft if a user is successfully deceived into installing a malicious extension.

Cross-origin data disclosure in Google Chrome's Skia graphics library (versions prior to 152.0.7977.65) enables a remote attacker who has already achieved renderer process compromise to leak cross-origin data by loading a crafted HTML page. The uninitialized resource flaw (CWE-908) exposes stale Skia memory contents that may contain pixel or data residue from other origins. No public exploit code has been identified, the vulnerability is absent from CISA KEV, and an EPSS of 0.34% (26th percentile) reflects low current exploitation activity.

Chrome's browser Sync subsystem in versions prior to 152.0.7977.65 leaks sensitive user data due to improper validation of crafted inbound network traffic (CWE-20), enabling a remote attacker to read high-confidentiality synchronized content such as credentials or browsing history. The CVSS 6.5 vector (AV:N/AC:L/PR:N/UI:R) confirms the attack is network-reachable with no privilege requirement, but a user interaction step limits opportunistic mass exploitation. No public exploit code or CISA KEV listing exists; EPSS at 0.25% (16th percentile) corroborates low near-term exploitation probability, and the vendor-released patch (152.0.7977.65) is already available.

Sensitive information disclosure via the QUIC protocol stack in Google Chrome affects all versions prior to 152.0.7977.65, exploitable by remote unauthenticated attackers through a crafted HTML page. When a victim navigates to an attacker-controlled page, Chrome's QUIC (HTTP/3) implementation improperly exposes confidential data, with high confidentiality impact but no integrity or availability consequences. No public exploit has been identified at time of analysis; CISA SSVC rates exploitation status as none and EPSS is 0.31% (23rd percentile), indicating low near-term exploitation probability despite the medium-severity classification.

Memory disclosure via uninitialized GPU resource in Google Chrome prior to 152.0.7977.65 enables a remote attacker - who has already compromised the renderer process - to read memory contents outside the Chrome sandbox through a crafted HTML page. This is a chained, second-stage attack: the GPU component fails to initialize memory before use (CWE-908), leaking data only after renderer compromise. No public exploit code exists and the vulnerability is not listed in CISA KEV; EPSS of 0.40% (33rd percentile) further signals limited real-world exploitation pressure. A vendor-released patch is available in Chrome 152.0.7977.65.

Observable discrepancy in Chrome's Autofill subsystem allows remote information disclosure via a crafted HTML page, affecting all desktop Chrome versions before 152.0.7977.65. The flaw (CWE-203) enables a network-reachable attacker to infer sensitive stored autofill data - such as addresses or payment fields - by measuring behavioral or timing differences triggered by form elements on a malicious page. Google has issued a patch in stable channel version 152.0.7977.65; no public exploit code exists and no CISA KEV listing has been recorded at time of analysis.

Cross-origin data exposure via the GPU subsystem in Google Chrome prior to 152.0.7977.65 allows a remote, unauthenticated attacker to read data from other web origins by luring a user to a crafted HTML page. The vulnerability resides in Chrome's GPU rendering path and violates the browser's same-origin policy, potentially exposing session tokens, rendered content, or other sensitive cross-origin data. No public exploit code or CISA KEV listing has been identified, and the EPSS score of 0.22% (13th percentile) reflects low current exploitation probability.

Uninitialized memory in Chrome's ANGLE graphics abstraction layer, across all desktop platforms prior to version 152.0.7977.65, enables remote attackers to read cross-origin data by delivering a crafted HTML page to a victim user. The flaw breaks the browser's same-origin policy through the graphics pipeline rather than through JavaScript or DOM manipulation. No public exploit or CISA KEV listing exists; EPSS of 0.24% at the 15th percentile reflects low current exploitation pressure.

Cross-origin information leak in Google Chrome's Paint rendering component (versions prior to 152.0.7977.65) enables remote attackers to bypass the web origin policy by delivering a crafted HTML page. The vulnerability is confined to the confidentiality dimension - no integrity or availability impact - and requires user interaction (visiting the attacker-controlled page) to trigger. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.33% places it in the 25th percentile, indicating low exploitation probability in the near term.

Cross-origin pixel data leakage in the Canvas API of Google Chrome prior to 152.0.7977.65 enables remote attackers to bypass the web same-origin policy by enticing a victim to visit a crafted HTML page. The flaw is classified High severity by the Chromium team and Medium (CVSS 4.3) by NVD, reflecting limited confidentiality impact with no integrity or availability consequences. No public exploit code or CISA KEV listing is identified at time of analysis, and EPSS at 0.33% indicates very low observed exploitation probability.

Cross-origin data leakage in Google Chrome's ANGLE graphics layer (versions prior to 152.0.7977.65) allows an unauthenticated remote attacker to read limited data across origin boundaries by inducing a victim to visit a crafted HTML page. The root cause is an uninitialized resource (CWE-908) in ANGLE, Chrome's graphics abstraction engine, which can expose residual GPU buffer contents from other origins. No public exploit identified at time of analysis; EPSS is low at 0.40% (33rd percentile), and the vulnerability is not listed in CISA KEV.

Information disclosure in Google Chrome's Autofill component on Android (prior to 152.0.7977.65) enables a remote attacker to extract sensitive user data - likely form-fill credentials or PII - by luring a victim to a specially crafted HTML page. The vulnerability stems from CWE-20 improper input validation in the Autofill subsystem, which fails to sanitize attacker-controlled HTML before processing it. No public exploit code or CISA KEV listing is present at time of analysis; EPSS sits at the 13th percentile, indicating low current exploitation momentum despite the high confidentiality impact.

Cross-origin data exposure in Google Chrome's GPU component prior to version 152.0.7977.65 can be triggered by a remote attacker who has already compromised the renderer process. The vulnerability stems from an uninitialized GPU resource (CWE-908) that leaks memory contents readable across origin boundaries. Exploitation requires chaining this issue with a separate renderer compromise, significantly raising the bar; no public exploit code has been identified and EPSS probability sits at 0.40%.

PyOpenEXR Python bindings in OpenEXR versions 3.3.0-3.3.12 and 3.4.0-3.4.13 leak uninitialized same-process heap memory to calling Python code when processing crafted deep scanline EXR files that contain layer-prefixed RGB channels. The flaw originates in PyPart::setDeepSliceData(), where lane assignment uses exact unprefixed string matching, leaving the green and blue NumPy array lanes uninitialized before returning them to the caller. Python applications ingesting untrusted EXR files that subsequently log, serialize, or transmit the resulting arrays may inadvertently expose heap contents; no public exploit code has been identified at time of analysis, and this vulnerability is not listed in CISA KEV.

Crash-inducing out-of-bounds read in OpenEXR's multipart file processing allows an attacker to cause a denial of service by supplying a crafted EXR file with an empty multiView header attribute. Affected are OpenEXR releases before 3.2.11, within the 3.3.x branch before 3.3.13, and within the 3.4.x branch before 3.4.14 - all maintained by the Academy Software Foundation. Exploitation requires user interaction to open the malicious file, limiting impact to availability only; no public exploit code or active exploitation has been identified at time of analysis.

Heap out-of-bounds read in OpenEXR's RLE decompression path crashes the decoding process on ILP32 (32-bit) builds across versions 3.2.0-3.2.10, 3.3.0-3.3.12, and 3.4.0-3.4.13. A crafted .exr file with a malicious RLE-compressed payload causes the 64-bit unpacked size to truncate before buffer allocation in OpenEXRCore decoding.c, after which unpack_32bit() reads past the allocated buffer boundary, resulting in denial of service. Exploitation requires a victim or automated pipeline to open the malicious file; no public exploit identified at time of analysis, and the vulnerability is constrained to ILP32 build environments.

Out-of-bounds read in OpenEXR's ILP32 builds enables denial of service via crafted uncompressed deep-tile EXR files across three active release branches (before 3.2.11, 3.3.0-3.3.12, and 3.4.0-3.4.13). The root cause is a 32-bit integer overflow in OpenEXRCore's sample-count table size calculation that causes unpack_sample_table() to iterate beyond an undersized allocation. No public exploit or active exploitation has been identified; vendor-released patches are available for all three affected branches.

Out-of-bounds read in Adobe Substance 3D Painter exposes sensitive process memory when a victim opens a specially crafted malicious file. The flaw, classified as CWE-125, causes the application to read beyond allocated buffer boundaries during file parsing, potentially leaking in-memory data such as credentials or session tokens accessible to the attacker. Adobe has published security advisory APSB26-129 addressing the issue; no public exploit code has been identified at time of analysis.

Out-of-bounds read in Adobe Illustrator Desktop 2025 and 2026 exposes sensitive process memory to disclosure when a victim opens a specially crafted file. The vulnerability carries a CVSS 3.1 score of 5.5 (Medium) with a local attack vector and required user interaction, limiting opportunistic exploitation but making it viable in targeted social-engineering campaigns. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog at time of analysis.

Arbitrary file system read in Adobe's Content Credentials (C2PA Tool and Content Credentials Rust SDK) exposes sensitive files and directories outside the intended access scope through improper input validation during file parsing. The attack requires a victim to open a malicious file crafted by the attacker, making this a local, user-interaction-dependent vulnerability with high confidentiality impact but no integrity or availability consequence. No public exploit code exists and this CVE is not listed in the CISA KEV catalog at time of analysis.

NVIDIA Unified Fabric Manager Enterprise session management embeds a hard-coded cryptographic key (CWE-321), enabling a local attacker to extract session material and potentially escalate privileges within the InfiniBand fabric management plane. All four active UFM Enterprise release tracks - GA, LTS 2023, LTS 2024, and LTS 2025 - are confirmed affected per CPE data published by NVIDIA. No public exploit code or CISA KEV listing has been identified at time of analysis; EPSS data is absent from available intelligence, limiting probabilistic exploitation forecasting.

Command injection in NVIDIA UFM Enterprise's IBDiagnet API allows an authenticated administrator with adjacency-level network access to execute arbitrary OS commands on the host system, potentially achieving full compromise. All major release trains are affected - GA, LTS 2023, LTS 2024, and LTS 2025 - as confirmed by NVIDIA's own advisory and NVD CPE data. No public exploit code or CISA KEV listing has been identified at time of analysis, keeping real-world opportunistic risk constrained by the high privilege and network adjacency prerequisites.

Command injection in NVIDIA UFM Enterprise's user management component enables an authenticated administrator to execute arbitrary OS-level commands by sending a crafted API request, spanning all active release tracks (GA, LTS 2023, LTS 2024, LTS 2025). Successful exploitation can yield full code execution on the UFM host, privilege escalation beyond the administrative role, and disclosure of sensitive InfiniBand fabric management data. No public exploit code or CISA KEV listing has been identified at time of analysis, and the adjacent network attack vector (AV:A) constrains the realistic attacker population to those with both admin credentials and access to the management network segment.

Integer overflow leading to out-of-bounds write in NI LabVIEW 2026 Q3 and prior enables information disclosure or arbitrary code execution when a user opens a specially crafted VI file. The attack is file-based and requires social engineering to deliver a malicious Virtual Instrument file to a target, making it a credible threat in engineering, research, and industrial automation environments where VI files are routinely shared. No public exploit identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.

Out-of-bounds read in the NVIDIA DGX Spark standalone Memory Management (MM) firmware enables a local high-privileged attacker to read beyond allocated buffer boundaries, leaking potentially sensitive memory contents across security boundaries (S:C/C:H per the CVSS vector). The scope change in the CVSS vector suggests that data disclosed may originate from security domains beyond the firmware itself, such as the host OS or adjacent processes. No public exploit code or active exploitation has been identified at time of analysis, and the high-privilege local access requirement substantially constrains the realistic attacker population.

Out-of-bounds read in NI LabVIEW 2026 Q3 and all prior versions can result in information disclosure or arbitrary code execution when the application processes a maliciously crafted VI file containing a specially structured image. The root cause is a signed-to-unsigned integer conversion error (CWE-195) in the image-loading code path, causing the parser to read beyond intended memory boundaries. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.

Out-of-bounds read in the Zephyr ext2 filesystem driver crashes any device that mounts a crafted ext2 image. The superblock fields s_blocks_count and s_first_data_block are consumed verbatim without being bounded against the single-group bitmap capacity, allowing a malicious image to drive ext2_bitmap_count_set() roughly 512 MB past the allocated bitmap block. The resulting memory access crosses an unmapped or MPU-protected region and faults, producing a denial-of-service crash. No public exploit exists and the vulnerability is not in CISA KEV; real-world risk is bounded by the requirement to supply untrusted ext2 media to a target device.

Credential exposure in rclone before v1.75.0 allows network-adjacent attackers to capture IBM IAM bearer tokens during same-host HTTPS-to-HTTP redirect downgrades, or SSE-C customer-provided encryption keys during cross-origin S3 redirects. The S3 redirect callback in s3.go correctly strips X-Amz-Security-Token on host changes but omits IBM IAM Authorization headers and SSE-C key headers from its denylist, exploiting a gap in Go's built-in redirect sanitization that does not treat scheme downgrades as a credential boundary. A proof-of-concept is documented in GHSA-8mxv-9xhp-86h4; no public exploit tool has been independently identified, and the vulnerability is not listed in CISA KEV at time of analysis.

Credential exposure in rclone's WebDAV backend allows an adjacent on-path attacker to capture and replay Basic authentication passwords, bearer tokens, or session cookies transmitted in cleartext after a same-host HTTPS-to-HTTP redirect. All rclone versions through v1.74.0-240 are affected when the WebDAV backend is configured with Basic credentials or cookie-based authentication. No public exploit code has been released, but a proof-of-concept was demonstrated and documented in the GHSA advisory as part of responsible disclosure.

Stack trace disclosure in rclone's RC API exposes internal file paths, Go module versions, goroutine states, and memory addresses to authenticated API callers who intentionally trigger panics. All rclone versions through v1.74.4 with the RC API enabled are affected; the vulnerability is rooted in the panic recovery handler at fs/rc/jobs/job.go including raw debug.Stack() output directly in HTTP JSON error responses. A proof-of-concept is confirmed in the GHSA advisory; no public exploit identified at time of analysis beyond that PoC, and this vulnerability is not listed in CISA KEV.

Unauthenticated credential exposure in rclone before 1.75.0 allows remote attackers to retrieve backend storage secrets via the pprof debug endpoint, bypassing the main handler's fail-closed authentication entirely. The root cause is architectural: rclone registers Go's net/http/pprof handler on its own separate router route rather than nesting it within the authenticated main handler, so GET /debug/pprof/cmdline returns the full process argv - including cloud backend credentials - to any unauthenticated caller. No CISA KEV listing or confirmed public exploit code exists at time of analysis, but exploitation requires no authentication, no special tooling, and no user interaction, making any network-exposed RC instance immediately vulnerable to credential theft.

Heap-based buffer under-read in libxml2's XML Schema identity constraint processor affects all Nokogiri releases prior to 1.18.8, which bundle the vulnerable libxml2 library. The flaw in xmlSchemaIDCFillNodeTables can be triggered by supplying a crafted XSD schema or by submitting untrusted XML documents for validation against trusted schemas that combine xsd:keyref with recursively defined types carrying additional identity constraints. No public exploit has been identified at time of analysis, and upstream libxml2 maintainers and MITRE independently rate actual exploitability as low - in notable conflict with the NVD-assigned CVSS 4.0 base score of 8.7.

Server-Side Request Forgery in PraisonAI before version 4.6.58 allows unauthenticated remote attackers to force the application server to make HTTP requests to internal network resources, including cloud metadata endpoints (169.254.169.254), loopback services, and RFC 1918 hosts. Two independent bypass paths exist in the Jobs API webhook_url validator: a DNS rebinding path exploiting the TOCTOU gap between validation and request dispatch, and a fail-open condition where socket.gaierror exceptions are silently swallowed, accepting unresolvable domains with no validation at all. A detailed proof-of-concept including curl commands is published in the GHSA advisory; no CISA KEV listing was present at time of analysis.

Item duplication and protected-item extraction in the MintyItanium Lost-Auction Minecraft auction plugin (all versions prior to commit 88c920b05042929db334ba06d57f052b42d6b3f8) allows authenticated players to manipulate GUI interactions to obtain barrier blocks or duplicate items from the auction interface. The root cause is improper control flow in the GUI handling logic (CWE-670), enabling players to bypass intended item restrictions without elevated permissions. No public exploit code has been identified at time of analysis, and the vulnerability is confined to Minecraft server game integrity rather than infrastructure security.

Cart quantity manipulation in macrozheng mall up to version 1.0.3 allows authenticated remote attackers to exploit a business logic error in the OmsCartItemServiceImpl.updateQuantity function at the /cart/update/quantity endpoint by submitting maliciously crafted quantity values. The CWE-840 classification confirms the root cause is improper enforcement of business rules rather than a memory-safety flaw, allowing attackers to potentially submit negative, zero, or arbitrarily large quantity values to distort cart totals or order pricing. No public exploit code has been identified at time of analysis, and the vendor's unexplained deletion of the associated GitHub issue (#984) leaves patch status unresolved.

Privileged information disclosure in YOOtheme Pro for Joomla (versions 1.0.0 through 5.0.41) allows authenticated users holding only com_template editing permissions to read metadata about arbitrary Joomla modules - access that normally requires the separate com_modules permission. The root cause is CWE-284 (Improper Access Control): the extension's template editor fails to verify whether the requesting user holds the appropriate module-management permission before returning module data. No public exploit identified at time of analysis, and the CVSS 4.0 score of 5.1 (Medium) reflects the high privilege requirement and limited confidentiality impact.

Ech0 before version 4.7.3 exposes guest commenter email addresses to unauthenticated remote callers via public comment-listing API endpoints, due to a missing `json:"-"` serialization tag on the Comment model's Email field. Any attacker with HTTP access to an Ech0 instance can enumerate every guest commenter email stored in the database by calling `/api/comments` or `/api/comments/public` without credentials. A working proof-of-concept script is published in the GHSA advisory; no public exploit has been confirmed as actively exploited (CISA KEV listing absent).

Missing HttpOnly cookie flags in HCL Hive expose session tokens and sensitive credentials to client-side script access, enabling session hijacking when combined with cross-site scripting. The CVE description cites broader infrastructure weaknesses - lateral movement, container breakout, and internal communications exposure - suggesting CWE-1004 is one root cause within a cluster of related configuration flaws. No public exploit has been identified at time of analysis, and no KEV listing exists, but the network-accessible attack surface with no privilege requirement (beyond user interaction) makes this relevant for any internet-exposed Hive deployment.

HCL Hive's software supply chain governance weaknesses expose the application to risk from vulnerable, unmaintained, or malicious third-party dependencies incorporated into its build or runtime environment. The flaw (CWE-1104) reflects insufficient vetting of upstream components, meaning existing dependencies may carry unpatched CVEs or could serve as an introduction vector for malicious code. With a CVSS of 4.2 (AV:N/AC:H/PR:N/UI:R), exploitation is constrained by high attack complexity and user interaction requirements; no public exploit and no CISA KEV listing were identified at time of analysis.

HCL Hive exposes sensitive host environment information through a network-accessible information disclosure flaw, enabling unauthenticated remote attackers - under high attack complexity conditions - to collect reconnaissance data about the underlying system. The CVSS 3.7 (Low) score reflects both the constrained confidentiality impact and the high exploitation complexity. No public exploit code or active exploitation has been identified at time of analysis.

Symlink following in LACT (Linux AMDGPU Control Tool) versions through 0.10.0 allows a local low-privileged user to redirect privileged file operations to attacker-chosen paths via a crafted UNIX symbolic link, resulting in local denial-of-service. Reported by SUSE and tracked in their Bugzilla (bsc#1276481), the flaw is rooted in CWE-61 and is confined to systems with multi-user local access where LACT is installed. No public exploit code has been identified and the issue does not appear in the CISA KEV catalog.

Filter injection in the EXT:solr (Apache Solr for TYPO3 - Enterprise Search) extension enables unauthenticated visitors to bypass per-site document isolation on shared Solr cores, exposing public search-indexed content belonging to adjacent TYPO3 site installations. The flaw exists because user-supplied additionalFilters request parameters can pre-register a named siteHash filter that the query builder then refuses to overwrite, undermining the multi-tenancy boundary the extension relies upon for site separation. No public exploit code has been identified at time of analysis, and exploitation is gated on a specific shared-core deployment pattern; no active exploitation is confirmed.

Unrestricted Solr query syntax passthrough in the TYPO3 EXT:solr enterprise search extension exposes indexed data to remote unauthenticated attackers via blind injection techniques. By crafting queries that exploit Solr's native field selectors, wildcards, and range operators, an attacker can enumerate schema field names and systematically extract stored values without triggering obvious errors. No public exploit code has been identified at time of analysis; the CVSS 4.0 score of 6.3 reflects high attack complexity (AC:H/AT:P) that limits opportunistic mass exploitation.

Insufficient JWT expiration validation in the TYPO3 'Syssy - TYPO3 Monitoring & Security Checks' extension allows an attacker already in possession of a valid SYSSY project API key to authenticate using an expired token, bypassing the intended session time boundary (CWE-613). The limited confidentiality and integrity impact (VC:L/VI:L per the CVSS 4.0 vector) reflects access to monitoring and security check data rather than full system compromise. No active exploitation has been confirmed (not listed in CISA KEV), and no public exploit code has been identified at time of analysis.

Cleartext transmission of TYPO3 system information occurs in the Syssy - TYPO3 Monitoring & Security Checks extension when OpenSSL is absent on the hosting server, exposing potentially sensitive configuration and system data to network interception (CWE-319). All tracked versions of the extension are affected per CPE data, though exploitation is constrained by the dual requirement of OpenSSL being unavailable and the attacker already possessing the SYSSY project's API key. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog; the CVSS 4.0 score of 5.3 reflects the medium-severity, partially-authenticated nature of the flaw.

Prototype pollution in the `@cleverbrush/deep` package (versions ≤ 4.4.0) allows a remote attacker to corrupt `Object.prototype` by supplying crafted JSON containing reserved JavaScript keys (`__proto__`, `constructor`, `prototype`) to the `deepExtend()` function without any privilege requirement. Any Node.js application that passes externally controlled input through `deepExtend()` is at risk of property injection affecting every plain object in the runtime, potentially enabling authentication bypass or logic manipulation downstream. A public exploit exists (GitHub issue #213); the vulnerability is not listed in CISA KEV, so widespread active exploitation is not confirmed at time of analysis.

Local File Inclusion in the Events Manager WordPress plugin (all versions through 7.3.7.4) allows an administrator-level attacker to store a malicious PHP file traversal path via the em_options_save function, which is then executed without any further authentication on every admin_init hook invocation - including unauthenticated admin-ajax.php requests. The two-phase attack converts a high-privilege write primitive into a persistent, unauthenticated code execution trigger that survives account remediation until the stored option is manually purged. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.

Rocket.Chat's unauthenticated DDP method sendForgotPasswordEmail lacks a rate-limiting rule, enabling any network caller to flood a target email address with password reset messages from the deployment's own mail sender and to enumerate account types at scale. The method is reachable both via the Meteor DDP protocol and the unauthenticated HTTP route POST /api/v1/method.callAnon/sendForgotPasswordEmail, requiring no credentials. A side-channel in the method's response - returning false only when the target belongs to an OAuth-authenticated account with Accounts_AllowPasswordChangeForOAuthUsers disabled - allows an attacker to distinguish account authentication types, confirming information disclosure beyond simple email abuse. No public exploit or KEV listing is identified at time of analysis.

Cookie-path scoping manipulation in Adminer 4.6.0-5.5.0 results from an incomplete fix for a prior X-Forwarded-Prefix header injection (GHSA-8478-xrj3-h9c2). The validation guard in bootstrap.inc.php blocks double-slash prefixes (//evil.com) but accepts backslash variants (/\evil.com); because browsers normalize backslash to forward slash, the malformed prefix survives as a network-path reference into cookie_path(), corrupting the Set-Cookie Path attribute. Exploitation depends on a misconfigured or absent reverse proxy that permits clients to supply the X-Forwarded-Prefix header, and no public exploit has been identified at time of analysis.

Infinite-loop denial of service in OpenEXR versions prior to 3.2.10, 3.3.12, and 3.4.13 allows an attacker to permanently hang any process that parses a crafted EXR image by triggering an integer overflow in the sample-count helper roundListSizeUp(). When UINT_MAX is passed as a sample-count value, 32-bit unsigned left-shift arithmetic wraps the accumulator to zero, producing a loop condition that never terminates. The vulnerability is reachable through public OpenEXRUtil APIs, making it exploitable wherever applications accept externally-supplied EXR files. No public exploit code or CISA KEV listing has been identified at time of analysis.

Uncontrolled recursion in Autodesk 3ds Max's SVG parser allows a crafted file to exhaust the call stack and crash the application, resulting in denial of service. The attack requires user interaction - a victim must open a maliciously crafted SVG file - and has no impact on confidentiality or integrity. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.

Null byte injection in Netty's MqttEncoder affects applications using versions prior to 4.1.137.Final and 4.2.17.Final that forward user-controlled input into MQTT UTF-8 string fields - specifically client identifiers, will topics, usernames, and PUBLISH topic names. Because the encoder performs no null byte validation, an attacker with adjacent-network access and low-level privileges can embed the prohibited U+0000 character, causing downstream MQTT brokers to misparse field boundaries and potentially bypass topic-based ACLs or misidentify client sessions. No public exploit has been identified at time of analysis, and the vulnerability has not been added to the CISA KEV catalog.

Universe checking state desynchronization in the Rocq Prover allows the kernel to continue accepting universe-inconsistent terms after a module using `Local Unset Universe Checking` is closed, despite user-visible diagnostics reporting the check as enabled. Once the module closes, Hurkens' paradox can be applied without axioms, plugins, or unsafe features to derive a proof of False, from which any proposition is provable. A public proof-of-concept is available, no patch exists, and neither `Print Assumptions` nor `Test Universe Checking` reveals the compromised kernel state.

Lean 4's formal proof kernel accepts unsound opaque declarations due to a missing closure check in environment::add_opaque, enabling a metaprogram to admit a constant of type False without sorry, unsafeCast, or any unsafe mechanism - directly shattering the kernel's soundness guarantee. All Lean 4 versions before 4.32.2 are affected; a publicly available proof-of-concept at https://github.com/endrazine/lean-cve-poc-14484 confirms exploitability. No CISA KEV listing exists, but the POC's public availability and the ecosystem's reliance on kernel soundness for formal guarantees make this a high-priority upgrade for any organization using Lean 4 for verified software or mathematical proofs.

Soundness violation in Rocq Prover's guard checker (versions V8.20 through V9.1.1) allows crafting a nested fixpoint that produces a proof of False from purely definitional code - no tactics, axioms, plugins, or unsafe flags required. The flaw stems from the checker's failure to track higher-order recursive calls when a fixpoint passes itself as an argument to a nested fixpoint, which then applies it to a non-subterm value, admitting a type definitionally equal to its own negation. A public proof-of-concept exploit exists at github.com/endrazine/rocq-cve-poc-21683; no active exploitation is confirmed in CISA KEV, but any proof corpus accepted by affected Rocq versions should be considered potentially unsound until re-verified under Rocq 9.2.0.

Rocq Prover's kernel guard checker fails to revalidate the recursive tree representation of inductive type parameters after they are altered by transport, allowing construction of provably non-terminating fixpoint definitions that the kernel accepts as structurally decreasing. Two cooperating fixpoints exploit this: the first corrupts the recursive tree via a transport rewrite, and the second inherits the corrupted tree without re-verification, enabling a structurally non-decreasing call to be accepted as terminating. The resulting definition derives a proof of False from axioms consistent with the calculus of inductive constructions, breaking logical soundness; a public proof-of-concept exists at https://github.com/endrazine/rocq-cve-poc-22024 and no merged patch is available at time of analysis.