Sandbox escape in Mozilla Firefox's DOM Navigation component (CVE-2026-100758, CVSS 9.6) lets attacker-controlled web content escape the content-process sandbox and reach high-integrity resources on the host once a user loads a malicious or compromised page, ad, or embedded frame. The flaw requires no authentication or special privileges but does require the victim to visit the attacker's content (UI:R), and because the escape changes security scope (S:C) with high confidentiality, integrity, and availability impact, every pre-fix Firefox build - including the legacy ESR 115 branch - is exposed. No public exploit code or confirmed active exploitation was identified at time of analysis; Mozilla shipped fixes in Firefox 157, Firefox ESR 153.4, Firefox ESR 140.17, and Firefox ESR 115.42, so risk is concentrated in unpatched installs and in organizations that lag on ESR updates.
Sandbox escape in Mozilla Firefox allows remote attackers to break out of the content sandbox by exploiting a use-after-free in the browser's Disability Access (accessibility) APIs. Affected are Firefox versions before 157 and Firefox ESR versions before 153.4; the attack is network-delivered and requires no authentication, but is not zero-click - the victim must open attacker-controlled web content that exercises the accessibility APIs and win the use-after-free race (CVSS 3.1 9.6, AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H). Mozilla has fixed the flaw in Firefox 157 and Firefox ESR 153.4, and no public exploit has been identified at time of analysis; the score reflects the high confidentiality, integrity, and availability impact combined with scope change once the sandbox boundary is crossed, while the UI:R component keeps it from being self-propagating.
Use-after-free in Chrome's Views UI framework allows a remote attacker who convinces a victim to open a crafted HTML page to execute arbitrary code outside the browser sandbox on any Chrome desktop build prior to 154.0.8037.92. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6) confirms remote, unauthenticated attack with no special privileges, but also confirms that user interaction - social engineering to get the victim to load the page - is mandatory, which is the main limiting factor; the scope change (S:C) reflects that impact is not confined to the renderer. No public exploit was identified at the time of analysis and CISA's SSVC assessment rates exploitation as 'none' and not automatable, but a vendor patch is available from Google and the technical impact is total, making prompt updating the priority.
Use-after-free in Google Chrome's FullScreen implementation prior to 154.0.8037.92 allows a remote, unauthenticated attacker to execute arbitrary code outside the browser's renderer sandbox by enticing a victim to load a crafted HTML page. The vulnerability carries a CVSS 3.1 base score of 9.6 with scope change (S:C) and High confidentiality, integrity, and availability impact, reflecting that successful exploitation escapes the sandbox rather than being confined to a compromised renderer. No public exploit code and no confirmed active exploitation have been identified at time of analysis (SSVC Exploitation: none), and the attack is not automatable for mass exploitation because it requires the victim to visit attacker-controlled content (UI:R); Google has released a vendor patch in Chrome 154.0.8037.92.
Remote code execution outside the browser sandbox is possible in Google Chrome builds prior to 154.0.8037.92 through a use-after-free in the Passwords component, which a remote attacker can trigger by convincing a victim to open a crafted HTML page. Because the CVSS vector is PR:N/UI:R, no authentication or special configuration is required, but the victim must actively navigate to the attacker's content and a successful chain must also defeat the sandbox, leaving full compromise achievable but non-trivial. No public exploit code has been identified at time of analysis and CISA's SSVC assessment rates exploitation as none, while Google has released a vendor patch in Chrome 154.0.8037.92; the scope-change (S:C) rating reflects that a working exploit would escape the renderer boundary rather than remain confined to a single security context.
A use-after-free in Chrome's Views UI framework allows an unauthenticated remote attacker who convinces a victim to open a crafted HTML page to execute arbitrary code outside the browser sandbox in Google Chrome desktop builds prior to 154.0.8037.92. Per the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), no credentials or special browser configuration are required - default installations are affected - but exploitation depends on user interaction with attacker-controlled content and on overcoming the difficulty of turning a use-after-free into a reliable sandbox escape, so a working exploit is not trivial. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited; a vendor patch (154.0.8037.92) is available, which makes rapid update the decisive control.
Use-after-free in Mozilla Firefox's Preferences: Backend component before version 157 enables a sandbox escape, allowing attacker-controlled web content to break out of the browser's renderer sandbox and gain code execution with browser privileges; exploitation requires the victim to load attacker-controlled content (UI:R) with no authentication or special privileges (PR:N), and default configurations are affected. Mozilla addressed this in Firefox 157 via the mfsa2026-97 advisory, and while the CVSS 9.6/S:C scoring reflects a genuinely high-severity memory-corruption issue, no public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis.
Reflected cross-site scripting in Webmin versions prior to 2.650 lets an attacker execute arbitrary script - and through the resulting session context, attacker-chosen commands - in the browser of an administrator who clicks a crafted link to the server's own Webmin instance. The flaw lives in the filter_javascript() sanitizer used when the core 'message' parameter is rendered through ui_alert_box() in webmin/index.cgi; because the payload is reflected only into a victim's already-authenticated admin session, exploitation is targeted and social-engineering dependent rather than autonomous. Vendor-released patch: 2.650. No public exploit code has been identified and the issue is not in CISA KEV; EPSS is only 0.30% (20th percentile) and the CISA SSVC assessment records Exploitation: none, Automatable: no, Technical Impact: partial, so the practical urgency is materially lower than the 9.6 base score suggests.
A use-after-free in Mozilla Firefox's Widget:Gtk component enables a sandbox escape: an unauthenticated remote attacker who persuades a user to load attacker-controlled web content can corrupt freed heap memory in the GTK widget rendering path and cross the browser's security boundary (CVSS 9.6, AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), turning a rendering bug into code-execution-class impact outside the sandbox. GTK-based (Linux/Unix) Firefox builds are the primary target surface, and the flaw affects Firefox releases prior to 157 as well as the ESR branches prior to 153.4 and 140.17, where Mozilla has shipped the fix. No public exploit code has been identified at time of analysis, and CISA's SSVC decision framework rates exploitation as 'none' with automation rated 'no', although the assessed technical impact is total if the bug is successfully triggered; the principal hurdles are the required user interaction and the difficulty of reliably grooming a UAF into a working sandbox escape.
Sandbox escape in Mozilla Firefox stems from a use-after-free in the DOM: Core & HTML component, allowing attacker-controlled web content to corrupt memory and break out of the browser's content-process sandbox. Affected builds are those prior to Firefox 157, Firefox ESR 153.4, and Firefox ESR 140.17; the flaw carries a CVSS 9.6 rating (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) because the scope change (S:C) reflects escape from the renderer sandbox into the wider browser/OS context with high confidentiality and integrity impact. No public exploit code has been identified at time of analysis, and this CVE is not in CISA KEV; however, exploitation only requires a victim to load attacker-controlled content (UI:R) and needs no authentication or non-default configuration, so browser auto-update to a fixed build fully removes exposure.
Sandbox escape in Mozilla Firefox stems from improper boundary checks in the XPCOM component, allowing remote attackers to break out of the browser's content sandbox and compromise the host when a victim loads attacker-controlled web content. The flaw carries a CVSS 9.6 with required user interaction (UI:R) and no authentication (PR:N), affecting unpatched versions below Firefox 157, Firefox ESR 153.4, Firefox ESR 140.17, and Firefox ESR 115.42. No public exploit identified at time of analysis, and CISA SSVC records Exploitation: none, so this is a high-severity patching priority rather than a confirmed active threat.
A sandbox escape in Mozilla Firefox's Graphics: WebRender component lets attacker-controlled web content break out of the browser's content-process sandbox and reach the parent/broker process, with a 9.6 CVSS score driven by scope change plus high confidentiality, integrity and availability impact. Successfully triggering it requires an unpatched build and mandatory user interaction (PR:N, UI:R) - the victim must load or render a malicious page that exercises the WebRender path - and because the flaw sits in the rendering/sandbox boundary rather than in a directly reachable network service, realistic abuse typically depends on chaining it with a separate content-process compromise, which is consistent with SSVC rating Exploitation 'none' and Automatable 'no'. Fixed builds are Firefox 157, Firefox ESR 153.4, Firefox ESR 140.17 and Firefox ESR 115.42; there is currently no public exploit identified at time of analysis and EPSS is low at 0.16% (4th percentile), so exploitation signals are sharply split between the very high severity rating and the low likelihood evidence.
Sandbox escape in Mozilla Firefox's Graphics component allows unauthenticated remote attackers to break out of the browser's content sandbox when a victim renders attacker-controlled web content (CVSS vector AV:N/AC:L/PR:N/UI:R/S:C, score 9.6). Affected builds are Firefox before 157 and Firefox ESR before 153.4, 140.17, and 115.42, all of which now have vendor fixes available across their respective release trains. Exploitation requires chaining the escape with a separate content-process compromise to achieve code execution, which is consistent with CISA SSVC's 'Automatable: no' and 'Exploitation: none' ratings; EPSS is low at 0.16% (4th percentile) and no public exploit code has been identified at time of analysis.
Mozilla Firefox's Internationalization component contains incorrect boundary conditions that permit a sandbox escape, allowing an attacker who already has code execution inside the content process to break out of the browser sandbox. The flaw affects Firefox before 157, Firefox ESR before 153.4, and Firefox ESR before 140.17; exploitation requires a victim to load attacker-controlled web content (UI:R) and typically must be chained with a separate content-process memory-corruption vulnerability because this is not a direct remote code execution flaw. No public exploit code has been identified at the time of analysis, and EPSS is 0.16% (4th percentile), indicating low predicted exploitation activity despite the critical CVSS score of 9.6.
A sandbox escape in Firefox's XUL component allows attacker-controlled content to break out of the browser's security boundary and gain the privileges of the parent process, resulting in high confidentiality and integrity impact with changed scope (CVSS 9.6). Exploitation requires the victim to load or interact with attacker-controlled content (UI:R), but no credentials are needed (PR:N), and default Firefox configurations are affected; SSVC rates the issue non-automatable, so mass-scanning-style campaigns are unlikely. The flaw is fixed in Firefox 157 and Firefox ESR 153.4, no public exploit code or confirmed active exploitation has been identified at time of analysis, and EPSS is low (0.15%, 4th percentile).
Sandbox escape in Mozilla Firefox's Security: Process Sandboxing component allows an attacker to break out of the browser's content-process sandbox when a victim loads attacker-controlled web content, yielding full confidentiality, integrity, and availability impact on the host. The flaw is rated CVSS 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), unauthenticated (PR:N) but requiring user interaction (UI:R), and affects Firefox versions prior to ESR 153.4 and Firefox 157. EPSS is low at 0.15% (4th percentile) and no public exploit code has been identified at time of analysis, though CISA SSVC assigns total technical impact with no known exploitation.
Unauthenticated remote attackers can bypass a DOM:Security mitigation in Mozilla Firefox (versions before 157 and Firefox ESR before 153.4) by enticing a victim to load attacker-controlled web content, defeating a browser protection mechanism rather than exploiting a memory-safety bug directly. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, score 9.6) and a scope change indicate high potential confidentiality, integrity and availability impact once the defense is circumvented, but the independent assessment characterizes this as a weakening primitive: full impact generally requires chaining with a separate content-process vulnerability, so it is not a self-contained compromise. Exploitation signals conflict sharply - a critical-looking CVSS score against an EPSS of only 0.15% (4th percentile), a CISA SSVC rating of Exploitation: none / Automatable: no, and no public exploit identified at time of analysis; there is no confirmed actively exploited (CISA KEV) status.
Mitigation bypass in Mozilla Firefox's Bookmarks & History component lets attacker-controlled web content defeat a built-in browser security protection, weakening the defenses that normally contain malicious pages. The issue affects Firefox builds prior to 157 and Firefox ESR builds prior to 153.4, is reachable without authentication (PR:N) but requires the victim to load attacker-supplied content (UI:R), and is confirmed fixed by the vendor in Firefox 157 and Firefox ESR 153.4. Independent assessment rates the real-world consequence as limited (C:L/I:L/A:N) because bypassing the protection alone yields little damage and must be chained with a separate content-process vulnerability to reach the headline CVSS 9.6 impact; EPSS is 0.15% (4th percentile), there is no KEV listing, and no public exploit identified at time of analysis.
Authentication controls in the management protocol of HPE Networking Instant On access points (firmware ≤3.4.1.0) can be circumvented by an unauthenticated attacker who is adjacent to the device, resulting in a complete bypass of security restrictions and potentially remote code execution with elevated privileges. Exploitation requires only network adjacency - an associated Wi-Fi client, guest-network user, or any host on the same Layer 2 segment - with no credentials, no user interaction, and low attack complexity, which is why the CVSS 3.1 score reaches 9.6. No public exploit code and no confirmed active exploitation were identified at time of analysis, and devices already updated beyond firmware 3.4.1.0 are not affected.
Unauthenticated command injection in the CLI of HPE Networking Instant On access points allows an attacker on the same adjacent network segment - within wireless range or on the same link-layer/LAN - to send specially crafted packets and execute arbitrary commands as a privileged user on the underlying operating system. Any Instant On AP running firmware up to and including 3.4.1.0 in its default configuration is affected, and the scope change (S:C) in the CVSS vector means compromise of the AP can extend into the host OS and anything it can reach. At the time of analysis no public exploit code or active exploitation telemetry has been identified, but the CVSS base of 9.6, the zero-privilege, zero-interaction attack path, and the ease of obtaining adjacent-network access make this a genuinely high-priority, patching-urgent issue rather than a theoretical one. There is no public exploit identified at time of analysis.
Unauthenticated attackers on the same Layer-2/wireless broadcast domain as an HPE Networking Instant On access point can trigger a buffer overflow in an exposed interface and execute arbitrary commands on the device's underlying operating system. Firmware versions at or below 3.4.1.0 are affected, including default configurations, and the CVSS 3.1 base score of 9.6 reflects a scope change (S:C) from the network-facing interface to the AP operating system, with high confidentiality, integrity, and availability impact. The adjacency requirement (AV:A) is the primary limiting factor, confining realistic attackers to associated Wi-Fi clients, hosts on the local LAN, or anyone with physical proximity; no public exploit code and no CISA KEV entry were identified in the provided data, and no EPSS score was supplied, so exploitation is not confirmed as active at time of analysis.
Email authentication bypass in OpenDMARC up to 1.4.2 allows remote unauthenticated attackers to spoof sender domains by exploiting a misordered domain-setting sequence in the SPF Macro Handler, causing SPF-backed DMARC checks to evaluate the attacker-controlled HELO domain instead of the envelope MAIL FROM domain. Publicly available exploit code exists, though successful exploitation depends on the libspf2 version (some versions treat the first-set domain as the SPF check domain). This is a low-to-medium severity email-authentication flaw with no confidentiality or availability impact, only limited integrity impact.
DMARC authentication bypass in Trusted Domain Project OpenDMARC through 1.4.2 lets a remote attacker defeat the DMARC anti-spoofing check by supplying a multi-record DMARC TXT set that the Multi-Record Set Handler evaluates more permissively than RFC 7489 requires. The affected mail server must run OpenDMARC as its DMARC verifier and the attacker must control or influence DNS for the spoofed sender domain; no credentials or user interaction are required (PR:N/UI:N), though the resulting impact is limited to forged mail passing DMARC rather than host compromise. Publicly available exploit code exists, the vendor was contacted early and did not respond, and no vendor-released patch was identified at time of analysis.
Missing authentication in the Circleback webhook handler of MODSetter SurfSense (up to and including 2.0.3) lets any remote party who can reach the endpoint submit forged webhook payloads without credentials, yielding low-impact confidentiality, integrity and availability effects scoped to whatever that webhook processes. Exploitation requires the Circleback integration to be enabled and network-reachable; no user interaction is needed and publicly available exploit code exists, though there is no evidence of confirmed active exploitation. With a CVSS 4.0 base score of 6.9 (E:P) and no vendor response to the disclosure, this is a modest-impact but easily testable exposure that should be closed by removing or firewalling the endpoint.
Rebuild instances up to and including 4.4.7 and 4.5.0-beta5 expose a login endpoint (/user/login) that fails to properly validate authentication, allowing unauthenticated remote attackers to bypass the intended login control (CWE-287). Exploitation requires no credentials, no user interaction, and low complexity (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L), so any internet- or network-reachable Rebuild login page in its default configuration is a viable target. Publicly available exploit code exists and the vulnerability is documented by VulDB with a linked GitHub POC, but it has not been confirmed as actively exploited (not in CISA KEV); all impacts are rated Low, so successful abuse appears to yield partial access rather than full administrative takeover. The vendor was contacted but did not respond, and no vendor-released patch has been identified, making exposure reduction the primary near-term defense.
Integer overflow in OpenDMARC through 1.4.2 allows unauthenticated remote attackers to corrupt DMARC policy-percentage handling by supplying a crafted 'pct=' value in a DMARC DNS TXT record. Publicly available exploit code exists, but the vulnerability is not confirmed actively exploited (CISA KEV). Exploitation requires the target to be actively performing DMARC verification on inbound mail and the attacker to control a queried domain's DMARC record; assessed impact is limited to integrity of policy-percentage handling and minor availability disruption, not RCE or data disclosure.
Unauthenticated remote code execution in the Balbooa Forms extension for Joomla (versions before 2.4.3.4) lets a visitor submit a crafted public form that results in attacker-controlled PHP being evaluated server-side. The root cause is that the extension substitutes form-field shortcodes with the raw value submitted by the visitor before passing administrator-defined 'PHP after submission' code to eval(), allowing a value to break out of a double-quoted PHP string. Exploitation is conditional, not blanket: it requires an administrator to have enabled the optional PHP-after-submission action and to have interpolated an attacker-controllable field shortcode inside a double-quoted string, a non-default configuration reflected as AT:P. No public exploit code or confirmed active exploitation was identified at time of analysis, and no CPE string was supplied; the vendor scores this 9.5 (critical) whereas our independent CVSS 3.1 assessment is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
Missing authorization in REBUILD up to 4.4.11 allows unauthenticated remote attackers to manipulate the url or fileKey parameter sent to /commons/file-editor-save, enabling unauthorized read and write actions against the file-editor resource. Publicly available exploit code exists, but no fixed version has been published and the vendor did not respond to the disclosure. The issue is medium severity with low confidentiality, integrity, and availability impact; priority depends on whether the Rebuild web interface is exposed.
Improper authorization in the api-admin backend of realjerrytang tacomall 1.0.0 lets remote attackers create organization-staff records with attacker-controlled isAdmin and jobId values, bypassing the privilege checks that OrgStaffServiceImpl.add is supposed to enforce. Publicly available exploit code exists (a GitHub proof-of-concept walking through the crafted request), and the upstream advisory assigns a CVSS 4.0 score of 6.9 with an E:P (proof-of-concept) exploit-maturity rating; the flaw is not listed in CISA KEV, so there is no confirmation of active exploitation. Our independent assessment is more conservative on prerequisites and impact, rating the issue low priority: exploitation realistically requires at least a low-privileged authenticated session on the management API rather than anonymous access, and confidentiality, integrity, and availability impacts are all limited given the niche open-source codebase and small deployment base.
Session fixation (CWE-384) in Toptech Systems TMS7 and TopHat terminal management platforms allows an attacker to seed a chosen session identifier into a victim's browser/client and then reuse that same identifier after the victim logs in, effectively hijacking the authenticated session and gaining the victim's privileges on the fuel-terminal management application. The reported severity is CVSS 7.5 (CVSS v4.0), and the independent assessment rates confidentiality and integrity impact as high with high attack complexity, because success requires both successful session-ID seeding and the victim subsequently authenticating with that identifier. No public exploit code has been identified and the flaw is not listed as confirmed actively exploited (CISA KEV) at time of analysis, though ICS-CERT has published an advisory (ICSA-26-272-02) indicating OT/ICS relevance.
SQL injection in mahonelau kykms (rolling release up to commit 8f130c2d85842d5b44caae78cc46d65e505949f7) allows remote attackers to inject arbitrary SQL through the column argument of QueryGenerator.doMultiFieldsOrder, a multi-field ordering routine in the SqlInjectionUtil component. The flaw is CWE-89 improper neutralization of SQL commands and, because the injection lands in an ORDER BY clause, exploitation is typically limited to blind/boolean or error-based extraction rather than direct UNION dumping. Publicly available exploit code exists, but there is no CISA KEV confirmation of active exploitation at time of analysis. The provided CVSS 4.0 vector claims network reachability with no privileges (PR:N) and no user interaction, yet the independent assessment notes that JeecgBoot-style deployments commonly authenticate sortable data-query endpoints, so a valid session may be required in practice - verify against the specific kykms build.
CRLF injection in psyb0t/docker-mailbox before 0.4.13 allows a remote unauthenticated attacker to append arbitrary IMAP commands to the service's already-authenticated upstream mailbox connection when bearer-token authentication is not configured. Attacker-controlled folder, UID, or search values are passed into IMAP command construction without neutralization, yielding high integrity and availability impact on the mail store; the exposed path only exists on instances deployed without bearer-token auth, and no public exploit has been identified at time of analysis. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects a network-reachable, low-complexity, no-interaction flaw, though real-world risk is constrained by the non-default configuration requirement and the project's very small deployment base.
Unauthenticated SQL injection in Flowring Agentflow 4.0 allows any remote attacker who can reach the web interface to execute arbitrary SQL statements through the 'words' parameter of the /WebAgenda/SMBAjaxAutoComplete.do endpoint. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H, 9.3) and our independent CVSS 3.1 assessment (9.8-equivalent high confidentiality, integrity and availability impact) agree that exploitation requires no credentials, privileges, or user interaction - only network reachability and an instance built before the 2025/08/08 fixed release. No public exploit code or confirmed active exploitation was identified at time of analysis; the issue was reported by ZUSO ART and remains a high-priority target for rapid patching given its trivial, pre-auth exploitation profile.
Unauthenticated SQL injection in Flowring Agentflow 4.0 lets remote attackers run arbitrary SQL commands against the application database through the id parameter of the /WebAgenda/SMBAjaxConfigProcess.do endpoint, giving full read/write access to back-end data as returned by the vulnerable query. Only deployments running a build older than the 2025/08/08 fixed release and exposing the WebAgenda API to the network are affected; the CVSS 4.0 base score of 9.3 and the parallel CVSS 3.1 assessment (AV:N/AC:L/PR:N/UI:N, C/I/A:H) both reflect that no authentication, user interaction, or non-default configuration is required. No public exploit code has been identified at time of analysis, but the report originates from ZUSO ART and the endpoint is trivially reachable wherever WebAgenda is internet-exposed, so the practical risk for unsegmented deployments is high.
Remote code execution in Flowring Agentflow 4.0 is possible through the /WebAgenda/download/uploadFile.jsp endpoint, where authenticated low-privilege users can upload a file of dangerous type that the server then executes. Affected deployments are builds prior to 2023/03/24, and exploitation requires a valid application session but no victim interaction; no public exploit has been identified at time of analysis, though the technical impact is severe and warrants urgent patching.
The EVbee DC-80 firmware ships with a hardcoded root password, allowing unauthenticated remote attackers to log in via SSH and gain full control of the device. All units share the same static credential, which can be recovered from firmware analysis, and no special configuration is needed. This is a high-severity flaw (CVSS 9.3) with no public exploit code identified at time of analysis.
Disabled mall4j accounts (through 4.0) can indefinitely renew their sessions by calling POST /token/refresh, because the refresh flow issues a new token without re-checking the account's enabled flag, letting a user that an administrator deactivated retain the access they already had. The attacker must already hold a valid, non-expired refresh token obtained before deactivation, so this is an authenticated access-control persistence flaw (CVSS 5.3, CWE-613), not an unauthenticated bypass or a route to new accounts. Publicly available exploit code exists (a proof-of-concept Python script), but no active exploitation has been confirmed (not in CISA KEV), and the practical impact is limited to preserving prior access rather than escalating privileges.
Vertical privilege escalation in mall4j through 4.0 lets any self-registered storefront customer reach back-office administrative endpoints - including menu listings, file uploads, and configuration routes - by presenting the same sa-token session that was issued for the customer storefront. The flaw (CWE-287 improper authentication) is that the session validation layer never checks the sysType field that is supposed to separate customer from admin identity, so only endpoints already guarded by @PreAuthorize remain safe. Independently assessed at CVSS 5.3 with limited confidentiality and integrity impact, this is a genuine but moderate-priority privilege-escalation bug; publicly available exploit code exists, and there is no KEV-listed evidence of confirmed active exploitation.
Unauthenticated network attackers can exploit a directory traversal flaw in the file-upload feature of Hitachi Energy RTU500 Series CMU firmware to write or overwrite arbitrary files on the device filesystem, potentially modifying device data or disrupting operation. The issue has a CVSS 3.1 score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H), reflecting high integrity and availability impact with no confidentiality impact. This is a genuine high-priority issue rather than a high-CVSS-but-low-risk artifact, but no public exploit code or confirmed active exploitation was identified at time of analysis, and practical exposure is limited by the typical OT network isolation of RTU500 substation devices.
Unauthenticated remote code execution affects ModelTC LightLLM through version 1.2.0 when it is run in a multimodal deployment configuration, which starts an embed-cache RPyC service bound to all network interfaces with pickle deserialization enabled. Because the service performs no authentication and accepts attacker-controlled serialized objects through its exposed cache methods, any remote party that can reach the RPyC port can execute arbitrary code with the privileges of the LightLLM service (CVSS 4.0 base score 9.3; AV:N/AC:L/AT:N/PR:N/UI:N with high confidentiality, integrity, and availability impact). Exposure is configuration-dependent: non-multimodal deployments do not start this service, and instances whose port is bound to loopback or blocked by firewall rules on the host or network are not remotely reachable. No public exploit code has been identified at time of analysis, and the issue has been reported publicly by VulnCheck (also tracked in the project's GitHub issue #1596), so the primary risk is rapid weaponization against internet-facing multimodal inference deployments that have not been patched or isolated.
Remote code execution in LightLLM through 1.2.0 allows unauthenticated attackers to run arbitrary code on the host when the server is launched with the --enable_profiling flag, because that flag starts a router profiler service that exposes an RPyC listener with pickle deserialization enabled and no authentication (CVSS 4.0 base 9.3; CWE-502). The flaw is not reachable in a default deployment since profiling must be explicitly enabled, but once it is on, any network-reachable attacker can push crafted serialized objects onto the profiler command queue and gain high-integrity, high-availability code execution without credentials or user interaction (PR:N/UI:N). There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV, so exposure is currently driven by the non-default profiling configuration and network reachability of the RPyC port rather than by active exploitation.
Unauthenticated ONVIF service endpoints in Anjvision YSSD-RTMP-H5 cameras running firmware 3.3.2.4 fail to enforce authentication on management requests, letting any attacker who can route to the device invoke sensitive device operations directly. No credentials, user interaction, or non-default configuration are required - the CVSS v4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms this is a remotely reachable, unauthenticated flaw in the default request-handling path, and the independent assessment rates it a genuine high-priority issue with high confidentiality, integrity, and availability impact. Exploitation is limited only by network exposure (same LAN, VPN, or an internet-exposed/port-forwarded device); no public exploit code has been identified and there is no confirmed active exploitation (not listed in CISA KEV), though the CISA ICS advisory ICSA-26-272-05 documents the issue.
User-mode-to-kernel privilege escalation in Eclipse ThreadX lets a loaded, memory-protected TXM module register an arbitrary function pointer as the global trace-full callback, which privileged kernel code then invokes directly with no pointer validation and no privilege-dropping trampoline when the trace buffer wraps. Affected builds are those compiled with the non-default TX_ENABLE_EVENT_TRACE option and running modules in TXM_MODULE_USER_MODE with TXM_MODULE_MEMORY_PROTECTION; an invalid pointer crashes the kernel (denial of service), while a pointer into the module's own code has been observed executing with kernel privilege (CONTROL.nPRIV = 0), producing a scope-crossing compromise of the RTOS kernel by a local, low-privileged attacker. Exploitation requires the attacker to already control executing code inside a loaded module plus the non-default trace build flag, and no public exploit code has been identified at time of analysis.
An out-of-bounds write in Eclipse NetX Duo's WebSocket client allows unauthenticated remote attackers to corrupt NX_PACKET control block structures via a maliciously crafted masked WebSocket frame, potentially leading to code execution or denial of service. The vulnerability, tracked as CVE-2026-102761 with a CVSS 4.0 score of 9.3, affects all versions of NetX Duo per the CPE. No public exploit code has been identified at time of analysis, and no KEV status is reported.
A stack-based buffer overflow in the web management interface of the Shenzhen Dbit T-CPE301K 4G mini WiFi router allows an attacker who already holds a session on the device to crash the router and force a reboot by sending an HTTP POST to /js/common/do_cmd.js with an excessively long parameter. The published CVSS 4.0 score of 9.3 treats this as remote, unauthenticated, and full impact to confidentiality, integrity, and availability, but our independent assessment scores it under CVSS 3.1 as AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, i.e. an authenticated, availability-only denial-of-service, because exploitation requires network reachability to the management interface plus a valid session on the endpoint, and the confirmed outcome is a crash and restart rather than code execution. There is no CISA KEV listing and no public exploit code identified at time of analysis, and the practical risk is further limited by the small deployment footprint of this consumer/SOHO-class router; a vendor patch is available per the INCIBE advisory.
Authentication bypass in Dockhand before 1.0.40 allows unauthenticated remote attackers to force redeployments of git-backed stacks by sending unsigned webhook requests when a stack's webhook secret is null or unset; the guard fails open and accepts the request. The immediate impact is denial of service through repeated git clone and docker compose operations, while full host compromise is possible only if the attacker also has write access to the tracked git branch to inject a malicious docker-compose.yml with privileged bind mounts. No public exploit identified at time of analysis, and the independent assessment rates exploitation complexity as high for the RCE chain, with the DoS path requiring only network reachability and stack ID enumeration.
Command injection in the Node.js shell-quote library (formerly published as shell-quote on npm) allows an attacker who controls a string placed after a { comment } token to break out of the generated shell command and execute arbitrary shell input. The flaw affects the quote() function before version 1.11.0: a line terminator (\n, \r, U+2028 or U+2029) inside a later string terminates the '#' comment emitted for the comment token, causing the remainder of that string to be interpreted as shell syntax - for example quote(['echo','ok',{comment:'x'},'a\nid;#']) executes id under sh, bash, dash, ksh and zsh. It is also reachable through the quote(parse(untrustedCommand).concat(untrustedArg)) idiom, because parse() emits a mid-word comment token for inputs such as a URL fragment (http://example.com/#frag). This is a genuine command-injection flaw (CWE-78) in a foundational Node.js utility; the vendor CVSS 4.0 score of 9.2 reflects the potential for full shell execution, though our independent CVSS 3.1 assessment is AV:N/AC:H (the vulnerable calling pattern is a prerequisite and is not present in a bare default install). No public exploit was identified at time of analysis and the issue is not in CISA KEV; the upstream fix commit includes test cases that demonstrate the triggering payload shapes. Vendor-released patch: shell-quote 1.11.0.
Command injection as root in WatchGuard Fireware OS occurs through the BOVPN Over TLS client configuration handling, allowing whoever controls the remote TLS VPN peer to push malicious configuration data that the connecting Firebox executes with root privileges, compromising the appliance's confidentiality, integrity, and availability (CVSS 3.1 base 9.2, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). Exposure is conditional rather than blanket internet-facing: the Firebox must be configured as a BOVPN Over TLS client and must actively initiate a session to an attacker-operated or attacker-compromised server, so a successful attack implies a malicious or hijacked peer relationship rather than an opportunistic scan-and-exploit against any Firebox. No credentials on the Firebox are required (PR:N) and no interactive user action is needed once the client connection is made; there is no indication of confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis, though the confirmed root-level impact on a perimeter security device justifies treating this as a high-priority patch item.
Command injection in IBM Guardium Data Protection 12.2 allows an authenticated, highly privileged CLI user to execute arbitrary operating-system commands as root, escaping the restricted certificate-export shell (scope change) and fully compromising confidentiality, integrity, and availability. The flaw is CWE-78 (OS command injection) in the certificate export CLI path and carries a vendor CVSS 3.1 score of 9.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H). Exploitation is gated behind privileged CLI authentication, and no public exploit code or confirmed active exploitation has been identified at time of analysis; IBM has released a vendor patch.
Unauthenticated attackers able to reach the firmware-update endpoint of Hitachi Energy RTU500 series CMU devices can upload arbitrary firmware through a crafted POST request, gaining control over device functionality without any credentials or user interaction (CVSS 9.1, CWE-306). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so there is no public exploit identified at time of analysis, but the PR:N/UI:N vector means any reachable instance of the affected interface is directly exploitable. Because the impact is rated integrity-high and availability-high with no confidentiality impact (C:N), the realistic outcome is persistent unauthorized firmware that alters or disrupts the device rather than data theft.