Duplicate order processing in @payloadcms/plugin-ecommerce allows remote, unauthenticated attackers to have a single Stripe order confirmation processed more than once, producing duplicate orders and repeated cart, inventory, and transaction side effects in affected Payload CMS deployments. The flaw affects @payloadcms/plugin-ecommerce versions before 3.90.0 and 4.x canary builds before 4.0.0-canary.34, and only installations that configure the Stripe payment adapter are exposed - deployments that do not use the Stripe payment flow are explicitly unaffected. No public exploit code has been identified at time of analysis, and the vendor has shipped patched releases plus guidance requiring order finalization to be idempotent.
Malformed multipart request bodies sent to Payload CMS versions 3.0.0 through 3.89.x and 4.0.0-canary.0 through 4.0.0-canary.33 trigger a ReDoS-style catastrophic backtracking path in multipart Content-Type validation, causing the parser to consume CPU/resources for an extremely long time and effectively hanging the affected endpoint. The flaw is reachable by remote attackers without authentication (CVSS 4.0 vector PR:N/UI:N, AV:N, VA:H), but exposure is limited to deployments that parse multipart bodies - i.e., upload-enabled collections or any route invoking Payload's Busboy-based request processing - and instances that place those endpoints behind access controls or that lack upload collections substantially reduce their attack surface. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; vendor-released patches are available in 3.90.0 and 4.0.0-canary.34.
Stack-based buffer overflow in the Tenda AC5 router's web management interface allows an authenticated remote attacker to corrupt memory and potentially execute code by submitting an oversized wifiPwd argument to /goform/setWifi on firmware 02.03.01.111_multi. Exploitation requires network reachability to the device's HTTP management interface plus a valid low-privilege administrative session (CVSS vector PR:L), meaning fully unauthenticated attackers cannot trigger it against a hardened default configuration unless the management port is openly exposed. Publicly available exploit code exists (a detailed write-up has been published on GitHub), and the vulnerability carries a CVSS 4.0 base score of 8.6 with high confidentiality, integrity and availability impact; there is no CISA KEV listing indicating confirmed active exploitation, and no vendor patch has been identified from the available references.
Ghostscript can execute arbitrary shell commands with the privileges of its process when it renders a crafted PostScript or EPS document, chaining memory corruption in document parsing with a runtime bypass of the -dSAFER sandbox. The flaw affects Ghostscript as shipped in Red Hat Enterprise Linux 6, 7, 8, 9, and 10, and the assessed vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, meaning no privileges are required but a victim or automated pipeline must render the malicious file, with the malicious document first reaching the processing system. Publicly available exploit code exists, including a GitHub proof-of-concept, but the provided data does not confirm CISA KEV active exploitation, so -dSAFER should not be treated as a protective mitigation for affected versions.
API key disclosure in Payload CMS lets an authenticated user with ordinary read access to other users' authentication documents retrieve those users' active API keys and then act with the victim accounts' full permissions until the keys are rotated or disabled. Affected deployments are the npm `payload` package from 3.0.0 before 3.90.0 and canary releases from 4.0.0-canary.0 before 4.0.0-canary.34, but only where an authentication collection has `useAPIKey` enabled and users can read authentication documents they do not own - configurations restricted to self-read, or with `useAPIKey` disabled, are not exploitable. The CVSS 4.0 score is 7.7 (AV:N/AC:L/AT:P/PR:L) and our independent review assesses it as a credible upper-medium priority issue for environments that actually use the feature rather than an internet-wide emergency; no CISA KEV entry or public exploit code was identified at time of analysis.
Authenticated users who can update an auth collection document in Payload CMS can change the password field on that document even when the collection explicitly defines a field-level access.update restriction intended to deny it, allowing account takeover of the affected user. The flaw affects the npm `payload` package before 3.90.0 and canary releases from 4.0.0-canary.0 through 4.0.0-canary.34, and exploitation is conditional: the deployment must have configured a field-level password update restriction, local auth must be active, and the write must not be a draft save. It is a genuine but conditional integrity flaw rather than an internet-scale emergency - the attacker must already hold valid credentials with document update rights on the target collection, so there is no unauthenticated path; no public exploit code was identified at time of analysis and the issue is not in CISA KEV.
Silent argument dropping in Coraza WAF v3 (>= 3.0.0, < 3.8.1) lets unauthenticated remote attackers evade every SecRule that inspects ARGS, ARGS_GET, ARGS_NAMES, ARGS_GET_NAMES or ARGS_PATH - including the OWASP CRS SQLi, XSS, RCE and LFI families - by padding a request past SecArgumentsLimit (default 1000) so the malicious parameter is discarded before phase 2 evaluation; roughly 10,000 GET parameters yields about a 94% per-request bypass, and the failure is completely silent (no audit-log entry, no transaction flag). The same advisory covers unbounded ARGS_POST growth because Coraza's urlencoded and JSON body processors ignored the argument cap entirely, which is also a per-request memory-exhaustion DoS surface. No public exploit identified at time of analysis and no confirmed active exploitation; vendor-released patch: 3.8.1 (the 3.8.0 fix was incomplete and 3.8.0 remains listed as affected), and the advisory/report is credited to the corazawaf project with AI-assisted analysis disclosed. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:L (7.2 High), a CWE-693 protection-mechanism failure whose impact lands on the protected application rather than Coraza itself.
Authenticated users with query access to a Payload CMS collection can infer hidden or read-restricted field values - including password-reset tokens - by abusing polymorphic join 'where' filters that were not validated against unknown field paths. The flaw affects the npm package 'payload' in the ranges >=3.0.0 <3.90.0 and >=4.0.0-canary.0 <4.0.0-canary.34, requires a valid account holding query access (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), and is a moderate-priority confidentiality-only issue (CWE-200); there is no public exploit identified at time of analysis, and vendor patches exist in 3.90.0 and 4.0.0-canary.34.
Command injection in the client software component of HPE Aruba ClearPass Policy Manager allows an attacker to execute arbitrary commands with elevated privileges on an affected host, provided they can get crafted input into the client's processing path. The flaw is rated 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H): it is network-reachable, low complexity, and requires no authentication, but exploitation depends on a user or operator of the client interacting with attacker-supplied input (UI:R), which is the principal limiting factor - the appliance/server is not compromised by an unsolicited remote request alone. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; no EPSS score was provided in the source data, so exploitation likelihood should be judged primarily on the user-interaction prerequisite and the elevated-privilege impact if triggered.
Prototype pollution in the npm package @stablelib/cbor (versions before 2.0.4) allows an attacker who supplies a CBOR payload to make decoder output inherit attacker-chosen properties, because a map key named "__proto__" is written via bracket assignment and reaches the JavaScript prototype setter instead of creating a normal data property. Applications that pass untrusted CBOR to decode() and then read properties through normal prototype lookup, or merge the decoded object into configuration, authorization or feature-flag state, can act on inherited attacker values - the upstream GHSA includes a working proof-of-concept, so publicly available exploit code exists, but there is no KEV listing and no confirmed active exploitation. Impact is conditional and integrity-only (no confidentiality or availability loss), and the independently assessed CVSS 3.1 vector AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N rates it below the vendor-supplied 8.9 CVSS 4.0 score because exploitation depends on that specific downstream consumption pattern.
Code injection in Microsoft Kiota 0.5.0 through pre-1.35.0 allows attacker-controlled text embedded in an OpenAPI description to break out of the generated Java or PHP documentation comment and execute in the consuming application or build environment once that generated source is compiled and loaded (Java) or loaded (PHP). The flaw is reachable unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:R) but requires user interaction: a developer or CI pipeline must generate client code from an untrusted or tampered spec and then build or load the output, making this a build-time/supply-chain path rather than an attack on already-deployed runtime services. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV; CVSS 3.1 base score is 8.8, and the issue is fixed in 1.35.0.
Command injection in the ClearPass Policy Manager API allows an authenticated remote attacker holding only low-privilege credentials to execute arbitrary commands and escalate to administrative control of the affected appliance, with high impact to confidentiality, integrity, and availability (CVSS 8.8). The vulnerability is network-reachable and requires no user interaction, but it is not exploitable by a fully unauthenticated attacker - valid low-privilege API access is a hard precondition. At time of analysis there is no public exploit identified, and no evidence of active exploitation (no CISA KEV listing); the risk is rated high-priority for organizations running the product but not an emergency absent exploitation signals.
Authenticated path traversal in the ClearPass Policy Manager command line interface allows a low-privileged remote user to escape the intended file path context and execute arbitrary code with elevated privileges on the underlying operating system. The flaw is rated CVSS 3.1 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning it is network-reachable, low complexity, requires only valid low-privilege CLI credentials and no user interaction, and yields full confidentiality, integrity, and availability impact. Exploitation prerequisites are non-trivial: the attacker must already hold valid authenticated access to the ClearPass CLI, so exposure is bounded by how broadly low-privilege appliance accounts are provisioned and by how tightly management-plane access is restricted; no public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV).
Remote code execution in the ACPT (Premium) WordPress plugin affects all versions up to and including 2.0.66, allowing an authenticated attacker with only subscriber-level access to run arbitrary code on the server. The chain works by abusing a REST API form-creation endpoint that performs no capability check, planting a malicious email_settings payload, and then triggering a form submission so the plugin's unsandboxed Twig environment renders attacker-controlled template expressions during email generation. No user interaction is required and no public exploit code has been identified at time of analysis, though the low authentication bar (subscriber) makes it considerably more dangerous on sites with open registration; exploitation is not confirmed actively exploited (no CISA KEV listing), and the vendor changelog points to a fixed release.
Authenticated remote code execution affects IBM Langflow OSS versions 1.0.0 through 1.12.2, where an incomplete blocklist in the built-in code security scanner can be bypassed to execute arbitrary code on the server. Exploitation requires a valid low-privilege account (CVSS PR:L) and the ability to submit code evaluated by the scanner; unauthenticated attackers are not sufficient. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, though the high CVSS base score of 8.8 and the multi-tenant exposure of typical Langflow deployments make the risk significant where untrusted users can register or be provisioned.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets an authenticated attacker escape the application's code execution sandbox and run arbitrary commands on the host. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) confirms network reachability and a low-privileged authenticated session as the only precondition, with no user interaction required. No public exploit code has been identified at time of analysis and there is no CISA KEV entry, but the low complexity and high impact make this a genuine prioritization concern for internet-exposed or multi-tenant deployments.
Unauthenticated remote attackers can force-delete arbitrary objects in Mooncake Store master through 0.3.13.post1 by sending forged Remove, RemoveByRegex, RemoveAll, or BatchRemove RPCs to the coro_rpc port with the force flag set, bypassing lease checks. This CWE-306 missing-authentication flaw is availability-scoped (CVSS 3.1: C:N/I:L/A:H) and requires only network reachability to the coro_rpc port, enabling cache loss and request failures. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
Google Chrome versions prior to 155.0.8059.39 contain a use-after-free in the WebRTC component that a remote, unauthenticated attacker can trigger by convincing a victim to visit a crafted HTML page, resulting in arbitrary code execution within the renderer sandbox (CVSS 3.1 base 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploitation is not automatable and requires user interaction, and the resulting code execution is confined to Chrome's renderer sandbox per the vendor description, so full host compromise would additionally require chaining a separate sandbox-escape flaw. No public exploit code has been identified at time of analysis, and CISA's SSVC assessment records no known exploitation; Chrome's built-in auto-update is the primary exposure-reduction control, as patched versions 155.0.8059.39 and later are not vulnerable.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.12.2 allows an authenticated attacker to run arbitrary operating-system commands by supplying crafted input to a component that fails to neutralize special elements before passing them to an OS command or code-evaluation path (CWE-94). Per the assessed CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), exploitation requires a valid low-privilege authenticated session on the Langflow instance, needs no victim interaction, and yields full confidentiality, integrity, and availability impact on the affected host. No public exploit code was identified at time of analysis, and the issue is not confirmed as actively exploited (CISA KEV); the practical risk is concentrated on network-exposed Langflow servers that use weak, shared, or default credentials, since a compromised or low-privilege account is the only prerequisite.
Broken authentication in the Simple JWT Login WordPress plugin 4.0.0 allows a remote authenticated attacker with subscriber-level privileges to bypass intended JWT authentication controls, resulting in high confidentiality, integrity, and availability impact (CVSS 8.8, CWE-288). The vulnerability is network-exploitable, requires low complexity, and needs no user interaction, but an attacker must first obtain a low-privileged account-often self-registerable when open registration is enabled. No public exploit code or confirmed active exploitation has been identified at time of analysis.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets any user who can log in to the instance run arbitrary code on the host, because the platform fails to properly constrain attacker-supplied input before it reaches a code-execution path. The flaw carries a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning low-complexity, network-reachable exploitation that requires only a low-privileged account but yields full confidentiality, integrity, and availability impact - no user interaction and no elevated privileges are needed. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation, but IBM has published a vendor advisory with a fix, so the practical exposure is greatest for organizations that expose Langflow to untrusted networks or provision accounts broadly.
Type confusion in the V8 JavaScript engine of Google Chrome prior to 155.0.8059.39 lets a remote, unauthenticated attacker execute arbitrary code inside the browser's renderer sandbox when a victim loads a crafted HTML page; the CVSS vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, so the sole prerequisite is that the victim renders attacker-controlled content in an unpatched desktop build. No public exploit code or active exploitation was identified at time of analysis, and CISA KEV does not list this CVE. The vendor-released patch is Chrome 155.0.8059.39, and installations already updated past that version are not affected. Because the impact is scoped to the sandbox (S:U) per the description, full host compromise would require chaining a separate sandbox-escape vulnerability.
Authorization bypass in Kibana's Fleet package installation process lets an authenticated user who holds delegated Fleet package-management privileges - but no direct Elasticsearch administrative rights - claim a data stream identifier already in use by another tenant sharing the same deployment. Because Fleet does not verify ownership of that identifier before applying the uploaded package's generated index and ingest-pipeline settings to pre-existing infrastructure, an attacker can redirect a victim tenant's subsequent data through infrastructure they control, achieving unauthorized disclosure and modification of that data and preventing it from reaching its intended destination (CVSS 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation requires a multi-tenant Kibana deployment with delegated Fleet privileges and valid authenticated access; it is impossible in single-tenant setups, and no public exploit identified at time of analysis.
Arbitrary code execution inside the renderer sandbox is achievable in Google Chrome builds prior to 155.0.8059.39, where a use-after-free in the browser's Media component can be triggered when a victim loads a crafted HTML page. Scoring 8.8 under CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, the bug requires no authentication but does require the user to visit attacker-controlled content, and because the resulting code execution is confined to the renderer sandbox, full host compromise would require chaining a separate sandbox-escape flaw. A vendor patch is available in the Chrome Stable channel update, and no public exploit has been identified at time of analysis - this is a high-priority patching item rather than an emergency.
Remote code execution inside the Chrome renderer sandbox is possible on Chrome builds prior to 155.0.8059.39, where a use-after-free in the WebRTC component can be triggered by a crafted HTML page. The flaw is rated 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and assigned Chromium severity High; no authentication or prior privileges are required, but the victim must open or be redirected to the attacker's page (UI:R). Impact is confined to the renderer sandbox - reaching the host OS would require chaining a separate sandbox-escape vulnerability - and no public exploit was identified at time of analysis; the primary exposure window is the short period before Chrome's auto-update moves users to the fixed build.
Use-after-free in Google Chrome's Web Audio implementation affects versions prior to 155.0.8059.39, where a remote attacker can achieve arbitrary code execution inside the browser's renderer sandbox by getting a victim to open a crafted HTML page that exercises the Web Audio API. The flaw carries an assessed CVSS of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), meaning no authentication or non-default configuration is required, but the attack does depend on user interaction (loading the page) and the resulting code execution is confined to the renderer sandbox, so full host compromise would require chaining a separate sandbox escape. Chromium rates the issue High severity, the vendor has published a fix in 155.0.8059.39, and no public exploit code has been identified at time of analysis; there is no CISA KEV confirmation of active exploitation.
Broken access control in the Progress Planner WordPress plugin through version 1.10.0 allows any authenticated user holding the low-privileged Subscriber role (or higher) to reach plugin functionality they are not authorized to invoke, yielding high impact to confidentiality, integrity, and availability at a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is network-reachable, requires no user interaction and no elevated privileges beyond a valid low-privilege session, and is classified as CWE-862 (Missing Authorization); risk is greatest on sites that permit open or self-service registration and materially lower where account creation is locked down. No public exploit code has been identified at time of analysis, and there is no indication of confirmed active exploitation in CISA KEV; the report originates from Patchstack. Authentication requirements are confirmed from the assessed vector, which carries PR:L, so exploitation is authenticated but does not require administrative access.
Subscriber-level privilege escalation in the JobZilla - Job Board WordPress theme through version 2.2 allows an authenticated low-privilege user to elevate their permissions, with high impact to confidentiality, integrity, and availability (CVSS 8.8). The attack is network-reachable, low-complexity, and requires no user interaction; because the CVSS vector includes PR:L, the attacker must be authenticated, and in typical job-board deployments with open self-registration obtaining a Subscriber account is trivial, while sites with registration disabled still require a valid low-privilege credential first. No public exploit identified at time of analysis, so this is an actionable priority for affected sites but not an unauthenticated emergency.
Use-after-free in Google Chrome's Track component before 155.0.8059.39 allows an unauthenticated remote attacker to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page. The CVSS 3.1 base score is 8.8 (High) with UI:R, meaning exploitation requires user interaction but no authentication; successful code execution remains confined to Chrome's renderer sandbox and would require a separate sandbox-escape bug to affect the host OS. No public exploit identified at time of analysis, and SSVC records Exploitation: none; CISA KEV does not list this CVE.
Use-after-free in Google Chrome's parser allows remote attackers to execute arbitrary code within the browser's renderer sandbox by convincing a victim to visit a crafted HTML page. All Chrome builds prior to 155.0.8059.39 are affected, and exploitation requires user interaction (UI:R) but no authentication (PR:N). The flaw carries a High Chromium severity rating (CVSS 8.8) and no public exploit has been identified at time of analysis; however, standalone impact is constrained because the description specifies code execution 'inside the sandbox,' meaning a second vulnerability would be needed to escape to the host.
Type confusion in the V8 JavaScript engine of Google Chrome before 155.0.8059.39 allows a remote attacker to execute arbitrary code inside the renderer sandbox when a victim renders a crafted HTML page, requiring user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8). Signals conflict and must be weighed carefully: the numeric severity is high, yet Google's own Chromium security severity for this issue is 'Low' and CISA's SSVC assessment records no exploitation and a non-automatable attack path, with no public exploit identified at time of analysis. A vendor-released patch exists in Chrome 155.0.8059.39, so fully updated installations are not exposed.
Type confusion in V8, Chrome's default JavaScript and WebAssembly engine, enables a remote attacker to run arbitrary code inside the browser's renderer sandbox in Google Chrome releases below 155.0.8059.39. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) confirms the attack is network-reachable and requires no authentication, though it does require the victim to open attacker-controlled web content, so a phishing, malvertising, or watering-hole lure is a prerequisite. No public exploit code has been identified at time of analysis and CISA's SSVC assessment records exploitation as 'none' and the issue as not automatable, so real-world priority currently sits below what the 8.8 base score alone implies; note that code execution is confined to the renderer sandbox, meaning full host compromise would require chaining a separate sandbox-escape flaw. Google has shipped a vendor patch.
Authenticated privilege escalation in the HPE Aruba Networking AOS-S management API allows a read-only account to escalate to full administrative access, giving the attacker complete control over confidentiality, integrity, and availability of the affected switch (CVSS 3.1 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is network-reachable and low-complexity, requiring no user interaction and no non-default configuration beyond the API being reachable, but it is gated by the prerequisite of a valid low-privilege credential (PR:L), so risk concentrates in environments where read-only accounts exist, are shared, or can be compromised; the vendor reports this as a privilege-escalation issue in the AOS-S API. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, yet the combination of a low-bar prerequisite and a total privilege gain makes this a credible, actionable priority rather than an inflated high-CVSS score.
Privilege escalation in the WordPress plugin WP User Profiles (versions 2.7.3 and earlier) allows an authenticated subscriber-level user to elevate to higher privileges, achieving full confidentiality, integrity and availability impact on the affected site. The flaw is network-exploitable with no user interaction and requires only a valid low-privilege account, which is trivially obtainable on any site that permits open user registration; sites that restrict account creation substantially raise the bar. At time of analysis there is no public exploit identified and the CVE is not listed in CISA KEV, but the 8.8 base score and the low prerequisite make prompt patching or plugin removal the priority.
Use-after-free in Google Chrome's Track component (versions prior to 155.0.8059.39) allows a remote attacker to achieve arbitrary code execution inside the renderer sandbox when a victim loads a crafted HTML page. The flaw carries a CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), meaning it is network-reachable, low-complexity, and requires no authentication, with mandatory user interaction - the victim must navigate to or be redirected to attacker-controlled content - as the only gating prerequisite. Google rates the issue Critical and shipped a fix in the 155.0.8059.39 stable-channel release; no public exploit code has been identified at time of analysis, and the escape from the browser sandbox would require a separate, independent vulnerability.
Incorrect authorization in Google Chrome's WebProtect component lets a remote, unauthenticated attacker who socially engineers a victim into opening a crafted HTML page read sensitive information held in the browser context - the assessed impact is confidentiality-only (C:H/I:N/A:N), with no integrity or availability loss. Every Chrome build prior to 155.0.8059.39 is affected across platforms, and Google rates the underlying issue as Chromium security severity Medium. Exploitation is not drive-by: the CVSS vector requires user interaction (UI:R) and PR:N, so no credentials or non-default configuration are needed but the victim must be lured to the attacker-controlled page, and no public exploit code has been identified at time of analysis, making the base score of 8.8 an overstatement of realistic risk.
Use-after-free in Google Chrome's built-in PDF handling (fixed in 155.0.8059.39) lets remote, unauthenticated attackers execute arbitrary code inside the Chrome renderer sandbox when a victim opens a crafted PDF file - exploitation is not automatic and depends entirely on the user interaction of opening the document (CVSS 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-416). Because the code execution is confined to the sandboxed renderer, turning this into full host compromise would require chaining a separate sandbox-escape bug; the advisory rates it Chromium severity High. At the time of analysis there is no public exploit identified and CISA SSVC records exploitation as none, though the vulnerability is fully described and a vendor patch plus the underlying Chromium issue tracker entry are publicly referenced. Google Chrome versions before 155.0.8059.39 are affected on all platforms tracked under cpe:2.3:a:google:chrome.
Information disclosure in Google Chrome for iOS Autofill allows an attacker who lures a victim to a crafted HTML page to obtain sensitive form data that the browser failed to properly clear. Only Chrome for iOS builds prior to 155.0.8059.39 are affected; vulnerable instances require the Autofill feature to have been used so that sensitive data is actually present for the incomplete cleanup to expose. Exploitation requires no authentication (PR:N) but is gated by mandatory user interaction and social engineering (UI:R), meaning it cannot be triggered silently; no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis. Note that the vendor-assigned CVSS of 8.8 overstates the impact relative to our independent assessment (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, base 6.5), which scores confidentiality impact only, with no integrity or availability effect.
Information disclosure in the HPE Networking ClearPass Policy Manager Android client application allows an unauthenticated remote attacker to invoke improperly access-controlled application functionality from an untrusted source, potentially exposing sensitive information held on or accessible to the victim's mobile device. Exploitation requires the ClearPass Android client to be installed plus mandatory victim interaction (UI:R) with attacker-supplied content - for example a malicious co-installed app, crafted intent, deep link, or content - so delivery likely relies on an Android inter-component path rather than direct internet-facing exposure, and no public exploit was identified at time of analysis. Note that the vendor-supplied CVSS 3.1 vector (8.8, C:H/I:H/A:H) overstates the issue relative to the described confidentiality-only impact; our independent assessment limits the score to AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N.
Incorrect authorization in Google Chrome's Autofill feature (versions prior to 155.0.8059.39) allows an unauthenticated remote attacker (PR:N) to obtain sensitive information via a crafted HTML page, but exploitation requires social engineering to trick the victim into visiting and interacting with the page (UI:R). The independent assessment limits the impact to confidentiality (C:L) with no integrity or availability effect, and exploitation further depends on the victim having relevant data stored in Autofill; no public exploit or active exploitation has been identified. A vendor patch is available.
Sensitive-information disclosure in Google Chrome for iOS before 155.0.8059.39 allows a remote, unauthenticated attacker to abuse a missing authorization check by socially engineering a victim into opening a crafted HTML page. The independent assessment limits the impact to confidentiality (C:H/I:N/A:N), so this should be treated as an information disclosure issue rather than code execution or data tampering, and exploitation requires user interaction on the iOS build only. Vendor patch 155.0.8059.39 is available, and no public exploit code or CISA KEV active exploitation was identified in the supplied intelligence.
Unauthenticated privilege escalation in the Salon Booking System WordPress plugin (versions 10.31.7 and earlier) allows remote attackers to elevate privileges by inducing a victim to trigger a crafted request, due to incorrect privilege assignment (CWE-266) in the plugin's role handling. The attack requires user interaction (UI:R) but no authentication (PR:N), and affects any WordPress site with the vulnerable plugin active. No public exploit code has been identified at time of analysis, and the issue is not confirmed as actively exploited, yet the high CVSS score (8.8) and potential for significant site compromise warrant prompt remediation.
Arbitrary code execution inside the Chrome renderer sandbox is possible in Google Chrome builds prior to 155.0.8059.39, where a race condition (CWE-367) in the V8 JavaScript engine can be won by a crafted HTML page. Exploitation requires only that the victim load the attacker's page in a vulnerable browser (UI:R, PR:N per the CVSS vector), with no credentials or prior privileges needed, but success additionally depends on hitting a time-of-check/time-of-use timing window, which our assessment captures by raising attack complexity to High (CVSS 3.1 base 8.1 under AC:H, versus the 8.8 score supplied with the CVE under AC:L). The critical caveat is scope: the code execution achieved stays within the renderer sandbox and does not by itself compromise the host operating system, so full system impact requires chaining a separate sandbox-escape vulnerability. No public exploit code has been identified at time of analysis, CISA SSVC records Exploitation: none (Automatable: no, Technical Impact: total), and a vendor-released patch exists in Chrome 155.0.8059.39.
Use-after-free in Chrome's font handling on Windows allows a remote attacker to execute arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page; the flaw affects Google Chrome versions prior to 155.0.8059.39. Exploitation requires user interaction (UI:R) - the victim must load attacker-controlled content - and there are no authentication prerequisites (PR:N), but the resulting code execution is confined to the Chrome sandbox, so host-level compromise would require a second, independent sandbox-escape bug. Consistent with the medium severity rating assigned by the Chromium team, CISA's SSVC assessment records no known exploitation and no automatable exploitation path, and no public exploit code has been identified at time of analysis.
A use-after-free memory-safety flaw in Google Chrome's Media component lets a remote, unauthenticated attacker execute arbitrary code inside the renderer sandbox when a user loads a crafted HTML page containing malicious media content. All Chrome builds prior to 155.0.8059.39 are affected, and exploitation requires the victim to visit or load the attacker-controlled page (UI:R), which is the main practical barrier; no credentials or special privileges are needed. There is no public exploit identified at time of analysis and the CISA SSVC assessment records no exploitation, but the vendor has shipped a fix in 155.0.8059.39, and the EPSS-style risk picture is dominated by Chrome's ubiquity and the high CVSS base score (8.8) rather than by observed attacks.
Use-after-free in Google Chrome's V8 JavaScript engine (all releases prior to 155.0.8059.39) lets unauthenticated remote attackers execute arbitrary code inside the renderer sandbox when a victim navigates to an attacker-controlled page containing crafted HTML/JavaScript. The bug carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and Chromium's own 'High' severity rating, and because the V8 engine is enabled by default in every standard installation, no special configuration or privileges are needed on the target side. Impact is bounded, however: per the vendor description code execution is confined to the sandbox, so a standalone exploit does not by itself compromise the host and a separate sandbox-escape would be required, and no public exploit identified at time of analysis (SSVC Exploitation: none, Automatable: no) - a genuine priority-worthy issue whose urgency is tempered by the required user interaction, sandbox confinement, and absence of observed exploitation.
Use-after-free in the Media component of Google Chrome prior to 155.0.8059.39 lets a remote attacker execute arbitrary code within the browser's renderer sandbox by luring a victim to open a crafted HTML page. The flaw carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), meaning no authentication or prior privileges are required, but successful exploitation depends on the user actively navigating to attacker-controlled content. There is no public exploit identified at time of analysis - CISA's SSVC assessment lists exploitation as 'none' - and code execution is contained within the renderer sandbox, so a separate sandbox-escape would be needed to reach the host OS; the vendor has released a patched build.
Arbitrary code execution confined to the renderer sandbox in Google Chrome builds prior to 155.0.8059.39, reachable when a user opens a crafted HTML page that drives the DevTools state-validation path into an inconsistent state. The flaw is network-delivered and requires no authentication (CVSS:3.1/AV:N/AC:L/PR:N), but exploitation is gated by mandatory user interaction (UI:R), which is why CISA's SSVC decision framework rates it as not automatable. No public exploit code and no confirmed active exploitation were identified at time of analysis; Google rates the Chromium severity as High and has shipped a fixed build, so the practical exposure is limited to unpatched clients that have not yet received the auto-update.
Stored cross-site scripting in the web-based management interface of Aruba/HPE ClearPass Policy Manager allows a remote attacker to plant script that is stored by the application and later executes in the browser of an administrative user who views the affected page. Consistent with our independent assessment (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N), the injection step requires no authentication, but the payload only fires after an authenticated administrator interacts with the affected view, yielding high confidentiality and integrity impact within that administrative session; the vendor/NVD vector rates it 8.8 under a slightly different scope/impact model. No public exploit code and no evidence of active exploitation were identified at time of analysis (CVE-2026-79799 is not in CISA KEV, and no EPSS score was supplied), so this is a credible, moderately high priority for organizations running ClearPass - particularly those that expose the management interface beyond an isolated management network or trusted admin VLAN.
Arbitrary code execution in AWS Bedrock AgentCore Starter Toolkit before 0.3.14 allows an authenticated same-account actor to inject malicious Python code into generated agent source by importing a crafted Bedrock Agent configuration, which executes when the victim runs or deploys the agent. Exploitation requires the victim to import and then run or deploy the agent, and the actor must have valid same-account credentials. No public exploit identified at time of analysis; remediation requires upgrading to 0.3.14 and re-importing any previously affected agents because the generated source persists.