Local privilege escalation exists in the Modem component of a broad range of MediaTek chipsets, where a missing permission check (CWE-280) lets code running with System privilege reach higher-integrity operations, with high impact on confidentiality, integrity and availability (CVSS 6.7, AV:L/AC:L/PR:H/UI:N/S:U). The prerequisite is explicit in the vendor description: an attacker must already hold the System privilege on the device, so this is a post-compromise escalation step rather than an entry point, and it is reachable locally with no user interaction and no network vector. No public exploit code was identified at time of analysis and there is no CISA KEV listing; MediaTek has published a fix under patch ID MOLY01790985 in its November 2026 product security bulletin, and the affected hardware spans dozens of chipsets including MT6761, MT6765, MT6768, MT6833, MT6877, MT6895, MT6983, MT8768 and MT8788E.
Out-of-bounds write in MediaTek's NeuroPilot AI/ML (APU) component allows a local attacker who already holds System privilege to escalate further on devices running affected MediaTek chipsets, with high impact to confidentiality, integrity and availability. Exploitation is local (AV:L), requires high privileges (PR:H) and needs no user interaction (UI:N), so it cannot be used for initial access or remote compromise - it is a post-compromise escalation primitive. No public exploit code has been identified at time of analysis (SSVC exploitation: none, CISA KEV: not listed); MediaTek has released patch ALPS11263078 in its November 2026 product security bulletin.
Local privilege escalation in MediaTek chipset USB handling allows an attacker who already holds System privilege to exploit a missing bounds check, corrupt memory, and escalate privileges on affected devices. The issue affects the MediaTek chipsets enumerated in EUVD-2026-115048, including MT6769, MT6833, MT6877, MT6895, MT6983, MT6991 and others listed in the advisory. No public exploit was identified at time of analysis.
Double free in the USB driver shipped with several MediaTek chipsets (MT6993, MT8668, MT8188, MT8518S, MT8532, MT8189) corrupts kernel memory and can be converted into a local privilege escalation by an attacker who already holds System privilege on the device; no user interaction is required (CVSS 6.7, AV:L/PR:H/UI:N). MediaTek has assigned fix ALPS11411924 (issue MSV-9748) and published it in the November 2026 product security bulletin. No public exploit code was identified at time of analysis and CISA SSVC records exploitation as none, so the practical risk profile is a post-compromise escalation step rather than an initial-access or remote vector.
A use-after-free memory corruption flaw in the USB component of several MediaTek chipset models (MT8189, MT8668, MT6881, MT8532, MT6993, MT8518S, MT6858, MT8188) can be triggered locally by an attacker who already holds System privilege, allowing further escalation of privileges. Because the pre-existing System privilege requirement is the dominant limiting factor, this is a conditional, lower-tier priority rather than an urgent emergency; exploitation requires local access at System level, and no user interaction is needed. No public exploit code or active exploitation has been identified at time of analysis, and the precise USB operation that triggers the use-after-free is not described in the available sources.
Local privilege escalation in the MediaTek afe audio front-end driver affects devices built on a set of MediaTek chipsets, including MT6985, MT6886, MT6993, MT6895, MT6897, MT6991, MT6989 and MT6789. An attacker who already holds System privilege can trigger a missing bounds check that leads to an out-of-bounds write, gaining high confidentiality, integrity and availability impact without user interaction; the issue is local only and does not provide an initial foothold. No public exploit was identified at time of analysis, and CISA SSVC records exploitation as none and automatable as no.
Use-after-free in the MediaTek audio front-end (afe) driver on affected MediaTek chipsets allows a local attacker who already holds System privilege to escalate to a higher privilege level, with high confidentiality, integrity, and availability impact and no user interaction (CVSS 3.1: 6.7, AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). The issue affects Android devices built on a broad set of MediaTek chipsets and has a vendor patch identified by ALPS11431394; no public exploit identified at time of analysis.
This is a genuine but constrained privilege-escalation issue rather than a top-tier emergency. Local privilege escalation in the MediaTek afe audio front-end driver affects Android devices using the listed MediaTek chipsets; an attacker who already holds System privilege can trigger memory corruption to gain higher-level code execution with high confidentiality, integrity, and availability impact. No user interaction is required, but the PR:H precondition confines this to a post-compromise escalation step, and no public exploit identified at time of analysis.
Local privilege escalation in MediaTek's afe component on affected chipsets is caused by a double-free memory-corruption flaw that a local attacker can trigger after already holding System privilege. Successful exploitation can compromise confidentiality, integrity, and availability at higher privilege, with no user interaction required. No public exploit was identified at the time of analysis; MediaTek assigns Patch ID ALPS11431412 in its November 2026 product security bulletin.
MediaTek adsp contains an out-of-bounds write caused by an integer overflow that can allow a local actor who already holds System privilege to escalate privileges further on affected MediaTek chipsets, with no user interaction required. The issue is rated 6.7 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) and affects a broad set of chipsets including MT8390, MT6989, MT8196, and MT6991. MediaTek has published patch ALPS11431442; no public exploit was identified at time of analysis.
Local privilege escalation in the MediaTek audio front-end (afe) driver affects more than 40 MediaTek chipsets, including MT6739, MT6768, MT6893, MT8195 and MT6983. The defect is a use-after-free that can corrupt memory and, for an attacker who already holds System privilege and has local access to the afe interface, can lead to high confidentiality, integrity and availability impact without user interaction. The vendor fix is identified by patch ID ALPS11434319; no public exploit identified at time of analysis, and CISA SSVC records exploitation as none.
Local privilege escalation in MediaTek's adsp (audio DSP) driver arises from a use-after-free that a local process already holding Android System privilege can use to extend its control over the device. Affected are devices built on a broad set of MediaTek chipsets, including MT6991, MT6989, MT6897, MT8195, MT8188, MT8186, MT6878 and others enumerated by EUVD, tracked under MediaTek patch ID ALPS11431474 and issue MSV-9926. No user interaction is required and attack complexity is low, but the PR:H precondition is decisive: without pre-existing System-level access there is no exploitation path, so no public exploit code has been identified at time of analysis, CISA SSVC records exploitation as none with automatable set to no, and the vendor-bulletin fix is scheduled into this month's remediation window.
Local privilege escalation in MediaTek's adsp (audio DSP) component allows an attacker who already holds System privilege to trigger a use-after-free and corrupt memory, escalating to code execution at a higher privilege level on a specific set of MediaTek chipsets (including MT6991, MT6989, MT8196, MT8195, MT8188, MT6897 and others). MediaTek tracks the fix as patch ALPS11431474 / issue MSV-9927, published in its November 2026 product security bulletin; no user interaction is required, and no public exploit code or confirmed active exploitation has been identified at time of analysis. The high-privilege precondition caps severity at CVSS 6.7 and makes realistic abuse a post-foothold escalation link rather than an initial access vector.
Moderate-severity local privilege escalation in MediaTek's afe (audio front-end) component can be triggered by an attacker who already holds System privilege on an affected MediaTek chipset, using a use-after-free to crash the system or gain higher-privilege code execution. The flaw affects a broad set of MediaTek chipsets, including MT6768, MT6789, MT6893, MT8188, MT6991 and many others, and requires local access with no user interaction. No public exploit has been identified at time of analysis; SSVC records no known exploitation and no automatable path.
Local privilege escalation in MediaTek's 'afe' (audio front-end) component allows an attacker who already holds System privilege to trigger an out-of-bounds write via a missing bounds check, gaining higher-integrity code execution on the device. The flaw (CWE-787, CVSS 6.7) is not remotely reachable - the vector is AV:L with PR:H and UI:N - and affects a broad set of MediaTek chipsets used in Android devices, including MT6765, MT6789, MT6893, MT6983, MT8188 and MT8195, with a vendor patch identified as ALPS11431394. No public exploit has been identified at time of analysis and CISA SSVC records no known exploitation; the practical exposure is confined to devices where an attacker has already escalated to System level, making this a post-compromise escalation step rather than an entry point.
Permission control flaws in the Huawei HarmonyOS and EMUI autofill service module allow a local attacker - in practice a malicious or compromised app installed on the device - to reach autofill data that the app's permissions should not permit, resulting in disclosure of confidential information. Exploitation is local (AV:L) and requires the victim to perform an action such as invoking autofill (UI:R); it cannot be triggered remotely. The vendor scores this 6.6, and no public exploit code or confirmed active exploitation was identified at time of analysis; the exact app-permission precondition that enables the bypass is not described in the available sources.
Authenticated SQL injection in ZTE Elasticnet RNIA R18 NGI allows a logged-in attacker to read sensitive database information, with a CVSS 3.1 score of 6.5 reflecting high confidentiality impact but no integrity or availability impact. Exploitation requires valid credentials (PR:L), which aligns with the vendor's internal threat-level classification and limits exposure to users who can already authenticate to the application. There is no CISA KEV confirmation and no public exploit identified at time of analysis; the priority label is this_month.
Denial of service in the Huawei HarmonyOS DSoftBus distributed soft-bus module allows an attacker on the same adjacent network to degrade or exhaust availability of affected devices without authentication or user interaction. The CVSS 3.1 vector (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 6.5) confines impact to availability, with no confidentiality or integrity effect, and the network-adjacency prerequisite is the primary factor limiting exposure - internet-scale exploitation is not possible. No public exploit code or CISA KEV entry was identified at time of analysis, and the vendor-reported issue is tracked at a this_month priority rather than an emergency.
Denial of service in the MediaTek ccci subsystem affects the enumerated chipsets (MT6880, MT6890, MT6813, MT6986, MT6982, MT6980D, MT2735 and MT2737, with MT6990 and MT6988 also listed by EUVD) when a user is induced to process crafted input; a missing bounds check allows an out-of-bounds write, but the assessed impact is availability only, with no confidentiality or integrity loss and no code execution per the vendor. The issue is medium severity (CVSS 6.5, AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H), requires user interaction, and is not reported as actively exploited; no public exploit identified at time of analysis, and SSVC records exploitation as none and automatable as no.
Elevation of privilege leading to arbitrary code execution in Dell Alienware Command Center (AWCC) versions prior to 6.14.54.0 arises because the software improperly verifies cryptographic signatures on the components it consumes (CWE-347). The attack path is strictly local: the CVSS vector CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H shows an attacker must already hold high privileges on the host and have local access, so this is not a remote or unauthenticated vector, and high attack complexity further narrows practical exposure. Successful abuse yields high confidentiality, integrity and availability impact through code execution at elevated privilege; no public exploit code or active exploitation was identified at time of analysis, and the moderate 6.4 base score together with the 'this_month' priority reflect a locally scoped, privilege-gated issue rather than an emergency.
Improper certificate validation (CWE-295) in Dell Alienware Command Center before 6.14.54.0 can lead to arbitrary code execution and denial of service, but only for an authenticated, high-privileged attacker (PR:H) with local access to the host. The CVSS 3.1 score is 6.4 (moderate), with high attack complexity (AC:H) reflecting conditions the attacker does not fully control; the specific trigger is not described in the available sources. No public exploit identified at time of analysis, and Dell advisory DSA-2026-429 identifies 6.14.54.0 as the fixed release.
Server-side request forgery in Chainlit's MCP client path lets an unauthenticated remote user slip past path-scoped allowed_urls grants by embedding '..;' segments in the user-supplied MCP URL posted to /mcp, because validate_mcp_url does not reject the semicolon character; on origins that strip semicolon path parameters the request lands on a path outside the operator's grant. Exposure is narrow and opt-in: MCP must be enabled (features.mcp.enabled = true, off by default since v2.7.0), user-provided servers must be enabled with a non-empty allowed_urls allowlist, and the target origin must discard ';' parameters, so reach is confined to paths on hosts the operator already allowlisted, and the SSRF is blind. No public exploit code was identified at time of analysis and no EPSS or KEV signal is present; the priority label is monitor, consistent with a low-to-moderate, conditional issue rather than an urgent one.
Route parameter confusion in Nuxt 4.6.0 through 4.6.1 (and the matching @nuxt/nitro-server releases) allows remote attackers to have the getRouterParam/getRouterParams helpers return a parameter value different from the one h3 actually matched, by sending a path segment containing an encoded question mark (%3F). Impact is conditional: only applications that read the same route param from two different sources - the Nuxt helper for an authorization decision and event.context.params or another h3 helper for resource selection - can be driven to check one resource and act on another, yielding limited confidentiality impact. Exploitation requires high attack complexity and a non-default dual-source coding pattern, no public exploit was identified at time of analysis, and the issue is fixed in nuxt@4.6.2.
Local denial of service in Google Android 14 through 17 can be triggered through a permission bypass caused by resource exhaustion, allowing code already running on the device to consume resources without user interaction or additional execution privileges. Impact is limited to availability (C:N/I:N/A:H) with scope unchanged. No CISA KEV entry or public exploit code was identified, and EPSS is 0.14% (3rd percentile), indicating low predicted exploitation activity.
Local denial of service in the Android kernel's protected-KVM (pKVM) hypervisor: an out-of-bounds write in __pkvm_guest_relinquish_to_host (mem_protect.c) lets code already running on the device crash the hypervisor by way of improper input validation, with no additional execution privileges and no user interaction required once the hypercall path is reachable. Per the CVSS vector (AV:L/AC:L/PR:N/UI:N) impact is limited to availability (C:N/I:N/A:H); the device must be an ARM64 Android build running pKVM with guest VMs, so generic Android devices without protected guests are not exposed. No public exploit code was identified at time of analysis, and EPSS is low at 0.14% (3rd percentile); the vulnerability is confirmed addressed through upstream Android common kernel commits referenced in the November 2026 Android security bulletin.
Local denial of service in Android's Trusty RPC server (handleConnectInternal in RpcServerTrusty.cpp) lets code already running on the device crash or hang a Trusty IPC service by issuing a crafted connection request. Only Android 16-qpr2 and Android 17 are confirmed affected, and the flaw is strictly local (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 6.2) with availability-only impact and no privilege gain, data exposure or integrity effect. There is no public exploit identified at time of analysis and EPSS is very low at 0.12% (2nd percentile); Google rates the issue for handling within the current monthly cycle (this_month), with the fix published in the November 2026 Android Security Bulletin.
A logic error in updateNotificationChannel within PreferencesHelper.java in Google Android (versions 14, 15, 16, 16-qpr2, and 17) allows a local attacker to cause UI obfuscation leading to a local denial of service. The flaw is rated 6.2 (AV:L/AC:L/PR:N/UI:N/C:N/I:N/A:H), meaning it is only reachable by an attacker who can already run code on the device, requires no additional privileges or user interaction, and affects only availability, with no confidentiality or integrity impact. No public exploit code is identified at time of analysis, EPSS is 0.12% (2nd percentile), the issue is not in CISA KEV, and the vendor bulletin is the Android Security Bulletin for 2026-11-01.
Local denial of service in Google Android 16, Android 16-qpr2 and Android 17 is caused by SQL injection (CWE-89) in multiple functions of SearchRequestDatabaseUtil.java, which can be reached by code already running on the device to access protected data and crash or destabilise the affected component. The vector is AV:L/AC:L/PR:N/UI:N with impact limited to availability (A:H), so a malicious or compromised application needs no additional privileges and no user interaction, but there is no remote path. Risk is moderate and low-urgency (CVSS 6.2, EPSS 0.12% / 2nd percentile, no CISA KEV entry), and no public exploit code was identified at time of analysis; the flaw is addressed by the Android Security Bulletin dated 2026-11-01.
Resource exhaustion in Android's DevicePolicyManagerService.setApplicationRestrictions allows a local party on the device to cause a denial of service on Android 16 QPR2 and Android 17 builds. The CVSS vector scores it AV:L/AC:L/PR:N/UI:N with availability-only impact (6.2), but in practice setApplicationRestrictions is a Device Policy Manager operation normally reserved for a device/profile owner or an app holding the corresponding management permission, which materially narrows who can reach the vulnerable path. There is no public exploit identified at time of analysis, EPSS is very low (0.11%, 1st percentile), and there is no KEV listing; the priority label is "this_month" rather than immediate action.
A persistent denial-of-service flaw in Google Android 14, 15, 16, 16-qpr2 and 17 lets code already running on the device crash or wedge one of several input-handling paths that fail to validate data properly (CWE-20). Because the vector is local, an attacker must first get code onto the phone - typically a malicious or compromised app - but then needs neither elevated privileges nor any user interaction to trigger a lasting availability impact; confidentiality and integrity are unaffected. The issue is rated CVSS 3.1 6.2, EPSS is 0.11% (1st percentile), there is no CISA KEV entry, and no public exploit code has been identified at time of analysis.
Local denial of service in Google Android 14, 15, 16, 16-qpr2 and 17 stems from improper input validation in multiple unspecified components, allowing a local unprivileged process to crash or destabilize the affected subsystem. The CVSS vector (AV:L/AC:L/PR:N/UI:N, availability-only, High) means an installed app or an attacker holding ADB/shell access can trigger it without additional privileges or user interaction, but only after already having a foothold on the device. Exploitation is not remote, no public exploit code has been identified at time of analysis, and EPSS is very low (0.11%, 1st percentile); the November 2026 Android Security Bulletin is the reference source.
Permanent denial of service in Google Android 14 through 17 (including 16-qpr2) can be triggered by crafted local input reaching parseKnownActivityEmbeddingCerts in ParsingUtils.java. The CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:N with high availability impact only, so an attacker able to supply input on the device needs no additional execution privileges and no user interaction. No public exploit was identified at time of analysis, KEV status is not indicated, and EPSS is 0.11% (1st percentile).
Local denial of service in Google Android 14, 15, 16, 16-qpr2 and 17 allows an already-installed application to crash the system launcher by publishing unauthorized shortcuts that exhaust launcher resources. The CVSS vector (AV:L/AC:L/PR:N/UI:N) means no additional privileges and no user interaction are needed once the attacker can execute code locally on the device, but the only consequence is an availability impact to the launcher - no confidentiality or integrity effect and no remote attack surface. Exploitation potential is constrained by that local-access prerequisite, EPSS is very low (0.11%, first percentile), and no public exploit has been identified at time of analysis.
Local denial of service in Google Android 16, Android 16-qpr2, and Android 17 lets code already running on the device impair availability by reaching functionality that lacks a required permission check in multiple locations, with no extra execution privileges or user interaction required. Severity is moderate (CVSS 6.2, availability-only) and the issue is not remotely reachable; EPSS is 0.11% and no public exploit has been identified at time of analysis. The Android Security Bulletin dated 2026-11-01 is the vendor reference.
A permission-control weakness in the HarmonyOS graphics module lets a locally present attacker read data that should be protected, with high confidentiality impact and no integrity or availability effect. Because the CVSS vector is local-only (AV:L) with no privileges or user interaction required (PR:N/UI:N), the realistic threat is a malicious or compromised app already installed on the device rather than a network-facing attacker. Exploitation status is unconfirmed: no public exploit code is known at time of analysis, CISA KEV does not list this CVE, and it is rated for attention this month rather than immediate action; the exact triggering interface and affected HarmonyOS versions are not described in the available sources.
An out-of-bounds write in MediaTek modem firmware lets a local actor crash or destabilize the modem on devices built on a long list of MediaTek chipsets, including MT6893, MT8768, MT6833, MT6990 and roughly 70 other parts. The defect is classified CWE-787 (incorrect bounds check leading to memory corruption) and is rated CVSS 6.2 with an availability-only impact (C:N/I:N/A:H); per the vector AV:L/PR:N/UI:N applies, so once local access to the device is obtained, no authentication or user interaction is required. Exploitation has not been observed (CISA SSVC exploitation: none, automatable: no) and no public exploit was identified at time of analysis; MediaTek has assigned patch ID MOLY01780439 in its November 2026 product security bulletin.
Out-of-bounds write in the GNSS (satellite positioning) component of MediaTek chipsets allows a local attacker with no additional execution privileges to crash or deny service on affected devices, with availability-only impact (CVSS 6.2, CWE-787). The issue affects chipsets MT6990, MT6890, MT6988, MT6880, MT6986, MT6982, MT6980D, MT2735 and MT2737 and is addressed by MediaTek Patch ID ALPS11309816 per the November 2026 Product Security Bulletin. No public exploit has been identified at time of analysis, and CISA SSVC records exploitation as none; the description states user interaction is needed, which limits unattended or remote abuse.
Reflected cross-site scripting in the Welcart e-Commerce plugin for WordPress (versions up to and including 2.12.6) lets remote attackers inject script into the payment error page generated by ESCOTT_MAIN::error_page_message through the unsanitized ResponseCd argument. The CVSS 4.0 vector indicates no privileges are required (PR:N) but the victim must interact (UI:P), since a crafted request or link has to be opened for the payload to execute, and impact is limited to low integrity/confidentiality effects within the page context. Version 2.12.7 fixes the issue by escaping the value with esc_html(); a public PoC reference exists but is not verified as working exploit code, there is no CISA KEV listing, and this is assessed as a moderate, genuinely low-urgency issue rather than a high-priority emergency, consistent with a this_month priority label.
Reflected cross-site scripting in the CREST framework's HTTP binding shipped in wrensec-commons lets an unauthenticated remote attacker execute arbitrary JavaScript in a victim's browser by luring them to a crafted URL. The HttpUtils.prepareResponse() method copied the _mimeType request parameter straight into the Content-Type response header, so a GET request carrying _mimeType=text/html makes an otherwise inert CREST JSON response be parsed and rendered as HTML, with the injected markup executing under the originating site's origin (CVSS 3.1 base 6.1, scope changed). Only deployments of the json-resource-http module below 22.6.2 or in the 23.0.0-M1 through 23.0.0 range are affected, and exploitation hinges on user interaction - the victim must open the attacker-supplied link; no public exploit code was identified at time of analysis, and patch releases 22.6.2 and 23.0.0 are available.
Path traversal (CWE-22) in Dell OpenManage Enterprise versions prior to 4.8.0 allows an attacker who already holds high-privileged console access and sits on an adjacent network segment to escape the intended restricted directory and reach filesystem locations, driving integrity and availability impact (CVSS 3.1: 6.1, AV:A/AC:L/PR:H/UI:N/C:N/I:H/A:H). The two compounding prerequisites - pre-existing administrative privilege and a position on the same logical network segment, typically the server-management or out-of-band network - are what bound real-world exposure to insiders or an actor who has already compromised the management network, rather than to arbitrary internet attackers. No public exploit has been identified at time of analysis, and the issue is tracked as a scheduled, this-month patch priority rather than an emergency.
Cross-site scripting in Dell OpenManage Enterprise versions prior to 4.8.0 allows an unauthenticated remote attacker to inject script that executes in the browser session of an operator or administrator who loads attacker-supplied content in the web console, potentially tampering with information viewed or acted upon in that session. The attacker needs network reachability to the console but no credentials (PR:N), while successful execution depends on victim interaction (UI:R) and non-trivial trigger conditions (AC:H); the specific page, parameter or feature that reflects the unneutralized input is not described in the available sources. No public exploit has been identified at time of analysis and the issue is not in CISA KEV; our assessment rates it a moderate-priority item (this_month) with scope-changed but low confidentiality and integrity impact and no availability impact, and Dell's advisory names upgrading to 4.8.0 as the remediation.
Dell OpenManage Enterprise versions prior to 4.8.0 contain a path traversal flaw (CWE-22) that lets a high-privileged attacker on an adjacent network segment write to and delete files outside the intended restricted directory, producing a high integrity and availability impact on the appliance (CVSS 6.1, AV:A/AC:L/PR:H/UI:N/C:N/I:H/A:H). Exploitation requires an already-authenticated administrative-level OpenManage Enterprise account and L2-adjacent placement (same management VLAN or broadcast domain), which markedly limits realistic exposure; there is no public exploit identified at time of analysis and the issue is not in CISA KEV. The vendor has published advisory DSA-2026-467 covering the fix in version 4.8.0.
Stored cross-site scripting in CloudClassroom-PHP-Project's manageassessment2.php allows remote unauthenticated attackers to supply crafted ExamName or Q1-Q5 values that execute script in a victim's browser when the page is viewed, with the CVSS 4.0 vector requiring user interaction. The issue is low severity (CVSS 2.1) and the supplied priority label is monitor; a public PoC reference exists, but it is not verified as working exploit code, and no KEV confirmation is present in the supplied intelligence.
Cross-site scripting in CloudClassroom-PHP-Project's updatedetailsfromfaculty.php allows remote attackers to manipulate the fname argument and inject script that executes when a victim loads the page where the value is rendered. The referenced advisory describes a stored-XSS condition, and a public PoC reference exists; it is not verified as working exploit code. No CISA KEV confirmation or EPSS score was supplied, and the assessed severity is low, with exploitation requiring user interaction and possible authentication ambiguity at the faculty detail-update endpoint.
Path traversal in deepset-ai FARM through 0.8.0 allows unauthenticated remote attackers to influence the vocab_filename argument of EmbeddingTokenizer.from_pretrained and read files outside the intended vocabulary location, with limited confidentiality impact and no integrity or availability effect; user interaction is required per the assessed vector. Exploitation depends on a host application passing attacker-influenceable input into vocab_filename, and a public PoC reference exists; it is not verified as working exploit code. The vendor did not respond, the project is unmaintained, and no vendor-released patch was identified.
Path traversal in the Knip developer CLI (Webpro-nl, versions up to and including 6.44.0) allows a crafted 'workspaces' value in a project's Knip configuration to escape the intended directory when the autofix writeFile routine in IssueFixer.ts is executed, overwriting or deleting files outside the project tree. The issue is rated 5.3 MEDIUM under CVSS 4.0 (CWE-22); exploitation is not passive, it requires a victim to run the autofix/IssueFixer path against a project whose configuration or repository content is attacker-influenced, making this a developer-workstation and supply-chain exposure rather than a service-facing remote flaw. No confirmed active exploitation (CISA KEV) is recorded, but a public PoC reference exists; it is not verified as working exploit code. The vendor was contacted about the disclosure and did not respond.
Warracker releases up to and including 1.0.3 mishandle authorization in their Paperless-ngx integration, letting any signed-in non-administrative user who owns at least one warranty link another user's private Paperless document to their own warranty and then download it, because the presence of a document ID on a warranty is treated as proof of ownership. Exploitation requires the optional Paperless-ngx integration to be enabled with a shared API token that can read the target document, and affects confidentiality only (private receipts, invoices and similar records) with no integrity or availability impact assessed. The vendor has fixed the flaw in 1.0.4; a public proof-of-concept walkthrough exists in the GHSA advisory, but it was validated against synthetic records and a mocked Paperless-ngx API rather than a live deployment, so it is not verified as working exploit code, and the issue is rated for this-month remediation rather than emergency action.
MoviePilot through 3.1.2 deserializes untrusted Python pickle data when restoring saved workflow execution context, and the workflow fork endpoint copied an attacker-supplied 'context' field from shared workflow payloads straight into that stored context, so a crafted shared workflow can trigger code execution on the instance that forks or later runs it. Exploitation requires an authenticated account with access to the Workflow feature (CVSS 4.0 PR:H in the supplied vector; the independently assessed 3.1 vector scores PR:L) and depends on the legacy Base64 pickle 'content' format being loaded by WorkflowExecutor.restore_context. A public PoC reference exists; it is not verified as working exploit code, no confirmed active exploitation (CISA KEV) has been reported, and the vendor has fixed the issue in 3.1.3.
Information disclosure in EchoHS GeekezBrowser through 1.8.0 lets any local process that can reach the application's localhost Public API read the /api/status response, because that endpoint served data without an authorization check and with a wildcard CORS origin. The exposure is local rather than remote, the leaked data is low sensitivity, and there is no integrity or availability impact, which keeps this at a low-to-moderate severity (CVSS 4.0 base 4.8). A public PoC reference exists in the project's GitHub issue tracker but is not verified as working exploit code; no CISA KEV listing was supplied, and the vendor has released 1.8.1 with a fix.
A stack-based buffer overflow in psqlODBC, the PostgreSQL ODBC driver, affects all releases before 18.00.0006 when updatable cursors are used - and they are enabled by default. The driver copies the server-supplied ctid (and oid, for tables with OIDs) value into a fixed 32-byte stack buffer using the server-declared length without validating it against the buffer size, so a value of 32 bytes or more overwrites adjacent stack memory; builds compiled with _FORTIFY_SOURCE abort instead. Reaching the flaw needs a specific attacker position: either a PostgreSQL server the client does not trust under its current SSL/TLS settings (malicious or man-in-the-middle server) or a database user able to create a view with its own column named ctid that the application then reads through an updatable cursor; the assessed vector (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) rates this medium severity with availability-only impact, and no public exploit or active exploitation has been reported.