Unbounded request-body reads in the ag-ui Java community server SDK (JdkAgentHttpHandler, used by applications that instantiate the two-argument handler constructors) allow a remote attacker to exhaust server heap memory by posting an oversized body - or a chunked body without a Content-Length header - to the agent context path, causing a denial of service. The issue affects ag-ui releases up to 2026-09-23 and is rated low-to-moderate (CVSS 4.0 base 5.3; our independent assessment CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L), with impact confined to availability and no confidentiality or integrity effect. No public exploit code or confirmed active exploitation was identified at time of analysis, and the handler's lack of built-in authentication means the practical privilege requirement depends on how each deployment fronts the endpoint; an upstream fix exists as pull request #2671 but is not yet merged/accepted.
Authentication bypass in Kaon AR2140X routers (firmware versions up to 4.2.17) allows unauthenticated attackers on the adjacent network to obtain a valid session cookie and access upgrade-related functionality, which can be abused to force the device to issue GET requests to arbitrary domains. The flaw requires local LAN or Wi-Fi adjacency (AV:A) and carries low confidentiality/integrity impact with no availability impact; no public exploit has been identified, and the status of firmware newer than 4.2.17 remains unknown.
mH-DEVELOPER smart home modules running firmware before 3.0.30 start up without loading any firewall rules, leaving SSH, HTTP, WebSocket, and Node-RED listening on the LAN with no access control, so any client on the same network segment can reach every service unauthenticated (CVSS 4.0 5.3; CVSS 3.1 AV:A/AC:L/PR:N/UI:N, low confidentiality and integrity impact). Exploitation requires network adjacency - the module is not reachable from the internet unless another device bridges access - and meaningful device takeover typically depends on chaining one of the sibling vulnerabilities covered by the same CERT-PL advisory. No public exploit identified at time of analysis, and the issue is a design/hygiene weakness (CWE-923) rather than a memory-corruption or code-execution flaw; the vendor fixed it in version 3.0.30.
Reflected cross-site scripting in multiple Dayforce Payroll endpoints lets an unauthenticated attacker craft a URL that, once opened by a logged-in payroll user, runs arbitrary JavaScript in that user's browser session. Confirmed only in Dayforce Payroll R2026.2.0, with applicability to other versions unverified because repeated attempts to reach the vendor were unsuccessful, and with no public exploit identified at time of analysis. The real-world risk is genuine but modest: exploitation is gated by a mandatory victim click (UI:A/UI:R) and impact is confined to the victim's browser session, with no server-side compromise - no CISA KEV listing and no evidence of active exploitation in the available data.
Authorization bypass in fuzui StudentInfo lets an authenticated remote attacker change another user's password by tampering with the sid/tid argument sent to the /StudentInfo/StudentHandler/moditypasswordstu endpoint, an insecure direct object reference (CWE-639) in the Password Change handler. The product ships as a rolling release, so no version boundary can be drawn and the affected set is effectively every deployment of the codebase up to commit fcc42a639ec7cef620651bfd0f07ebb660529e3f; the vendor was contacted early but never responded, and no public exploit code is identified at time of analysis. Scoring diverges sharply between sources: the vendor's CVSS 4.0 rating is 5.1 (medium) with all impacts rated Low and user interaction asserted, whereas our assessment rates the same issue as an unauthenticated-interaction, high confidentiality and integrity impact flaw (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L), so account-takeover risk should be treated as the governing concern rather than the vendor's medium score.
Malicious or compromised X servers can crash X clients linked against libX11 before 1.8.14 by supplying crafted byte-oriented codeset/locale data that triggers an out-of-bounds read in the client's codeset parser. The flaw is a client-side denial of service with only incidental memory disclosure, not code execution, and it works in the reverse of the usual trust direction: the server attacks the client, so exposure requires a victim application to open an X11 connection to an X server the attacker controls or has compromised (such as a hostile remote or forwarded display). The local attack vector and the requirement for an untrusted display keep realistic risk low; no public exploit code or confirmed active exploitation was identified at time of analysis, and vendor patches are available (upstream fix merged for the 1.8.14 release).
Unauthenticated physical attackers with access to a server's internals can exploit an improperly protected on-chip debug and test interface on the SMCU of Dell BOSS-N1 17G controllers (firmware prior to 2.2.13.2038) to gain unauthorized access, primarily threatening integrity. This is a low-priority, high-friction vulnerability requiring physical presence, high attack complexity, and user interaction, and no public exploit has been identified. Dell has released firmware version 2.2.13.2038 to address the issue.
Stored cross-site scripting in the Items Management Module of amirsanni Mini Inventory and Sales Management System allows an authenticated low-privileged user to inject script through the itemName argument in application/controllers/Items.php, which executes in another user's browser when the affected item page is viewed. The issue affects all versions under the project's rolling-release model (CPE wildcard), with no vendor response or released fix identified, and no public exploit code identified at time of analysis. Risk is integrity-focused client-side script execution requiring victim interaction; CVSS 4.0 scores it 5.1 while the 3.1 assessment is consistent with low-to-moderate real-world impact.
CPU-exhaustion denial of service in PyJWT versions prior to 2.14.0, where the lazy PEM-detection regular expression used by is_pem_format() backtracks without bound on certificate-like input containing repeated '-----BEGIN <label>-----' markers and no matching END marker. The flaw is reachable only through the key-preparation path (the key/secret material supplied to PyJWT for verification/signing), which in normal deployments is operator- or configuration-controlled; the assessed vector accordingly requires high privileges (PR:H) and a specifically crafted input (AC:H), and impact is limited to availability with no confidentiality or integrity effect. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), but a vendor fix exists and the issue was publicly disclosed, so unpatched instances should be upgraded promptly given the trivial resource-consumption nature of ReDoS bugs once a trigger is known.
Stored cross-site scripting in TPVEnlanube enables an authenticated backend user to store malicious JavaScript in the 'Apellido 1' field of the Joomla/VirtueMart administrator user-add endpoint '/administrator/index.php?page=admin.user_add&user_id=45&option=com_virtuemart'; the payload executes in the browser of a privileged user or administrator who later views the affected user record. The flaw is not self-triggering and requires two actors-an authenticated low-privileged account to store the payload and an administrator to render it-so the assessed impact is low-to-moderate, limited to script execution in the victim's admin session, with no public exploit identified at time of analysis and no direct server-side code execution.
Stored cross-site scripting in TPVEnlanube allows an authenticated user with access to the VirtueMart store administration function to persist arbitrary script through the 'vendor_store_name' parameter at the '/administrator/index.php?pshop_mode=admin&page=store.store_add&option=com_virtuemart&vendor_id=[ID]' endpoint; the payload then executes in the browser of any administrator or user who later renders the poisoned store record. Exploitation is high-friction: it requires valid backend credentials (CVSS PR:L), reachability of the store-management feature, and a separate privileged victim who opens the affected record (UI:A), which caps the realistic impact at low-confidentiality/low-integrity for the victim's session. No public exploit code has been identified at time of analysis and the vulnerability is not listed in CISA KEV; severity is low (CVSS 4.0 base 4.8).
Stored cross-site scripting (XSS) in TPVEnlanube, a Joomla/VirtueMart payment gateway extension, allows an authenticated attacker to inject malicious script into the 'Nombre Completo' field, which then executes in the browser of any privileged user viewing the VirtueMart administrator user-list page (admin.user_list). The vulnerability affects all versions of the extension (CPE wildcard) and requires the victim to interact with the page. No public exploit has been identified, and the overall risk is assessed as low-to-moderate due to the need for authentication and user interaction, with impact limited to browser-based script execution rather than server compromise.
In rhukster/dom-sanitizer versions prior to 1.0.15, a data: URL containing Base64-encoded active markup (for example data:text/html;base64,… or data:image/svg+xml;base64,… with an onload handler) survives the isDangerousUrl() check and is emitted intact inside href and xlink:href attributes of sanitized HTML/SVG/MathML, allowing a sanitizer bypass that turns sanitized output into an injection vector when the application renders it. Exploitation is unauthenticated by the sanitizer itself (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, assessed), but requires victim interaction - the victim must follow or trigger the surviving link - and is further constrained because modern browsers block top-level navigation to data:text/html URLs, which neutralizes the most common payload form; data: payloads consumed in other contexts (for example SVG <image> or embedded resource loading) remain more viable. There is no public exploit identified at time of analysis and no KEV listing; EPSS data was not provided, and the vendor has released a patched version.
Log-download path traversal (Zip Slip) in Dozzle before 11.1.2 allows attackers who control container display names to embed directory-traversal sequences such as '../../etc/cron.d/evil' into ZIP entry names, so that files are written outside the intended extraction directory when a user downloads and unpacks the log archive. The flaw affects the web log-download endpoint (/api/containers/.../download), which previously sanitized only the 'name' query parameter while writing unsanitized container names into archive entries; the assessed CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:H/A:N, 4.6 in the CVE's CVSS 4.0 scoring) reflects that exploitation requires an attacker who can name/label containers plus a legitimate user who downloads and extracts the archive with a traversal-unsafe tool, and the resulting integrity impact lands on the extracting user's machine (SI:H) rather than on the Dozzle server. There is no indication of active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, but a vendor patch is available: Dozzle 11.1.2 ships a sanitizeFileName helper that reduces entry names to alphanumerics, hyphens, underscores and dots and trims leading dots. Because the traversal is written into the archive rather than triggered server-side, this is a client-side/Zip Slip write primitive, not a direct remote code execution path against the Dozzle instance itself.
Replay of HMAC confirmation tokens in Zscaler MCP Server 0.7.0 and 0.7.1 lets an authenticated MCP client or agent reuse a confirmation token minted for one resource to authorize a destructive delete against a different resource of the same type. Because the affected delete handlers called check_confirmation() with empty parameters ({}), the resulting HMAC-SHA256 tokens carried no binding to the target resource identifier, making them fungible across 31 delete operations in the ZPA, ZIA, and ZTW service modules. The vendor addressed the issue by binding the resource identifier into the HMAC payload and shipping regression tests (including AST-based static analysis) in version 0.7.2; there is no KEV listing, and no public exploit identified at time of analysis, with the moderate CVSS score of 4.6 (AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L) reflecting that exploitation requires prior authenticated access, a legitimately issued token, and is limited to same-type resources.
Out-of-bounds memory access in Google Chrome's video codec handling - fixed in the 147.0.7727.55 desktop release - can be triggered when a victim loads a crafted video file, resulting in a bounded memory over-read that leaks limited process data rather than enabling code execution. The issue is network-reachable without authentication (CVSS PR:N) but strictly requires the user to load attacker-controlled media (UI:R), and CISA's SSVC assessment classifies it as non-automatable with only partial technical impact; no public exploit code identified at time of analysis and it is not listed in CISA KEV. With a CVSS base of 4.3 and Chromium's own rating of 'Low', this is a low-priority, routine-patching issue, notable mainly because Chrome's ubiquity makes even low-severity memory-safety defects worth closing promptly.
Path traversal in the Canonical LXD CLI image export and copy code (client/lxd_images.go) lets a malicious or machine-in-the-middle image server steer the filename used for a downloaded image outside the local destination directory via a crafted Content-Disposition header, allowing arbitrary local file overwrite that can lead to code execution as the invoking user. Affected releases are LXD 4.0.2 through 4.0.13, 5.0.x before 5.0.10, 5.21.x before 5.21.8, and 6.x before 6.10; exploitation requires the victim to actively run `lxc image export` or `lxc image copy` into a local directory while pulling from an attacker-controlled or intercepted remote (CVSS 3.1 base 4.2, AV:N/AC:H/PR:N/UI:R, unauthenticated network attacker but with required user interaction). No public exploit code has been identified at time of analysis, and the issue is publicly documented with vendor-released patches and upstream pull requests already merged.
Cross-site scripting (XSS) in Enocta Platform allows authenticated users to inject script into HTML attribute contexts, potentially modifying the appearance or behavior of pages viewed by other users. The flaw affects all versions through 2026-09-28 according to TR-CERT, and exploitation requires an authenticated account (PR:L) plus a victim who views the crafted content (UI:R), yielding only limited integrity impact (CVSS 4.1). No public exploit identified at time of analysis.