UI misrepresentation in Google Chrome's FullScreen mode on Windows allows a remote attacker to spoof browser chrome and security-relevant UI elements by directing a victim to a crafted HTML page. Affected are all Chrome versions on Windows prior to 153.0.8010.36. This is a phishing-class attack vector: by hijacking the fullscreen rendering to simulate trusted UI (OS dialogs, address bar, lock icons, or other sites), an attacker can deceive users into performing unsafe actions or disclosing credentials. No public exploit has been identified and EPSS is 0.22%, reflecting low near-term exploitation probability.
UI element spoofing in Google Chrome's Geometry rendering component (versions prior to 153.0.8010.36) enables a remote attacker to misrepresent browser chrome and UI elements through a crafted HTML page, requiring the victim to visit the malicious page via social engineering. The vulnerability, classified under CWE-451 (User Interface Misrepresentation of Critical Information), allows an attacker to render fake address bars, security dialogs, or browser-level indicators in a way that deceives users into disclosing credentials or taking unintended actions. No public exploit code has been identified and no CISA KEV listing exists; EPSS at 0.21% (11th percentile) reflects negligible observed exploitation activity.
Google Chrome's browser UI component (all versions prior to 153.0.8010.36) is vulnerable to visual spoofing attacks where an attacker can manipulate how the browser presents security-critical interface elements to users. By serving a specially crafted HTML page combined with social engineering, a remote unauthenticated attacker can make Chrome display misleading UI indicators - such as deceptive origin representations or manipulated security signals - potentially enabling credential theft or unauthorized permission grants. No public exploit code exists and the EPSS score of 0.21% (11th percentile) indicates low near-term exploitation probability, consistent with Chromium's own Medium severity classification.
Authorization bypass in Eventin - Event Calendar plugin for WordPress (all versions ≤4.1.17) allows authenticated subscriber-level users to fully manage notification flow automation workflows restricted to administrators. Exploitation requires only a low-privilege WordPress account, enabling unauthorized read, create, update, clone, and delete operations on event automation configurations. No public exploit or KEV listing identified; vendor-released patch 4.1.18 resolves the flaw.
UI misrepresentation in Google Chrome's FedCM (Federated Credential Management) API prior to 153.0.8010.36 enables remote attackers to spoof identity-provider sign-in dialogs via crafted HTML pages, requiring user interaction. The flaw (CWE-451) allows a malicious page to manipulate how FedCM presents credential prompts, potentially misleading users into authorizing the wrong identity provider or disclosing credential context to an attacker-controlled endpoint. No public exploit code or active exploitation has been identified; EPSS is 0.17%, consistent with Chromium's 'Medium' severity classification.
Improper input validation in Chrome's Interstitials component - the full-page security warning screens shown for SSL errors, Safe Browsing alerts, and download warnings - allows a remote attacker to spoof UI elements by delivering a crafted HTML page to an unsuspecting user. Affected versions are all Chrome releases prior to 153.0.8010.36 across desktop platforms. No public exploit code has been identified and EPSS stands at 0.17% (7th percentile), reflecting low near-term exploitation probability, though successful abuse could undermine user trust in browser security indicators and facilitate phishing or credential harvesting.
UI spoofing in Google Chrome's Passwords component (versions prior to 153.0.8010.36) allows a remote unauthenticated attacker to misrepresent password-related UI elements by delivering a crafted HTML page to a victim. Classified as CWE-451 (UI Misrepresentation of Critical Information), this flaw could deceive users into believing they are interacting with a legitimate password prompt or credential management interface when they are not, potentially facilitating credential phishing or confusion attacks. No public exploit or active exploitation (CISA KEV) has been identified; EPSS is 0.17% (7th percentile), consistent with Chromium's own 'Medium' severity rating.
Improper access controls in Tanium Comply (CWE-862, Missing Authorization) allow authenticated low-privileged users to perform unauthorized actions affecting the integrity and availability of the compliance module. Three active release branches are affected - 2.32.x, 2.35.x, and 2.37.x - with vendor-issued patches available for each. No active exploitation has been identified and no public proof-of-concept exists at time of analysis.
Improper access controls in Tanium Comply allow authenticated low-privileged users to perform unauthorized actions affecting integrity and availability via CWE-639 (Authorization Bypass Through User-Controlled Key). Affected versions span three active release branches: 2.32, 2.35, and 2.37, each with specific fixed builds. Tanium has released patched versions and no active exploitation or public exploit code has been identified at time of analysis.
Tanium Comply contains an improper access control vulnerability (CWE-639, Authorization Bypass Through User-Controlled Key) that allows authenticated low-privileged users to perform unauthorized integrity-affecting or availability-impacting actions against compliance data by manipulating user-controlled object references. Affected branches span three minor release lines (2.32, 2.35, 2.37) with fixed versions available. No public exploit code and no CISA KEV listing are present at time of analysis, consistent with the medium CVSS score of 5.4. The vendor (Tanium) self-reported and released patches across all affected branches.
Incorrect authorization in Chrome's Isolated component (all versions prior to 153.0.8010.36) enables remote attackers to spoof UI elements by directing users to a crafted HTML page. The flaw stems from CWE-863 authorization failures within Chrome's isolation architecture, allowing cross-boundary deception without requiring attacker authentication. No public exploit exists and EPSS is 0.17% (6th percentile), placing this firmly in the routine-patching tier despite the network-accessible attack vector.
Incorrect authorization in Chrome's Loader component allows a remote attacker to bypass system access restrictions with limited confidentiality and integrity impact. Affected versions are all Chrome releases prior to 153.0.8010.36, and exploitation requires user interaction via a crafted HTML page combined with social engineering. No public exploit or active exploitation (CISA KEV) has been identified; the EPSS score of 0.17% (6th percentile) and Chromium's own 'Low' severity rating confirm this is a low-priority issue relative to the broader Chrome vulnerability landscape.
Stored XSS in money-pos 1.0 allows a low-privileged attacker with product-creation access to inject malicious JavaScript into order log entries via an unsanitized goodsName parameter during return processing. The payload persists server-side and executes in the browser of any administrator who views the order logs, because the Vue.js frontend renders the log description through v-html without sanitization. No public exploit code has been identified at time of analysis, and EPSS at 0.16% signals negligible automated exploitation probability.
UI spoofing in Google Chrome's Passwords component on Android (prior to 153.0.8010.36) enables a remote attacker to misrepresent password-related UI elements by delivering a crafted HTML page to a victim. The CVSS 5.4 (Medium) rating contrasts with Chromium's own 'Low' severity classification, a common divergence for UI-redressing issues. No public exploit code or active exploitation (CISA KEV) has been identified, and EPSS of 0.16% (6th percentile) confirms negligible near-term exploitation probability.
Bluetooth Classic L2CAP channel state confusion in Zephyr RTOS (versions 1.6.0 through pre-4.4.2) enables an adjacent unauthenticated peer to inject data PDUs into half-open L2CAP channels before configuration or security handshaking completes, forcing processing on stale or uninitialized channel fields. In the worst case, reused channel objects expose dangling _sdu reassembly buffer pointers, creating a memory-safety condition that causes channel and link teardown (denial of service) alongside unintended delivery of attacker-controlled data to upper-layer protocol handlers. No public exploit has been identified and the flaw is absent from CISA KEV; a vendor-released fix is available via Zephyr commit 2738ee9, targeting release 4.4.2.
SQL injection in Dell Secure Connect Gateway (SCG) 5.0 allows a remote attacker holding low-privilege credentials to execute unauthorized SQL commands against the product's backend database. Both the Appliance variant (prior to 5.36.00.16) and the Application variant (prior to 5.36.00.00) are affected, with confirmed limited confidentiality and integrity impact but no availability consequence. No active exploitation or public proof-of-concept has been identified at time of analysis; Dell has released patched versions under advisory DSA-2026-382.
Stored cross-site scripting in the announcement preview component of REBUILD 4.4.3 allows an authenticated user who can author announcement content to run arbitrary JavaScript in the browsers of anyone who views the affected announcement — potentially including the dashboard, activity feed, or login page depending on the announcement's visibility settings. The server correctly HTML-escapes the announcement body, but the client-side preview code reverses those escapes via jQuery's html().text() chain and then re-injects the decoded string into the DOM, defeating the server-side defense. No public exploit code has been identified and the vulnerability is not in CISA KEV; EPSS is very low at 0.15% (4th percentile), indicating limited expected mass exploitation.
Race condition in the Payments component of Google Chrome prior to 153.0.8010.36 enables remote attackers to spoof payment UI elements by delivering a crafted HTML page combined with social engineering, requiring user interaction to trigger the vulnerable timing window. The CWE-362 race condition in Chrome's Payment Request handling allows the attacker to substitute or overlay legitimate payment dialogs with fraudulent ones during the race window, potentially tricking victims into submitting payment credentials to attacker-controlled endpoints. No public exploit code exists and EPSS of 0.14% (4th percentile) reflects very low exploitation probability; Chromium rates this Medium severity.
Improper access controls in Tanium Comply (CWE-862 Missing Authorization) allow authenticated low-privilege users to perform actions or access data beyond their authorized scope. Three active release branches are affected: 2.32, 2.35, and 2.37. No public exploit code and no CISA KEV listing have been identified at time of analysis; Tanium has released patched builds across all affected branches.
Improper certificate validation in Google Chrome's Loader component (prior to 153.0.8010.36) enables remote attackers to bypass the browser's web origin policy via crafted network traffic combined with social engineering. The flaw (CWE-295) permits partial cross-origin data access and integrity impact, rated Low severity by Chromium's own classification despite a CVSS base score of 5.4. No public exploit exists and EPSS sits at 0.13% (3rd percentile), indicating very low exploitation probability at this time.
Heap out-of-bounds read in VLC Media Player 3.0.0 through 3.0.23 allows a hostile RTSP server to extract adjacent heap memory from a connecting client. The flaw lies in the realrtsp access module: `RtspReadLine` in `modules/access/rtsp/access.c` uses `strncpy` with the full buffer length into a 4096-byte allocation, omitting the null terminator when the source is at least as long; `rtsp_get` in `modules/access/rtsp/rtsp.c` then passes that unterminated buffer to `strdup`, which walks heap memory until an incidental zero byte. The disclosed bytes are retained as the RTSP Session identifier and echoed back to the server on every subsequent request, giving the server operator a continuous read of arbitrary heap contents from the victim process. No public exploit code has been identified at time of analysis, and the module is disabled in some distribution packages.
ControlledFrame in Google Chrome prior to 153.0.8010.36 exposes sensitive information to an attacker who has already achieved renderer process compromise, exploitable via a crafted HTML page (UI:R). This is a chained post-exploitation primitive rather than an initial access vector: it extends the damage of a separate renderer exploit by enabling cross-origin data exfiltration from the victim's session. No public exploit code exists, EPSS stands at 0.29% (21st percentile), and no CISA KEV listing is present, consistent with the high effective exploitation barrier imposed by the renderer pre-compromise requirement.
ServiceWorker information leak in Google Chrome prior to 153.0.8010.36 enables a remote attacker who has already compromised the renderer process to extract sensitive information via a crafted HTML page. This is a chained exploitation technique rather than a standalone attack - requiring prior renderer process control as a hard prerequisite, making it a second-stage capability within a broader browser exploit chain. No public exploit code exists and EPSS sits at 0.29% (21st percentile), indicating low observed exploitation activity; the vulnerability is not listed in CISA KEV.
Cross-company asset acceptance report exposure in Snipe-IT before 8.7.0 allows authenticated users holding the reports.view permission to read pending asset acceptances belonging to other companies within the same multi-tenant instance. The unaccepted_assets report page and its CSV export endpoint lack per-company scoping on their database queries, so any user with the reports.view role can enumerate inventory details and assignee names across organizational boundaries. No public exploit exists at time of analysis; a vendor-released patch is available in version 8.7.0.
Unauthenticated SSRF in Yordam Informatics' Library Information and Document Automation Program allows remote attackers to induce the server to issue arbitrary HTTP requests to internal or external destinations. Affecting all versions before v22.2, the flaw is reachable without credentials over the network, giving attackers a pivot point to probe internal network resources, cloud metadata endpoints, or other services inaccessible from the public internet. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Price manipulation via missing authorization in WPFunnels plugin for WordPress (all versions ≤3.12.13) lets unauthenticated attackers add arbitrary WooCommerce products to a cart at any discounted price configured on any funnel step. The `wpfnl_load_payment` AJAX action is exposed via `wp_ajax_nopriv_` with no nonce verification, no capability check, and no server-side validation confirming the caller-supplied `product_id` corresponds to the configured offer on the specified `step_id`. Exploitation enables systematic checkout price manipulation and direct merchant revenue loss; no public exploit identified at time of analysis.
Observable discrepancy (CWE-203) in the Safebrowsing component of Google Chrome on iOS prior to 153.0.8010.36 enables a remote attacker with a pre-compromised renderer process to leak sensitive information through behavioral differences when processing a crafted HTML page. The vulnerability is iOS-platform-specific and is chained after renderer compromise rather than exploited standalone. No public exploit exists and EPSS probability is 0.24%, consistent with the multi-stage exploitation requirement.
Ticket inventory exhaustion in WP Event Solution (Eventin) ≤4.1.22 allows any unauthenticated visitor to forge completed event orders and permanently lock out legitimate ticket buyers. The REST endpoint /wp-json/eventin/v2/orders relies solely on a wp_rest nonce for authorization, but that nonce is broadcast to every site visitor via the etn-public script's localized_data_obj - making the check functionally equivalent to no check at all. By submitting crafted POST requests with status='completed', attackers create persistent fake sold-order records that count against ticket inventory indefinitely, since the auto-cleanup scheduler only targets pending orders. No public exploit code or active exploitation has been identified at time of analysis.
Unauthenticated manipulation of guest account settings in HPE Aruba ClearPass Policy Manager's (CPPM) web-based management interface allows remote attackers to extend guest network access beyond enforced policy limits. The flaw resides in the guest account management service and requires no credentials, no user interaction, and no special network position - only HTTP reachability to the management interface. No public exploit code and no CISA KEV listing have been identified at time of analysis, and the CVSS score of 5.3 (Medium) reflects limited integrity-only impact, but the policy-enforcement bypass angle elevates business risk in zero-trust or time-limited guest environments.
Script injection via improper sanitization of special characters in Dell Secure Connect Gateway 5.0 allows unauthenticated remote attackers to inject script content, resulting in limited confidentiality exposure. Both the Appliance form factor (versions prior to 5.36.00.16) and the Application form factor (versions prior to 5.36.00.00) are affected. No public exploit code or active exploitation has been identified at time of analysis; Dell has issued a vendor-confirmed patch under advisory DSA-2026-382.
Snipe-IT before version 8.7.0 allows authenticated users to circumvent administrative asset request controls by submitting checkout requests directly to the POST /account/request/asset_model/{modelId} endpoint, which fails to validate the server-side `requestable` flag on asset models. This business logic flaw enables any authenticated user to request assets that administrators have explicitly restricted, undermining allocation and compliance controls enforced through the requestable designation. No public exploit code or active exploitation has been identified at time of analysis; CVSS 4.0 rates this at 5.3 Medium.
Script injection via alternate XSS syntax affects Dell Secure Connect Gateway (SCG) 5.0 in both Appliance (prior to 5.36.00.16) and Application (prior to 5.36.00.00) editions, as disclosed in Dell advisory DSA-2026-382. An unauthenticated remote attacker exploiting CWE-87 can bypass the application's standard XSS filters using alternative injection syntax, causing malicious scripts to execute in the context of affected users' browsers and potentially enabling session hijacking or credential exfiltration. No public exploit code and no CISA KEV listing have been identified; Dell has released patches for both product variants.
Incorrect authorization in Snipe-IT 8.2.0-8.6.x lets any authenticated user holding the users.edit permission toggle the activated flag on arbitrary accounts - including admin and superuser accounts - by submitting a complete PUT request to the single-user web UI edit route /users/{id}. Because UsersController::update() assigned the activated field from the request payload before evaluating the canEditAuthFields authorization gate, the unauthorized write persisted through to save(); deactivating a targeted admin account locks it out of the application until re-enabled by another privileged user. No data is disclosed, and the API and bulk-edit paths are unaffected; the issue is fully remediated in 8.7.0.
Out-of-bounds read via integer overflow in the HarmonyOS graphics module exposes affected devices to a denial-of-service condition. Exploitation targets HarmonyOS 6.1.0 and, per the vendor CVSS vector (AV:N/AC:L/PR:N/UI:N), requires no authentication or user interaction - suggesting a network-facing graphics processing pathway is reachable without privilege. The sole confirmed impact is availability (A:L), consistent with a crash or partial service disruption in the graphics subsystem; no confidentiality or integrity impact is reported. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Sensitive information disclosure in Google Chrome's BackgroundFetch API allows a remote attacker who has already compromised the renderer process to leverage the BackgroundFetch service worker mechanism as a confused deputy, leaking sensitive data via a crafted HTML page. Affected versions are all Chrome releases prior to 153.0.8010.36; Chromium rates this Medium, consistent with the CVSS 5.3 score that reflects the high-complexity prerequisite of a compromised renderer. No public exploit code or active exploitation (CISA KEV) has been identified, and EPSS places exploitation probability at 0.20% (10th percentile).
Snipe-IT versions 4.2.0 through 8.6.3 allow any authenticated user with a web session to mint long-lived Laravel Passport bearer tokens via the auto-registered /oauth/personal-access-tokens route, even when an administrator has explicitly denied that user the self.api permission. The root cause is that Laravel Passport's OAuth routes carry only generic 'web' and 'auth:web' middleware, bypassing Snipe-IT's own can:self.api permission gate that protects the application's native token management endpoints. Crucially, the issued tokens remain subject to all existing per-endpoint authorization checks, so this is an authorization-control bypass that defeats administrative intent - not a privilege escalation. No public exploit has been identified at time of analysis, and a fix is available in version 8.7.0.
Information disclosure in Google Chrome's DataTransfer API via a TOCTOU race condition allows a remote attacker to obtain sensitive data from a victim's browser session. Affected versions are all Chrome releases prior to 153.0.8010.36 on desktop platforms. Exploitation requires social engineering to induce user interaction with a crafted HTML page - no active exploitation has been identified and EPSS sits at the 9th percentile, indicating very low real-world exploitation probability at this time.
Incorrect authorization in Snipe-IT before 8.7.0 allows authenticated users holding the assets.audit permission to write audit log entries against assets belonging to other companies in multi-tenant deployments. The flaw stems from the asset audit endpoints relying exclusively on query-layer filtering for FMCS (multi-company scoping) rather than enforcing policy-layer authorization checks, meaning the tenant boundary can be bypassed by targeting cross-company asset identifiers directly. No public exploit code has been identified, and a vendor patch is available in version 8.7.0.
Cross-tenant information disclosure in Snipe-IT before 8.7.0 allows authenticated users with standard assets.view permission to read pending asset request records belonging to other companies when the Full Multiple Company Support feature is enabled. The GET /hardware/requested endpoint omits company scope filtering entirely, returning cross-tenant data including asset names, requester display names and profile links, locations, and expected check-in dates without requiring any parameter manipulation. No public exploit has been identified and no active exploitation is listed in CISA KEV; impact is bounded by what the endpoint exposes - operational metadata rather than credentials or full asset inventories.
Authorization scope bypass in Snipe-IT versions up to 8.6.3 allows an authenticated low-privilege user to send acceptance-reminder emails to users in foreign companies and permanently delete asset acceptance audit records across all companies in a multi-tenant installation. The flaw exists in two report endpoints whose company-isolation guard either was absent (pre-8.6.3) or contains a logic error that grants unconditional access to 'pivot-only' users - those whose scalar `users.company_id` column is NULL. Sequential integer acceptance IDs make cross-company record enumeration trivial. No public exploit has been identified and the CVE is not in CISA KEV; the vendor fix is available in version 8.7.0.
Observable discrepancy in Chrome's Layout engine prior to version 153.0.8010.36 allows a remote attacker to infer sensitive cross-origin information by measuring rendering differences triggered by a crafted HTML page. The CWE-203 root cause - an attacker-observable behavioral difference that correlates with secret state - places this in the browser side-channel (XSLeak) family, where layout timing or geometry variations can reveal whether a user is authenticated to a third-party origin or whether specific cross-origin resources exist. No public exploit has been identified at time of analysis, and the EPSS score of 0.17% (7th percentile) reflects low observed exploitation interest.
Insufficient session expiration in Dell Secure Connect Gateway 5.0 (both Appliance and Application deployments) enables a low-privileged remote attacker to capture and replay session tokens that remain valid beyond their intended lifetime, resulting in session theft and unauthorized access to sensitive data. Both form factors are affected: Application versions prior to 5.36.00.00 and Appliance versions prior to 5.36.00.16. Dell has released patched versions via advisory DSA-2026-382; no public exploit or active exploitation has been identified at time of analysis.
Incorrect authorization in Chrome's DataTransfer API (prior to 153.0.8010.36) permits an attacker who has already achieved renderer process compromise to read sensitive data via a crafted HTML page. The flaw (CWE-863) bypasses intended access-control checks on clipboard or drag-and-drop data within the renderer context, enabling information disclosure rather than code execution. No public exploit code exists and EPSS sits at 0.17% (6th percentile), reflecting this as a chained, second-stage attack primitive rather than a standalone initial-access vector.
Missing authorization in the Contacts component of Google Chrome before 153.0.8010.36 allows a remote attacker who has already compromised the renderer process to extract sensitive contact data by delivering a crafted HTML page through social engineering. This is a secondary, post-renderer-compromise vulnerability - not an initial access vector - and Chromium's own team rates it 'Low' severity, reflecting the elevated prerequisite chain. No public exploit has been identified, EPSS sits at 0.16% (5th percentile), and CISA SSVC rates exploitation likelihood as none, collectively indicating minimal real-world risk at this time.
Unauthenticated remote attackers can exploit sqladmin's `ModelView` list view to probe hidden model column values via an ordering oracle, bypassing the UI-level `column_sortable_list` restriction. The `sortBy` HTTP query parameter is resolved through `getattr(model, ...)` and fed directly into ORM `ORDER BY` clauses without server-side validation, meaning any column - including those deliberately hidden from `column_list` - and related-model columns via dotted paths can be sorted. By observing row-order changes across ascending and descending requests, an attacker incrementally infers relative values of unexposed fields. No public exploit code and no CISA KEV listing exist at time of analysis; vendor-released patch is available in 0.27.1.
Session fixation in tirreno versions prior to 0.10.0 allows an attacker who can inject a known session identifier into a victim's browser to hijack that victim's authenticated session. The framework's authentication flow validates credentials and establishes a session but omits the PHP session_regenerate_id() call, so the same token that existed before login remains valid after it. No public exploit code has been identified; exploitation requires a prerequisite attack capability such as network man-in-the-middle access, a companion cross-site scripting flaw, or subdomain cookie injection.
Broken access control in Snipe-IT before version 8.7.0 allows authenticated users holding only the assets.files permission to upload and delete file attachments on Asset Model records, which are shared catalog objects that normally require the separate models.files permission. The flaw in AssetModelPolicy causes the files() authorization method to cascade from the wrong permission scope, creating an unintended privilege boundary bypass. In multi-company Snipe-IT deployments, this enables cross-tenant mutation of shared Asset Model file attachments; no public exploit has been identified at time of analysis.
Object-level authorization failure in Snipe-IT through 8.6.3 permits an authenticated user holding only the low-privilege `kits.edit` permission to attach Licenses, Consumables, Accessories, or Asset Models - resources they are explicitly denied (HTTP 403) from reading directly - to Predefined Kits via the updateLicense, updateConsumable, updateAccessory, and storeModel endpoints. The kit relation index then discloses the attached objects' names back to the attacker, yielding both unauthorized writes and limited information disclosure. This is the update-path counterpart to CVE-2026-55478, which patched only the store methods in 8.6.2, revealing a pattern of incomplete authorization fixes in this code area. No public exploit or KEV listing identified at time of analysis.
Snipe-IT's consumables checkout API endpoint writes the checkout target user's identifier into the `created_by` audit column rather than the authenticated caller's identifier, poisoning the audit trail. Authenticated attackers holding only the `consumables.checkout` permission can silently attribute their checkout actions to any target user in the `consumables_users` pivot table, effectively laundering their operational footprint from the system's records. The fix is available in version 8.7.0; no public exploit or active exploitation has been identified at time of analysis.
Integrity corruption in Snipe-IT before 8.7.0 allows any authenticated user holding checkout permissions to bind live inventory records to soft-deleted users, assets, or locations via the REST API. By submitting POST requests to the hardware, component, or consumable checkout endpoints with IDs of trashed entities, attackers create orphaned database references that corrupt the asset ledger and undermine audit trail integrity. No public exploit code has been identified and the flaw is not listed in CISA KEV, but the network-reachable API and low privilege bar make this straightforward to abuse internally.