Information Disclosure
Monthly
Unauthenticated information disclosure in the Mapster WP Maps WordPress plugin (all versions before 1.24.0) exposes the full title and body content of any post - including drafts, private, pending, and trashed posts - through an unprotected public REST API endpoint. Any remote attacker with network access to the WordPress site can enumerate and read content that site owners explicitly withheld from publication, bypassing WordPress's native post-status and capability access controls. A publicly available proof-of-concept exists per WPScan reporting; however, the EPSS score of 0.14% (4th percentile) indicates exploitation has not yet become widespread, and the vulnerability is not listed in the CISA KEV catalog.
Heap memory disclosure in Coturn 4.5.2-4.14.0 allows an unauthenticated remote attacker to extract up to ~870 bytes of adjacent process heap per request by sending a single HTTP GET to the ACME redirect plaintext TCP listener. The leaked memory originates from recycled, unzeroed network receive buffers and on busy relay servers can contain TURN credentials, OAuth tokens, or relayed session payloads from concurrent clients. Exploitation is trivially automatable against the affected configuration; no public exploit identified at time of analysis beyond the proof-of-concept test case shipped with the advisory.
Pterodactyl Wings before v1.13.0 crashes when its SFTP handler receives a crafted packet with fewer than 4 bytes in the payload during the SSH connection handshake, triggering a Go runtime index-out-of-bounds panic that kills the Wings daemon. The crash is exploitable by any unauthenticated network attacker who can reach the SFTP port, requiring no credentials because the vulnerable slice operation executes prior to authentication. No public exploit code exists at time of analysis, but the patch diff makes the trigger trivially reproducible: any packet with a short payload in the SSH subsystem channel request is sufficient.
mTLS authentication bypass in aap-gateway, the gateway component of Red Hat Ansible Automation Platform's Event-Driven Ansible (EDA), permits unauthenticated remote attackers to inject arbitrary events into automation workflows. The bypass exploits event stream URL manipulation and HTTP Subject header forgery; the attack surface is further reduced by the component's inadvertent disclosure of the expected TLS certificate subject in error responses (CWE-295). No public exploit code or CISA KEV listing has been identified at time of analysis, but the low attack complexity and CVSS 8.2 score make this a credible priority for organizations running EDA-integrated automation pipelines.
Cross-tenant credential theft in pgAdmin 4 (9.0 through 9.16) lets an authenticated non-owner user hijack another user's shared server connection by abusing the Workspaces adhoc-connect endpoint (/misc/workspace/adhoc_connect_server), which clones a target server row verbatim - including its owner's stored database password and tunnel password - and reassigns ownership to the caller. The victim is typically an administrator whose shared server carries saved credentials, and the attacker gains use of those database credentials and any privileges they confer. There is no public exploit identified at time of analysis and it is not on CISA KEV, but the fix (pgAdmin 4 9.17) and the underlying commit are public, and EPSS was not provided.
Sensitive-credential disclosure leading to full node compromise in Pterodactyl Wings before v1.12.3 lets a low-privileged, authenticated panel user (a server owner or a subuser holding startup.update) smuggle a {{config.*}} placeholder through a user-editable egg variable, causing Wings to resolve it against its entire daemon configuration and write secrets - including the node daemon token, token_id, and Docker registry credentials - into a file the user can read via the file manager or SFTP. Because the daemon token is both the Panel⇆Wings API bearer and the HMAC signing key for every JWT the node issues, an attacker can then forge tokens and act against every server on the node. No public exploit identified at time of analysis and it is not listed in CISA KEV, but the CVSS is 9.9 and the affected templating pattern is common across stock and community eggs.
Credential and cryptographic-key exposure in the VPS.org one-click Zulip deployment template ships every instance with an identical hardcoded application signing key, a default database password of "zulip", and HTTPS disabled (DISABLE_HTTPS=True), allowing remote attackers who know the public template defaults to forge authenticated sessions, read Zulip's database, and intercept traffic. Any organization that provisioned Zulip through this VPS.org one-click image is affected until the secrets are rotated. There is no public exploit identified at time of analysis, and the EPSS score is low (0.13%, 3rd percentile), but SSVC rates technical impact as total and automatable, reflecting that the shared secrets are identical across all deployments.
Information disclosure in 389 Directory Server (upstream of Red Hat Directory Server 11-13, shipped across RHEL 6-10) lets an unauthenticated remote attacker inject LDAP search filters into the CleanAllRUV replication status-check extended operation. Because the handler evaluates attacker-controlled filters against cn=config using elevated replication-plugin privileges and leaks a boolean match result, attackers can blindly enumerate sensitive configuration metadata such as replication bind DNs and password storage scheme details. No public exploit is identified at time of analysis and it is not listed in CISA KEV, but the network-reachable, no-authentication attack surface makes it a meaningful reconnaissance primitive.
Sensitive credential exposure in ANDRITZ HIPASE-250 (formerly 250 SCALA) stems from storing and transmitting user passwords in a reversible format rather than as one-way hashes, letting anyone who can read the credential store or sniff network traffic recover every stored password in cleartext. The flaw affects the HIPASE-250 protection, control and monitoring platform and carries a CVSS 7.5 (confidentiality-only) rating. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV; recovered credentials could enable follow-on authenticated access to the device or connected OT systems.
Tenant-restriction bypass in Keycloak's Microsoft identity provider integration allows attackers holding any valid Microsoft OAuth token - even from a completely unrelated Azure AD organization - to authenticate into a Keycloak realm via the token exchange feature. Affected deployments include Red Hat Build of Keycloak, Red Hat Single Sign-On 7, and Red Hat JBoss EAP Expansion Pack. With CVSS PR:L reflecting the need for a valid Microsoft credential (trivially obtained by registering a free Azure tenant), successful exploitation grants high confidentiality and integrity impact within the realm. No public exploit or active exploitation has been identified at time of analysis; EPSS sits at 0.19% (9th percentile), consistent with SSVC exploitation=none.
Unauthenticated information disclosure in the Geeky Bot WordPress plugin (all versions before 1.2.8) permits any remote, unauthenticated user to retrieve chat-history session metadata - including WordPress usernames, user IDs, and timestamps - by invoking an unprotected AJAX endpoint. Reported by WPScan with a publicly available proof-of-concept, this flaw provides attackers with a ready-made user enumeration primitive against any publicly reachable WordPress site running the affected plugin. CISA KEV listing is absent and EPSS sits at 0.14% (4th percentile), indicating limited current mass-exploitation, but the POC lowers the barrier for targeted attacks significantly.
GiveWP WordPress plugin before 4.16.3 exposes sensitive donor privacy data through an unauthenticated REST API endpoint that returns recurring-donation records without access controls. Any unauthenticated remote party can enumerate donor names and subscription details for donors who explicitly chose to give anonymously, directly violating donor privacy expectations. A publicly available exploit exists per WPScan reporting, though EPSS sits at the 5th percentile, suggesting limited opportunistic exploitation at time of analysis. No active exploitation is confirmed via CISA KEV.
Default-credential unauthorized access affects the Advantech ECU-1251D industrial communication gateway, which ships with a root SSH account protected by no password and is documented as such in the device manual. An attacker on the same network segment can log in as root over SSH without any credential, and because configuration provides no prompt or guidance to change these defaults, exploitable devices are likely to persist in the field. No public exploit identified at time of analysis, but the vulnerability requires no exploitation skill - knowledge of the documented default is sufficient.
Denial-of-service in an IEC 61850 GOOSE subscriber component allows an adjacent, unauthenticated attacker on the same Layer-2 network to crash the message-processing process by sending a crafted GOOSE frame (EtherType 0x88B8) with an undersized UTC timestamp field, triggering a heap out-of-bounds read (CWE-125). The flaw was reported by DHS ICS-CERT and documented in CISA ICS advisory ICSA-26-211-10; there is no public exploit identified at time of analysis, and the CVSS 4.0 vector scores availability impact only (VA:H) with no confidentiality or integrity effect.
Denial-of-service in an IEC 61850 GOOSE subscriber implementation allows an attacker with access to the substation process bus to crash the subscriber process using a single unauthenticated Layer-2 multicast frame. An off-by-one boundary error in the GOOSE parser triggers a heap out-of-bounds read (CWE-125) that reliably terminates the process. No public exploit identified at time of analysis; this is not listed in CISA KEV, and no EPSS score was provided.
Denial-of-service in an IEC 61850 MMS (Manufacturing Message Specification) protocol implementation allows an attacker with an established MMS session to crash the MMS handling process by sending a malformed BER-encoded confirmed-request message over TCP port 102. The flaw is a heap out-of-bounds read (CWE-125) in the BER decoder's boundary handling. No public exploit or active exploitation is identified at time of analysis; the CVSS 4.0 score of 7.1 reflects a high availability impact with low required privileges and no user interaction.
Heap buffer over-read in MZ Automation GmbH's libiec61850 (versions prior to 1.6.2) allows an unauthenticated adjacent-network attacker to crash the MMS service process by sending a crafted BER-encoded message with an invalid length value in a BOOLEAN or INTEGER field. The MMS BER decoder performs no bounds validation on the attacker-supplied length, causing a read past the end of a heap-allocated buffer and subsequent process termination. CISA ICS-CERT issued advisory ICSA-26-211-10 for this vulnerability; no public exploit code or KEV listing has been identified at time of analysis.
Denial-of-service in MZ Automation's libiec61850 (versions before 1.6.2) allows an unauthenticated attacker on the process bus to crash IEC 61850 subscriber processes with a single crafted GOOSE frame. The GOOSE payload parser mishandles nested length fields, so an inner element length that exceeds its enclosing length forces a one-byte out-of-bounds read (CWE-125) that reliably terminates the subscriber. No public exploit identified at time of analysis, and it is not listed in CISA KEV; the CISA ICS advisory (ICSA-26-211-10) and a vendor patch are available.
Remote unauthenticated denial of service in MZ Automation's libiec61850 (all versions before 1.6.2) allows an attacker to crash IEC 61850/MMS server processes by opening a crafted TCP/102 connection. The flaw sits in the ISO Presentation layer's normal-mode negotiation, where a missing length check on an attacker-controlled zero-length field triggers a bounded heap out-of-bounds read that terminates the process before any MMS session is even established. No public exploit identified at time of analysis and it is not on CISA KEV, but the pre-authentication network reach and low complexity make it a credible availability threat to exposed OT/ICS devices.
Sensitive information disclosure in RapidRAW before 1.6.0 (an open-source cross-platform RAW photo editor) allows a remote attacker to steal a Windows victim's NTLMv2 credentials by embedding a UNC path in the lutPath field of a preset file. Because RapidRAW passes lutPath directly to File::open() without validation, opening the poisoned preset forces an outbound SMB authentication to an attacker-controlled host. There is no public exploit identified at time of analysis, but the technique (UNC-path credential coercion) is well understood and trivially reproducible, so real-world abuse is realistic once a malicious preset is shared.
Hard-coded shared RSA private keys and their matching X.509 certificates in Watchfire digital billboard controller software (BC550, BC750, BC760, BC760DC) let an attacker who extracts them decrypt and impersonate the controller's built-in HTTPS/TLS web management interface. Because the keys ship in plaintext inside the firmware patch binaries - retrievable from Watchfire's Remote Support filestore - any attacker with the same firmware can recover the identical keys used across all deployed units. This is an information-disclosure/authentication-bypass class flaw (CWE-321) reported through CISA ICS-CERT; no public exploit identified at time of analysis and it is not listed in CISA KEV.
Default-credential authentication bypass in the LazyOwn RedTeam/APT Framework (grisuno/lazyown) before 0.2.154 lets any network-reachable attacker log into the C2 dashboard using the hardcoded operator credentials 'LazyOwn'/'LazyOwn', gaining full operator-level control of the command-and-control server. The framework ships these defaults in payload.json and core/payload_schema.py and passes them unchanged into lazyc2.py's HTTP Basic authentication. No public exploit identified at time of analysis, but the credentials are trivially known from the source code, and the CVSS base score is 9.8 (Critical).
Out-of-bounds heap read in the open62541 OPC UA C library allows a remote unauthenticated attacker to disclose sensitive process memory by supplying a crafted UA_Variant whose arrayDimensions provoke an integer overflow in the dimension-product computation. The overflow makes the computed element/stride total wrap to a small value, so bounds checks pass and subsequent index math walks past the heap allocation. CVSS 4.0 is 8.7 (confidentiality-only impact); no public exploit identified at time of analysis, though it is tracked in a CISA ICS advisory (ICSA-26-211-08) given the industrial/OT exposure of OPC UA servers.
Cross-tenant vector document disclosure in IBM Langflow OSS 1.0.0 through 1.10.1 lets an authenticated low-privilege user read another user's private Chroma-backed documents by building a flow that reuses the victim's persist_directory and collection_name, returning exact victim content in the attacker's workflow output. The same shared-namespace flaw also lets the attacker write their own documents into the victim's collection, corrupting its integrity. No public exploit is identified at time of analysis and CISA SSVC rates exploitation as none, but the CVSS 8.1 rating reflects the combined high confidentiality and integrity impact.
Unauthenticated credential leakage in SGLang's /server_info HTTP endpoint exposes configured API keys and SSL keyfile paths to any network-reachable caller on all versions through v0.5.15. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms no authentication or user interaction is required, and SSVC classifies the attack as automatable with a proof-of-concept available, making mass scanning for exposed instances a realistic threat. EPSS sits at just 0.14% (4th percentile), reflecting SGLang's niche deployment footprint rather than any technical difficulty - for internet-facing deployments using --admin-api-key, this is a high-priority credential-rotation and patching event.
Cross-tenant code injection and data disclosure in Activepieces (the open-source AI workflow automation platform) before 0.84.0 allows an authenticated flow author to escape their Code-piece sandbox and reach the read-write cached flow and code files of other tenants sharing the same worker. By abusing an unsanitized path segment, an attacker can read embedded secrets and data from co-tenants and overwrite cached code so that it executes under a victim tenant's identity on their next flow run. Publicly available intelligence shows no public exploit identified at time of analysis and no CISA KEV listing, but the vendor-confirmed fix and the broad impact (VC:H/VI:H plus subsequent-system SC:H/SI:H) make this a high-priority multi-tenant isolation failure.
OAuth 2.0 authorization-code theft in Dromara MaxKey through 4.1.12 lets remote attackers hijack a victim's authorization code and exchange it for an access token, taking over the victim's federated identity. The flaw lives in DefaultRedirectResolver.hostMatches(), where a naive endsWith() suffix comparison lets an attacker-controlled domain that ends with a registered redirect URI hostname pass validation. Publicly available exploit code exists and a vendor patch (commit ddbb72f) is available; no active exploitation has been confirmed (not in CISA KEV).
Local information disclosure in IBM App Connect Enterprise (versions 13.0.1.0-13.0.7.2 and 12.0.1.0-12.0.12.27) occurs because the integration runtime writes potentially sensitive information into log files that any local user can read. An attacker with local access to the host can harvest secrets such as credentials, connection strings, or message payload data from these logs to escalate access or pivot to backend systems. No public exploit identified at time of analysis, and there is no KEV listing; note that the NVD CVSS vector (AV:N) conflicts with the description's explicit 'local user' wording.
Privilege escalation via dynamic client registration in malach-it's Boruta OAuth 2.0/OpenID Connect provider library (Elixir) lets an unauthenticated registrant create OIDC clients that carry administrative security attributes. Because Boruta.Openid.register_client/3 forwards caller-supplied parameters straight into the administrative client-creation changeset with no public/admin allowlist, a self-registering client can dictate its own supported grant types, authorized scopes, PKCE enforcement, public refresh/revocation behavior, token lifetimes, and signing settings on versions 2.3.0 through 2.3.6. There is no public exploit identified at time of analysis and it is not in CISA KEV, but a vendor-released patch (2.3.7) is available.
Privilege escalation in the Serendipity (s9y) PHP blogging platform before 2.6.1 lets an authenticated Editor take over an Administrator account by exploiting an authentication context confusion (CWE-304): password checking and session loading resolve the user independently rather than binding to a single record. By registering a username that collides with an Administrator's, the Editor logs in with their own password yet has the Administrator's account loaded into their session, inheriting full admin rights. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the CVSS 4.0 base score of 8.7 reflects high confidentiality, integrity, and availability impact.
Unauthenticated Wiki Markup rendering in Apache JSPWiki up to 2.12.3 exposes sensitive data stored in internal JSPWiki variables to remote attackers. The flaw stems from a missing authentication check (CWE-306) on the markup rendering endpoint, allowing any network-reachable attacker to trigger rendering and extract variable contents without credentials. No public exploit has been identified and EPSS sits at a low 0.21% (12th percentile), but the CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivially easy remote unauthenticated exploitation against default deployments. Vendor patches are available.
Apache JSPWiki versions up to and including 2.12.3 expose sensitive application internals through debug messages returned in HTTP responses, classified under CWE-1295 (Debug Messages Revealing Unnecessary Information). The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates any unauthenticated remote user can trigger disclosure of high-confidentiality data - potentially including session tokens, internal paths, configuration details, or stack traces - without requiring special privileges or user interaction. Despite the high CVSS score of 7.5, real-world exploitation probability is notably low at 0.17% EPSS (7th percentile), and no public exploit code or active exploitation via CISA KEV has been identified at time of analysis.
Silent date corruption in Date::Manip through version 6.99 allows any caller passing untrusted character strings to ParseDate() or Date::Manip::Date->parse() to receive silently incorrect parsed dates when non-ASCII Unicode decimal digits (such as Arabic-Indic, Devanagari, or other Unicode script numerals) appear in year, month, or day fields. Perl's \d regex shorthand matches the full Unicode decimal-digit property (\p{Nd}), so non-ASCII digits are captured; subsequent numeric range validation then passes them because Perl truncates the string-to-number conversion at the first non-ASCII character, producing an in-range but wrong value — for example, '202٤' evaluates to year 202, not 2024. No public exploit has been identified at time of analysis and EPSS is very low (0.19%), but SSVC flags the flaw as automatable and the impact is meaningful for any application where Date::Manip parses externally-supplied dates to gate expiry checks, retention windows, or access-control logic.
Information disclosure and host-process Denial-of-Service affects VMware ESX, Workstation, and Fusion via an out-of-bounds read (CWE-125) reachable by an actor holding VM deployment privileges. On ESX the flaw can crash or leak memory from the host VMX process (a guest-to-host scope crossing), while on Workstation and Fusion the impact is limited to information disclosure. Reported by VMware/Broadcom with no public exploit identified at time of analysis and no CISA KEV listing.
Full system compromise of Phoenix Contact CHARX SEC EV charging controllers (SEC-3000/3050/3100/3150, versions 1.0.0 through 1.9.0) is possible because an incorrect script execution order tears down the firewall too early during system shutdown, briefly exposing internal-only services to the network. During this transient window a remote unauthenticated attacker can reach services that are normally firewalled off and gain complete control of the device. No public exploit identified at time of analysis, but the flaw is vendor-confirmed (CERT@VDE / advisory VDE-2026-008) and carries a CVSS 4.0 base score of 9.3.
Denial-of-service in Phoenix Contact CHARX SEC EV charging controllers (SEC-3000/3050/3100/3150, firmware 1.0.0 up to but not including 1.9.1) allows an unauthenticated network attacker to reboot the charging controller by sending a crafted Modbus TCP command to the CharxModbusServer. The attack requires no credentials or user interaction and, per the CVSS 4.0 vector, produces high availability impact with no confidentiality or integrity effect. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV, but the low attack complexity makes reliable disruption of charging service straightforward once the Modbus port is reachable.
Unauthenticated firmware implantation in Phoenix Contact CHARX SEC-3000/3050/3100/3150 EV charging controllers allows a remote attacker to push a modified firmware image to the basemodule because the update routine only checks a CRC32 checksum and performs no cryptographic signature verification (CWE-347). A successful upload yields full system compromise of the controller. No public exploit has been identified at time of analysis, but the flaw is network-reachable with no authentication and a vendor patch (v1.9.1) is available.
Insecure firmware-fallback in Phoenix Contact CHARX SEC EV charging controllers (SEC-3000, SEC-3050, SEC-3100, SEC-3150, versions 1.0.0 up to 1.9.1) lets a remote unauthenticated attacker force the device to boot an alternate firmware partition that ships with an insecure configuration and default credentials, yielding SSH access as the unprivileged 'user-app' account and allowing charging to be interrupted. The issue was reported by CERT@VDE (VDE-2026-008 / EUVD-2026-51029) and carries a CVSS 4.0 base score of 8.3, driven by high availability impact. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Unauthenticated configuration injection in Phoenix Contact CHARX SEC-3000/3050/3100/3150 EV charging controllers (versions 1.0.0 through 1.9.0) lets a remote attacker POST a malicious ID to the device's MQTT broker and thereby create a new entry in the system configuration, causing integrity and availability loss. Reported by CERT@VDE (advisory VDE-2026-008), the flaw carries a CVSS 4.0 base score of 8.8 and requires no authentication or user interaction. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
Communication-data tampering in Mitsubishi Electric's CC-Link IE TSN product family - spanning MELSEC MX Controllers, motion modules, MELSERVO-J5/JET AC servos, FR-A800/F800/E800 inverters, GOT3000 HMIs, remote I/O modules and TSN communication LSIs/SDKs - allows an attacker on the same CC-Link IE TSN network to forge control input/output values by injecting specially crafted packets under specific timing conditions. Because message integrity is not enforced on the channel (CWE-924), successful tampering can drive incorrect operation of the control function or produce a denial-of-service condition on the affected device. No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV; EPSS was not provided.
SQL injection in the Online Scheduling and Appointment Booking System WordPress plugin before version 27.8 lets unauthenticated attackers extract sensitive database contents, including WordPress user password hashes, through the plugin's public-facing booking request handler. The flaw stems from a user-supplied parameter being neither sanitized nor properly type-cast before use in a SQL query, and is reachable pre-authentication over the network. Publicly available exploit code exists (reported by WPScan), a vendor patch is available, and the EPSS score is low (0.20%) despite the high CVSS of 8.6.
Predictable shared-secret generation in Spring Tools for Eclipse (5.2.0 and earlier) weakens the authentication protecting Spring Boot DevTools remote-restart uploads to remotely deployed targets such as Docker containers or Cloud Foundry apps. Because the secret is derived from a non-cryptographic PRNG rather than a secure random source, an attacker able to reach the deployed application's DevTools remote endpoint may predict the secret, authenticate restart uploads, and push arbitrary code, yielding remote code execution (CVSS 8.3, scope-changed). There is no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Network exposure of Docker container control ports in Spring Tools for Eclipse (versions 5.2.0 and earlier) occurs because the Boot Dashboard Docker integration binds these ports to 0.0.0.0 (all interfaces) instead of loopback. Any attacker on the same network segment as a developer running the integration can reach the container control interface without authentication, yielding high confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and the issue is not in CISA KEV, but the flaw is trivially triggered once a developer starts the affected feature.
Sandbox escape in Google Chrome on macOS (versions prior to 151.0.7922.72) stems from an inappropriate implementation in the Tint component and lets a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Google rated the Chromium severity as Low, though the reported CVSS is 9.6; there is no public exploit identified at time of analysis and the EPSS score is only 0.16% (6th percentile), pointing to low near-term exploitation likelihood. The flaw is Mac-specific and requires user interaction (visiting a malicious page).
Sandbox escape in Google Chrome's Google Lens component (versions prior to 151.0.7922.72) lets an attacker who has already compromised the renderer process break out of the browser sandbox using a crafted HTML page. The flaw is a second-stage privilege boundary bypass rather than an initial-access bug: it requires a pre-existing renderer compromise to reach, and Google's own Chromium team rated its security severity as Low despite the 9.6 CVSS. No public exploit identified at time of analysis, and EPSS is very low at 0.16% (6th percentile).
Out-of-bounds memory read in the Dawn (WebGPU) component of Google Chrome before 151.0.7922.72 lets a remote attacker read memory outside intended bounds when a victim opens a crafted HTML page. Google's Chrome team reported it and a fixed Stable-channel build is available; there is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.17%, 7th percentile). Notably, Chromium internally rated the security severity 'Low' even though the NVD-style CVSS base score is 8.1, so real-world impact is likely narrower than the raw score implies.
Sandbox escape in Google Chrome desktop before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out to higher-privileged browser context via a crafted HTML page, rooted in insufficient validation of untrusted input in the AI component (CWE-20). NVD rates it CVSS 9.6 while Google labels the Chromium security severity 'Low', reflecting that renderer compromise is a hard prerequisite; there is no public exploit identified at time of analysis and EPSS is low at 0.17%. A vendor patch is available and CISA SSVC records exploitation as none.
Sandbox escape in Google Chrome desktop before 151.0.7922.72 lets an attacker who has already compromised the renderer process abuse insufficient input validation in the WebAuthn implementation, using a crafted PDF file to break out of the renderer sandbox and gain higher-privilege code execution. Google's Chrome team reported the flaw internally and rated it 'Low' severity within Chromium, even though NVD scores it 9.6 (Critical); there is no public exploit identified at time of analysis and CISA SSVC lists exploitation status as none. EPSS is very low at 0.16% (6th percentile), consistent with a second-stage bug that requires a pre-existing renderer compromise rather than a directly weaponizable entry point.
Sandbox escape in Google Chrome before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the sandbox by feeding a crafted PDF through the Notifications component, which insufficiently validates untrusted input (CWE-20). Full technical impact (SSVC: total) means a successful escape yields code execution outside the constrained renderer. Despite a 9.6 CVSS, Chromium rated this Low severity, EPSS is 0.16%, and there is no public exploit identified at time of analysis.
Out-of-bounds memory access in Google Chrome's Frame component affects all Desktop builds prior to 151.0.7922.72, letting a remote attacker read memory outside intended bounds when a victim opens a crafted HTML page. Chromium rated the underlying flaw Low severity, yet NVD scores it 8.8 (High) and tags flag potential RCE; there is no public exploit identified at time of analysis and EPSS is a low 0.18% (8th percentile). A vendor patch is available and the issue is not listed in CISA KEV.
Sandbox escape in Google Chrome for Android before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the sandbox via crafted HTML delivered through the Picture-in-Picture feature. Chromium rates the severity Low and CISA SSVC exploitation is 'none', making this a second-stage bug in an exploit chain rather than a standalone entry point. No public exploit identified at time of analysis, and EPSS is low at 0.17% (7th percentile).
Sandbox escape in Google Chrome desktop before 151.0.7922.72 stems from insufficient validation of untrusted input in a WebUI component, letting a remote attacker on the same network segment potentially break out of the renderer sandbox via malicious network traffic. Google rates the Chromium severity as Medium and vendor-tagged intelligence flags it as 'Potential RCE'; a vendor patch is available, but no public exploit identified at time of analysis and EPSS is low (0.17%, 6th percentile). CISA SSVC records no observed exploitation and only partial technical impact.
Heap corruption in Google Chrome's WebRTC component (versions prior to 151.0.7922.72) allows a remote attacker to exploit a use-after-free by luring a victim to a crafted HTML page, potentially leading to arbitrary code execution in the renderer process. The flaw is a CWE-416 object-lifecycle error rated CVSS 8.8 with user interaction required. There is no public exploit identified at time of analysis, and EPSS is low at 0.18% (8th percentile), indicating no observed weaponization despite the high CVSS.
Out-of-bounds memory read in Chrome's WebXR component allows remote attackers to disclose sensitive renderer process memory or crash the browser tab by luring a victim to a crafted HTML page. All Google Chrome releases prior to 151.0.7922.72 are affected across all platforms, with the vendor confirming a patch in the stable channel update. No public exploit identified at time of analysis, and an EPSS of 0.18% (8th percentile) indicates low near-term exploitation probability despite the high CVSS base score of 8.1.
Sandbox escape in Google Chrome's Dawn (WebGPU) component affects all desktop Chrome builds prior to 151.0.7922.72, where insufficient validation of untrusted input lets a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Chromium rates the severity Medium and the issue carries a CVSS 7.1 with scope change, but there is no public exploit identified at time of analysis and EPSS is very low at 0.18% (8th percentile). Google has shipped a patched Stable channel release addressing it.
Sandbox escape in Google Chrome for macOS before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the browser sandbox using a crafted HTML page, escalating a contained renderer foothold toward the host. The flaw sits in Chrome's Crypto component and is a second-stage bug that must be chained with an initial renderer compromise. There is no public exploit identified at time of analysis, EPSS is low (0.18%, 8th percentile), and Google rates the Chromium security severity as Medium despite the high CVSS.
Sandbox escape in Google Chrome on macOS before 151.0.7922.72 lets a remote attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page, escalating a contained renderer exploit into broader access on the host. The flaw stems from an inappropriate implementation in Chrome's Network component and is fixed in the stable channel update. There is no public exploit identified at time of analysis, EPSS is low (0.18%, 8th percentile), and Chromium rated the underlying severity Medium despite the NVD-style CVSS 9.6.
Sandbox escape in Google Chrome for macOS (versions before 151.0.7922.72) can be achieved by an attacker who has already compromised the renderer process, chaining a DevTools race condition via a crafted HTML page to break out of the renderer sandbox. Reported internally by the Chrome team and rated Medium by Chromium, it carries an NVD CVSS of 9.6 due to the scope change, though EPSS is very low (0.14%, 4th percentile). No public exploit identified at time of analysis and it is not on CISA KEV, indicating no confirmed active exploitation.
Sandbox escape in Google Chrome's ANGLE graphics layer (versions prior to 151.0.7922.72) allows a remote attacker who lures a victim to a crafted HTML page to potentially break out of the renderer sandbox, undermining the browser's core containment boundary. The flaw stems from insufficient validation of untrusted input (CWE-20) in ANGLE, Chrome's WebGL/OpenGL-to-native translation layer. It was reported internally by the Chrome team; there is no public exploit identified at time of analysis, and the EPSS score is low at 0.18% (8th percentile).
Sandbox escape in Google Chrome's DevTools (versions prior to 151.0.7922.72) lets an attacker who has already compromised the renderer process break out of the sandbox and gain broader host access via a crafted HTML page. It stems from insufficient validation of untrusted input (CWE-20) and requires user interaction plus a pre-existing renderer foothold, so it functions as a second-stage exploit rather than a standalone entry point. There is no public exploit identified at time of analysis, and EPSS is low (0.17%), consistent with Chromium's internal 'Medium' severity rating despite the high NVD CVSS score.
Sandbox escape in Google Chrome desktop versions prior to 151.0.7922.72 lets a remote attacker who has already compromised the renderer process break out of the sandbox via a crafted HTML page, chaining into the higher-privileged browser process. The flaw stems from insufficient validation of untrusted input in the Passwords component (CWE-20) and is rated Medium by Chromium despite an NVD CVSS of 9.6. There is no public exploit identified at time of analysis, and EPSS is low at 0.17% (7th percentile).
Sandbox escape in Google Chrome's "Save to Drive" feature (prior to 151.0.7922.72) lets a remote attacker who has already compromised the renderer process break out of the browser sandbox by supplying a crafted PDF file. The flaw stems from insufficient validation of untrusted input (CWE-20) and, while scored CVSS 9.6, is rated only Medium by Chromium because it is a second-stage bug requiring a prior renderer compromise. There is no public exploit identified at time of analysis and EPSS is low (0.19%, 9th percentile), consistent with a chained, non-trivial exploitation path rather than mass exploitation.
Sandbox escape in Google Chrome's ANGLE graphics layer allows a remote attacker to corrupt memory via a crafted HTML page in versions prior to 151.0.7922.72. The flaw is an out-of-bounds read and write (CWE-125) that a victim triggers simply by visiting a malicious page, potentially letting attacker-controlled code break out of the renderer sandbox. Google has released a fixed stable channel build; there is no public exploit identified at time of analysis and EPSS risk is currently low (0.21%).
Heap corruption in Google Chrome's Variations component before 151.0.7922.72 lets an attacker holding a privileged network position (an on-path / man-in-the-middle attacker) corrupt memory by delivering malicious network traffic, stemming from CWE-20 insufficient input validation. Google rates the Chromium severity as Medium and has shipped a fixed Stable-channel build; there is no public exploit identified at time of analysis and the flaw is not in CISA KEV. Because Variations (Chrome's server-driven feature-flag/experiment system) is fetched at startup in the browser process, a successful attacker could turn intercepted config traffic into a memory-safety primitive.
Sandbox escape in Google Chrome desktop prior to 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the browser sandbox via insufficient input validation in the WebSockets implementation, triggered by a crafted HTML page. This is a second-stage exploitation primitive rather than an initial-access bug: it requires a pre-existing renderer compromise plus user navigation to attacker content. No public exploit identified at time of analysis; EPSS is low at 0.21% (11th percentile) and it is not on CISA KEV, though Google has shipped a fixed Stable channel build.
Sandbox escape in Google Chrome desktop prior to 151.0.7922.72 allows an attacker who tricks a user into installing a malicious extension to break out of the renderer/extension sandbox via a crafted extension exploiting insufficient input validation. The flaw was reported internally by the Chrome team and carries an NVD CVSS of 9.6, though Chromium rates the security severity only Medium and SSVC shows no known exploitation; no public exploit identified at time of analysis. A vendor patch is available, and exploitation hinges on the significant precondition of the victim installing an attacker-controlled extension.
Sandbox escape in Google Chrome's Android WebView (versions prior to 151.0.7922.72) allows a remote attacker to break out of the renderer sandbox when a victim views a crafted HTML page. Rated Medium by Chromium and CVSS 7.1, it carries a scope-changing impact but requires user interaction; there is no public exploit identified at time of analysis and EPSS is low (0.21%, 11th percentile), indicating limited near-term mass exploitation likelihood.
Sandbox escape in Google Chrome's Payments component before 151.0.7922.72 lets a remote attacker who has already compromised the renderer process break out of the sandbox by serving a crafted HTML page, driven by insufficient validation of untrusted input (CWE-20). Google rates the Chromium security severity as Medium, but the assigned CVSS is 9.6 due to the scope-changing sandbox escape. There is no public exploit identified at time of analysis, no CISA KEV listing, and EPSS is low at 0.21%.
BFCache in Google Chrome prior to 151.0.7922.72 contains insufficient input validation that enables a renderer-compromised attacker to escape Chrome's sandbox and execute code in the higher-privileged browser process via a crafted HTML page. The Scope:Changed metric in the CVSS vector (8.7) confirms the escape crosses the renderer-to-browser process boundary, yielding high confidentiality and integrity impact. No public exploit or active exploitation has been identified; EPSS sits at 0.21% (11th percentile) and SSVC rates exploitation as none and not automatable, consistent with the chained, technically demanding nature of this attack.
Sandbox escape in Google Chrome's Android WebView allows a remote attacker who has already compromised the renderer process to break out of the sandbox via a crafted HTML page in versions prior to 151.0.7922.72. Rooted in a use-after-free (object lifecycle) flaw rated High by Chromium, this is a second-stage privilege-boundary bypass rather than a standalone entry point. No public exploit identified at time of analysis, and the EPSS score is low (0.21%, 11th percentile), consistent with a bug reported internally by the Chrome team and patched before evidence of exploitation.
Sandbox escape in Google Chrome for Android before 151.0.7922.72 lets an attacker who already controls a compromised renderer process break out of the sandbox through crafted input handled by the browser's Accessibility component. Rated High by Chromium and CVSS 9.6, it is a second-stage bug typically chained after an initial renderer exploit, giving an attacker a path to full compromise of the browser/host context. There is no public exploit identified at time of analysis, EPSS risk is low (0.29%, 21st percentile), and it is not on CISA KEV.
Sandbox escape in Google Chrome on macOS prior to 151.0.7922.72 lets a remote attacker who has already compromised the renderer process break out of the browser sandbox by exploiting a race condition in the Downloads component through a crafted HTML page. Rated High by Chromium and carrying a CVSS 9.6 due to the scope-changing total impact, it is patched in the July 2026 Stable channel update. There is no public exploit identified at time of analysis, EPSS is low at 0.23%, and CISA SSVC records exploitation as 'none'.
Sandbox escape in Google Chrome for macOS prior to 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the sandbox and reach the more-privileged browser process by loading a crafted HTML page that abuses Chrome's MHTML handling. It is rated High by Chromium and carries a CVSS 9.6 (scope-changed) score, but exploitation is a second-stage step that presupposes prior renderer compromise. There is no public exploit identified at time of analysis, and EPSS is low at 0.29% (21st percentile).
Sandbox escape in Google Chrome on macOS prior to 151.0.7922.72 lets a remote attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page that triggers a race condition in the Downloads component. Chromium rates it High severity and the CVSS is 9.6 (scope-changed). This is no public exploit identified at time of analysis; EPSS is low at 0.23% (14th percentile) and CISA SSVC records exploitation status as none.
Sandbox escape in Google Chrome's ANGLE graphics layer on macOS (versions prior to 151.0.7922.72) lets an attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page. Rated High by Chromium and carrying a CVSS 9.6 due to the scope change from renderer to host, it enables full compromise of the browser process. There is no public exploit identified at time of analysis and it is not on CISA KEV; EPSS is low at 0.29% (21st percentile).
Cross-origin data disclosure in Google Chrome for Android before 151.0.7922.72 lets a remote attacker leak data from other origins by luring a victim to a crafted HTML page that abuses insufficient input validation in the browser UI. Rated High by Chromium and CVSS 7.5 (confidentiality-only). There is no public exploit identified at time of analysis, and EPSS is low at 0.18%, though SSVC flags the attack as automatable with partial technical impact.
Sandbox escape in Google Chrome's ANGLE graphics layer prior to version 151.0.7922.72 lets a remote attacker who lures a victim to a crafted HTML page trigger a type confusion (CWE-843) and potentially break out of the renderer sandbox. Google rates the Chromium severity High, and the CVSS 9.6 reflects a scope-changing bug requiring only that the victim open a page. There is no public exploit identified at time of analysis, EPSS is low at 0.31% (24th percentile), and CISA's SSVC marks exploitation as none.
Sandbox escape in Google Chrome on macOS (versions prior to 151.0.7922.72) stems from an inappropriate implementation in ANGLE, Chrome's graphics abstraction layer, allowing a remote attacker to break out of the renderer sandbox via a crafted HTML page after the victim loads it. Rated High by Chromium and carrying a CVSS 9.6 (scope-changed), it enables an attacker to escalate from web content into higher-privilege execution on the host. No public exploit identified at time of analysis, and EPSS exploitation probability is low (0.29%, 21st percentile).
Sandbox escape in Google Chrome's ANGLE graphics layer (versions prior to 151.0.7922.72) lets a remote attacker who has already compromised the renderer process break out of the browser sandbox using a crafted HTML page. Rated High by Chromium and CVSS 9.6, the flaw is a CWE-843 type confusion; Google has shipped a fixed Stable channel build. There is no public exploit identified and no CISA KEV listing, and EPSS is low at 0.31% (24th percentile), indicating no evidence of active exploitation at time of analysis.
Sandbox escape in Google Chrome for iOS before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the sandbox via a crafted HTML page, escalating a contained renderer foothold into broader control (CVSS 9.6, scope-changed). Reported internally by the Chrome team under CWE-20 insufficient input validation; no public exploit identified at time of analysis, and EPSS is low at 0.29% (21st percentile), consistent with a chained bug that is not yet weaponized. Vendor-released patch is available in stable channel 151.0.7922.72.
Sandbox escape in Google Chrome for Android before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the browser sandbox by feeding crafted untrusted input to the Web Authentication (WebAuthn) component. Rated High severity by Chromium and scored CVSS 9.6, it is a second-stage bug chained after an initial renderer exploit rather than a standalone remote compromise. No public exploit identified at time of analysis, and EPSS exploitation probability is low at 0.34% (27th percentile).
Out-of-bounds read in Chrome's ANGLE graphics abstraction layer (versions prior to 151.0.7922.72) can be leveraged by an attacker who has already compromised the renderer process to potentially escape the browser sandbox via a crafted HTML page. Google rates the Chromium severity High and has shipped a fixed Stable-channel build; no public exploit identified at time of analysis, and the EPSS score is low (0.29%, 21st percentile), consistent with a second-stage bug rather than a standalone drive-by. Because it requires a pre-compromised renderer, it is typically one link in an exploit chain rather than a single-shot RCE.
Sandbox escape in Google Chrome for Android (versions prior to 151.0.7922.72) stems from an inappropriate implementation in ANGLE, Chrome's graphics abstraction layer, allowing a remote attacker to break out of the renderer sandbox using a crafted HTML page. Rated High severity by Chromium with a CVSS of 8.8, the flaw requires the victim to visit a malicious page (user interaction) but no authentication. There is no public exploit identified at time of analysis, and the EPSS score is low (0.29%, 21st percentile), consistent with a recently disclosed browser bug fixed before weaponization.
Sandbox escape in Google Chrome's ANGLE graphics layer on Android (versions prior to 151.0.7922.72) allows a remote attacker who has already compromised the renderer process to break out of the renderer sandbox and gain broader access on the device via a crafted HTML page. Rated High by Chromium and scored CVSS 9.6 largely because of the scope change from a successful escape. There is no public exploit identified at time of analysis, and EPSS is low (0.29%, 21st percentile), consistent with a bug that only becomes useful after a prior renderer compromise.
Sandbox escape in Google Chrome's Chromecast component (versions prior to 151.0.7922.72) allows a remote attacker who has already compromised the renderer process to break out of the sandbox via a crafted HTML page. Rated High by Chromium and scored CVSS 9.6 due to scope change, it is a classic second-stage browser exploit chained after an initial renderer bug. No public exploit is identified at time of analysis and EPSS is low (0.29%), consistent with a bug requiring a prior renderer foothold rather than a single-shot drive-by.
Sandbox escape in Google Chrome's ANGLE graphics component (versions prior to 151.0.7922.72) allows a remote attacker who has already compromised the renderer process to break out of the browser sandbox via a crafted HTML page. Rated High by Chromium with a CVSS 9.6 due to scope change and full CIA impact, though it requires a pre-existing renderer compromise as a chained prerequisite. There is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.29%).
Sandbox escape in Google Chrome for iOS before version 151.0.7922.72 allows a remote attacker to break out of the browser's security boundary when a victim opens a crafted HTML page. Rated High by Chromium and carrying a 9.6 CVSS due to a scope-changing, high-impact outcome requiring only user interaction, though there is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.29%, 21st percentile). A vendor-released patch is available and CISA SSVC currently records exploitation status as none.
Sandbox escape in Google Chrome for Android before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the browser sandbox through crafted input to the GPU component. This is a second-stage vulnerability (CWE-20, improper input validation) that Google rates High severity and CVSS 8.3 with a scope change; it is chained after an initial renderer bug rather than exploited alone. No public exploit has been identified at time of analysis, EPSS is low (0.29%, 21st percentile), and CISA SSVC records exploitation as none, though technical impact is rated total.
Sandbox escape in Google Chrome's Network component before 151.0.7922.72 allows a remote attacker who has already compromised the renderer process to break out of the sandbox and gain broader access on the host via a crafted HTML page. Rated High by Chromium and scored CVSS 8.3, it is a second-stage bug that must be chained with an initial renderer exploit rather than exploited in isolation. There is no public exploit identified at time of analysis, and the EPSS probability is low at 0.29% (21st percentile).
Sandbox escape in Google Chrome's ANGLE graphics layer, fixed in stable release 151.0.7922.72, lets a remote attacker who lures a victim to a crafted HTML page break out of the renderer sandbox and gain broader access on the host. Rated Critical by Chromium and scored CVSS 9.6, the flaw stems from insufficient validation of untrusted input (CWE-20) processed by ANGLE and carries a scope-changing impact. There is no public exploit identified at time of analysis and EPSS is low at 0.31% (23rd percentile), but the Critical rating and sandbox-escape primitive make prompt patching important.
Unauthenticated information disclosure in the Mapster WP Maps WordPress plugin (all versions before 1.24.0) exposes the full title and body content of any post - including drafts, private, pending, and trashed posts - through an unprotected public REST API endpoint. Any remote attacker with network access to the WordPress site can enumerate and read content that site owners explicitly withheld from publication, bypassing WordPress's native post-status and capability access controls. A publicly available proof-of-concept exists per WPScan reporting; however, the EPSS score of 0.14% (4th percentile) indicates exploitation has not yet become widespread, and the vulnerability is not listed in the CISA KEV catalog.
Heap memory disclosure in Coturn 4.5.2-4.14.0 allows an unauthenticated remote attacker to extract up to ~870 bytes of adjacent process heap per request by sending a single HTTP GET to the ACME redirect plaintext TCP listener. The leaked memory originates from recycled, unzeroed network receive buffers and on busy relay servers can contain TURN credentials, OAuth tokens, or relayed session payloads from concurrent clients. Exploitation is trivially automatable against the affected configuration; no public exploit identified at time of analysis beyond the proof-of-concept test case shipped with the advisory.
Pterodactyl Wings before v1.13.0 crashes when its SFTP handler receives a crafted packet with fewer than 4 bytes in the payload during the SSH connection handshake, triggering a Go runtime index-out-of-bounds panic that kills the Wings daemon. The crash is exploitable by any unauthenticated network attacker who can reach the SFTP port, requiring no credentials because the vulnerable slice operation executes prior to authentication. No public exploit code exists at time of analysis, but the patch diff makes the trigger trivially reproducible: any packet with a short payload in the SSH subsystem channel request is sufficient.
mTLS authentication bypass in aap-gateway, the gateway component of Red Hat Ansible Automation Platform's Event-Driven Ansible (EDA), permits unauthenticated remote attackers to inject arbitrary events into automation workflows. The bypass exploits event stream URL manipulation and HTTP Subject header forgery; the attack surface is further reduced by the component's inadvertent disclosure of the expected TLS certificate subject in error responses (CWE-295). No public exploit code or CISA KEV listing has been identified at time of analysis, but the low attack complexity and CVSS 8.2 score make this a credible priority for organizations running EDA-integrated automation pipelines.
Cross-tenant credential theft in pgAdmin 4 (9.0 through 9.16) lets an authenticated non-owner user hijack another user's shared server connection by abusing the Workspaces adhoc-connect endpoint (/misc/workspace/adhoc_connect_server), which clones a target server row verbatim - including its owner's stored database password and tunnel password - and reassigns ownership to the caller. The victim is typically an administrator whose shared server carries saved credentials, and the attacker gains use of those database credentials and any privileges they confer. There is no public exploit identified at time of analysis and it is not on CISA KEV, but the fix (pgAdmin 4 9.17) and the underlying commit are public, and EPSS was not provided.
Sensitive-credential disclosure leading to full node compromise in Pterodactyl Wings before v1.12.3 lets a low-privileged, authenticated panel user (a server owner or a subuser holding startup.update) smuggle a {{config.*}} placeholder through a user-editable egg variable, causing Wings to resolve it against its entire daemon configuration and write secrets - including the node daemon token, token_id, and Docker registry credentials - into a file the user can read via the file manager or SFTP. Because the daemon token is both the Panel⇆Wings API bearer and the HMAC signing key for every JWT the node issues, an attacker can then forge tokens and act against every server on the node. No public exploit identified at time of analysis and it is not listed in CISA KEV, but the CVSS is 9.9 and the affected templating pattern is common across stock and community eggs.
Credential and cryptographic-key exposure in the VPS.org one-click Zulip deployment template ships every instance with an identical hardcoded application signing key, a default database password of "zulip", and HTTPS disabled (DISABLE_HTTPS=True), allowing remote attackers who know the public template defaults to forge authenticated sessions, read Zulip's database, and intercept traffic. Any organization that provisioned Zulip through this VPS.org one-click image is affected until the secrets are rotated. There is no public exploit identified at time of analysis, and the EPSS score is low (0.13%, 3rd percentile), but SSVC rates technical impact as total and automatable, reflecting that the shared secrets are identical across all deployments.
Information disclosure in 389 Directory Server (upstream of Red Hat Directory Server 11-13, shipped across RHEL 6-10) lets an unauthenticated remote attacker inject LDAP search filters into the CleanAllRUV replication status-check extended operation. Because the handler evaluates attacker-controlled filters against cn=config using elevated replication-plugin privileges and leaks a boolean match result, attackers can blindly enumerate sensitive configuration metadata such as replication bind DNs and password storage scheme details. No public exploit is identified at time of analysis and it is not listed in CISA KEV, but the network-reachable, no-authentication attack surface makes it a meaningful reconnaissance primitive.
Sensitive credential exposure in ANDRITZ HIPASE-250 (formerly 250 SCALA) stems from storing and transmitting user passwords in a reversible format rather than as one-way hashes, letting anyone who can read the credential store or sniff network traffic recover every stored password in cleartext. The flaw affects the HIPASE-250 protection, control and monitoring platform and carries a CVSS 7.5 (confidentiality-only) rating. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV; recovered credentials could enable follow-on authenticated access to the device or connected OT systems.
Tenant-restriction bypass in Keycloak's Microsoft identity provider integration allows attackers holding any valid Microsoft OAuth token - even from a completely unrelated Azure AD organization - to authenticate into a Keycloak realm via the token exchange feature. Affected deployments include Red Hat Build of Keycloak, Red Hat Single Sign-On 7, and Red Hat JBoss EAP Expansion Pack. With CVSS PR:L reflecting the need for a valid Microsoft credential (trivially obtained by registering a free Azure tenant), successful exploitation grants high confidentiality and integrity impact within the realm. No public exploit or active exploitation has been identified at time of analysis; EPSS sits at 0.19% (9th percentile), consistent with SSVC exploitation=none.
Unauthenticated information disclosure in the Geeky Bot WordPress plugin (all versions before 1.2.8) permits any remote, unauthenticated user to retrieve chat-history session metadata - including WordPress usernames, user IDs, and timestamps - by invoking an unprotected AJAX endpoint. Reported by WPScan with a publicly available proof-of-concept, this flaw provides attackers with a ready-made user enumeration primitive against any publicly reachable WordPress site running the affected plugin. CISA KEV listing is absent and EPSS sits at 0.14% (4th percentile), indicating limited current mass-exploitation, but the POC lowers the barrier for targeted attacks significantly.
GiveWP WordPress plugin before 4.16.3 exposes sensitive donor privacy data through an unauthenticated REST API endpoint that returns recurring-donation records without access controls. Any unauthenticated remote party can enumerate donor names and subscription details for donors who explicitly chose to give anonymously, directly violating donor privacy expectations. A publicly available exploit exists per WPScan reporting, though EPSS sits at the 5th percentile, suggesting limited opportunistic exploitation at time of analysis. No active exploitation is confirmed via CISA KEV.
Default-credential unauthorized access affects the Advantech ECU-1251D industrial communication gateway, which ships with a root SSH account protected by no password and is documented as such in the device manual. An attacker on the same network segment can log in as root over SSH without any credential, and because configuration provides no prompt or guidance to change these defaults, exploitable devices are likely to persist in the field. No public exploit identified at time of analysis, but the vulnerability requires no exploitation skill - knowledge of the documented default is sufficient.
Denial-of-service in an IEC 61850 GOOSE subscriber component allows an adjacent, unauthenticated attacker on the same Layer-2 network to crash the message-processing process by sending a crafted GOOSE frame (EtherType 0x88B8) with an undersized UTC timestamp field, triggering a heap out-of-bounds read (CWE-125). The flaw was reported by DHS ICS-CERT and documented in CISA ICS advisory ICSA-26-211-10; there is no public exploit identified at time of analysis, and the CVSS 4.0 vector scores availability impact only (VA:H) with no confidentiality or integrity effect.
Denial-of-service in an IEC 61850 GOOSE subscriber implementation allows an attacker with access to the substation process bus to crash the subscriber process using a single unauthenticated Layer-2 multicast frame. An off-by-one boundary error in the GOOSE parser triggers a heap out-of-bounds read (CWE-125) that reliably terminates the process. No public exploit identified at time of analysis; this is not listed in CISA KEV, and no EPSS score was provided.
Denial-of-service in an IEC 61850 MMS (Manufacturing Message Specification) protocol implementation allows an attacker with an established MMS session to crash the MMS handling process by sending a malformed BER-encoded confirmed-request message over TCP port 102. The flaw is a heap out-of-bounds read (CWE-125) in the BER decoder's boundary handling. No public exploit or active exploitation is identified at time of analysis; the CVSS 4.0 score of 7.1 reflects a high availability impact with low required privileges and no user interaction.
Heap buffer over-read in MZ Automation GmbH's libiec61850 (versions prior to 1.6.2) allows an unauthenticated adjacent-network attacker to crash the MMS service process by sending a crafted BER-encoded message with an invalid length value in a BOOLEAN or INTEGER field. The MMS BER decoder performs no bounds validation on the attacker-supplied length, causing a read past the end of a heap-allocated buffer and subsequent process termination. CISA ICS-CERT issued advisory ICSA-26-211-10 for this vulnerability; no public exploit code or KEV listing has been identified at time of analysis.
Denial-of-service in MZ Automation's libiec61850 (versions before 1.6.2) allows an unauthenticated attacker on the process bus to crash IEC 61850 subscriber processes with a single crafted GOOSE frame. The GOOSE payload parser mishandles nested length fields, so an inner element length that exceeds its enclosing length forces a one-byte out-of-bounds read (CWE-125) that reliably terminates the subscriber. No public exploit identified at time of analysis, and it is not listed in CISA KEV; the CISA ICS advisory (ICSA-26-211-10) and a vendor patch are available.
Remote unauthenticated denial of service in MZ Automation's libiec61850 (all versions before 1.6.2) allows an attacker to crash IEC 61850/MMS server processes by opening a crafted TCP/102 connection. The flaw sits in the ISO Presentation layer's normal-mode negotiation, where a missing length check on an attacker-controlled zero-length field triggers a bounded heap out-of-bounds read that terminates the process before any MMS session is even established. No public exploit identified at time of analysis and it is not on CISA KEV, but the pre-authentication network reach and low complexity make it a credible availability threat to exposed OT/ICS devices.
Sensitive information disclosure in RapidRAW before 1.6.0 (an open-source cross-platform RAW photo editor) allows a remote attacker to steal a Windows victim's NTLMv2 credentials by embedding a UNC path in the lutPath field of a preset file. Because RapidRAW passes lutPath directly to File::open() without validation, opening the poisoned preset forces an outbound SMB authentication to an attacker-controlled host. There is no public exploit identified at time of analysis, but the technique (UNC-path credential coercion) is well understood and trivially reproducible, so real-world abuse is realistic once a malicious preset is shared.
Hard-coded shared RSA private keys and their matching X.509 certificates in Watchfire digital billboard controller software (BC550, BC750, BC760, BC760DC) let an attacker who extracts them decrypt and impersonate the controller's built-in HTTPS/TLS web management interface. Because the keys ship in plaintext inside the firmware patch binaries - retrievable from Watchfire's Remote Support filestore - any attacker with the same firmware can recover the identical keys used across all deployed units. This is an information-disclosure/authentication-bypass class flaw (CWE-321) reported through CISA ICS-CERT; no public exploit identified at time of analysis and it is not listed in CISA KEV.
Default-credential authentication bypass in the LazyOwn RedTeam/APT Framework (grisuno/lazyown) before 0.2.154 lets any network-reachable attacker log into the C2 dashboard using the hardcoded operator credentials 'LazyOwn'/'LazyOwn', gaining full operator-level control of the command-and-control server. The framework ships these defaults in payload.json and core/payload_schema.py and passes them unchanged into lazyc2.py's HTTP Basic authentication. No public exploit identified at time of analysis, but the credentials are trivially known from the source code, and the CVSS base score is 9.8 (Critical).
Out-of-bounds heap read in the open62541 OPC UA C library allows a remote unauthenticated attacker to disclose sensitive process memory by supplying a crafted UA_Variant whose arrayDimensions provoke an integer overflow in the dimension-product computation. The overflow makes the computed element/stride total wrap to a small value, so bounds checks pass and subsequent index math walks past the heap allocation. CVSS 4.0 is 8.7 (confidentiality-only impact); no public exploit identified at time of analysis, though it is tracked in a CISA ICS advisory (ICSA-26-211-08) given the industrial/OT exposure of OPC UA servers.
Cross-tenant vector document disclosure in IBM Langflow OSS 1.0.0 through 1.10.1 lets an authenticated low-privilege user read another user's private Chroma-backed documents by building a flow that reuses the victim's persist_directory and collection_name, returning exact victim content in the attacker's workflow output. The same shared-namespace flaw also lets the attacker write their own documents into the victim's collection, corrupting its integrity. No public exploit is identified at time of analysis and CISA SSVC rates exploitation as none, but the CVSS 8.1 rating reflects the combined high confidentiality and integrity impact.
Unauthenticated credential leakage in SGLang's /server_info HTTP endpoint exposes configured API keys and SSL keyfile paths to any network-reachable caller on all versions through v0.5.15. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms no authentication or user interaction is required, and SSVC classifies the attack as automatable with a proof-of-concept available, making mass scanning for exposed instances a realistic threat. EPSS sits at just 0.14% (4th percentile), reflecting SGLang's niche deployment footprint rather than any technical difficulty - for internet-facing deployments using --admin-api-key, this is a high-priority credential-rotation and patching event.
Cross-tenant code injection and data disclosure in Activepieces (the open-source AI workflow automation platform) before 0.84.0 allows an authenticated flow author to escape their Code-piece sandbox and reach the read-write cached flow and code files of other tenants sharing the same worker. By abusing an unsanitized path segment, an attacker can read embedded secrets and data from co-tenants and overwrite cached code so that it executes under a victim tenant's identity on their next flow run. Publicly available intelligence shows no public exploit identified at time of analysis and no CISA KEV listing, but the vendor-confirmed fix and the broad impact (VC:H/VI:H plus subsequent-system SC:H/SI:H) make this a high-priority multi-tenant isolation failure.
OAuth 2.0 authorization-code theft in Dromara MaxKey through 4.1.12 lets remote attackers hijack a victim's authorization code and exchange it for an access token, taking over the victim's federated identity. The flaw lives in DefaultRedirectResolver.hostMatches(), where a naive endsWith() suffix comparison lets an attacker-controlled domain that ends with a registered redirect URI hostname pass validation. Publicly available exploit code exists and a vendor patch (commit ddbb72f) is available; no active exploitation has been confirmed (not in CISA KEV).
Local information disclosure in IBM App Connect Enterprise (versions 13.0.1.0-13.0.7.2 and 12.0.1.0-12.0.12.27) occurs because the integration runtime writes potentially sensitive information into log files that any local user can read. An attacker with local access to the host can harvest secrets such as credentials, connection strings, or message payload data from these logs to escalate access or pivot to backend systems. No public exploit identified at time of analysis, and there is no KEV listing; note that the NVD CVSS vector (AV:N) conflicts with the description's explicit 'local user' wording.
Privilege escalation via dynamic client registration in malach-it's Boruta OAuth 2.0/OpenID Connect provider library (Elixir) lets an unauthenticated registrant create OIDC clients that carry administrative security attributes. Because Boruta.Openid.register_client/3 forwards caller-supplied parameters straight into the administrative client-creation changeset with no public/admin allowlist, a self-registering client can dictate its own supported grant types, authorized scopes, PKCE enforcement, public refresh/revocation behavior, token lifetimes, and signing settings on versions 2.3.0 through 2.3.6. There is no public exploit identified at time of analysis and it is not in CISA KEV, but a vendor-released patch (2.3.7) is available.
Privilege escalation in the Serendipity (s9y) PHP blogging platform before 2.6.1 lets an authenticated Editor take over an Administrator account by exploiting an authentication context confusion (CWE-304): password checking and session loading resolve the user independently rather than binding to a single record. By registering a username that collides with an Administrator's, the Editor logs in with their own password yet has the Administrator's account loaded into their session, inheriting full admin rights. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the CVSS 4.0 base score of 8.7 reflects high confidentiality, integrity, and availability impact.
Unauthenticated Wiki Markup rendering in Apache JSPWiki up to 2.12.3 exposes sensitive data stored in internal JSPWiki variables to remote attackers. The flaw stems from a missing authentication check (CWE-306) on the markup rendering endpoint, allowing any network-reachable attacker to trigger rendering and extract variable contents without credentials. No public exploit has been identified and EPSS sits at a low 0.21% (12th percentile), but the CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivially easy remote unauthenticated exploitation against default deployments. Vendor patches are available.
Apache JSPWiki versions up to and including 2.12.3 expose sensitive application internals through debug messages returned in HTTP responses, classified under CWE-1295 (Debug Messages Revealing Unnecessary Information). The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates any unauthenticated remote user can trigger disclosure of high-confidentiality data - potentially including session tokens, internal paths, configuration details, or stack traces - without requiring special privileges or user interaction. Despite the high CVSS score of 7.5, real-world exploitation probability is notably low at 0.17% EPSS (7th percentile), and no public exploit code or active exploitation via CISA KEV has been identified at time of analysis.
Silent date corruption in Date::Manip through version 6.99 allows any caller passing untrusted character strings to ParseDate() or Date::Manip::Date->parse() to receive silently incorrect parsed dates when non-ASCII Unicode decimal digits (such as Arabic-Indic, Devanagari, or other Unicode script numerals) appear in year, month, or day fields. Perl's \d regex shorthand matches the full Unicode decimal-digit property (\p{Nd}), so non-ASCII digits are captured; subsequent numeric range validation then passes them because Perl truncates the string-to-number conversion at the first non-ASCII character, producing an in-range but wrong value — for example, '202٤' evaluates to year 202, not 2024. No public exploit has been identified at time of analysis and EPSS is very low (0.19%), but SSVC flags the flaw as automatable and the impact is meaningful for any application where Date::Manip parses externally-supplied dates to gate expiry checks, retention windows, or access-control logic.
Information disclosure and host-process Denial-of-Service affects VMware ESX, Workstation, and Fusion via an out-of-bounds read (CWE-125) reachable by an actor holding VM deployment privileges. On ESX the flaw can crash or leak memory from the host VMX process (a guest-to-host scope crossing), while on Workstation and Fusion the impact is limited to information disclosure. Reported by VMware/Broadcom with no public exploit identified at time of analysis and no CISA KEV listing.
Full system compromise of Phoenix Contact CHARX SEC EV charging controllers (SEC-3000/3050/3100/3150, versions 1.0.0 through 1.9.0) is possible because an incorrect script execution order tears down the firewall too early during system shutdown, briefly exposing internal-only services to the network. During this transient window a remote unauthenticated attacker can reach services that are normally firewalled off and gain complete control of the device. No public exploit identified at time of analysis, but the flaw is vendor-confirmed (CERT@VDE / advisory VDE-2026-008) and carries a CVSS 4.0 base score of 9.3.
Denial-of-service in Phoenix Contact CHARX SEC EV charging controllers (SEC-3000/3050/3100/3150, firmware 1.0.0 up to but not including 1.9.1) allows an unauthenticated network attacker to reboot the charging controller by sending a crafted Modbus TCP command to the CharxModbusServer. The attack requires no credentials or user interaction and, per the CVSS 4.0 vector, produces high availability impact with no confidentiality or integrity effect. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV, but the low attack complexity makes reliable disruption of charging service straightforward once the Modbus port is reachable.
Unauthenticated firmware implantation in Phoenix Contact CHARX SEC-3000/3050/3100/3150 EV charging controllers allows a remote attacker to push a modified firmware image to the basemodule because the update routine only checks a CRC32 checksum and performs no cryptographic signature verification (CWE-347). A successful upload yields full system compromise of the controller. No public exploit has been identified at time of analysis, but the flaw is network-reachable with no authentication and a vendor patch (v1.9.1) is available.
Insecure firmware-fallback in Phoenix Contact CHARX SEC EV charging controllers (SEC-3000, SEC-3050, SEC-3100, SEC-3150, versions 1.0.0 up to 1.9.1) lets a remote unauthenticated attacker force the device to boot an alternate firmware partition that ships with an insecure configuration and default credentials, yielding SSH access as the unprivileged 'user-app' account and allowing charging to be interrupted. The issue was reported by CERT@VDE (VDE-2026-008 / EUVD-2026-51029) and carries a CVSS 4.0 base score of 8.3, driven by high availability impact. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Unauthenticated configuration injection in Phoenix Contact CHARX SEC-3000/3050/3100/3150 EV charging controllers (versions 1.0.0 through 1.9.0) lets a remote attacker POST a malicious ID to the device's MQTT broker and thereby create a new entry in the system configuration, causing integrity and availability loss. Reported by CERT@VDE (advisory VDE-2026-008), the flaw carries a CVSS 4.0 base score of 8.8 and requires no authentication or user interaction. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
Communication-data tampering in Mitsubishi Electric's CC-Link IE TSN product family - spanning MELSEC MX Controllers, motion modules, MELSERVO-J5/JET AC servos, FR-A800/F800/E800 inverters, GOT3000 HMIs, remote I/O modules and TSN communication LSIs/SDKs - allows an attacker on the same CC-Link IE TSN network to forge control input/output values by injecting specially crafted packets under specific timing conditions. Because message integrity is not enforced on the channel (CWE-924), successful tampering can drive incorrect operation of the control function or produce a denial-of-service condition on the affected device. No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV; EPSS was not provided.
SQL injection in the Online Scheduling and Appointment Booking System WordPress plugin before version 27.8 lets unauthenticated attackers extract sensitive database contents, including WordPress user password hashes, through the plugin's public-facing booking request handler. The flaw stems from a user-supplied parameter being neither sanitized nor properly type-cast before use in a SQL query, and is reachable pre-authentication over the network. Publicly available exploit code exists (reported by WPScan), a vendor patch is available, and the EPSS score is low (0.20%) despite the high CVSS of 8.6.
Predictable shared-secret generation in Spring Tools for Eclipse (5.2.0 and earlier) weakens the authentication protecting Spring Boot DevTools remote-restart uploads to remotely deployed targets such as Docker containers or Cloud Foundry apps. Because the secret is derived from a non-cryptographic PRNG rather than a secure random source, an attacker able to reach the deployed application's DevTools remote endpoint may predict the secret, authenticate restart uploads, and push arbitrary code, yielding remote code execution (CVSS 8.3, scope-changed). There is no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Network exposure of Docker container control ports in Spring Tools for Eclipse (versions 5.2.0 and earlier) occurs because the Boot Dashboard Docker integration binds these ports to 0.0.0.0 (all interfaces) instead of loopback. Any attacker on the same network segment as a developer running the integration can reach the container control interface without authentication, yielding high confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and the issue is not in CISA KEV, but the flaw is trivially triggered once a developer starts the affected feature.
Sandbox escape in Google Chrome on macOS (versions prior to 151.0.7922.72) stems from an inappropriate implementation in the Tint component and lets a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Google rated the Chromium severity as Low, though the reported CVSS is 9.6; there is no public exploit identified at time of analysis and the EPSS score is only 0.16% (6th percentile), pointing to low near-term exploitation likelihood. The flaw is Mac-specific and requires user interaction (visiting a malicious page).
Sandbox escape in Google Chrome's Google Lens component (versions prior to 151.0.7922.72) lets an attacker who has already compromised the renderer process break out of the browser sandbox using a crafted HTML page. The flaw is a second-stage privilege boundary bypass rather than an initial-access bug: it requires a pre-existing renderer compromise to reach, and Google's own Chromium team rated its security severity as Low despite the 9.6 CVSS. No public exploit identified at time of analysis, and EPSS is very low at 0.16% (6th percentile).
Out-of-bounds memory read in the Dawn (WebGPU) component of Google Chrome before 151.0.7922.72 lets a remote attacker read memory outside intended bounds when a victim opens a crafted HTML page. Google's Chrome team reported it and a fixed Stable-channel build is available; there is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.17%, 7th percentile). Notably, Chromium internally rated the security severity 'Low' even though the NVD-style CVSS base score is 8.1, so real-world impact is likely narrower than the raw score implies.
Sandbox escape in Google Chrome desktop before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out to higher-privileged browser context via a crafted HTML page, rooted in insufficient validation of untrusted input in the AI component (CWE-20). NVD rates it CVSS 9.6 while Google labels the Chromium security severity 'Low', reflecting that renderer compromise is a hard prerequisite; there is no public exploit identified at time of analysis and EPSS is low at 0.17%. A vendor patch is available and CISA SSVC records exploitation as none.
Sandbox escape in Google Chrome desktop before 151.0.7922.72 lets an attacker who has already compromised the renderer process abuse insufficient input validation in the WebAuthn implementation, using a crafted PDF file to break out of the renderer sandbox and gain higher-privilege code execution. Google's Chrome team reported the flaw internally and rated it 'Low' severity within Chromium, even though NVD scores it 9.6 (Critical); there is no public exploit identified at time of analysis and CISA SSVC lists exploitation status as none. EPSS is very low at 0.16% (6th percentile), consistent with a second-stage bug that requires a pre-existing renderer compromise rather than a directly weaponizable entry point.
Sandbox escape in Google Chrome before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the sandbox by feeding a crafted PDF through the Notifications component, which insufficiently validates untrusted input (CWE-20). Full technical impact (SSVC: total) means a successful escape yields code execution outside the constrained renderer. Despite a 9.6 CVSS, Chromium rated this Low severity, EPSS is 0.16%, and there is no public exploit identified at time of analysis.
Out-of-bounds memory access in Google Chrome's Frame component affects all Desktop builds prior to 151.0.7922.72, letting a remote attacker read memory outside intended bounds when a victim opens a crafted HTML page. Chromium rated the underlying flaw Low severity, yet NVD scores it 8.8 (High) and tags flag potential RCE; there is no public exploit identified at time of analysis and EPSS is a low 0.18% (8th percentile). A vendor patch is available and the issue is not listed in CISA KEV.
Sandbox escape in Google Chrome for Android before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the sandbox via crafted HTML delivered through the Picture-in-Picture feature. Chromium rates the severity Low and CISA SSVC exploitation is 'none', making this a second-stage bug in an exploit chain rather than a standalone entry point. No public exploit identified at time of analysis, and EPSS is low at 0.17% (7th percentile).
Sandbox escape in Google Chrome desktop before 151.0.7922.72 stems from insufficient validation of untrusted input in a WebUI component, letting a remote attacker on the same network segment potentially break out of the renderer sandbox via malicious network traffic. Google rates the Chromium severity as Medium and vendor-tagged intelligence flags it as 'Potential RCE'; a vendor patch is available, but no public exploit identified at time of analysis and EPSS is low (0.17%, 6th percentile). CISA SSVC records no observed exploitation and only partial technical impact.
Heap corruption in Google Chrome's WebRTC component (versions prior to 151.0.7922.72) allows a remote attacker to exploit a use-after-free by luring a victim to a crafted HTML page, potentially leading to arbitrary code execution in the renderer process. The flaw is a CWE-416 object-lifecycle error rated CVSS 8.8 with user interaction required. There is no public exploit identified at time of analysis, and EPSS is low at 0.18% (8th percentile), indicating no observed weaponization despite the high CVSS.
Out-of-bounds memory read in Chrome's WebXR component allows remote attackers to disclose sensitive renderer process memory or crash the browser tab by luring a victim to a crafted HTML page. All Google Chrome releases prior to 151.0.7922.72 are affected across all platforms, with the vendor confirming a patch in the stable channel update. No public exploit identified at time of analysis, and an EPSS of 0.18% (8th percentile) indicates low near-term exploitation probability despite the high CVSS base score of 8.1.
Sandbox escape in Google Chrome's Dawn (WebGPU) component affects all desktop Chrome builds prior to 151.0.7922.72, where insufficient validation of untrusted input lets a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Chromium rates the severity Medium and the issue carries a CVSS 7.1 with scope change, but there is no public exploit identified at time of analysis and EPSS is very low at 0.18% (8th percentile). Google has shipped a patched Stable channel release addressing it.
Sandbox escape in Google Chrome for macOS before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the browser sandbox using a crafted HTML page, escalating a contained renderer foothold toward the host. The flaw sits in Chrome's Crypto component and is a second-stage bug that must be chained with an initial renderer compromise. There is no public exploit identified at time of analysis, EPSS is low (0.18%, 8th percentile), and Google rates the Chromium security severity as Medium despite the high CVSS.
Sandbox escape in Google Chrome on macOS before 151.0.7922.72 lets a remote attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page, escalating a contained renderer exploit into broader access on the host. The flaw stems from an inappropriate implementation in Chrome's Network component and is fixed in the stable channel update. There is no public exploit identified at time of analysis, EPSS is low (0.18%, 8th percentile), and Chromium rated the underlying severity Medium despite the NVD-style CVSS 9.6.
Sandbox escape in Google Chrome for macOS (versions before 151.0.7922.72) can be achieved by an attacker who has already compromised the renderer process, chaining a DevTools race condition via a crafted HTML page to break out of the renderer sandbox. Reported internally by the Chrome team and rated Medium by Chromium, it carries an NVD CVSS of 9.6 due to the scope change, though EPSS is very low (0.14%, 4th percentile). No public exploit identified at time of analysis and it is not on CISA KEV, indicating no confirmed active exploitation.
Sandbox escape in Google Chrome's ANGLE graphics layer (versions prior to 151.0.7922.72) allows a remote attacker who lures a victim to a crafted HTML page to potentially break out of the renderer sandbox, undermining the browser's core containment boundary. The flaw stems from insufficient validation of untrusted input (CWE-20) in ANGLE, Chrome's WebGL/OpenGL-to-native translation layer. It was reported internally by the Chrome team; there is no public exploit identified at time of analysis, and the EPSS score is low at 0.18% (8th percentile).
Sandbox escape in Google Chrome's DevTools (versions prior to 151.0.7922.72) lets an attacker who has already compromised the renderer process break out of the sandbox and gain broader host access via a crafted HTML page. It stems from insufficient validation of untrusted input (CWE-20) and requires user interaction plus a pre-existing renderer foothold, so it functions as a second-stage exploit rather than a standalone entry point. There is no public exploit identified at time of analysis, and EPSS is low (0.17%), consistent with Chromium's internal 'Medium' severity rating despite the high NVD CVSS score.
Sandbox escape in Google Chrome desktop versions prior to 151.0.7922.72 lets a remote attacker who has already compromised the renderer process break out of the sandbox via a crafted HTML page, chaining into the higher-privileged browser process. The flaw stems from insufficient validation of untrusted input in the Passwords component (CWE-20) and is rated Medium by Chromium despite an NVD CVSS of 9.6. There is no public exploit identified at time of analysis, and EPSS is low at 0.17% (7th percentile).
Sandbox escape in Google Chrome's "Save to Drive" feature (prior to 151.0.7922.72) lets a remote attacker who has already compromised the renderer process break out of the browser sandbox by supplying a crafted PDF file. The flaw stems from insufficient validation of untrusted input (CWE-20) and, while scored CVSS 9.6, is rated only Medium by Chromium because it is a second-stage bug requiring a prior renderer compromise. There is no public exploit identified at time of analysis and EPSS is low (0.19%, 9th percentile), consistent with a chained, non-trivial exploitation path rather than mass exploitation.
Sandbox escape in Google Chrome's ANGLE graphics layer allows a remote attacker to corrupt memory via a crafted HTML page in versions prior to 151.0.7922.72. The flaw is an out-of-bounds read and write (CWE-125) that a victim triggers simply by visiting a malicious page, potentially letting attacker-controlled code break out of the renderer sandbox. Google has released a fixed stable channel build; there is no public exploit identified at time of analysis and EPSS risk is currently low (0.21%).
Heap corruption in Google Chrome's Variations component before 151.0.7922.72 lets an attacker holding a privileged network position (an on-path / man-in-the-middle attacker) corrupt memory by delivering malicious network traffic, stemming from CWE-20 insufficient input validation. Google rates the Chromium severity as Medium and has shipped a fixed Stable-channel build; there is no public exploit identified at time of analysis and the flaw is not in CISA KEV. Because Variations (Chrome's server-driven feature-flag/experiment system) is fetched at startup in the browser process, a successful attacker could turn intercepted config traffic into a memory-safety primitive.
Sandbox escape in Google Chrome desktop prior to 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the browser sandbox via insufficient input validation in the WebSockets implementation, triggered by a crafted HTML page. This is a second-stage exploitation primitive rather than an initial-access bug: it requires a pre-existing renderer compromise plus user navigation to attacker content. No public exploit identified at time of analysis; EPSS is low at 0.21% (11th percentile) and it is not on CISA KEV, though Google has shipped a fixed Stable channel build.
Sandbox escape in Google Chrome desktop prior to 151.0.7922.72 allows an attacker who tricks a user into installing a malicious extension to break out of the renderer/extension sandbox via a crafted extension exploiting insufficient input validation. The flaw was reported internally by the Chrome team and carries an NVD CVSS of 9.6, though Chromium rates the security severity only Medium and SSVC shows no known exploitation; no public exploit identified at time of analysis. A vendor patch is available, and exploitation hinges on the significant precondition of the victim installing an attacker-controlled extension.
Sandbox escape in Google Chrome's Android WebView (versions prior to 151.0.7922.72) allows a remote attacker to break out of the renderer sandbox when a victim views a crafted HTML page. Rated Medium by Chromium and CVSS 7.1, it carries a scope-changing impact but requires user interaction; there is no public exploit identified at time of analysis and EPSS is low (0.21%, 11th percentile), indicating limited near-term mass exploitation likelihood.
Sandbox escape in Google Chrome's Payments component before 151.0.7922.72 lets a remote attacker who has already compromised the renderer process break out of the sandbox by serving a crafted HTML page, driven by insufficient validation of untrusted input (CWE-20). Google rates the Chromium security severity as Medium, but the assigned CVSS is 9.6 due to the scope-changing sandbox escape. There is no public exploit identified at time of analysis, no CISA KEV listing, and EPSS is low at 0.21%.
BFCache in Google Chrome prior to 151.0.7922.72 contains insufficient input validation that enables a renderer-compromised attacker to escape Chrome's sandbox and execute code in the higher-privileged browser process via a crafted HTML page. The Scope:Changed metric in the CVSS vector (8.7) confirms the escape crosses the renderer-to-browser process boundary, yielding high confidentiality and integrity impact. No public exploit or active exploitation has been identified; EPSS sits at 0.21% (11th percentile) and SSVC rates exploitation as none and not automatable, consistent with the chained, technically demanding nature of this attack.
Sandbox escape in Google Chrome's Android WebView allows a remote attacker who has already compromised the renderer process to break out of the sandbox via a crafted HTML page in versions prior to 151.0.7922.72. Rooted in a use-after-free (object lifecycle) flaw rated High by Chromium, this is a second-stage privilege-boundary bypass rather than a standalone entry point. No public exploit identified at time of analysis, and the EPSS score is low (0.21%, 11th percentile), consistent with a bug reported internally by the Chrome team and patched before evidence of exploitation.
Sandbox escape in Google Chrome for Android before 151.0.7922.72 lets an attacker who already controls a compromised renderer process break out of the sandbox through crafted input handled by the browser's Accessibility component. Rated High by Chromium and CVSS 9.6, it is a second-stage bug typically chained after an initial renderer exploit, giving an attacker a path to full compromise of the browser/host context. There is no public exploit identified at time of analysis, EPSS risk is low (0.29%, 21st percentile), and it is not on CISA KEV.
Sandbox escape in Google Chrome on macOS prior to 151.0.7922.72 lets a remote attacker who has already compromised the renderer process break out of the browser sandbox by exploiting a race condition in the Downloads component through a crafted HTML page. Rated High by Chromium and carrying a CVSS 9.6 due to the scope-changing total impact, it is patched in the July 2026 Stable channel update. There is no public exploit identified at time of analysis, EPSS is low at 0.23%, and CISA SSVC records exploitation as 'none'.
Sandbox escape in Google Chrome for macOS prior to 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the sandbox and reach the more-privileged browser process by loading a crafted HTML page that abuses Chrome's MHTML handling. It is rated High by Chromium and carries a CVSS 9.6 (scope-changed) score, but exploitation is a second-stage step that presupposes prior renderer compromise. There is no public exploit identified at time of analysis, and EPSS is low at 0.29% (21st percentile).
Sandbox escape in Google Chrome on macOS prior to 151.0.7922.72 lets a remote attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page that triggers a race condition in the Downloads component. Chromium rates it High severity and the CVSS is 9.6 (scope-changed). This is no public exploit identified at time of analysis; EPSS is low at 0.23% (14th percentile) and CISA SSVC records exploitation status as none.
Sandbox escape in Google Chrome's ANGLE graphics layer on macOS (versions prior to 151.0.7922.72) lets an attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page. Rated High by Chromium and carrying a CVSS 9.6 due to the scope change from renderer to host, it enables full compromise of the browser process. There is no public exploit identified at time of analysis and it is not on CISA KEV; EPSS is low at 0.29% (21st percentile).
Cross-origin data disclosure in Google Chrome for Android before 151.0.7922.72 lets a remote attacker leak data from other origins by luring a victim to a crafted HTML page that abuses insufficient input validation in the browser UI. Rated High by Chromium and CVSS 7.5 (confidentiality-only). There is no public exploit identified at time of analysis, and EPSS is low at 0.18%, though SSVC flags the attack as automatable with partial technical impact.
Sandbox escape in Google Chrome's ANGLE graphics layer prior to version 151.0.7922.72 lets a remote attacker who lures a victim to a crafted HTML page trigger a type confusion (CWE-843) and potentially break out of the renderer sandbox. Google rates the Chromium severity High, and the CVSS 9.6 reflects a scope-changing bug requiring only that the victim open a page. There is no public exploit identified at time of analysis, EPSS is low at 0.31% (24th percentile), and CISA's SSVC marks exploitation as none.
Sandbox escape in Google Chrome on macOS (versions prior to 151.0.7922.72) stems from an inappropriate implementation in ANGLE, Chrome's graphics abstraction layer, allowing a remote attacker to break out of the renderer sandbox via a crafted HTML page after the victim loads it. Rated High by Chromium and carrying a CVSS 9.6 (scope-changed), it enables an attacker to escalate from web content into higher-privilege execution on the host. No public exploit identified at time of analysis, and EPSS exploitation probability is low (0.29%, 21st percentile).
Sandbox escape in Google Chrome's ANGLE graphics layer (versions prior to 151.0.7922.72) lets a remote attacker who has already compromised the renderer process break out of the browser sandbox using a crafted HTML page. Rated High by Chromium and CVSS 9.6, the flaw is a CWE-843 type confusion; Google has shipped a fixed Stable channel build. There is no public exploit identified and no CISA KEV listing, and EPSS is low at 0.31% (24th percentile), indicating no evidence of active exploitation at time of analysis.
Sandbox escape in Google Chrome for iOS before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the sandbox via a crafted HTML page, escalating a contained renderer foothold into broader control (CVSS 9.6, scope-changed). Reported internally by the Chrome team under CWE-20 insufficient input validation; no public exploit identified at time of analysis, and EPSS is low at 0.29% (21st percentile), consistent with a chained bug that is not yet weaponized. Vendor-released patch is available in stable channel 151.0.7922.72.
Sandbox escape in Google Chrome for Android before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the browser sandbox by feeding crafted untrusted input to the Web Authentication (WebAuthn) component. Rated High severity by Chromium and scored CVSS 9.6, it is a second-stage bug chained after an initial renderer exploit rather than a standalone remote compromise. No public exploit identified at time of analysis, and EPSS exploitation probability is low at 0.34% (27th percentile).
Out-of-bounds read in Chrome's ANGLE graphics abstraction layer (versions prior to 151.0.7922.72) can be leveraged by an attacker who has already compromised the renderer process to potentially escape the browser sandbox via a crafted HTML page. Google rates the Chromium severity High and has shipped a fixed Stable-channel build; no public exploit identified at time of analysis, and the EPSS score is low (0.29%, 21st percentile), consistent with a second-stage bug rather than a standalone drive-by. Because it requires a pre-compromised renderer, it is typically one link in an exploit chain rather than a single-shot RCE.
Sandbox escape in Google Chrome for Android (versions prior to 151.0.7922.72) stems from an inappropriate implementation in ANGLE, Chrome's graphics abstraction layer, allowing a remote attacker to break out of the renderer sandbox using a crafted HTML page. Rated High severity by Chromium with a CVSS of 8.8, the flaw requires the victim to visit a malicious page (user interaction) but no authentication. There is no public exploit identified at time of analysis, and the EPSS score is low (0.29%, 21st percentile), consistent with a recently disclosed browser bug fixed before weaponization.
Sandbox escape in Google Chrome's ANGLE graphics layer on Android (versions prior to 151.0.7922.72) allows a remote attacker who has already compromised the renderer process to break out of the renderer sandbox and gain broader access on the device via a crafted HTML page. Rated High by Chromium and scored CVSS 9.6 largely because of the scope change from a successful escape. There is no public exploit identified at time of analysis, and EPSS is low (0.29%, 21st percentile), consistent with a bug that only becomes useful after a prior renderer compromise.
Sandbox escape in Google Chrome's Chromecast component (versions prior to 151.0.7922.72) allows a remote attacker who has already compromised the renderer process to break out of the sandbox via a crafted HTML page. Rated High by Chromium and scored CVSS 9.6 due to scope change, it is a classic second-stage browser exploit chained after an initial renderer bug. No public exploit is identified at time of analysis and EPSS is low (0.29%), consistent with a bug requiring a prior renderer foothold rather than a single-shot drive-by.
Sandbox escape in Google Chrome's ANGLE graphics component (versions prior to 151.0.7922.72) allows a remote attacker who has already compromised the renderer process to break out of the browser sandbox via a crafted HTML page. Rated High by Chromium with a CVSS 9.6 due to scope change and full CIA impact, though it requires a pre-existing renderer compromise as a chained prerequisite. There is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.29%).
Sandbox escape in Google Chrome for iOS before version 151.0.7922.72 allows a remote attacker to break out of the browser's security boundary when a victim opens a crafted HTML page. Rated High by Chromium and carrying a 9.6 CVSS due to a scope-changing, high-impact outcome requiring only user interaction, though there is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.29%, 21st percentile). A vendor-released patch is available and CISA SSVC currently records exploitation status as none.
Sandbox escape in Google Chrome for Android before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the browser sandbox through crafted input to the GPU component. This is a second-stage vulnerability (CWE-20, improper input validation) that Google rates High severity and CVSS 8.3 with a scope change; it is chained after an initial renderer bug rather than exploited alone. No public exploit has been identified at time of analysis, EPSS is low (0.29%, 21st percentile), and CISA SSVC records exploitation as none, though technical impact is rated total.
Sandbox escape in Google Chrome's Network component before 151.0.7922.72 allows a remote attacker who has already compromised the renderer process to break out of the sandbox and gain broader access on the host via a crafted HTML page. Rated High by Chromium and scored CVSS 8.3, it is a second-stage bug that must be chained with an initial renderer exploit rather than exploited in isolation. There is no public exploit identified at time of analysis, and the EPSS probability is low at 0.29% (21st percentile).
Sandbox escape in Google Chrome's ANGLE graphics layer, fixed in stable release 151.0.7922.72, lets a remote attacker who lures a victim to a crafted HTML page break out of the renderer sandbox and gain broader access on the host. Rated Critical by Chromium and scored CVSS 9.6, the flaw stems from insufficient validation of untrusted input (CWE-20) processed by ANGLE and carries a scope-changing impact. There is no public exploit identified at time of analysis and EPSS is low at 0.31% (23rd percentile), but the Critical rating and sandbox-escape primitive make prompt patching important.