Monthly
Cross-team credential disclosure in the Apache Airflow Google Provider's Cloud Secret Manager backend exposes every team's Connections and Variables to every other team in multi-team deployments. The backend's public methods accepted a team_name parameter but silently discarded it before the internal secret lookup, collapsing all team namespaces into one shared, unscoped lookup. No public exploit has been identified at time of analysis; the vendor-released fix is apache-airflow-providers-google 22.3.0.
Session token exposure in the Mira Android app (Quanovate Tech Inc.) leaks live authentication credentials to third-party web properties and referrer logs whenever users trigger in-app WebView flows such as shop redirects. The app appends the active session token as a URL query string parameter and embeds a persistent user identifier in the WebView User-Agent header, both of which are transmitted to any destination or JavaScript context receiving that traffic. Reported by ICS-CERT under medical advisory ICSMA-26-223-01, this vulnerability affects a healthcare-adjacent platform, amplifying the sensitivity of exposed credentials; no public exploit code or CISA KEV listing has been identified at time of analysis.
Remote code execution in Microsoft Edge (Chromium-based) below version 151.0.4129.78 stems from a type confusion flaw (CWE-843) in the browser engine, exploitable over the network when a user visits or interacts with attacker-controlled content. The vendor has confirmed patch availability and the flaw is tagged as causing memory corruption, which aligns with the typical consequence of type confusion in browser engines. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis, though the unauthenticated network vector with low attack complexity warrants prioritized patching in enterprise environments.
Information disclosure in Nuxt's development server exposes the project's absolute filesystem root path and a persistent per-project workspace UUID to unauthenticated LAN-adjacent attackers via the Chrome DevTools workspace endpoint. The prior security fix (GHSA-rq7w-g337-39qq) introduced a local-request gate that trusts the attacker-supplied Host header instead of the actual TCP peer address, meaning a non-browser client such as curl can bypass it by omitting Sec-Fetch-Site, Origin, and Referer headers while forging Host: localhost. Impact is confined to information disclosure; no public exploit has been independently identified at time of analysis, though the official advisory provides a working proof-of-concept curl command. Production builds are entirely unaffected.
Improper cryptographic signature verification in Estonian RIA's libdigidocpp core library and its consumer applications - DigiDoc4, DigiDoc for Android, and DigiDoc for iOS - enables bypassing of XAdES signature validity checks through unhandled exceptional conditions during BDOC container parsing. Affected versions span libdigidocpp 4.1.0-4.2.0, DigiDoc4 4.7.0-4.8.1, DigiDoc Android 2.7.0-2.7.1, and DigiDoc iOS 2.8.0, all of which have vendor-released patches. A proof-of-concept is indicated by the CVSS 4.0 E:P exploit maturity modifier, though no active exploitation has been confirmed and this CVE is not listed in CISA KEV.
Uninitialized heap memory exposure in GNU Emacs for Android's sfnt font parser allows a remote, unauthenticated attacker to trigger information disclosure, process crashes, or arbitrary memory access on 32-bit targets by delivering a crafted font file. The flaw in sfnt_read_table_directory() (src/sfnt.c) stems from an incorrect comparison variable in the read-length check, causing the parser to trust an attacker-controlled table-entry count without proper bounds validation. No public exploit or CISA KEV listing exists at time of analysis; exploitation requires user interaction with attacker-delivered content such as an email, EWW-rendered webpage, or a document referencing a malicious font face.
Heap buffer overflow in GNU Emacs for Android's TrueType font parser (sfnt_read_name_table() in src/sfnt.c) enables potential code execution when a 32-bit Emacs process loads a crafted font file. The root cause is a CWE-190 integer overflow that wraps a 32-bit allocation size calculation, producing an undersized heap buffer that a subsequent read() call overflows. Delivery is possible through multiple standard Emacs workflows - email rendering, EWW web browsing, or documents with custom font faces - requiring only passive user interaction, with no authentication required from the attacker. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, though a patch commit is confirmed upstream.
Heap buffer overflow via integer wraparound in GNU Emacs for Android's TrueType font parser allows an attacker to corrupt heap memory and potentially achieve code execution by delivering a crafted font file through email, the built-in EWW browser, or documents using custom typefaces. The flaw is confined to 32-bit builds where an unguarded addition in sfnt_read_cmap_format_12() wraps around when computing an xmalloc allocation size, producing a fatally undersized heap buffer. No public exploit has been identified at time of analysis and this vulnerability is not listed in CISA KEV; however, CERT-PL reported the issue and an upstream patch commit is available.
GNU Emacs for Android leaks heap memory contents through a crafted TrueType variable font, enabling ASLR bypass as a stepping stone to further exploitation. The flaw resides in the gvar table parser (src/sfnt.c), where an off-by-one error in shared-coordinate index boundary checks allows a font file to trigger an out-of-bounds heap read via memcpy. Attack delivery is broad: malicious fonts can reach victims through email rendered in Emacs, EWW (Emacs Web Wowser) browsing, or documents applying custom faces - all requiring user interaction but no authentication. No public exploit code or CISA KEV listing has been identified at time of analysis; an upstream fix commit is available but no formally released patched version has been independently confirmed.
Man-in-the-middle interception of ECOVACS PRO app traffic is possible due to improper TLS server certificate validation (CWE-295) in both the Android and iOS versions of the application, published by ECOVACS Robotics and coordinated by JPCERT under JVNVU92804348. An attacker with a network-positioned MITM capability can present a rogue certificate that the app accepts without proper validation, enabling retrieval and alteration of all app-server communications, which may include device control commands, account credentials, and home telemetry. No active exploitation is confirmed (not in CISA KEV), and no public exploit code has been identified at time of analysis.
SamsungPassAutofill prior to version 5.2.10.x on Samsung Android devices improperly exports application components, enabling a locally-installed malicious app to access sensitive autofill credential data with user interaction. The CVSS 4.0 vector (AV:L/PR:L/UI:A/VC:H) confirms the attack is constrained to on-device, low-privilege access requiring user-triggered activity, yielding a moderate score of 5.1 despite high confidentiality impact. No public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV.
AppLock on Samsung Mobile Devices prior to SMR Aug-2026 Release 1 exposes improperly exported Android application components, enabling a physical attacker to bypass the app lock protection layer entirely. The flaw grants access to confidentiality- and integrity-sensitive data within locked applications without satisfying the intended authentication challenge. No public exploit is identified at time of analysis; exploitation is constrained to physical device access, limiting but not eliminating real-world risk for lost or stolen device scenarios.
Unauthorized file deletion via improperly exported Android components in Samsung Contacts prior to SMR Aug-2026 Release 1 allows any locally-installed malicious application to invoke the exported component and delete files under Samsung Contacts' privilege without requiring any elevated permissions of its own. The vulnerability stems from an Android component export misconfiguration, granting third-party apps unintended access to privileged file operations. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low attack complexity and absence of privilege requirements make this straightforward to exploit on affected devices.
OAuth token hijacking in the Salon Booking System WordPress plugin (through 10.30.33) allows unauthenticated remote attackers to overwrite the site's stored Google Calendar connection credentials with attacker-controlled OAuth tokens, fully hijacking the calendar integration. Exploitation requires the target site to have independently configured a Google OAuth client for the calendar sync feature, limiting the exposed population. No public exploit has reached CISA KEV status, but a publicly available proof-of-concept was published by WPScan, and EPSS remains low at 0.14% (3rd percentile), consistent with a niche plugin requiring a non-default configuration. The primary consequence is persistent integrity and availability disruption of the booking-calendar workflow, with a secondary confidentiality risk if future appointment data is synced to the attacker's Google account.
Server-Side Request Forgery in adenot mcp-google-search up to version 0.3.1 allows a local low-privileged user to direct the read_webpage tool to fetch arbitrary internal network resources, including localhost, RFC 1918 ranges, cloud metadata endpoints, and link-local addresses, by supplying a crafted url argument. The vulnerability stems from the absence of URL validation prior to Axios-driven HTTP fetching in src/index.ts. No active exploitation is confirmed and no CISA KEV listing exists, though the CVSS 4.0 E:P modifier indicates proof-of-concept code exists; an upstream fix is available via a specific commit.
Open redirect in the Home Assistant Android Companion App (prior to 2026.6.1) enables credential phishing attacks against new users via crafted homeassistant://invite deep links. Because no screen in the invitation or onboarding flow displays the parsed server hostname before the WebView commits to it, an attacker who delivers a malicious invite link can silently redirect the victim's onboarding session to an attacker-controlled server presenting a look-alike login page. No public exploit code has been identified at time of analysis; the CVSS score of 4.3 (C:L) understates real-world impact given that captured credentials yield full smart-home access.
Datadog Android app versions prior to 5.9.2 structurally associate authenticated users' Datadog UUIDs with Google Firebase Installation IDs on every successful login, transmitting this stable cross-session identifier - alongside crash stack traces that may include in-flight application data, internal class names, package names, and breadcrumbs - to Google's Firebase Crashlytics backend without an identifiable user consent gate or opt-out mechanism. The exposure is not triggered by an external attacker but occurs automatically during normal authenticated app usage for all affected users. No active exploitation has been identified (SSVC Exploitation: none; no CISA KEV listing), and no public exploit code exists; the primary risk is regulatory and privacy-related rather than direct technical compromise.
Session injection in the Datadog Android app (versions prior to 5.9.2) allows any zero-permission co-installed application to hijack the victim's Datadog identity by delivering crafted OAuth tokens directly to an unguarded exported activity, which auto-logs the victim in under an attacker-controlled identity without backend token validation. The vulnerability stems from AppActivity being declared android:exported='true' with no permission guard, accepting and persisting arbitrary UserSession data deserialized from intent Bundle extras. SSVC assessment lists exploitation as none and no public exploit has been identified, but the zero-permission precondition dramatically lowers the attacker capability bar.
Plaintext SQLite database storage in the Datadog Android application exposes operationally sensitive monitoring metadata to anyone with physical access to the device or the ability to perform forensic acquisition. Two Room-managed databases - LocalNotificationDatabase and SearchRecentDatabase - store incident notification recipients, deeplinks, service names, and free-text search queries without at-rest encryption; no SQLCipher or equivalent openHelperFactory configuration was found in the codebase. Protection relies entirely on the Android application sandbox, which is insufficient for this class of data in high-risk deployment environments such as on-call engineering teams managing production infrastructure. No public exploit code exists and CISA has not added this to the KEV catalog.
Notification dismissal in the Datadog Android application (versions prior to 5.9.2) can be triggered by any zero-permission co-installed application through the improperly exported BubbleChatActivity component (CWE-926), allowing silent cancellation of the hard-coded Bits AI chat notification (ID 9201) with no identity validation of the caller or their supplied conversation_id. The impact is limited to nuisance-level denial of that specific notification and potential facilitation of in-app phishing workflows, with chat content remaining server-authentication gated and inaccessible to the attacker. SSVC assessment confirms no known active exploitation, and no public exploit code has been identified at time of analysis.
Six exported Android App Widget configuration activities in the Datadog Android application (versions prior to 5.9.2) allow a co-installed zero-permission malicious app to brute-force sequential App Widget IDs and trigger automatic Datadog session login for the victim, exposing live operational data - dashboards, SLOs, on-call schedules, incident details - as a visual side-channel. Exploitation is constrained by three simultaneous preconditions and data exfiltration is limited to screen-visible disclosure only, with no programmatic return path. No public exploit has been identified at time of analysis; SSVC rates exploitation as none with partial technical impact.
Forged on-call acknowledgment and confused-deputy execution in the Datadog Android application (versions prior to 5.9.2) allows any co-installed malicious app to silently dismiss real production incident alerts on behalf of the victim by exploiting an unguarded exported Activity with no permission check. An attacker-controlled app can supply crafted Intent extras to forge a backend Acknowledge API call using the victim's authenticated session, redirect the Datadog process into non-exported internal components, and surface a spoofed alert over the device lock screen. No public exploit has been identified at time of analysis; exploitation requires a malicious co-installed app plus a single user tap.
Null pointer dereference in the llama.cpp LLaMA-Android JNI wrapper's bench_1model() function allows denial of service via a crafted model file. Builds b1886 through b7445 (packaged releases 0.9.0-0.17.1) are affected; the function skips null validation on the model context pointer before dereferencing it, so supplying a malformed or truncated GGUF model file triggers a SIGSEGV that terminates the Android application process. No public exploit has been identified at time of analysis and this is not listed in CISA KEV, but the attack path is mechanically simple for anyone able to deliver a crafted model to the device.
Cross-origin data leakage in Google Chrome's GPU process - caused by an integer overflow (CWE-190) - enables a remote attacker who has already achieved renderer process compromise to read data across origin boundaries by delivering a crafted HTML page. All Chrome desktop releases prior to 151.0.7922.109 are affected. No public exploit or CISA KEV listing exists at time of analysis; the chained nature of the attack (requiring a prior renderer compromise) substantially constrains real-world risk despite the broad deployment footprint of Chrome.
Uninitialized memory use in Skia, Chrome's 2D graphics engine, exposes a cross-origin data leak primitive in Google Chrome prior to 151.0.7922.109. Exploitation is constrained to attackers who have already achieved renderer process compromise - making this a second-stage, chained vulnerability rather than a standalone initial-access vector. No public exploit or active exploitation has been identified; SSVC rates this as non-automatable with partial technical impact, consistent with the low CVSS base score of 3.1.
Cross-origin data leakage in Google Chrome's Skia graphics library (versions prior to 151.0.7922.109) enables a remote attacker who has already achieved renderer process compromise to extract cross-origin data through a specially crafted HTML page. The vulnerability is classified CWE-457 (Use of Uninitialized Variable) and carries a low CVSS base score of 3.1, reflecting its dependency on a pre-existing renderer compromise as a prerequisite. No public exploit code has been identified at time of analysis, SSVC exploitation status is rated none, and a vendor-released patch is available in Chrome 151.0.7922.109.
Uninitialized GPU memory in Google Chrome on Android prior to 151.0.7922.109 exposes sensitive process memory contents to a remote attacker who has already achieved renderer process compromise. The CWE-457 flaw allows the GPU component to read and return uninitialized memory regions when processing attacker-controlled HTML, resulting in confidentiality impact bounded to the compromised process scope. No public exploit code exists and CISA SSVC rates exploitation as none at time of analysis, making this a second-stage information disclosure component rather than a standalone critical threat.
Timing side-channel exposure in Apache Portable Runtime Utility (APR-util) versions 1.2.0 through 1.6.3 allows network-accessible attackers to statistically recover passwords or hashes by measuring response-time variance in the `apr_password_validate()` function, which performs non-constant-time comparisons. The risk is materially elevated on platforms lacking native `crypt()` support - specifically Windows, Android, BeOS, and NetWare - where the non-constant-time code path is always exercised rather than conditionally. No public exploit has been identified at time of analysis, though the SSVC framework assesses the attack as automatable with partial technical impact.
Cross-site request forgery in the Google Authenticator WordPress plugin before version 0.56 allows an unauthenticated attacker to overwrite a logged-in user's TOTP secret by tricking them into loading a malicious page. The forged request silently replaces the victim's two-factor secret with one the attacker controls, enabling the attacker to generate valid OTPs and lock the legitimate account owner out. A public proof-of-concept is available via WPScan; no active exploitation is confirmed in CISA KEV, and EPSS of 0.11% (2nd percentile) aligns with SSVC's 'not automatable' designation.
Session isolation bypass in Electron allows a malicious or compromised Chrome extension loaded into one session to cross session boundaries and access, navigate, and script windows belonging to a completely separate session. Affected are Electron applications prior to versions 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3 that invoke session.loadExtension and rely on multi-session architecture as a security boundary - a narrowly scoped but architecturally significant trust boundary violation. No public exploit code or CISA KEV listing exists at time of analysis; exploitation requires attacker control of an extension the application has explicitly loaded.
Remote code execution and privilege escalation are the headline risks in this Jenkins advisory covering multiple vulnerabilities in Jenkins core (versions 2.575/LTS 2.568.1 and earlier) and eleven plugins. The most critical flaw (CVE-2026-70426) bypasses the JEP-200 deserialization class filter via a fallback path in the Remoting library, allowing an agent process or a user with Agent/Connect permission to execute arbitrary code on the Jenkins controller. A companion archive-extraction vulnerability (CVE-2026-70427) enables arbitrary file writes to the controller filesystem - including into init.groovy.d or the plugins directory - through crafted tar/tar.gz archives delivered from an agent; no public exploits or CISA KEV listing were identified for any issue in this advisory at time of analysis.
Local root escalation on the ZTE Nubia Red Magic 11 Air (NX799J) gaming smartphone stems from a built-in PostgreSQL service that runs as root, listens on a device port, and is guarded only by weak credentials. Because PostgreSQL's COPY FROM PROGRAM syntax executes OS commands with the server's privileges, any local app that reaches the database can break out of the Android application sandbox and run commands as root. No public exploit identified at time of analysis, though the technique (weak-cred Postgres plus COPY FROM PROGRAM) is well understood and trivially reproducible.
Unauthorized access to other users' personal data in SirenGPS Android Application 2.19.44 stems from the backend API failing to verify that a requesting user is authorized to act on the target user identifier supplied in API parameters. An authenticated attacker exploiting this horizontal privilege escalation can read and overwrite arbitrary users' personal information with only low-privilege access. No public exploit identified at time of analysis and EPSS is extremely low (0.15%, 5th percentile), but a detailed researcher advisory is publicly available on GitHub, lowering the bar for replication.
Authentication bypass in the My Safetipin Android application version 5.2.1 stems from hardcoded credentials in the authentication module that produce predictable OTP values, letting remote attackers log in as arbitrary users and take over accounts without legitimate credentials. Any personal-safety data stored in a victim's account - location history, safety pins, and profile details - becomes exposed and modifiable. No public exploit has been identified at time of analysis, and the EPSS score of 0.27% (18th percentile) reflects low observed exploitation activity despite the maximal CVSS rating.
Path traversal in ZomboDroid Meme Generator App 4.6830 for Android exposes file system access beyond intended directories through manipulation of function t5.l.c in the com.zombodroid.MemeGenerator component. Exploitation is constrained to local access, yielding limited confidentiality, integrity, and availability impact consistent with the CVSS 4.0 score of 1.9. A public proof-of-concept is available on GitHub, though no patch has been released and the vendor did not respond to coordinated disclosure - leaving no official remediation path.
URI scheme injection in @a2ui/web_core's openUrl function enables stored or reflected XSS by allowing an agent-controlled javascript: URI to be passed directly to window.open() without validation. Any application using the Button component's functionCall action on default deployments is affected, since the Basic Catalog is enabled with no special configuration required. CVSS 4.0 impact metrics VC:H/VI:H confirm full confidentiality and integrity compromise at the vulnerable-system level; no active exploitation is confirmed (CVSS E:U, no CISA KEV listing).
Information disclosure in Firefox for Android and Firefox Focus for Android exposes sensitive user data to network-based attackers who can lure a victim into interacting with a crafted web resource. The vulnerability, tracked under CWE-200 and assigned a CVSS score of 6.5 with high confidentiality impact, is limited to Android platform builds and does not affect desktop Firefox. Mozilla patched this in Firefox 153.0.3 per advisory mfsa2026-73; no public exploit or active exploitation has been identified at time of analysis.
Signature forgery in the MonsterInsights WordPress plugin before 11.1.0 allows unauthenticated network attackers to overwrite plugin configuration values when the site is not connected to Google Analytics. The root cause is that the HMAC signing key used to authenticate a specific AJAX action defaults to an empty string in that disconnected state, making any forged HMAC trivially valid. The practical impact is limited to disrupting server-side analytics in Manual GA4 mode; no public exploit identified as actively exploited (not in CISA KEV), though a publicly available proof-of-concept exists and the EPSS probability is low at 0.15%.
Server-Side Request Forgery in Simple Google Calendar Outlook Events Widget WordPress plugin (all versions before 3.1.0) permits unauthenticated remote attackers to supply arbitrary URLs that the server fetches without validation, potentially exposing responses from internal services. The plugin is confirmed vulnerable by WPScan and a public exploit exists, though EPSS at 0.14% (4th percentile) indicates limited observed exploitation despite the available POC. This vulnerability is not listed in CISA KEV at time of analysis.
Server-Side Request Forgery (SSRF) in Microsoft Edge (Chromium-based) enables a remote, unauthenticated attacker to perform network-level spoofing by manipulating the browser into issuing crafted requests to unintended destinations. All versions of the Chromium-based Edge are affected per the CPE wildcard match, and the CVSS scope change (S:C) confirms the impact extends beyond the browser itself to backend or internal systems reachable from the victim host. No public exploit exists (E:U) and an official vendor patch has been released (RL:O), keeping real-world exploitation probability low at this time.
Origin validation error in Microsoft Edge (Chromium-based) enables a remote unauthenticated attacker to perform cross-origin spoofing attacks, achieving high confidentiality impact and limited integrity impact against victims who interact with attacker-controlled content. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N) with temporal indicators E:U/RL:O/RC:C indicates an officially patched vulnerability with no publicly proven exploit code and confirmed vendor reporting. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Origin validation error in Microsoft Edge (Chromium-based) allows network-positioned unauthenticated attackers to perform cross-origin tampering when a victim user interacts with malicious web content. The flaw (CWE-346) undermines the browser's origin enforcement logic, enabling integrity and confidentiality compromise at low severity per CVSS 5.4. Tagged as an Authentication Bypass vector, suggesting edge cases where origin-gated auth flows in Edge may be bypassed. No active exploitation confirmed (not in CISA KEV), no public POC identified, and a vendor patch is available via MSRC.
Missing authorization controls in Microsoft Edge (Chromium-based) allow a local attacker without any system privileges to bypass authorization and perform tampering actions against the browser. The flaw (CWE-862) results in high confidentiality impact per the CVSS vector, though the description characterizes the effect as tampering - a discrepancy addressed in confidence notes below. No public exploit code has been identified and Microsoft has released an official patch through the MSRC advisory portal.
Code injection (CWE-94) in Microsoft Edge (Chromium-based) enables network-based spoofing attacks against users who interact with attacker-controlled content. An unauthorized remote attacker can exploit improper code generation controls to inject and execute code within the browser's execution context, crossing security scope boundaries (S:C) to spoof content or interfaces presented to the victim. No public exploit has been identified at time of analysis (E:U temporal metric), and Microsoft has released an official fix via the MSRC update guide.
Spoofing via origin validation failure in Microsoft Edge (Chromium-based) allows a network-adjacent unauthenticated attacker to deceive users or systems about the true origin of web content or requests. All Chromium-based Edge versions are affected per the wildcard CPE, and a vendor-released patch is confirmed via the Microsoft Security Response Center. No public exploit code exists and active exploitation is not confirmed - the CVSS temporal metric E:U (exploit unproven) and absence of CISA KEV listing reinforce a currently theoretical risk level.
Microsoft Edge (Chromium-based) is affected by a Time-of-Check Time-of-Use (TOCTOU) race condition that allows a remote, unauthenticated attacker to disclose sensitive information over the network, contingent on user interaction. The flaw exploits the timing gap between a security check and subsequent resource use within the Chromium-based browser engine, potentially exposing cross-origin data or internal browser state. No active exploitation has been confirmed by CISA KEV, and the temporal CVSS metrics (E:U) confirm no proven exploit code exists at time of analysis; a vendor patch is available via MSRC.
Origin validation error in Microsoft Edge (Chromium-based) enables a local, unauthenticated attacker to bypass cross-origin restrictions and perform data tampering. The CVSS vector (AV:L/PR:N) indicates that any unprivileged local user - including guest or kiosk session users - can trigger this flaw without requiring prior authentication or user interaction. With a high confidentiality impact (C:H) and low integrity impact (I:L), exploitation could expose sensitive browser-held data while also permitting limited content manipulation. No public exploit code has been identified and CISA KEV does not list this CVE; the temporal metric E:U corroborates no known active exploitation at time of analysis.
Improper export of the DialerActivity component in textPlus Text Message and Call App (Android, versions up to 8.3.5) allows any co-installed application on the same device to invoke the com.gogii.textplus dialer component without authorization. Classified under CWE-926, this flaw permits a locally-present malicious app to trigger dialer functionality, leading to limited information disclosure and unauthorized interaction with call-related features. No public KEV listing confirms active exploitation, but a proof-of-concept is publicly available on GitHub, lowering the technical barrier for abuse.
Cleartext storage of personally identifiable information in Meesho Online Shopping App (Android, versions through 20260607) exposes user_id, phone number, email address, and name in the com.meesho.supply component without encryption. Exploitation requires physical access to the device and a degree of local privilege, making this a low-severity, localized threat rather than a remote or mass-exploitation risk. A proof-of-concept is publicly available via GitHub and Google Drive, though no active exploitation has been confirmed by CISA KEV.
Sensitive WooCommerce order data exposure in the PixelYourSite WordPress plugin (all versions through 11.2.1) allows unauthenticated remote attackers to retrieve full purchase metadata - product names, quantities, per-item prices, order totals, currency, and transaction IDs - for any order by supplying an arbitrary or invalid order key alongside a known order ID. The plugin's getWooPurchaseEventParams function resolves orders solely from the URL path order ID without validating the accompanying key, then emits the complete woo_purchase tracking payload directly into rendered page HTML via the pysOptions JavaScript object across all three supported integrations (Facebook Pixel, Google Analytics, and Google Tag Manager). No public exploit has been identified at time of analysis, but because WooCommerce order IDs are sequential integers by default, mass enumeration of the entire order history requires only a trivial HTTP loop.
SQL injection in the GSheetConnector CF7 Google Sheets Connector WordPress plugin (all versions through 5.2.1) enables authenticated administrators to exfiltrate arbitrary database contents via the unsanitized 's' search parameter. The root cause is a flawed sanitization chain: wp_unslash() removes magic-quote escaping while sanitize_text_field() fails to neutralize SQL metacharacters, leaving single quotes intact before direct query interpolation. No public exploit or CISA KEV listing has been identified at time of analysis, but the Wordfence disclosure includes direct source-code references confirming the vulnerable code paths in class-gs-cf7db-formEntryList.php and gs-cf7db.php.
Arbitrary local file read in gemini-bridge (versions 1.0.0-1.3.0) exposes any file accessible to the server process - SSH keys, cloud credentials, `.env` files, source code - through the `consult_gemini_with_files` tool when operating in inline mode. Compounding the local disclosure, file contents are simultaneously exfiltrated to Google's infrastructure via the Gemini CLI round-trip, extending blast radius beyond the local host. No public exploit identified at time of analysis, but the CVSS vector (AV:L/AC:L/PR:N/UI:N) indicates trivially low exploitation complexity, and the GHSA advisory explicitly calls out prompt-injection as a realistic delivery vector for AI agent pipelines. Vendor-released patch available in version 1.3.1.
Cleartext storage of sensitive information in Johnson Controls XAAP Application on Android (versions before 1.53) exposes sensitive data to retrieval by attackers who already have access to a jailbroken or otherwise compromised device. The flaw stems from insufficient data-at-rest protection (CWE-312), meaning credentials, tokens, or configuration data are stored without encryption in the app's local storage. No public exploit code exists and this vulnerability is not listed in CISA KEV; real-world risk is constrained by the requirement for prior device compromise.
Unbounded memory consumption in Google mcp-toolbox versions through 1.4.0 allows unauthenticated remote attackers to crash the service via a single oversized HTTP request. The /mcp endpoint's toolInvokeHandler uses Go's io.ReadAll without any body-size guard - no http.MaxBytesReader, no Content-Length pre-check - so a sufficiently large POST body linearly exhausts host RAM until the OS OOM killer terminates the process. No active exploitation is confirmed (CVSS 4.0 E:U), but the attack requires no authentication and trivial complexity, making any internet-exposed deployment an easy target for denial of service.
Authorization bypass in Google mcp-toolbox's bigquery-execute-sql tool (versions 0.16.1-1.4.0) allows authenticated low-privileged users to exfiltrate DDL schemas from explicitly restricted datasets and query federated external data via EXTERNAL_QUERY connections. The fail-open logic flaw stems from the tool treating an empty tableIDSet returned by the BigQuery dry-run API - which occurs for INFORMATION_SCHEMA and EXTERNAL_QUERY constructs - as a signal to skip allowedDatasets enforcement entirely. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though the bypass mechanism is straightforward for any authenticated toolbox user.
node-re2, the Node.js native binding for Google's RE2 regular expression engine, enters an infinite loop and leaks unbounded native memory when String.prototype.match is called with a global pattern capable of producing zero-width (empty string) matches. All versions prior to 1.25.2 are affected; because RE2 executes synchronously within the Node.js event loop thread, the hang is unrecoverable without a process restart, making any service that exposes RE2 global matching to externally-supplied input susceptible to complete denial of service. No public exploit code or CISA KEV listing has been identified at time of analysis, but the trigger condition is mechanically trivial and directly exercisable from patterns confirmed in the vendor's own test additions.
Out-of-bounds heap read in node-re2 prior to 1.25.2 allows process termination and limited heap memory disclosure when an attacker-influenced lastIndex value is used against a non-ASCII subject string. The flaw arises because lastIndex is validated against the UTF-8 byte length of the input but consumed as a UTF-16 code-unit offset - for any non-ASCII character, the UTF-8 byte count exceeds the UTF-16 unit count, creating a gap where a lastIndex passes the guard yet reads past the allocated buffer. The resulting crash is uncatchable by the Node.js process, making it an effective denial-of-service vector in any server application exposing this code path to external input. No active exploitation confirmed (not in CISA KEV); no public exploit code identified at time of analysis.
Search Atlas SEO WordPress plugin (all versions before 2.6.12) exposes its Google Indexing API integration to any authenticated user - including low-privilege subscribers - due to a missing capability and nonce check in an AJAX handler. Any user with a valid WordPress session can invoke the plugin's Google Indexing API endpoint to submit or remove site URLs from Google's search index and exhaust the site's indexing API quota. A publicly available exploit exists via WPScan, though EPSS at 0.14% (4th percentile) and the absence of a CISA KEV listing indicate limited observed exploitation activity at this time.
Side-channel information leakage in Google Chrome's Media component (versions prior to 151.0.7922.72) enables a remote attacker to leak cross-origin data by directing a victim to a crafted HTML page, bypassing same-origin policy protections through measurable side effects of media processing. Affected desktop users on all platforms running any Chrome release before 151.0.7922.72 are exposed to limited confidentiality loss. EPSS is 0.16% (6th percentile), SSVC exploitation status is none, and no public exploit has been identified at time of analysis - all signals converge on low real-world risk.
UI spoofing in the Google Chrome Updater component on Windows (prior to 151.0.7922.72) enables a local attacker to present a falsified interface to users by placing a malicious file in a location the Updater processes. Chromium's own team rates this 'Low' severity, consistent with the 4.0 CVSS score, EPSS of 0.10% (1st percentile), and SSVC exploitation status of 'none'. No public exploit exists at time of analysis, and a vendor-confirmed patch is available in Chrome 151.0.7922.72.
UI spoofing in Google Chrome for iOS prior to 151.0.7922.72 enables a remote attacker to deceive users into believing they are interacting with a legitimate browser interface by serving a crafted HTML page. The root cause is insufficient policy enforcement (CWE-346, origin validation error), allowing the attacker to manipulate rendered UI elements. No public exploit code exists and no active exploitation has been confirmed; EPSS stands at 0.16% (6th percentile) and CISA SSVC classifies exploitation as none, placing this firmly in a patch-and-monitor priority tier rather than an emergency response.
Navigation restriction bypass in Google Chrome DevTools prior to version 151.0.7922.72 enables remote attackers to circumvent browser navigation controls by luring a user into opening a specially crafted malicious file. The flaw stems from CWE-20 insufficient input validation within the DevTools component, resulting in high integrity impact per CVSS. No public exploit has been identified and EPSS exploitation probability is very low at 0.16% (6th percentile); notably, the Chromium security team internally rated this 'Low' severity despite the medium NVD CVSS score of 6.5.
UI spoofing in Google Chrome for iOS prior to version 151.0.7922.72 enables a remote unauthenticated attacker to misrepresent critical interface elements - such as the address bar or origin indicators - through a specially crafted HTML page. Classified as CWE-451 (UI Misrepresentation of Critical Information), the impact is limited to integrity: no code execution or data exfiltration is possible directly, but users can be deceived into trusting a malicious page as legitimate. No public exploit code exists, EPSS sits at 0.16% (6th percentile), and Chromium internally rated this as Low severity - consistent with a constrained, social-engineering-dependent attack surface.
Chrome for iOS prior to 151.0.7922.72 exposes potentially sensitive process memory contents to an attacker with physical access to the device through an inappropriate implementation flaw. The vulnerability is classified CWE-200 (Information Disclosure) and is iOS-platform-specific, not affecting Chrome on other operating systems. No public exploit code exists and CISA SSVC confirms no active exploitation, placing this firmly in the low-urgency tier despite requiring prompt patching for high-assurance mobile environments.
UI spoofing in Google Chrome's Passwords subsystem (versions prior to 151.0.7922.72) enables remote attackers to manipulate password-related UI elements through malicious network traffic, potentially deceiving users into submitting credentials to unintended destinations. Exploitation requires active user interaction (UI:R per CVSS), and real-world risk is constrained by an EPSS of 0.15% (5th percentile) and SSVC confirmation of no known exploitation and a non-automatable attack path. No public exploit identified at time of analysis; vendor patch is available in Chrome 151.0.7922.72.
UI spoofing in Google Chrome's Passwords component (versions prior to 151.0.7922.72) allows a remote unauthenticated attacker to manipulate how credential-related UI elements are displayed by delivering maliciously crafted network traffic to a browsing user. The root cause is insufficient input validation (CWE-20) in the Passwords subsystem, which fails to sanitize externally sourced data before rendering it in the browser interface. No public exploit code has been identified and CISA has not listed this in KEV; EPSS of 0.15% (5th percentile) confirms low automated exploitation probability, consistent with the SSVC rating of exploitation: none.
UI spoofing in Google Chrome's Settings component (versions prior to 151.0.7922.72) enables remote attackers to misrepresent critical interface elements to victims via malicious network traffic, requiring user interaction to trigger. EPSS at 0.15% (5th percentile) and CISA SSVC exploitation rating of none align with the Chromium team's own Low severity classification, making this a low-urgency issue despite its network-accessible attack vector. Google has released a patch in stable channel version 151.0.7922.72; no public exploits are identified at time of analysis.
UI spoofing in Google Chrome for Android (prior to 151.0.7922.72) enables remote unauthenticated attackers to present misleading interface elements to users through a crafted HTML page. The flaw stems from an inappropriate implementation in Chrome's input handling on Android, classified under CWE-451 (UI Misrepresentation of Critical Information), meaning the browser fails to correctly represent critical UI state to the user. No public exploit code exists and CISA has not listed this in KEV; EPSS is extremely low at 0.16% (6th percentile), consistent with Chromium's own Low severity classification.
UI spoofing via Google Lens in Google Chrome prior to 151.0.7922.72 is achievable by a remote attacker who has already compromised the renderer process, using a crafted HTML page to misrepresent interface elements to the victim. The attack requires a chained exploitation scenario: renderer compromise as a prerequisite, followed by abuse of an inappropriate implementation in the Lens component (CWE-451) to manipulate what the user perceives in the browser UI. No active exploitation is confirmed - CISA KEV does not list this CVE, SSVC assessment shows exploitation status of none, and EPSS sits at 0.16% (6th percentile), indicating very low real-world exploitation probability at time of analysis.
Information disclosure in Google Chrome's WebXR subsystem prior to version 151.0.7922.72 allows unauthenticated remote attackers to read potentially sensitive process memory contents by luring a victim to a crafted HTML page. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) indicates a network-accessible, low-complexity path to high confidentiality impact, though Chromium's internal severity rating of Low and an EPSS of 0.16% (6th percentile) reflect limited real-world exploitation risk. No public exploit code exists and CISA SSVC rates exploitation as none, making this a watch-and-patch item rather than an emergency response trigger.
Cross-origin data leakage in Google Chrome's Speech component prior to version 151.0.7922.72 exposes sensitive information to attackers who have already achieved renderer process compromise. The vulnerability stems from insufficient policy enforcement in the Speech API, allowing a crafted HTML page to bypass cross-origin boundaries and exfiltrate data. With no CISA KEV listing, no public POC, and an EPSS of 0.16% (6th percentile), this is a low-probability exploitation scenario best understood as a potential second-stage component in a multi-vulnerability chain rather than a standalone attack.
UI spoofing in Google Chrome on iOS prior to 151.0.7922.72 enables a remote attacker to deceive users about page identity or browser security state by serving a crafted HTML page. The flaw is iOS-specific, exploiting an inappropriate implementation in the Chrome for iOS rendering layer rather than the broader Chromium engine, and requires only that the victim navigate to an attacker-controlled page. No public exploit has been identified and EPSS stands at 0.19% (9th percentile), consistent with Chromium's own 'Low' internal severity classification; this is a real but low-urgency integrity issue.
Process memory disclosure in Google Chrome's WebGL implementation allows a remote attacker to read potentially sensitive data from the browser's memory by luring a user to a specially crafted HTML page. Affected versions are all Chrome releases prior to 151.0.7922.72 across desktop platforms. No public exploit code has been identified and EPSS sits at 0.16% (6th percentile), indicating low real-world exploitation probability despite the High confidentiality rating in the CVSS vector.
Cross-origin data leakage in Google Chrome for Android (prior to 151.0.7922.72) stems from insufficient policy enforcement in the USB component, exploitable only after the attacker has already compromised the renderer process. Exploitation requires luring a victim to a crafted HTML page in a pre-compromised renderer context, making this a secondary-stage vulnerability in a chained attack rather than a standalone threat. EPSS sits at 0.19% (9th percentile), SSVC records no exploitation activity, and the vulnerability is not listed in CISA KEV - consistent with its low severity rating and demanding prerequisite.
Domain spoofing in Google Chrome on Android (all versions prior to 151.0.7922.72) results from a race condition in the PictureInPicture component, enabling a remote attacker to misrepresent the origin domain shown to a user when they interact with a crafted HTML page. The integrity impact is limited to the browser UI trust indicator - no code execution or data exfiltration occurs directly - but successful spoofing can be chained with credential phishing against a falsely trusted domain. No active exploitation has been confirmed (not listed in CISA KEV), and the EPSS score of 0.16% at the 6th percentile reflects very low exploitation probability, consistent with Chromium's own 'Low' severity classification.
UI spoofing in Google Chrome's Extensions subsystem (all versions prior to 151.0.7922.72) allows an attacker who tricks a user into installing a crafted malicious extension to misrepresent critical security indicators within the browser interface. The flaw stems from incorrect security UI rendering in the Extensions component (CWE-451), enabling deceptive presentation of extension trust signals or permissions. No public exploit has been identified at time of analysis and EPSS is 0.10% (1st percentile), aligning with Chromium's own internal 'Low' severity rating; however, the ubiquitous deployment footprint of Chrome elevates the aggregate exposure.
Cross-origin data leakage in Google Chrome's Passwords component (versions prior to 151.0.7922.72) exposes password-related data to attackers who have already compromised the renderer process and can deliver a crafted HTML page. The flaw stems from an inappropriate implementation that fails to enforce proper origin validation within the Passwords subsystem, making it a second-stage element in a chained attack rather than a standalone threat. No public exploit has been identified, EPSS is 0.16% (6th percentile), SSVC records no known exploitation, and Chromium internally rates this Low severity - consistent with the high prerequisite bar of prior renderer compromise.
Navigation restriction bypass in Google Chrome on macOS (versions prior to 151.0.7922.72) permits a local attacker to circumvent the browser's navigation controls by delivering a crafted malicious file. The CVSS vector (AV:L/I:H) confirms the impact is limited to integrity - an attacker who achieves local access can subvert Chrome's navigation security model without requiring elevated privileges or user interaction beyond obtaining local system access. With an EPSS score of 0.10% (1st percentile), no CISA KEV listing, and Chromium's own classification of Low severity, real-world exploitation risk is low despite the 6.2 CVSS base score.
Navigation restriction bypass in Google Chrome for Android (prior to 151.0.7922.72) originates from an inappropriate implementation in the browser's Media component, permitting a remote attacker to circumvent built-in navigation controls by delivering a crafted HTML page to a victim. The CVSS 4.3 score reflects a limited integrity-only impact - no code execution, no data exfiltration - and user interaction is required per the vector (UI:R). EPSS at 0.18% (8th percentile) and the absence of any KEV listing or public exploit indicate low real-world exploitation probability; Chromium's own internal severity rating of 'Low' is consistent with this assessment.
Uninitialized memory use in Skia, Chrome's 2D graphics rendering engine, exposes process memory contents to remote attackers on Windows via crafted HTML pages in Google Chrome versions prior to 151.0.7922.72. The flaw is strictly an information disclosure issue (CWE-457), with no integrity or availability impact, affecting only the Windows platform per the vulnerability description. No public exploit code has been identified, EPSS places exploitation probability at 0.19% (9th percentile), and SSVC classifies exploitation as none with partial technical impact - collectively suggesting limited real-world risk despite the CVSS C:H rating.
Navigation input validation bypass in Google Chrome prior to 151.0.7922.72 enables a renderer-compromised attacker to circumvent navigation restrictions via a crafted HTML page. The flaw is the second stage of a chained attack - exploitation requires a prior renderer process compromise, substantially raising the practical bar for abuse. No public exploit code or active exploitation has been identified; EPSS sits at 0.18% (8th percentile), consistent with its role as a post-exploitation primitive rather than an initial access vector.
Same-origin policy bypass in Google Chrome's Bluetooth subsystem (prior to 151.0.7922.72) can be triggered by an attacker who has already achieved renderer process compromise, using a crafted HTML page to abuse insufficient policy enforcement in the Web Bluetooth layer. The exploit chain requires a pre-existing foothold in the renderer, which limits real-world risk considerably - Chrome's own security team rated this 'Low' severity. No active exploitation has been confirmed (not listed in CISA KEV), and the EPSS score of 0.18% (8th percentile) reflects negligible observed exploitation activity.
Insufficient policy enforcement in Chrome's Speech component prior to version 151.0.7922.72 enables remote attackers to bypass site isolation - a core security boundary - via a crafted HTML page requiring only user interaction. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N) signals high integrity impact with no privilege requirement, meaning an unrelated web page can be weaponized as the delivery vehicle. No public exploit code has been identified and EPSS sits at a low 0.18% (8th percentile), consistent with the Chromium team's own 'Low' severity classification despite the NVD medium score; however, the site isolation bypass class of vulnerability is historically sensitive and warrants prompt patching.
Cross-origin data leakage in Google Chrome on Android prior to 151.0.7922.72 enables a local attacker to read data from a different origin by directing a victim user to a crafted HTML page. The flaw stems from an inappropriate browser implementation (CWE-346 Origin Validation Error), undermining the Same-Origin Policy's isolation guarantees on the Android platform. No public exploit code exists and no active exploitation has been observed; SSVC assessment confirms exploitation status as none, making this a low-urgency but noteworthy information-disclosure defect.
UI spoofing in Google Chrome's Global Media Controls component prior to version 151.0.7922.72 enables remote attackers to misrepresent interface elements when a victim visits a crafted HTML page. The flaw is rooted in CWE-451 (misrepresentation of critical UI information), allowing attacker-controlled content to manipulate what the media controls overlay displays. No public exploit code exists and no active exploitation has been identified; EPSS at 0.17% (7th percentile) and SSVC exploitation status of 'none' both corroborate this as a low-urgency, routine-patching-priority finding.
Same-origin policy bypass in Google Chrome's Cast component allows remote attackers to perform limited cross-origin integrity actions against victims who visit a crafted HTML page. All Chrome versions prior to 151.0.7922.72 are affected across Windows, macOS, and Linux. No active exploitation is confirmed (not in CISA KEV), no public exploit code has been identified, and Chromium's own internal severity rating is Low - signals that align with the very low EPSS score of 0.18% at the 8th percentile.
Cross-origin data leakage in Google Chrome's Blink rendering engine (versions prior to 151.0.7922.72) exposes data protected by the Same-Origin Policy to remote attackers who can lure a victim to a crafted HTML page. The flaw, classified as CWE-346 (Origin Validation Error), allows Blink to improperly handle origin boundaries, enabling a malicious page to read cross-origin resource data. No public exploit has been identified and EPSS sits at 0.17% (7th percentile), consistent with SSVC's 'Exploitation: none' designation and absence from CISA KEV.
Cross-origin data leakage in Google Chrome on Android (prior to 151.0.7922.72) results from an inappropriate UI implementation that allows a remote attacker to extract data from a different web origin when a user is socially engineered into performing specific UI gestures on a crafted HTML page. Rated CVSS 3.1 (Low) with EPSS at 0.17% (7th percentile) and SSVC exploitation status of 'none,' this vulnerability presents minimal immediate operational risk. No public exploit code exists and the issue is not listed in CISA KEV; a vendor-released patch is available in the stable channel update.
Side-channel memory leakage in Chrome's WebCodecs API prior to version 151.0.7922.72 enables a remote, unauthenticated attacker to extract potentially sensitive data from the browser's process memory by luring a victim to a crafted HTML page. The vulnerability stems from improper protection of physical side-channels (CWE-1300) within the WebCodecs media processing subsystem. No active exploitation has been identified - SSVC rates exploitation as none and EPSS places this in the 7th percentile - but the high confidentiality impact score reflects that successful exploitation could expose in-memory session data or other sensitive content.
Cross-origin data leakage in Google Chrome prior to 151.0.7922.72 is achievable through a CSS policy bypass, enabling remote unauthenticated attackers to exfiltrate data across origin boundaries when a victim visits a crafted HTML page. The root cause is improper origin validation (CWE-346) in Chrome's CSS subsystem, allowing CSS mechanisms to circumvent same-origin policy enforcement and read restricted cross-origin content. No public exploit code exists and no active exploitation has been identified; EPSS probability is 0.18% (8th percentile), consistent with the SSVC 'Exploitation: none' assessment and Chrome's own 'Low' severity designation for this issue.
Cross-team credential disclosure in the Apache Airflow Google Provider's Cloud Secret Manager backend exposes every team's Connections and Variables to every other team in multi-team deployments. The backend's public methods accepted a team_name parameter but silently discarded it before the internal secret lookup, collapsing all team namespaces into one shared, unscoped lookup. No public exploit has been identified at time of analysis; the vendor-released fix is apache-airflow-providers-google 22.3.0.
Session token exposure in the Mira Android app (Quanovate Tech Inc.) leaks live authentication credentials to third-party web properties and referrer logs whenever users trigger in-app WebView flows such as shop redirects. The app appends the active session token as a URL query string parameter and embeds a persistent user identifier in the WebView User-Agent header, both of which are transmitted to any destination or JavaScript context receiving that traffic. Reported by ICS-CERT under medical advisory ICSMA-26-223-01, this vulnerability affects a healthcare-adjacent platform, amplifying the sensitivity of exposed credentials; no public exploit code or CISA KEV listing has been identified at time of analysis.
Remote code execution in Microsoft Edge (Chromium-based) below version 151.0.4129.78 stems from a type confusion flaw (CWE-843) in the browser engine, exploitable over the network when a user visits or interacts with attacker-controlled content. The vendor has confirmed patch availability and the flaw is tagged as causing memory corruption, which aligns with the typical consequence of type confusion in browser engines. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis, though the unauthenticated network vector with low attack complexity warrants prioritized patching in enterprise environments.
Information disclosure in Nuxt's development server exposes the project's absolute filesystem root path and a persistent per-project workspace UUID to unauthenticated LAN-adjacent attackers via the Chrome DevTools workspace endpoint. The prior security fix (GHSA-rq7w-g337-39qq) introduced a local-request gate that trusts the attacker-supplied Host header instead of the actual TCP peer address, meaning a non-browser client such as curl can bypass it by omitting Sec-Fetch-Site, Origin, and Referer headers while forging Host: localhost. Impact is confined to information disclosure; no public exploit has been independently identified at time of analysis, though the official advisory provides a working proof-of-concept curl command. Production builds are entirely unaffected.
Improper cryptographic signature verification in Estonian RIA's libdigidocpp core library and its consumer applications - DigiDoc4, DigiDoc for Android, and DigiDoc for iOS - enables bypassing of XAdES signature validity checks through unhandled exceptional conditions during BDOC container parsing. Affected versions span libdigidocpp 4.1.0-4.2.0, DigiDoc4 4.7.0-4.8.1, DigiDoc Android 2.7.0-2.7.1, and DigiDoc iOS 2.8.0, all of which have vendor-released patches. A proof-of-concept is indicated by the CVSS 4.0 E:P exploit maturity modifier, though no active exploitation has been confirmed and this CVE is not listed in CISA KEV.
Uninitialized heap memory exposure in GNU Emacs for Android's sfnt font parser allows a remote, unauthenticated attacker to trigger information disclosure, process crashes, or arbitrary memory access on 32-bit targets by delivering a crafted font file. The flaw in sfnt_read_table_directory() (src/sfnt.c) stems from an incorrect comparison variable in the read-length check, causing the parser to trust an attacker-controlled table-entry count without proper bounds validation. No public exploit or CISA KEV listing exists at time of analysis; exploitation requires user interaction with attacker-delivered content such as an email, EWW-rendered webpage, or a document referencing a malicious font face.
Heap buffer overflow in GNU Emacs for Android's TrueType font parser (sfnt_read_name_table() in src/sfnt.c) enables potential code execution when a 32-bit Emacs process loads a crafted font file. The root cause is a CWE-190 integer overflow that wraps a 32-bit allocation size calculation, producing an undersized heap buffer that a subsequent read() call overflows. Delivery is possible through multiple standard Emacs workflows - email rendering, EWW web browsing, or documents with custom font faces - requiring only passive user interaction, with no authentication required from the attacker. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, though a patch commit is confirmed upstream.
Heap buffer overflow via integer wraparound in GNU Emacs for Android's TrueType font parser allows an attacker to corrupt heap memory and potentially achieve code execution by delivering a crafted font file through email, the built-in EWW browser, or documents using custom typefaces. The flaw is confined to 32-bit builds where an unguarded addition in sfnt_read_cmap_format_12() wraps around when computing an xmalloc allocation size, producing a fatally undersized heap buffer. No public exploit has been identified at time of analysis and this vulnerability is not listed in CISA KEV; however, CERT-PL reported the issue and an upstream patch commit is available.
GNU Emacs for Android leaks heap memory contents through a crafted TrueType variable font, enabling ASLR bypass as a stepping stone to further exploitation. The flaw resides in the gvar table parser (src/sfnt.c), where an off-by-one error in shared-coordinate index boundary checks allows a font file to trigger an out-of-bounds heap read via memcpy. Attack delivery is broad: malicious fonts can reach victims through email rendered in Emacs, EWW (Emacs Web Wowser) browsing, or documents applying custom faces - all requiring user interaction but no authentication. No public exploit code or CISA KEV listing has been identified at time of analysis; an upstream fix commit is available but no formally released patched version has been independently confirmed.
Man-in-the-middle interception of ECOVACS PRO app traffic is possible due to improper TLS server certificate validation (CWE-295) in both the Android and iOS versions of the application, published by ECOVACS Robotics and coordinated by JPCERT under JVNVU92804348. An attacker with a network-positioned MITM capability can present a rogue certificate that the app accepts without proper validation, enabling retrieval and alteration of all app-server communications, which may include device control commands, account credentials, and home telemetry. No active exploitation is confirmed (not in CISA KEV), and no public exploit code has been identified at time of analysis.
SamsungPassAutofill prior to version 5.2.10.x on Samsung Android devices improperly exports application components, enabling a locally-installed malicious app to access sensitive autofill credential data with user interaction. The CVSS 4.0 vector (AV:L/PR:L/UI:A/VC:H) confirms the attack is constrained to on-device, low-privilege access requiring user-triggered activity, yielding a moderate score of 5.1 despite high confidentiality impact. No public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV.
AppLock on Samsung Mobile Devices prior to SMR Aug-2026 Release 1 exposes improperly exported Android application components, enabling a physical attacker to bypass the app lock protection layer entirely. The flaw grants access to confidentiality- and integrity-sensitive data within locked applications without satisfying the intended authentication challenge. No public exploit is identified at time of analysis; exploitation is constrained to physical device access, limiting but not eliminating real-world risk for lost or stolen device scenarios.
Unauthorized file deletion via improperly exported Android components in Samsung Contacts prior to SMR Aug-2026 Release 1 allows any locally-installed malicious application to invoke the exported component and delete files under Samsung Contacts' privilege without requiring any elevated permissions of its own. The vulnerability stems from an Android component export misconfiguration, granting third-party apps unintended access to privileged file operations. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low attack complexity and absence of privilege requirements make this straightforward to exploit on affected devices.
OAuth token hijacking in the Salon Booking System WordPress plugin (through 10.30.33) allows unauthenticated remote attackers to overwrite the site's stored Google Calendar connection credentials with attacker-controlled OAuth tokens, fully hijacking the calendar integration. Exploitation requires the target site to have independently configured a Google OAuth client for the calendar sync feature, limiting the exposed population. No public exploit has reached CISA KEV status, but a publicly available proof-of-concept was published by WPScan, and EPSS remains low at 0.14% (3rd percentile), consistent with a niche plugin requiring a non-default configuration. The primary consequence is persistent integrity and availability disruption of the booking-calendar workflow, with a secondary confidentiality risk if future appointment data is synced to the attacker's Google account.
Server-Side Request Forgery in adenot mcp-google-search up to version 0.3.1 allows a local low-privileged user to direct the read_webpage tool to fetch arbitrary internal network resources, including localhost, RFC 1918 ranges, cloud metadata endpoints, and link-local addresses, by supplying a crafted url argument. The vulnerability stems from the absence of URL validation prior to Axios-driven HTTP fetching in src/index.ts. No active exploitation is confirmed and no CISA KEV listing exists, though the CVSS 4.0 E:P modifier indicates proof-of-concept code exists; an upstream fix is available via a specific commit.
Open redirect in the Home Assistant Android Companion App (prior to 2026.6.1) enables credential phishing attacks against new users via crafted homeassistant://invite deep links. Because no screen in the invitation or onboarding flow displays the parsed server hostname before the WebView commits to it, an attacker who delivers a malicious invite link can silently redirect the victim's onboarding session to an attacker-controlled server presenting a look-alike login page. No public exploit code has been identified at time of analysis; the CVSS score of 4.3 (C:L) understates real-world impact given that captured credentials yield full smart-home access.
Datadog Android app versions prior to 5.9.2 structurally associate authenticated users' Datadog UUIDs with Google Firebase Installation IDs on every successful login, transmitting this stable cross-session identifier - alongside crash stack traces that may include in-flight application data, internal class names, package names, and breadcrumbs - to Google's Firebase Crashlytics backend without an identifiable user consent gate or opt-out mechanism. The exposure is not triggered by an external attacker but occurs automatically during normal authenticated app usage for all affected users. No active exploitation has been identified (SSVC Exploitation: none; no CISA KEV listing), and no public exploit code exists; the primary risk is regulatory and privacy-related rather than direct technical compromise.
Session injection in the Datadog Android app (versions prior to 5.9.2) allows any zero-permission co-installed application to hijack the victim's Datadog identity by delivering crafted OAuth tokens directly to an unguarded exported activity, which auto-logs the victim in under an attacker-controlled identity without backend token validation. The vulnerability stems from AppActivity being declared android:exported='true' with no permission guard, accepting and persisting arbitrary UserSession data deserialized from intent Bundle extras. SSVC assessment lists exploitation as none and no public exploit has been identified, but the zero-permission precondition dramatically lowers the attacker capability bar.
Plaintext SQLite database storage in the Datadog Android application exposes operationally sensitive monitoring metadata to anyone with physical access to the device or the ability to perform forensic acquisition. Two Room-managed databases - LocalNotificationDatabase and SearchRecentDatabase - store incident notification recipients, deeplinks, service names, and free-text search queries without at-rest encryption; no SQLCipher or equivalent openHelperFactory configuration was found in the codebase. Protection relies entirely on the Android application sandbox, which is insufficient for this class of data in high-risk deployment environments such as on-call engineering teams managing production infrastructure. No public exploit code exists and CISA has not added this to the KEV catalog.
Notification dismissal in the Datadog Android application (versions prior to 5.9.2) can be triggered by any zero-permission co-installed application through the improperly exported BubbleChatActivity component (CWE-926), allowing silent cancellation of the hard-coded Bits AI chat notification (ID 9201) with no identity validation of the caller or their supplied conversation_id. The impact is limited to nuisance-level denial of that specific notification and potential facilitation of in-app phishing workflows, with chat content remaining server-authentication gated and inaccessible to the attacker. SSVC assessment confirms no known active exploitation, and no public exploit code has been identified at time of analysis.
Six exported Android App Widget configuration activities in the Datadog Android application (versions prior to 5.9.2) allow a co-installed zero-permission malicious app to brute-force sequential App Widget IDs and trigger automatic Datadog session login for the victim, exposing live operational data - dashboards, SLOs, on-call schedules, incident details - as a visual side-channel. Exploitation is constrained by three simultaneous preconditions and data exfiltration is limited to screen-visible disclosure only, with no programmatic return path. No public exploit has been identified at time of analysis; SSVC rates exploitation as none with partial technical impact.
Forged on-call acknowledgment and confused-deputy execution in the Datadog Android application (versions prior to 5.9.2) allows any co-installed malicious app to silently dismiss real production incident alerts on behalf of the victim by exploiting an unguarded exported Activity with no permission check. An attacker-controlled app can supply crafted Intent extras to forge a backend Acknowledge API call using the victim's authenticated session, redirect the Datadog process into non-exported internal components, and surface a spoofed alert over the device lock screen. No public exploit has been identified at time of analysis; exploitation requires a malicious co-installed app plus a single user tap.
Null pointer dereference in the llama.cpp LLaMA-Android JNI wrapper's bench_1model() function allows denial of service via a crafted model file. Builds b1886 through b7445 (packaged releases 0.9.0-0.17.1) are affected; the function skips null validation on the model context pointer before dereferencing it, so supplying a malformed or truncated GGUF model file triggers a SIGSEGV that terminates the Android application process. No public exploit has been identified at time of analysis and this is not listed in CISA KEV, but the attack path is mechanically simple for anyone able to deliver a crafted model to the device.
Cross-origin data leakage in Google Chrome's GPU process - caused by an integer overflow (CWE-190) - enables a remote attacker who has already achieved renderer process compromise to read data across origin boundaries by delivering a crafted HTML page. All Chrome desktop releases prior to 151.0.7922.109 are affected. No public exploit or CISA KEV listing exists at time of analysis; the chained nature of the attack (requiring a prior renderer compromise) substantially constrains real-world risk despite the broad deployment footprint of Chrome.
Uninitialized memory use in Skia, Chrome's 2D graphics engine, exposes a cross-origin data leak primitive in Google Chrome prior to 151.0.7922.109. Exploitation is constrained to attackers who have already achieved renderer process compromise - making this a second-stage, chained vulnerability rather than a standalone initial-access vector. No public exploit or active exploitation has been identified; SSVC rates this as non-automatable with partial technical impact, consistent with the low CVSS base score of 3.1.
Cross-origin data leakage in Google Chrome's Skia graphics library (versions prior to 151.0.7922.109) enables a remote attacker who has already achieved renderer process compromise to extract cross-origin data through a specially crafted HTML page. The vulnerability is classified CWE-457 (Use of Uninitialized Variable) and carries a low CVSS base score of 3.1, reflecting its dependency on a pre-existing renderer compromise as a prerequisite. No public exploit code has been identified at time of analysis, SSVC exploitation status is rated none, and a vendor-released patch is available in Chrome 151.0.7922.109.
Uninitialized GPU memory in Google Chrome on Android prior to 151.0.7922.109 exposes sensitive process memory contents to a remote attacker who has already achieved renderer process compromise. The CWE-457 flaw allows the GPU component to read and return uninitialized memory regions when processing attacker-controlled HTML, resulting in confidentiality impact bounded to the compromised process scope. No public exploit code exists and CISA SSVC rates exploitation as none at time of analysis, making this a second-stage information disclosure component rather than a standalone critical threat.
Timing side-channel exposure in Apache Portable Runtime Utility (APR-util) versions 1.2.0 through 1.6.3 allows network-accessible attackers to statistically recover passwords or hashes by measuring response-time variance in the `apr_password_validate()` function, which performs non-constant-time comparisons. The risk is materially elevated on platforms lacking native `crypt()` support - specifically Windows, Android, BeOS, and NetWare - where the non-constant-time code path is always exercised rather than conditionally. No public exploit has been identified at time of analysis, though the SSVC framework assesses the attack as automatable with partial technical impact.
Cross-site request forgery in the Google Authenticator WordPress plugin before version 0.56 allows an unauthenticated attacker to overwrite a logged-in user's TOTP secret by tricking them into loading a malicious page. The forged request silently replaces the victim's two-factor secret with one the attacker controls, enabling the attacker to generate valid OTPs and lock the legitimate account owner out. A public proof-of-concept is available via WPScan; no active exploitation is confirmed in CISA KEV, and EPSS of 0.11% (2nd percentile) aligns with SSVC's 'not automatable' designation.
Session isolation bypass in Electron allows a malicious or compromised Chrome extension loaded into one session to cross session boundaries and access, navigate, and script windows belonging to a completely separate session. Affected are Electron applications prior to versions 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3 that invoke session.loadExtension and rely on multi-session architecture as a security boundary - a narrowly scoped but architecturally significant trust boundary violation. No public exploit code or CISA KEV listing exists at time of analysis; exploitation requires attacker control of an extension the application has explicitly loaded.
Remote code execution and privilege escalation are the headline risks in this Jenkins advisory covering multiple vulnerabilities in Jenkins core (versions 2.575/LTS 2.568.1 and earlier) and eleven plugins. The most critical flaw (CVE-2026-70426) bypasses the JEP-200 deserialization class filter via a fallback path in the Remoting library, allowing an agent process or a user with Agent/Connect permission to execute arbitrary code on the Jenkins controller. A companion archive-extraction vulnerability (CVE-2026-70427) enables arbitrary file writes to the controller filesystem - including into init.groovy.d or the plugins directory - through crafted tar/tar.gz archives delivered from an agent; no public exploits or CISA KEV listing were identified for any issue in this advisory at time of analysis.
Local root escalation on the ZTE Nubia Red Magic 11 Air (NX799J) gaming smartphone stems from a built-in PostgreSQL service that runs as root, listens on a device port, and is guarded only by weak credentials. Because PostgreSQL's COPY FROM PROGRAM syntax executes OS commands with the server's privileges, any local app that reaches the database can break out of the Android application sandbox and run commands as root. No public exploit identified at time of analysis, though the technique (weak-cred Postgres plus COPY FROM PROGRAM) is well understood and trivially reproducible.
Unauthorized access to other users' personal data in SirenGPS Android Application 2.19.44 stems from the backend API failing to verify that a requesting user is authorized to act on the target user identifier supplied in API parameters. An authenticated attacker exploiting this horizontal privilege escalation can read and overwrite arbitrary users' personal information with only low-privilege access. No public exploit identified at time of analysis and EPSS is extremely low (0.15%, 5th percentile), but a detailed researcher advisory is publicly available on GitHub, lowering the bar for replication.
Authentication bypass in the My Safetipin Android application version 5.2.1 stems from hardcoded credentials in the authentication module that produce predictable OTP values, letting remote attackers log in as arbitrary users and take over accounts without legitimate credentials. Any personal-safety data stored in a victim's account - location history, safety pins, and profile details - becomes exposed and modifiable. No public exploit has been identified at time of analysis, and the EPSS score of 0.27% (18th percentile) reflects low observed exploitation activity despite the maximal CVSS rating.
Path traversal in ZomboDroid Meme Generator App 4.6830 for Android exposes file system access beyond intended directories through manipulation of function t5.l.c in the com.zombodroid.MemeGenerator component. Exploitation is constrained to local access, yielding limited confidentiality, integrity, and availability impact consistent with the CVSS 4.0 score of 1.9. A public proof-of-concept is available on GitHub, though no patch has been released and the vendor did not respond to coordinated disclosure - leaving no official remediation path.
URI scheme injection in @a2ui/web_core's openUrl function enables stored or reflected XSS by allowing an agent-controlled javascript: URI to be passed directly to window.open() without validation. Any application using the Button component's functionCall action on default deployments is affected, since the Basic Catalog is enabled with no special configuration required. CVSS 4.0 impact metrics VC:H/VI:H confirm full confidentiality and integrity compromise at the vulnerable-system level; no active exploitation is confirmed (CVSS E:U, no CISA KEV listing).
Information disclosure in Firefox for Android and Firefox Focus for Android exposes sensitive user data to network-based attackers who can lure a victim into interacting with a crafted web resource. The vulnerability, tracked under CWE-200 and assigned a CVSS score of 6.5 with high confidentiality impact, is limited to Android platform builds and does not affect desktop Firefox. Mozilla patched this in Firefox 153.0.3 per advisory mfsa2026-73; no public exploit or active exploitation has been identified at time of analysis.
Signature forgery in the MonsterInsights WordPress plugin before 11.1.0 allows unauthenticated network attackers to overwrite plugin configuration values when the site is not connected to Google Analytics. The root cause is that the HMAC signing key used to authenticate a specific AJAX action defaults to an empty string in that disconnected state, making any forged HMAC trivially valid. The practical impact is limited to disrupting server-side analytics in Manual GA4 mode; no public exploit identified as actively exploited (not in CISA KEV), though a publicly available proof-of-concept exists and the EPSS probability is low at 0.15%.
Server-Side Request Forgery in Simple Google Calendar Outlook Events Widget WordPress plugin (all versions before 3.1.0) permits unauthenticated remote attackers to supply arbitrary URLs that the server fetches without validation, potentially exposing responses from internal services. The plugin is confirmed vulnerable by WPScan and a public exploit exists, though EPSS at 0.14% (4th percentile) indicates limited observed exploitation despite the available POC. This vulnerability is not listed in CISA KEV at time of analysis.
Server-Side Request Forgery (SSRF) in Microsoft Edge (Chromium-based) enables a remote, unauthenticated attacker to perform network-level spoofing by manipulating the browser into issuing crafted requests to unintended destinations. All versions of the Chromium-based Edge are affected per the CPE wildcard match, and the CVSS scope change (S:C) confirms the impact extends beyond the browser itself to backend or internal systems reachable from the victim host. No public exploit exists (E:U) and an official vendor patch has been released (RL:O), keeping real-world exploitation probability low at this time.
Origin validation error in Microsoft Edge (Chromium-based) enables a remote unauthenticated attacker to perform cross-origin spoofing attacks, achieving high confidentiality impact and limited integrity impact against victims who interact with attacker-controlled content. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N) with temporal indicators E:U/RL:O/RC:C indicates an officially patched vulnerability with no publicly proven exploit code and confirmed vendor reporting. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Origin validation error in Microsoft Edge (Chromium-based) allows network-positioned unauthenticated attackers to perform cross-origin tampering when a victim user interacts with malicious web content. The flaw (CWE-346) undermines the browser's origin enforcement logic, enabling integrity and confidentiality compromise at low severity per CVSS 5.4. Tagged as an Authentication Bypass vector, suggesting edge cases where origin-gated auth flows in Edge may be bypassed. No active exploitation confirmed (not in CISA KEV), no public POC identified, and a vendor patch is available via MSRC.
Missing authorization controls in Microsoft Edge (Chromium-based) allow a local attacker without any system privileges to bypass authorization and perform tampering actions against the browser. The flaw (CWE-862) results in high confidentiality impact per the CVSS vector, though the description characterizes the effect as tampering - a discrepancy addressed in confidence notes below. No public exploit code has been identified and Microsoft has released an official patch through the MSRC advisory portal.
Code injection (CWE-94) in Microsoft Edge (Chromium-based) enables network-based spoofing attacks against users who interact with attacker-controlled content. An unauthorized remote attacker can exploit improper code generation controls to inject and execute code within the browser's execution context, crossing security scope boundaries (S:C) to spoof content or interfaces presented to the victim. No public exploit has been identified at time of analysis (E:U temporal metric), and Microsoft has released an official fix via the MSRC update guide.
Spoofing via origin validation failure in Microsoft Edge (Chromium-based) allows a network-adjacent unauthenticated attacker to deceive users or systems about the true origin of web content or requests. All Chromium-based Edge versions are affected per the wildcard CPE, and a vendor-released patch is confirmed via the Microsoft Security Response Center. No public exploit code exists and active exploitation is not confirmed - the CVSS temporal metric E:U (exploit unproven) and absence of CISA KEV listing reinforce a currently theoretical risk level.
Microsoft Edge (Chromium-based) is affected by a Time-of-Check Time-of-Use (TOCTOU) race condition that allows a remote, unauthenticated attacker to disclose sensitive information over the network, contingent on user interaction. The flaw exploits the timing gap between a security check and subsequent resource use within the Chromium-based browser engine, potentially exposing cross-origin data or internal browser state. No active exploitation has been confirmed by CISA KEV, and the temporal CVSS metrics (E:U) confirm no proven exploit code exists at time of analysis; a vendor patch is available via MSRC.
Origin validation error in Microsoft Edge (Chromium-based) enables a local, unauthenticated attacker to bypass cross-origin restrictions and perform data tampering. The CVSS vector (AV:L/PR:N) indicates that any unprivileged local user - including guest or kiosk session users - can trigger this flaw without requiring prior authentication or user interaction. With a high confidentiality impact (C:H) and low integrity impact (I:L), exploitation could expose sensitive browser-held data while also permitting limited content manipulation. No public exploit code has been identified and CISA KEV does not list this CVE; the temporal metric E:U corroborates no known active exploitation at time of analysis.
Improper export of the DialerActivity component in textPlus Text Message and Call App (Android, versions up to 8.3.5) allows any co-installed application on the same device to invoke the com.gogii.textplus dialer component without authorization. Classified under CWE-926, this flaw permits a locally-present malicious app to trigger dialer functionality, leading to limited information disclosure and unauthorized interaction with call-related features. No public KEV listing confirms active exploitation, but a proof-of-concept is publicly available on GitHub, lowering the technical barrier for abuse.
Cleartext storage of personally identifiable information in Meesho Online Shopping App (Android, versions through 20260607) exposes user_id, phone number, email address, and name in the com.meesho.supply component without encryption. Exploitation requires physical access to the device and a degree of local privilege, making this a low-severity, localized threat rather than a remote or mass-exploitation risk. A proof-of-concept is publicly available via GitHub and Google Drive, though no active exploitation has been confirmed by CISA KEV.
Sensitive WooCommerce order data exposure in the PixelYourSite WordPress plugin (all versions through 11.2.1) allows unauthenticated remote attackers to retrieve full purchase metadata - product names, quantities, per-item prices, order totals, currency, and transaction IDs - for any order by supplying an arbitrary or invalid order key alongside a known order ID. The plugin's getWooPurchaseEventParams function resolves orders solely from the URL path order ID without validating the accompanying key, then emits the complete woo_purchase tracking payload directly into rendered page HTML via the pysOptions JavaScript object across all three supported integrations (Facebook Pixel, Google Analytics, and Google Tag Manager). No public exploit has been identified at time of analysis, but because WooCommerce order IDs are sequential integers by default, mass enumeration of the entire order history requires only a trivial HTTP loop.
SQL injection in the GSheetConnector CF7 Google Sheets Connector WordPress plugin (all versions through 5.2.1) enables authenticated administrators to exfiltrate arbitrary database contents via the unsanitized 's' search parameter. The root cause is a flawed sanitization chain: wp_unslash() removes magic-quote escaping while sanitize_text_field() fails to neutralize SQL metacharacters, leaving single quotes intact before direct query interpolation. No public exploit or CISA KEV listing has been identified at time of analysis, but the Wordfence disclosure includes direct source-code references confirming the vulnerable code paths in class-gs-cf7db-formEntryList.php and gs-cf7db.php.
Arbitrary local file read in gemini-bridge (versions 1.0.0-1.3.0) exposes any file accessible to the server process - SSH keys, cloud credentials, `.env` files, source code - through the `consult_gemini_with_files` tool when operating in inline mode. Compounding the local disclosure, file contents are simultaneously exfiltrated to Google's infrastructure via the Gemini CLI round-trip, extending blast radius beyond the local host. No public exploit identified at time of analysis, but the CVSS vector (AV:L/AC:L/PR:N/UI:N) indicates trivially low exploitation complexity, and the GHSA advisory explicitly calls out prompt-injection as a realistic delivery vector for AI agent pipelines. Vendor-released patch available in version 1.3.1.
Cleartext storage of sensitive information in Johnson Controls XAAP Application on Android (versions before 1.53) exposes sensitive data to retrieval by attackers who already have access to a jailbroken or otherwise compromised device. The flaw stems from insufficient data-at-rest protection (CWE-312), meaning credentials, tokens, or configuration data are stored without encryption in the app's local storage. No public exploit code exists and this vulnerability is not listed in CISA KEV; real-world risk is constrained by the requirement for prior device compromise.
Unbounded memory consumption in Google mcp-toolbox versions through 1.4.0 allows unauthenticated remote attackers to crash the service via a single oversized HTTP request. The /mcp endpoint's toolInvokeHandler uses Go's io.ReadAll without any body-size guard - no http.MaxBytesReader, no Content-Length pre-check - so a sufficiently large POST body linearly exhausts host RAM until the OS OOM killer terminates the process. No active exploitation is confirmed (CVSS 4.0 E:U), but the attack requires no authentication and trivial complexity, making any internet-exposed deployment an easy target for denial of service.
Authorization bypass in Google mcp-toolbox's bigquery-execute-sql tool (versions 0.16.1-1.4.0) allows authenticated low-privileged users to exfiltrate DDL schemas from explicitly restricted datasets and query federated external data via EXTERNAL_QUERY connections. The fail-open logic flaw stems from the tool treating an empty tableIDSet returned by the BigQuery dry-run API - which occurs for INFORMATION_SCHEMA and EXTERNAL_QUERY constructs - as a signal to skip allowedDatasets enforcement entirely. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though the bypass mechanism is straightforward for any authenticated toolbox user.
node-re2, the Node.js native binding for Google's RE2 regular expression engine, enters an infinite loop and leaks unbounded native memory when String.prototype.match is called with a global pattern capable of producing zero-width (empty string) matches. All versions prior to 1.25.2 are affected; because RE2 executes synchronously within the Node.js event loop thread, the hang is unrecoverable without a process restart, making any service that exposes RE2 global matching to externally-supplied input susceptible to complete denial of service. No public exploit code or CISA KEV listing has been identified at time of analysis, but the trigger condition is mechanically trivial and directly exercisable from patterns confirmed in the vendor's own test additions.
Out-of-bounds heap read in node-re2 prior to 1.25.2 allows process termination and limited heap memory disclosure when an attacker-influenced lastIndex value is used against a non-ASCII subject string. The flaw arises because lastIndex is validated against the UTF-8 byte length of the input but consumed as a UTF-16 code-unit offset - for any non-ASCII character, the UTF-8 byte count exceeds the UTF-16 unit count, creating a gap where a lastIndex passes the guard yet reads past the allocated buffer. The resulting crash is uncatchable by the Node.js process, making it an effective denial-of-service vector in any server application exposing this code path to external input. No active exploitation confirmed (not in CISA KEV); no public exploit code identified at time of analysis.
Search Atlas SEO WordPress plugin (all versions before 2.6.12) exposes its Google Indexing API integration to any authenticated user - including low-privilege subscribers - due to a missing capability and nonce check in an AJAX handler. Any user with a valid WordPress session can invoke the plugin's Google Indexing API endpoint to submit or remove site URLs from Google's search index and exhaust the site's indexing API quota. A publicly available exploit exists via WPScan, though EPSS at 0.14% (4th percentile) and the absence of a CISA KEV listing indicate limited observed exploitation activity at this time.
Side-channel information leakage in Google Chrome's Media component (versions prior to 151.0.7922.72) enables a remote attacker to leak cross-origin data by directing a victim to a crafted HTML page, bypassing same-origin policy protections through measurable side effects of media processing. Affected desktop users on all platforms running any Chrome release before 151.0.7922.72 are exposed to limited confidentiality loss. EPSS is 0.16% (6th percentile), SSVC exploitation status is none, and no public exploit has been identified at time of analysis - all signals converge on low real-world risk.
UI spoofing in the Google Chrome Updater component on Windows (prior to 151.0.7922.72) enables a local attacker to present a falsified interface to users by placing a malicious file in a location the Updater processes. Chromium's own team rates this 'Low' severity, consistent with the 4.0 CVSS score, EPSS of 0.10% (1st percentile), and SSVC exploitation status of 'none'. No public exploit exists at time of analysis, and a vendor-confirmed patch is available in Chrome 151.0.7922.72.
UI spoofing in Google Chrome for iOS prior to 151.0.7922.72 enables a remote attacker to deceive users into believing they are interacting with a legitimate browser interface by serving a crafted HTML page. The root cause is insufficient policy enforcement (CWE-346, origin validation error), allowing the attacker to manipulate rendered UI elements. No public exploit code exists and no active exploitation has been confirmed; EPSS stands at 0.16% (6th percentile) and CISA SSVC classifies exploitation as none, placing this firmly in a patch-and-monitor priority tier rather than an emergency response.
Navigation restriction bypass in Google Chrome DevTools prior to version 151.0.7922.72 enables remote attackers to circumvent browser navigation controls by luring a user into opening a specially crafted malicious file. The flaw stems from CWE-20 insufficient input validation within the DevTools component, resulting in high integrity impact per CVSS. No public exploit has been identified and EPSS exploitation probability is very low at 0.16% (6th percentile); notably, the Chromium security team internally rated this 'Low' severity despite the medium NVD CVSS score of 6.5.
UI spoofing in Google Chrome for iOS prior to version 151.0.7922.72 enables a remote unauthenticated attacker to misrepresent critical interface elements - such as the address bar or origin indicators - through a specially crafted HTML page. Classified as CWE-451 (UI Misrepresentation of Critical Information), the impact is limited to integrity: no code execution or data exfiltration is possible directly, but users can be deceived into trusting a malicious page as legitimate. No public exploit code exists, EPSS sits at 0.16% (6th percentile), and Chromium internally rated this as Low severity - consistent with a constrained, social-engineering-dependent attack surface.
Chrome for iOS prior to 151.0.7922.72 exposes potentially sensitive process memory contents to an attacker with physical access to the device through an inappropriate implementation flaw. The vulnerability is classified CWE-200 (Information Disclosure) and is iOS-platform-specific, not affecting Chrome on other operating systems. No public exploit code exists and CISA SSVC confirms no active exploitation, placing this firmly in the low-urgency tier despite requiring prompt patching for high-assurance mobile environments.
UI spoofing in Google Chrome's Passwords subsystem (versions prior to 151.0.7922.72) enables remote attackers to manipulate password-related UI elements through malicious network traffic, potentially deceiving users into submitting credentials to unintended destinations. Exploitation requires active user interaction (UI:R per CVSS), and real-world risk is constrained by an EPSS of 0.15% (5th percentile) and SSVC confirmation of no known exploitation and a non-automatable attack path. No public exploit identified at time of analysis; vendor patch is available in Chrome 151.0.7922.72.
UI spoofing in Google Chrome's Passwords component (versions prior to 151.0.7922.72) allows a remote unauthenticated attacker to manipulate how credential-related UI elements are displayed by delivering maliciously crafted network traffic to a browsing user. The root cause is insufficient input validation (CWE-20) in the Passwords subsystem, which fails to sanitize externally sourced data before rendering it in the browser interface. No public exploit code has been identified and CISA has not listed this in KEV; EPSS of 0.15% (5th percentile) confirms low automated exploitation probability, consistent with the SSVC rating of exploitation: none.
UI spoofing in Google Chrome's Settings component (versions prior to 151.0.7922.72) enables remote attackers to misrepresent critical interface elements to victims via malicious network traffic, requiring user interaction to trigger. EPSS at 0.15% (5th percentile) and CISA SSVC exploitation rating of none align with the Chromium team's own Low severity classification, making this a low-urgency issue despite its network-accessible attack vector. Google has released a patch in stable channel version 151.0.7922.72; no public exploits are identified at time of analysis.
UI spoofing in Google Chrome for Android (prior to 151.0.7922.72) enables remote unauthenticated attackers to present misleading interface elements to users through a crafted HTML page. The flaw stems from an inappropriate implementation in Chrome's input handling on Android, classified under CWE-451 (UI Misrepresentation of Critical Information), meaning the browser fails to correctly represent critical UI state to the user. No public exploit code exists and CISA has not listed this in KEV; EPSS is extremely low at 0.16% (6th percentile), consistent with Chromium's own Low severity classification.
UI spoofing via Google Lens in Google Chrome prior to 151.0.7922.72 is achievable by a remote attacker who has already compromised the renderer process, using a crafted HTML page to misrepresent interface elements to the victim. The attack requires a chained exploitation scenario: renderer compromise as a prerequisite, followed by abuse of an inappropriate implementation in the Lens component (CWE-451) to manipulate what the user perceives in the browser UI. No active exploitation is confirmed - CISA KEV does not list this CVE, SSVC assessment shows exploitation status of none, and EPSS sits at 0.16% (6th percentile), indicating very low real-world exploitation probability at time of analysis.
Information disclosure in Google Chrome's WebXR subsystem prior to version 151.0.7922.72 allows unauthenticated remote attackers to read potentially sensitive process memory contents by luring a victim to a crafted HTML page. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) indicates a network-accessible, low-complexity path to high confidentiality impact, though Chromium's internal severity rating of Low and an EPSS of 0.16% (6th percentile) reflect limited real-world exploitation risk. No public exploit code exists and CISA SSVC rates exploitation as none, making this a watch-and-patch item rather than an emergency response trigger.
Cross-origin data leakage in Google Chrome's Speech component prior to version 151.0.7922.72 exposes sensitive information to attackers who have already achieved renderer process compromise. The vulnerability stems from insufficient policy enforcement in the Speech API, allowing a crafted HTML page to bypass cross-origin boundaries and exfiltrate data. With no CISA KEV listing, no public POC, and an EPSS of 0.16% (6th percentile), this is a low-probability exploitation scenario best understood as a potential second-stage component in a multi-vulnerability chain rather than a standalone attack.
UI spoofing in Google Chrome on iOS prior to 151.0.7922.72 enables a remote attacker to deceive users about page identity or browser security state by serving a crafted HTML page. The flaw is iOS-specific, exploiting an inappropriate implementation in the Chrome for iOS rendering layer rather than the broader Chromium engine, and requires only that the victim navigate to an attacker-controlled page. No public exploit has been identified and EPSS stands at 0.19% (9th percentile), consistent with Chromium's own 'Low' internal severity classification; this is a real but low-urgency integrity issue.
Process memory disclosure in Google Chrome's WebGL implementation allows a remote attacker to read potentially sensitive data from the browser's memory by luring a user to a specially crafted HTML page. Affected versions are all Chrome releases prior to 151.0.7922.72 across desktop platforms. No public exploit code has been identified and EPSS sits at 0.16% (6th percentile), indicating low real-world exploitation probability despite the High confidentiality rating in the CVSS vector.
Cross-origin data leakage in Google Chrome for Android (prior to 151.0.7922.72) stems from insufficient policy enforcement in the USB component, exploitable only after the attacker has already compromised the renderer process. Exploitation requires luring a victim to a crafted HTML page in a pre-compromised renderer context, making this a secondary-stage vulnerability in a chained attack rather than a standalone threat. EPSS sits at 0.19% (9th percentile), SSVC records no exploitation activity, and the vulnerability is not listed in CISA KEV - consistent with its low severity rating and demanding prerequisite.
Domain spoofing in Google Chrome on Android (all versions prior to 151.0.7922.72) results from a race condition in the PictureInPicture component, enabling a remote attacker to misrepresent the origin domain shown to a user when they interact with a crafted HTML page. The integrity impact is limited to the browser UI trust indicator - no code execution or data exfiltration occurs directly - but successful spoofing can be chained with credential phishing against a falsely trusted domain. No active exploitation has been confirmed (not listed in CISA KEV), and the EPSS score of 0.16% at the 6th percentile reflects very low exploitation probability, consistent with Chromium's own 'Low' severity classification.
UI spoofing in Google Chrome's Extensions subsystem (all versions prior to 151.0.7922.72) allows an attacker who tricks a user into installing a crafted malicious extension to misrepresent critical security indicators within the browser interface. The flaw stems from incorrect security UI rendering in the Extensions component (CWE-451), enabling deceptive presentation of extension trust signals or permissions. No public exploit has been identified at time of analysis and EPSS is 0.10% (1st percentile), aligning with Chromium's own internal 'Low' severity rating; however, the ubiquitous deployment footprint of Chrome elevates the aggregate exposure.
Cross-origin data leakage in Google Chrome's Passwords component (versions prior to 151.0.7922.72) exposes password-related data to attackers who have already compromised the renderer process and can deliver a crafted HTML page. The flaw stems from an inappropriate implementation that fails to enforce proper origin validation within the Passwords subsystem, making it a second-stage element in a chained attack rather than a standalone threat. No public exploit has been identified, EPSS is 0.16% (6th percentile), SSVC records no known exploitation, and Chromium internally rates this Low severity - consistent with the high prerequisite bar of prior renderer compromise.
Navigation restriction bypass in Google Chrome on macOS (versions prior to 151.0.7922.72) permits a local attacker to circumvent the browser's navigation controls by delivering a crafted malicious file. The CVSS vector (AV:L/I:H) confirms the impact is limited to integrity - an attacker who achieves local access can subvert Chrome's navigation security model without requiring elevated privileges or user interaction beyond obtaining local system access. With an EPSS score of 0.10% (1st percentile), no CISA KEV listing, and Chromium's own classification of Low severity, real-world exploitation risk is low despite the 6.2 CVSS base score.
Navigation restriction bypass in Google Chrome for Android (prior to 151.0.7922.72) originates from an inappropriate implementation in the browser's Media component, permitting a remote attacker to circumvent built-in navigation controls by delivering a crafted HTML page to a victim. The CVSS 4.3 score reflects a limited integrity-only impact - no code execution, no data exfiltration - and user interaction is required per the vector (UI:R). EPSS at 0.18% (8th percentile) and the absence of any KEV listing or public exploit indicate low real-world exploitation probability; Chromium's own internal severity rating of 'Low' is consistent with this assessment.
Uninitialized memory use in Skia, Chrome's 2D graphics rendering engine, exposes process memory contents to remote attackers on Windows via crafted HTML pages in Google Chrome versions prior to 151.0.7922.72. The flaw is strictly an information disclosure issue (CWE-457), with no integrity or availability impact, affecting only the Windows platform per the vulnerability description. No public exploit code has been identified, EPSS places exploitation probability at 0.19% (9th percentile), and SSVC classifies exploitation as none with partial technical impact - collectively suggesting limited real-world risk despite the CVSS C:H rating.
Navigation input validation bypass in Google Chrome prior to 151.0.7922.72 enables a renderer-compromised attacker to circumvent navigation restrictions via a crafted HTML page. The flaw is the second stage of a chained attack - exploitation requires a prior renderer process compromise, substantially raising the practical bar for abuse. No public exploit code or active exploitation has been identified; EPSS sits at 0.18% (8th percentile), consistent with its role as a post-exploitation primitive rather than an initial access vector.
Same-origin policy bypass in Google Chrome's Bluetooth subsystem (prior to 151.0.7922.72) can be triggered by an attacker who has already achieved renderer process compromise, using a crafted HTML page to abuse insufficient policy enforcement in the Web Bluetooth layer. The exploit chain requires a pre-existing foothold in the renderer, which limits real-world risk considerably - Chrome's own security team rated this 'Low' severity. No active exploitation has been confirmed (not listed in CISA KEV), and the EPSS score of 0.18% (8th percentile) reflects negligible observed exploitation activity.
Insufficient policy enforcement in Chrome's Speech component prior to version 151.0.7922.72 enables remote attackers to bypass site isolation - a core security boundary - via a crafted HTML page requiring only user interaction. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N) signals high integrity impact with no privilege requirement, meaning an unrelated web page can be weaponized as the delivery vehicle. No public exploit code has been identified and EPSS sits at a low 0.18% (8th percentile), consistent with the Chromium team's own 'Low' severity classification despite the NVD medium score; however, the site isolation bypass class of vulnerability is historically sensitive and warrants prompt patching.
Cross-origin data leakage in Google Chrome on Android prior to 151.0.7922.72 enables a local attacker to read data from a different origin by directing a victim user to a crafted HTML page. The flaw stems from an inappropriate browser implementation (CWE-346 Origin Validation Error), undermining the Same-Origin Policy's isolation guarantees on the Android platform. No public exploit code exists and no active exploitation has been observed; SSVC assessment confirms exploitation status as none, making this a low-urgency but noteworthy information-disclosure defect.
UI spoofing in Google Chrome's Global Media Controls component prior to version 151.0.7922.72 enables remote attackers to misrepresent interface elements when a victim visits a crafted HTML page. The flaw is rooted in CWE-451 (misrepresentation of critical UI information), allowing attacker-controlled content to manipulate what the media controls overlay displays. No public exploit code exists and no active exploitation has been identified; EPSS at 0.17% (7th percentile) and SSVC exploitation status of 'none' both corroborate this as a low-urgency, routine-patching-priority finding.
Same-origin policy bypass in Google Chrome's Cast component allows remote attackers to perform limited cross-origin integrity actions against victims who visit a crafted HTML page. All Chrome versions prior to 151.0.7922.72 are affected across Windows, macOS, and Linux. No active exploitation is confirmed (not in CISA KEV), no public exploit code has been identified, and Chromium's own internal severity rating is Low - signals that align with the very low EPSS score of 0.18% at the 8th percentile.
Cross-origin data leakage in Google Chrome's Blink rendering engine (versions prior to 151.0.7922.72) exposes data protected by the Same-Origin Policy to remote attackers who can lure a victim to a crafted HTML page. The flaw, classified as CWE-346 (Origin Validation Error), allows Blink to improperly handle origin boundaries, enabling a malicious page to read cross-origin resource data. No public exploit has been identified and EPSS sits at 0.17% (7th percentile), consistent with SSVC's 'Exploitation: none' designation and absence from CISA KEV.
Cross-origin data leakage in Google Chrome on Android (prior to 151.0.7922.72) results from an inappropriate UI implementation that allows a remote attacker to extract data from a different web origin when a user is socially engineered into performing specific UI gestures on a crafted HTML page. Rated CVSS 3.1 (Low) with EPSS at 0.17% (7th percentile) and SSVC exploitation status of 'none,' this vulnerability presents minimal immediate operational risk. No public exploit code exists and the issue is not listed in CISA KEV; a vendor-released patch is available in the stable channel update.
Side-channel memory leakage in Chrome's WebCodecs API prior to version 151.0.7922.72 enables a remote, unauthenticated attacker to extract potentially sensitive data from the browser's process memory by luring a victim to a crafted HTML page. The vulnerability stems from improper protection of physical side-channels (CWE-1300) within the WebCodecs media processing subsystem. No active exploitation has been identified - SSVC rates exploitation as none and EPSS places this in the 7th percentile - but the high confidentiality impact score reflects that successful exploitation could expose in-memory session data or other sensitive content.
Cross-origin data leakage in Google Chrome prior to 151.0.7922.72 is achievable through a CSS policy bypass, enabling remote unauthenticated attackers to exfiltrate data across origin boundaries when a victim visits a crafted HTML page. The root cause is improper origin validation (CWE-346) in Chrome's CSS subsystem, allowing CSS mechanisms to circumvent same-origin policy enforcement and read restricted cross-origin content. No public exploit code exists and no active exploitation has been identified; EPSS probability is 0.18% (8th percentile), consistent with the SSVC 'Exploitation: none' assessment and Chrome's own 'Low' severity designation for this issue.