Core
Monthly
Improper authorization handling in OPNsense core before 26.1.11 lets an authenticated low-privileged user (CVSS PR:L) bypass the user-config-readonly restriction and persist configuration changes through MVC APIs that rely on the throwReadOnly() guard. The flaw only triggers for accounts whose privileges are assigned directly: when a user is given both a component write privilege and user-config-readonly inside one comma-separated <priv> value, ACL::hasPrivilege() fails to detect the read-only flag through its exact string comparison, so the write is allowed; accounts receiving privileges through groups are unaffected. Impact is confined to configuration integrity for the affected component (I:H with C:N and A:L), no public exploit has been identified at time of analysis, and the vendor has shipped the fix in OPNsense 26.1.11.
Unauthenticated log injection in the OPNsense WebGUI login handler lets a network-adjacent attacker forge authentication events that manipulate the firewall's sshlockout protection state. Because the usernamefld parameter prior to version 26.1.11 passes carriage-return and line-feed characters through LOG_AUTH into the syslog-ng lockout pipeline, an attacker who can reach the login page can plant a fabricated failure event naming a victim IP, causing that address to be added to the sshlockout PF table and its active states killed, or plant a forged accepted event to reset their own brute-force counter and defeat password-guessing lockout. The flaw requires no authentication and no user interaction, but the assessed AV:A vector means exploitation presumes adjacency or management-network reachability to the GUI; impact is integrity of lockout state and availability of blocked systems (administrative, DNS, gateway, or monitoring addresses), with no confidentiality impact, and no public exploit or confirmed in-the-wild activity was identified at time of analysis.
Stored cross-site scripting in the OPNsense OpenVPN connection-status dashboard widget and status view lets an authenticated VPN client execute arbitrary JavaScript inside a firewall administrator's browser session, which the advisory demonstrates can read config.xml, invoke privileged APIs, reset the root password and ultimately obtain root command execution on the appliance. Exploitation is heavily gated: the OpenVPN server must be configured with username-as-common-name and a RADIUS or LDAP authentication backend, the attacker must be able to provision or self-register a backend username containing a double quote, a separate trust boundary must exist between the identity backend and the firewall (the local user database is unaffected because its username validator rejects quotes), and an administrator must open the affected dashboard or status page and trigger the injected handler - the demonstrated payload required pointer movement over the client row rather than unconditional page-load execution. Consistent with the CVSS vector (AV:N/AC:H/PR:L/UI:R) this is a low-privilege, high-complexity, admin-interaction-dependent issue; no public exploit code was identified at time of analysis, and the fix shipped in OPNsense 26.1.11.
Root-level code execution on OPNsense firewalls running versions prior to 26.1.11 is achievable by an authenticated operator who holds the 'Firewall Alias Edit' privilege and can point a GeoIP alias at an attacker-controlled source URL. The GeoIP importer's process_zip() and process_gzip() routines trust the CSV country_code field when building output filenames under /usr/local/share/GeoIP/alias, so a crafted value traverses out of that directory and writes attacker-controlled files as root; chaining a planted newsyslog fragment with an oversized log file then lets the default hourly root cron job execute the payload, yielding complete firewall compromise (CVSS 9.9, AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). No public exploit code and no confirmed active exploitation were identified at time of analysis, and exploitation requires a non-default alias configuration that the operator must supply.
Authenticated XPath injection in the OPNsense firewall and routing platform (all versions prior to 26.1.10) lets a user holding CA Manager or Certificate Manager privileges recover values stored in config.xml character by character. The Trust module stores attacker-controlled certificate and CA refid values and interpolates them unescaped into XPath queries in CAsField.php and CertificatesField.php; because the resulting refcount/in_use boolean is returned to the requester, it acts as a blind injection oracle for secrets such as password hashes, API credentials, certificate private keys, VPN key material, and high-availability credentials, which in turn can enable privilege escalation and compromise of other security domains. Exploitation is post-authentication, requires those specific trust-management privileges, and is high-complexity and iterative (roughly one boolean leak per request), so this is a genuine but second-tier information-disclosure issue rather than a drive-by remote compromise; no public exploit code has been identified at time of analysis. Vendor-released patch: 26.1.10.
Untrusted-link activation inside an Ionic Capacitor app on Android or iOS can render attacker-controlled HTML at the application's own origin via the internal /_capacitor_http_interceptor_ proxy path, giving that script full same-origin access to storage, cookies and registered Capacitor plugin capabilities. Affected releases are 6.0.0 up to (but not including) 6.2.2, 7.6.9, 8.3.5, 8.4.3 and 8.5.1; exploitation requires the victim to activate an attacker-supplied link in the WebView (UI:R) but no authentication (PR:N) and no non-default feature flag, so apps are exposed even when the CapacitorHttp plugin is disabled because vulnerable builds serve the proxy path regardless of that setting. No public exploit code or confirmed active exploitation was identified at time of analysis, though the high CVSS score of 9.3 (S:C/C:H/I:H) and the broad mobile install base make patch urgency high.
Local privilege escalation in Kiteworks Core lets an attacker who already holds code execution as an unprivileged backend service account invoke a privileged routine that mishandles attacker-influenced input, running arbitrary OS commands as root. The flaw requires a prior local foothold on the appliance - the CVSS vector (AV:L, PR:L, UI:N) confirms it cannot be reached directly over the network and demands an existing initial compromise or misconfiguration to obtain the service account. No public exploit code or active exploitation is identified at time of analysis, and the realistic risk is bounded by how easily that initial service-account access can be obtained on a given deployment; the vendor's advisory is GHSA-658c-86vw-g9hf.
Local privilege escalation in Kiteworks Core lets an attacker who already has code execution as an unprivileged backend service account on the appliance obtain root. A privileged, root-owned routine consumes a filesystem path that the lower-privileged service account can influence, so the attacker can steer that root operation into executing arbitrary commands with full privileges (CWE-59 link-following / unsafe path handling). The attack is local-only (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8) and is a second-stage primitive requiring an existing foothold; no public exploit was identified at time of analysis and the CVE is not reported as confirmed actively exploited (CISA KEV), though the 7.8 severity and availability of a vendor advisory make prompt patching advisable.
Command injection in Kiteworks Core lets an authenticated administrator with elevated privileges run arbitrary operating-system commands as root on the affected appliance node, so an admin-only function can be turned into full host compromise. The flaw is remotely reachable and needs no user interaction (CVSS:3.1/AV:N/AC:L/PR:H/UI:N, base score 7.2), but PR:H is the dominant limiting factor: no unauthenticated or low-privilege path is indicated, so practical exploitation presupposes an insider or stolen high-privilege administrative credentials. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV, keeping real-world urgency moderate and dependent on the value of the credentials required.
Unauthenticated attackers who know a target's email address can take over Kiteworks Core accounts that use locally stored passwords - including administrative accounts - by abusing insufficient parameter validation in the password reset workflow, which lets them bypass the emailed reset-link step and set a new password themselves before authenticating as that user. The flaw is classified CWE-640 (weak password recovery mechanism) and scores CVSS v3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication, no user interaction, and no non-default configuration are required; any internet-reachable Kiteworks Core instance hosting local-password accounts is exploitable. Independent assessment rates this a genuine top-priority issue rather than a high-score-but-low-risk case. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, but the pre-authentication, low-complexity nature warrants urgent action.
OS command execution in Kiteworks Core is possible when the remote-support capability is licensed and enabled and an authenticated System Administrator also possesses the key protecting submitted data, allowing that administrator to redirect the outbound support connection to an attacker-chosen destination that can then execute OS commands with local service account privileges. The CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, so exploitation requires high application privileges plus the additional key-possession condition, and deployments without remote support enabled are not exposed; there is no public exploit identified at time of analysis and no CISA KEV indication. The independent assessment rates real-world priority low-to-medium despite the 7.2 High base score.
Local privilege escalation in Kiteworks Core allows an attacker who already holds a shell under a low-privileged service account to elevate to root on the appliance, gaining complete control of the system and the sensitive content it brokers. The weakness is a link-following issue (CWE-59) in a root-privileged operation, reachable with local access as the service account (CVSS:3.1/AV:L/AC:L/PR:L/UI:N), no user interaction, and no non-default configuration, making it a realistic second-stage escalation after a separate initial-access compromise. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the CVE is not associated with a KEV listing; the primary limiting factor is the prerequisite service-account foothold, while the primary risk is full root compromise of the appliance.
Command injection in Kiteworks Core's internal cluster-management function allows an attacker who already has code execution on one node of a clustered deployment to run operating system commands with elevated privileges on other nodes in the same cluster. The vulnerable function is not reachable from outside the cluster, so the attack path is confined to the internal cluster network and requires a pre-existing foothold on a cluster member; single-node deployments are not exposed. Rated CVSS 8.8 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) with scope change reflecting cross-node impact, and no public exploit identified at time of analysis.
Unauthenticated path traversal in the Kiteworks Core appliance setup interface allows an attacker who can reach that interface to write a file to any location writable by the appliance service account, enabling integrity compromise of the appliance or a denial-of-service condition that persists until an operator intervenes. The exposure is narrow: the setup interface is not reachable on a fully configured appliance in its default configuration, so exploitation is realistically limited to the transient provisioning window of a new appliance or a non-default configuration that leaves setup exposed, which is why AC:H applies despite PR:N and UI:N (CVSS 7.4). No public exploit code and no confirmed active exploitation were identified at time of analysis, and the flaw does not by itself provide code execution.
Sandbox escape in Kiteworks Core's document-conversion feature (CVE-2026-102125, CVSS 8.8) allows code already executing inside the conversion sandbox to break confinement and act with the privileges of the application service account, enabling reads or modifications of application data and configuration or disruption of the service. Exploitation is conditional: the attacker must first get code running inside the sandbox, typically by submitting a crafted document for conversion, and the CVSS vector (AV:L/PR:L/UI:N/S:C) confirms a local, low-privilege prerequisite with no user interaction once that foothold exists. No public exploit code has been identified at time of analysis, making this a genuine but conditional integrity and availability risk rather than a mass-exploitation threat; a vendor-released patch is documented in Kiteworks advisory GHSA-58j2-hj9r-c258.
Stored cross-site scripting in Kiteworks Core allows an administrator holding only a single narrowly scoped delegated permission to plant crafted content that later executes as JavaScript in the authenticated session of a higher-privileged System Administrator, enabling the lower-privileged attacker to escalate to full tenant administrative control and create a new administrative account. The flaw is tracked as CVE-2026-102126 with a vendor CVSS 3.1 score of 8.1 (AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N) and is rated high severity under CWE-79. Exploitation requires an authenticated admin with the delegated permission (PR:H) and depends on the victim System Administrator viewing the affected page (UI:R); no public exploit code has been identified at time of analysis, and the issue is not in CISA KEV.
Privilege escalation in Kiteworks Core allows a delegated administrator whose scope includes role changes to promote an account to full system-administrator through the user-provisioning interface, which fails to verify that the requester is entitled to grant the role being assigned (CWE-266). The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, 7.2 High) confirms the flaw is network-reachable but requires high-privileged, delegated-admin credentials and no user interaction, so anonymous or ordinary-user accounts cannot exploit it and environments without scoped admin roles have no trust boundary to cross. No public exploit identified at time of analysis and no KEV listing; independent assessment rates this a genuine but low-to-medium operational priority rather than a high-urgency issue.
Privilege escalation in Kiteworks Core versions before 9.5.1 allows an authenticated delegated administrator holding only a single narrowly scoped administrative permission to obtain full system administrator privileges by abusing the administrative import function for integration credentials, which fails to verify that the requesting administrator is entitled to create the privileged credential being imported (CVE-2026-102132, CVSS 7.2 High). The attacker must already possess a valid delegated-admin account (PR:H), so this is an insider or lateral privilege-escalation issue rather than an unauthenticated internet-facing takeover, and no action by an existing system administrator is required for the escalation to succeed (UI:N). A vendor patch is available in Kiteworks Core 9.5.1; no public exploit code or confirmed active exploitation has been identified at time of analysis.
Deserialization of untrusted data in Kiteworks Core before 9.5.0 can escalate to remote code execution on the appliance, but only as a secondary, chained weakness rather than a standalone attack. The issue is not exploitable in isolation: an attacker must first obtain a way to influence the data that Core deserializes, which in practice means chaining a separate flaw (for example one of the file-write or injection issues in the same CISA CSAF batch, va-26-274-01) or leveraging an existing foothold. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, and although the base score is 8.1, the local/config-adjacent reachability (AV:L), high attack complexity (AC:H) and the mandatory data-influence precondition materially lower real-world risk; the CVSS vector indicates no privileges are required (PR:N), but exploitation is not remotely self-contained.
Server-side template injection in the Kiteworks Core appliance allows an authenticated System Administrator to store a crafted system-notification template whose embedded template-engine expressions are evaluated when the notification is next rendered, resulting in operating-system command execution on the appliance. Exploitation requires a high-privileged admin account (CVSS vector PR:H, UI:N) and has a timing dependency because the payload only fires when the affected notification is triggered, making this a malicious-insider or compromised-admin scenario rather than a perimeter-reachable RCE. No public exploit code and no confirmed active exploitation were identified at time of analysis; the vendor-assigned CVSS 3.1 score of 7.2 (C:H/I:H/A:H) reflects full compromise of confidentiality, integrity, and availability once the template is rendered.
Stored cross-site scripting in Kiteworks Core before version 9.5.0 allows an authenticated user with only low privileges to submit content that executes arbitrary JavaScript in the browser session of any other user who later views it, potentially enabling full account takeover of higher-privileged users such as administrators. The issue scores 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N = High) because a successful attack crosses the browser privilege boundary into the victim's session, yielding high confidentiality and integrity impact while availability is unaffected. No public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation is constrained by two prerequisites: the attacker must already hold a valid low-privileged account, and a second user must subsequently render the stored payload in the web UI.
Stored cross-site scripting in Kiteworks Core (all versions prior to 9.5.0) enables unauthenticated attackers to persist malicious JavaScript that executes in an administrator's browser session when the poisoned page is viewed. Successful exploitation could grant the attacker full administrative control, including creating new admin accounts, as reflected by the CVSS 9.3 score (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N). The primary limiting factor is the required user interaction-an administrator must actively view the affected page-and no public exploit identified at time of analysis.
OS command injection in Kiteworks Core appliances running versions before 9.5.0 allows an authenticated administrator to upload a configuration package whose contents are not sufficiently validated, resulting in arbitrary operating-system command execution that may run with elevated privileges on the underlying appliance. The attack requires a valid administrator account with access to the configuration-package upload functionality in the administrative interface (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, 7.2 High), so the high-privilege prerequisite is the dominant constraint and the realistic scenario is a malicious, compromised, or coerced administrator rather than opportunistic unauthenticated remote exploitation; the assessed vector is internally consistent and concurred with. No public exploit code and no confirmed active exploitation were identified at time of analysis, and successful exploitation yields full compromise of confidentiality, integrity, and availability on the affected appliance.
Arbitrary file write in Kiteworks Core before 9.5.0 lets a holder of an existing administrative account steer the platform's administrative export feature to write files to any path on the underlying host, which can be chained into command execution on the appliance. The root cause is an improper restriction of a user-supplied file path (CWE-22), scored CVSS v3.1 7.2 with vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, so the flaw is not reachable by unauthenticated or standard users and command execution is a downstream consequence of the write rather than a guaranteed outcome. No public exploit code and no confirmed active exploitation (no CISA KEV listing) were identified at time of analysis; the primary constraint on real-world risk is the high-privilege prerequisite.
Improper privilege management in Kiteworks Core before 9.5.0 allows an authenticated administrative user who holds only limited, non-Sysadmin role-management permissions to grant another account full system-administrator (Sysadmin) rights that the grantor was never authorized to confer. The flaw sits in the role-assignment logic, which fails to constrain grantable privileges to the subset the granting administrator actually possesses, so a single delegated-admin session is enough to escalate a chosen account to the highest privilege level. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, score 7.2) the attack is network-reachable with no user interaction but requires an already-authenticated high-privilege session; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (not in CISA KEV). This is best characterized as a genuine but access-gated integrity risk whose real-world exposure depends on how many delegated administrators exist in a deployment and how tightly their role scopes are managed.
Stored cross-site scripting in Kiteworks Core allows an authenticated user to store crafted content that executes arbitrary JavaScript in another user's authenticated session when that victim previews the shared content, potentially enabling session compromise or account takeover. Affected deployments are Kiteworks Core versions before 9.5.0, and exploitation requires a valid platform account plus victim interaction with the preview rendering path. No public exploit code or CISA KEV listing has been identified at time of analysis, and the independent assessment classifies this as a moderate-priority, contingent-risk finding rather than an urgent one.
Stored SQL injection in Kiteworks Core before 9.5.0 allows an authenticated administrator to read sensitive data from the underlying database and to degrade availability of the service. Exploitation is only reachable through the affected administrative reporting feature and requires an existing, authenticated administrative account (CVSS:3.1/AV:N/AC:L/PR:H/UI:N), so the flaw is not exposed to unauthenticated or low-privileged users; no public exploit code has been identified at time of analysis, and no CISA KEV entry or EPSS score accompanies this CVE. Our independent assessment rates the issue at moderate priority: confidentiality and availability impact are high, but integrity impact is limited (C:H/I:L/A:H), and the mandatory full administrative privilege sharply narrows the realistic attack surface to trusted insiders or attackers who have already compromised an admin session.
Incorrect authorization in Cheshire Cat AI's GET /memory/collections/{collection_id}/points endpoint allows any authenticated user holding MEMORY:READ permission to retrieve episodic memory records belonging to all other users by paginating through the collection via the offset cursor. The route implementation in core/cat/routes/memory/points.py omits per-user scoping when querying the vector store, exposing stored conversation histories and personal data across the entire tenant base. No public exploit or CISA KEV listing has been identified at time of analysis.
OS command injection in Liman server management software (limanmys/core) before version 2.2.2 - 1103 lets an authenticated administrator run arbitrary operating-system commands on the host via the log rotation configuration endpoint. The unsanitized `ip_address` parameter is concatenated into a shell command, allowing single-quote shell-escape to break out and execute attacker-controlled commands. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; it is fixed in 2.2.2 - 1103.
Denial of service in NextAuth.js's getToken() helper allows unauthenticated remote attackers to crash any API route, middleware, or server-side handler that calls getToken() directly by sending a single HTTP request with a malformed Authorization: Bearer header containing invalid percent-encoding. The vulnerability affects next-auth 4.0.6-4.24.14, next-auth 5.0.0-beta.0-5.0.0-beta.31, and @auth/core 0.1.0-0.41.2, and is fixed in next-auth 4.24.15, next-auth 5.0.0-beta.32, and @auth/core 0.41.3. No public exploit code has been identified at time of analysis, but the trigger condition is trivially constructible from the public advisory description alone.
The Home Assistant iOS Companion app silently executes tag-triggered automations when any co-installed untrusted app forwards a crafted tag event via iOS universal links, bypassing physical scan validation entirely. Affected versions are all iOS Companion app releases prior to 2026.5.0; the underlying Home Assistant core CPE (cpe:2.3:a:home-assistant:core:*:*:*:*:*:*:*:*) is also cited. Because automations can control physical devices such as smart locks and alarms, the I:H CVSS metric reflects real-world consequences beyond software state. No public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Silent automation execution in the Home Assistant Android Companion App prior to 2026.8.1 allows any co-installed app on the device to trigger arbitrary HA automations by forwarding a crafted tag URL to an exported Activity without user confirmation. The flaw exists because TagReaderActivity accepted both physical NFC intents and OS-routed deep links identically, with no caller validation or approval prompt before dispatching the tag scan to the Home Assistant server. No public exploit has been identified at time of analysis, but the attack is unattended and can control physical actuators such as locks or alarms.
Unsandboxed Twig template rendering in Bolt CMS allows any user holding an editor-level CMS role to inject arbitrary OS commands via Server-Side Template Injection (SSTI), achieving remote code execution as the web server process. The root cause is that Bolt's Twig environment never registers a SandboxExtension, so the full Twig filter chain - including dangerous filters like `passthru` - is available to content authors. The default out-of-the-box configuration of the 'pages' content type ships with `allow_twig: true`, meaning this is exploitable in a standard Bolt installation without any additional misconfiguration. No public exploit has been independently confirmed, though the CVE description includes a working payload demonstrating command execution.
Remote code execution in REDAXO CMS versions 5.18.2 through 5.21.0 is reachable by authenticated backend users with media upload permissions via a multi-segment filename bypass (e.g., shell.php.any.jpg) that defeats the extension blocklist in rex_mediapool::isAllowedExtension. The flaw is a confirmed regression introduced in PR #6213 (February 2025), which replaced a historically correct str_contains guard with weaker str_ends_with logic, reintroducing a double-extension attack class that the codebase had explicitly defended against since 2018. Exploitation additionally requires the target server to run a multi-extension PHP handler (Apache mod_mime AddHandler or unanchored FilesMatch); no public exploit or CISA KEV listing has been identified at time of analysis, and the vendor-released fix is available in version 5.21.1.
Sensitive token disclosure affects the Home Assistant iOS companion app prior to 2025.5.0, where the app ignores the configured SSID allowlist meant to gate internal-network access. Because the app falls back to the internal URL whenever no other URL is available, it can transmit the user's authentication token to the internal endpoint while the device is connected to an untrusted or insecure Wi-Fi network, enabling interception. No public exploit has been identified at time of analysis, and the issue is not in CISA KEV; vendor advisory GHSA-cm5v-547m-qh5h confirms the fix in 2025.5.0.
Location spoofing in the Home Assistant Android companion app prior to 2026.5.3 allows any co-installed application - even one with zero runtime permissions - to forge the device's reported GPS position by broadcasting a crafted Google Play Services LocationResult to an unprotected exported BroadcastReceiver. The forged coordinates are forwarded to the user's Home Assistant server as the device's real location, defeating Android's developer-mode Mock Location gate and enabling abuse of zone-based automations such as unlocking doors, disarming alarms, or opening garages. No public exploit identified at time of analysis, and the issue is patched in 2026.5.3 by unexporting LocationSensorManager and introducing a thin RequestAccurateLocationReceiver proxy that drops attacker-supplied extras.
Cross-origin JavaScript injection in Home Assistant Companion apps for Android (before 2026.4.4) and iOS (before 2026.4.1) allows a malicious iframe loaded inside the app's WebView to execute arbitrary JavaScript in the Home Assistant frontend's origin and steal the signed-in user's access token. The flaw stems from exposing the native JavaScript bridge (window.externalApp on Android, webkit.messageHandlers.getExternalAuth on iOS) to all frames combined with unsanitized callback identifier interpolation. No public exploit identified at time of analysis, and the issue is not in CISA KEV.
Authentication bypass in UltraDAG Core blockchain allows remote unauthenticated attackers to drain all pocket-derived sub-addresses on smart accounts, completely bypassing vault delays and daily spending limits. The StateEngine fails to resolve pocket addresses to their parent account during policy enforcement, treating virtual pocket addresses as unrestricted accounts. Confirmed actively exploited (CISA KEV). Vendor-released patch: commit fb6ef59 resolves pocket-to-parent mapping before all policy checks. EPSS data unavailable but attack vector is network-accessible with no complexity (CVSS 4.0 AV:N/AC:L/PR:N), making this a critical priority for any UltraDAG deployment using smart account pockets.
LDAP filter injection in OPNsense firewall allows unauthenticated attackers to enumerate valid LDAP usernames and bypass group membership restrictions via the WebGUI login page. Affects OPNsense versions prior to 26.1.6. The vulnerability stems from failure to escape user-supplied input before insertion into LDAP search filters, enabling metacharacter injection. Attackers can authenticate as any LDAP user with known credentials, circumventing Extended Query group membership controls. No public exploit identified at time of analysis.
An access control vulnerability exists in Kiteworks Core versions 9.2.0 and 9.2.1 that allows authenticated users to access unauthorized content within the private data network. With a CVSS score of 8.8 (High), an attacker with low-level authenticated access can potentially access, modify, or delete sensitive data they should not have permissions to view. No public proof-of-concept or active exploitation (KEV listing) has been reported at this time.
A remote code execution vulnerability in MobileIron Core & Connector versions 10.3.0.3 and earlier, 10.4.0.0, 10.4.0.1, 10.4.0.2, 10.4.0.3, 10.5.1.0, 10.5.2.0 and 10.6.0.0; and Sentry versions 9.7.2. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Stored cross-site scripting in OPNsense core prior to 26.1.11 lets a user who holds the page-system-certmanager privilege inject HTML metacharacters into a certificate description field, and that markup is later rendered unescaped in the SSL Certificate selector on System Settings > Administration, executing in the browser session of any other user who opens that page. Exploitation requires a multi-user deployment and deliberate victim interaction (CVSS 3.1 base 5.2, Medium; vendor vector AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N, with the independent assessment treating the impact as scope-changing and limited to low confidentiality/integrity), and the attacker must already be authenticated with a high-privilege account. No confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; the flaw is resolved by upgrading to OPNsense 26.1.11.
Stored cross-site scripting in the NTP GPS configuration page of OPNsense (FreeBSD-based firewall/router platform) lets an authenticated user who holds the page-services-ntp-gps privilege persist a malicious initcmd value that closes the GPS textarea and injects script into the page. The payload executes in the browser session of any user - including an administrator - who later opens that page, letting the script read CSRF material and perform authenticated actions with the victim's privileges, which is why the CVSS vector assigns a changed scope (S:C). Affected are OPNsense core builds prior to 26.1.11; the flaw is fixed in 26.1.11, no public exploit was identified at time of analysis, and exploitation requires both a privileged operator account and a second user (UI:R) visiting the page.
Authenticated OPNsense users who hold at least one affected module privilege can supply a crafted safe-delete token that is interpolated into an XPath query over config.xml, letting them read configuration metadata from modules they are not authorized to access. The flaw, tracked as CVE-2026-58395, affects OPNsense releases prior to 26.1.11 and yields a substring-presence oracle that leaks configuration item names, descriptions, reference paths, and UUIDs, though it cannot modify configuration or delete data. It is a read-only information-disclosure issue rated 4.3 medium; no public exploit code identified at time of analysis, and CISA KEV does not list it.
A path traversal in OPNsense's OpenVPN Client Specific Override (CSO) handling allows an authenticated user holding CSO privileges to store a traversal sequence such as '../' in the common_name field, which openvpn_csc_conf_write() concatenates into the target path /var/etc/openvpn-csc/<vpnid>/<common_name> without normalization or a basename check; when a matching OpenVPN client-connect or authentication event is later processed by client_connect.php or user_pass_verify.php, a generated CSO configuration file is written outside the intended directory. Exploitation is constrained: the attacker must first have operator-level CSO access and must cause a matching common name or username to be processed, and the written content is generated OpenVPN configuration rather than arbitrary attacker-controlled bytes, which limits achievable impact - there is no public exploit identified at time of analysis. The issue is rated medium severity (vendor CVSS 5.9, independent assessment CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L) and is fixed in OPNsense 26.1.11.
Stored cross-site scripting in OPNsense core before 26.1.11 allows a user holding Firewall Categories or Firewall Alias Edit privileges to plant script that executes in the browser session of an administrator or other operator who opens the Firewall Rules or NAT page. The injected code runs with the victim's context, can read CSRF tokens, and can therefore perform authenticated actions on the firewall as that victim. Exploitation is not anonymous - it requires the attacker to already possess category or alias editing rights (PR:L, CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, base 5.4), and the malicious category must be attached to a rule or the alias referenced as a rule source/destination and saved so the tooltip renders; no public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited in CISA KEV. Fixed in OPNsense 26.1.11.
Cheshire Cat AI core through 2.0.23 is affected by a stored cross-site scripting vulnerability in its uploads plugin, which allows any authenticated user to upload HTML files via POST /uploads without type restrictions. A signed-in victim who opens a crafted GET /uploads/{path} link executes attacker-controlled script in the application's origin, potentially exposing the access_token cookie and enabling session hijacking, with administrators at highest risk. The issue requires victim interaction and a valid account; no public exploit code or active exploitation (CISA KEV) has been identified, and the overall risk is assessed as moderate (CVSS 5.1).
An authenticated user of Kiteworks Core can abuse the file-request feature to send a request that appears to originate from a different, trusted account, because the server fails to verify that the requester is authorized to act on behalf of the identity they specify. Exploitation is gated by three conditions that substantially lower real-world risk: the attacker must hold a valid account (PR:L), the file-request feature must be enabled for the attacker's profile, and the targeted recipient must actively act on the spoofed request (UI:R). There is no memory corruption, code execution, or availability impact - the flaw only enables identity misrepresentation to solicit files or information. Consistent with an assessed CVSS of 4.6, a public exploit has not been identified at time of analysis and there is no confirmed active exploitation.
Kiteworks Core appliances that are mid-way through first-time activation expose an unauthenticated setup endpoint which enforces neither authentication (CWE-306) nor its intended state precondition, letting an unauthenticated, network-positioned attacker repeatedly re-trigger the privileged activation routine and drive the appliance into an incompletely configured state. The exposure is confined to the transient initial-activation window before the system is fully configured, so only newly deployed or re-provisioned appliances are at risk and the resulting impact is limited to setup integrity disruption - there is no confidentiality loss, no code execution, and no persistent takeover. No public exploit code or confirmed active exploitation has been identified at time of analysis (no CISA KEV listing), and vendor-supplied patching is available; practical priority is consequently LOW-to-MEDIUM despite the network-reachable, unauthenticated vector.
Kiteworks Core deployments earlier than 9.5.0 allow an authenticated administrator to silently render a security-policy control ineffective by setting its configurable value outside the intended range, while the control continues to appear enabled in the administrative interface and audit log. The assessed impact is correspondingly limited - CVSS 4.9 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N) with no confidentiality or availability impact - because exploitation requires full administrative privileges and produces a masking of enforcement rather than direct system compromise. No public exploit code was identified at time of analysis, and the realistic risk is confined to insider misuse or an already-compromised administrator session; a vendor patch is available.
Kiteworks Core versions below 9.5.1 fail to enforce which roles a shared folder's Manager is allowed to assign, so an authenticated user who already holds the Manager role on a folder can grant the Owner role on that same folder to themselves or to other members. The weakness works in a default configuration, but its impact is bounded: it is an escalation to Owner within that one folder and does not by itself confer tenant-wide or system-administrator rights. Rated CVSS 4.3 (integrity-only, low confidentiality and availability impact), with no public exploit code identified at time of analysis and no CISA KEV entry.
Kiteworks Core appliances running versions before 9.5.0 leave their setup interface reachable without authentication once initial configuration has completed, so any remote attacker with network access to that interface can read and modify a limited set of setup records - specifically the contact name and email address captured during provisioning. The flaw is state-dependent: authentication is enforced during first-run provisioning but the interface remains exposed afterward, and the exposed data is narrow, with no code execution, no broader configuration control, and no availability impact. No public exploit code has been identified at time of analysis, and there is no evidence of active exploitation; the practical risk is gated by whether the appliance's setup or management plane is reachable from untrusted networks.
Command injection in the optional repository-connector feature of Kiteworks Core allows an authenticated system administrator to append shell commands to a user-supplied path, resulting in code execution as the connector's service account and arbitrary file writes within that account's permissions. Only deployments running Kiteworks Core below 9.5.1 that have licensed and enabled the non-default repository connector are exposed, and successful exploitation additionally requires the appliance to be able to reach an attacker-controlled host over the network, as the injected command must pull or deliver content externally. Rated CVSS 6.6 (AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H); there is no public exploit code identified at time of analysis and the vulnerability is not confirmed actively exploited (no CISA KEV listing), so real-world risk is best characterised as LOW-to-MEDIUM despite the high-integrity/high-availability outcome, given the layered prerequisites of admin privilege, a separately licensed feature, and outbound egress.
Kiteworks Core versions before 9.5.1 fail to apply gateway-level API security controls to every request authenticated through the central authentication service, enabling an authenticated attacker to access REST API functionality on an unprotected path even with a revoked or signed-out session. This CWE-420 unprotected alternate channel yields low confidentiality and integrity impact (CVSS 5.4) and requires a valid authenticated session (PR:L). No public exploit code has been identified at time of analysis.
OS command execution on a second appliance node is possible in multi-node (clustered) Kiteworks Core deployments running versions below 9.5.1, but only for an attacker who has already achieved code execution on another node in the same cluster. An unvalidated value submitted through an internal cluster interface is written into the monitoring configuration of a peer node, where it can be interpreted as an OS command running under an unprivileged service account. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); the CVSS 3.1 score of 6.3 (AV:L/PR:L/S:C) reflects the strong prerequisites - local-adjacent access, existing low-privilege foothold, and a multi-node topology.
An authenticated administrator on Kiteworks Core can bypass server-side content validation for administrative file uploads, allowing storage of files with dangerous content. While this alone does not execute code, it could be leveraged in a chained attack with a separate vulnerability. Affected versions are prior to 9.5.1, and a vendor patch is available. The low CVSS score (4.1) reflects the high privilege requirement and complex bypass, and no public exploit has been identified.
Server-side request forgery in Kiteworks Core before 9.5.1 lets an authenticated administrator on a node with the separately licensed gateway role enabled supply a connector URL that the server fetches without adequately validating the URL scheme or destination, causing outbound requests to internal network services. Exploitation requires two prerequisites: a valid administrative session (CVSS PR:H) and an active optional gateway role, which is not a default configuration, and the resulting impact is constrained to limited confidentiality and integrity with no availability effect (CVSS 3.3, AC:H). No public exploit code has been identified at time of analysis and there is no evidence of active exploitation; the vendor has released a fixed version, 9.5.1, and the issue was reported through CISA's coordinated disclosure channel.
Insufficient verification of user-supplied data (CWE-345) in Kiteworks Core before version 9.5.1 allows an authenticated administrator to import a file whose header passes validation while its full contents remain forged or unverified, undermining the integrity of the imported data. The flaw is reachable over the network but requires high privileges (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N), so only attackers holding a Kiteworks Core administrative account and access to the administrative import function can trigger it; there is no confidentiality or availability impact and no user interaction is needed. The CVSS base score of 4.9 (Medium) accurately reflects this constrained, integrity-only issue, and no public exploit code or confirmed active exploitation was identified at time of analysis. Kiteworks has released a fix in Core 9.5.1.
Two cluster-management operations in Kiteworks Core before 9.5.1 fail to validate attacker-supplied file paths, letting an attacker who already holds backend root on one node of a multi-node cluster write files as root onto another node and have them executed there. Exploitation is heavily gated: it is local-only (AV:L), requires pre-existing high privilege (PR:H, backend root), and depends on a software patch being simultaneously pending/staged on the target node to serve as the execution trigger - making this a lateral-movement and privilege-persistence primitive for an already-compromised cluster rather than an initial-access bug. This is a genuine but heavily gated post-compromise flaw, not a top-of-queue emergency; vendor patches are available and no public exploit code has been identified at time of analysis.
Authenticated administrators on Kiteworks Core deployments earlier than 9.5.1 can abuse the administrative interface to make the server issue requests to, and interact with, internal network services that should not be reachable through that interface - a server-side request forgery (SSRF) style weakness with a scope change (S:C) that still carries a moderate 6.6 base score. Exploitation is gated behind high privileges (PR:H) and, as the vendor and our assessment both note, does not by itself achieve remote code execution; meaningful impact would require chaining with a separate flaw. No public exploit has been identified at time of analysis, but a vendor patch is available in Kiteworks Core 9.5.1, so the primary risk is to organizations that expose the admin plane to untrusted networks or allow unrestricted egress from the appliance.
Content injection in the Kiteworks Core PDF viewer in versions before 9.5.1 allows remote attackers to load an attacker-controlled document inside the application's own trusted domain, because a URL parameter used by the viewer is not sufficiently validated (CWE-601). Under the assessed CVSS:3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N (base 4.3), no authentication is required of the attacker, but exploitation depends on a victim clicking a crafted link and then trusting the rendered content; the resulting impact is limited to integrity/content spoofing (I:L) with no reading of Kiteworks data, no code execution, and no availability impact. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; the primary abuse case is raising the credibility of phishing that relies on links embedded in the displayed content. A vendor-released patch exists in Kiteworks Core 9.5.1.
Authenticated REDAXO backend users can exploit improper validation of the 'sort' parameter in rex_list::getSortColumn() (redaxo/core before 5.21.2) to inject unauthorized column names into SQL ORDER BY clauses, enabling error-based enumeration of columns in joined tables and ordering by sensitive fields such as rex_user.password. This low-to-moderate severity information-disclosure issue requires valid backend credentials (PR:L) and yields inference-based leaks-schema enumeration and ordering oracles-rather than direct data dumps. The vendor fixed it in 5.21.2 by validating the requested column against registered sortable columns; no public exploit code or active exploitation is identified at time of analysis.
Provider-confusion in NextAuth.js (next-auth and @auth/core) allows an attacker to link their own OAuth identity at a target provider to a victim's Auth.js user account, granting the attacker persistent unauthorized sign-in. The flaw stems from OAuth anti-CSRF cookies - state, nonce, and PKCE verifier - being stored globally without binding to the originating provider, so a callback for one provider can consume check values minted during a flow initiated with a different provider. No public exploit code or CISA KEV listing exists at time of analysis, but the CVSS 6.8 score with C:H/I:H reflects a full account-takeover outcome when the required multi-condition setup is present.
Open redirect in the Home Assistant Android Companion App (prior to 2026.6.1) enables credential phishing attacks against new users via crafted homeassistant://invite deep links. Because no screen in the invitation or onboarding flow displays the parsed server hostname before the WebView commits to it, an attacker who delivers a malicious invite link can silently redirect the victim's onboarding session to an attacker-controlled server presenting a look-alike login page. No public exploit code has been identified at time of analysis; the CVSS score of 4.3 (C:L) understates real-world impact given that captured credentials yield full smart-home access.
Cross-user attribute structure leakage in API Platform Core's JSON:API and HAL serializers exposes the schema layout of security-gated properties to lower-privileged users through improper cache reuse. Versions from 2.6.0 up to 4.1.29, 4.2.26, and 4.3.12 are affected across the core, hal, and json-api packages. The component structure computed for a higher-privileged user's request can be served from cache to a subsequent lower-privileged user's request, bypassing the per-request evaluation of #[ApiProperty(security: ...)] predicates. No public exploit identified at time of analysis; vendor-released patches are available.
Type confusion in API Platform Core's AbstractItemNormalizer allows authenticated API consumers to corrupt relational data by supplying IRIs pointing to resources of the wrong type during write operations (POST/PUT/PATCH). The root cause is that getResourceFromIri() omits the $operation context when calling IriConverter::getResourceFromIri(), silently bypassing the is_a type guard at IriConverter.php:86. All 4.1.x, 4.2.x, and 4.3.x releases prior to the patched versions are affected; no public exploit or CISA KEV listing has been identified at time of analysis.
Dräger Core 1.0.5 and Dräger M540 Converter Service 1.0.9 contain a denial of service vulnerability that allows network-adjacent attackers to trigger high CPU load by sending specially crafted,. Rated high severity (CVSS 8.7), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This Uncontrolled Resource Consumption vulnerability could allow attackers to cause denial of service by exhausting system resources.
Excessive Data Query Operations in a Large Data Table in GitHub repository pimcore/demo prior to 10.3.0. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.
API Platform Core is the server component of API Platform: hypermedia and GraphQL APIs. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity.
Onlyoffice Document Server v6.0.0 and below and Core 6.1.0.26 and below were discovered to contain a heap overflow via the component DesktopEditor/fontengine/fontconverter/FontFileBase.h. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.
Onlyoffice Document Server v6.0.0 and below and Core 6.1.0.26 and below were discovered to contain a stack overflow via the component DesktopEditor/common/File.cpp. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.
An issue was discovered in Form Tools through 3.0.20. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
An issue was discovered in Form Tools through 3.0.20. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
An issue was discovered in Form Tools through 3.0.20. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
In RACTF before commit f3dc89b, unauthenticated users are able to get the value of sensitive config keys that would normally be hidden to everyone except admins. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This Exposure of Sensitive Information vulnerability could allow attackers to access sensitive data that should not be disclosed.
An arbitrary file reading vulnerability in MobileIron Core versions 10.3.0.3 and earlier, 10.4.0.0, 10.4.0.1, 10.4.0.2, 10.4.0.3, 10.5.1.0, 10.5.2.0 and 10.6.0.0 that allows remote attackers to read. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
An authentication bypass vulnerability in MobileIron Core & Connector versions 10.3.0.3 and earlier, 10.4.0.0, 10.4.0.1, 10.4.0.2, 10.4.0.3, 10.5.1.0, 10.5.2.0 and 10.6.0.0 that allows remote. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
API Platform version from 2.2.0 to 2.3.5 contains an Incorrect Access Control vulnerability in GraphQL delete mutations that can result in a user authorized to delete a resource can delete any. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Improper authorization handling in OPNsense core before 26.1.11 lets an authenticated low-privileged user (CVSS PR:L) bypass the user-config-readonly restriction and persist configuration changes through MVC APIs that rely on the throwReadOnly() guard. The flaw only triggers for accounts whose privileges are assigned directly: when a user is given both a component write privilege and user-config-readonly inside one comma-separated <priv> value, ACL::hasPrivilege() fails to detect the read-only flag through its exact string comparison, so the write is allowed; accounts receiving privileges through groups are unaffected. Impact is confined to configuration integrity for the affected component (I:H with C:N and A:L), no public exploit has been identified at time of analysis, and the vendor has shipped the fix in OPNsense 26.1.11.
Unauthenticated log injection in the OPNsense WebGUI login handler lets a network-adjacent attacker forge authentication events that manipulate the firewall's sshlockout protection state. Because the usernamefld parameter prior to version 26.1.11 passes carriage-return and line-feed characters through LOG_AUTH into the syslog-ng lockout pipeline, an attacker who can reach the login page can plant a fabricated failure event naming a victim IP, causing that address to be added to the sshlockout PF table and its active states killed, or plant a forged accepted event to reset their own brute-force counter and defeat password-guessing lockout. The flaw requires no authentication and no user interaction, but the assessed AV:A vector means exploitation presumes adjacency or management-network reachability to the GUI; impact is integrity of lockout state and availability of blocked systems (administrative, DNS, gateway, or monitoring addresses), with no confidentiality impact, and no public exploit or confirmed in-the-wild activity was identified at time of analysis.
Stored cross-site scripting in the OPNsense OpenVPN connection-status dashboard widget and status view lets an authenticated VPN client execute arbitrary JavaScript inside a firewall administrator's browser session, which the advisory demonstrates can read config.xml, invoke privileged APIs, reset the root password and ultimately obtain root command execution on the appliance. Exploitation is heavily gated: the OpenVPN server must be configured with username-as-common-name and a RADIUS or LDAP authentication backend, the attacker must be able to provision or self-register a backend username containing a double quote, a separate trust boundary must exist between the identity backend and the firewall (the local user database is unaffected because its username validator rejects quotes), and an administrator must open the affected dashboard or status page and trigger the injected handler - the demonstrated payload required pointer movement over the client row rather than unconditional page-load execution. Consistent with the CVSS vector (AV:N/AC:H/PR:L/UI:R) this is a low-privilege, high-complexity, admin-interaction-dependent issue; no public exploit code was identified at time of analysis, and the fix shipped in OPNsense 26.1.11.
Root-level code execution on OPNsense firewalls running versions prior to 26.1.11 is achievable by an authenticated operator who holds the 'Firewall Alias Edit' privilege and can point a GeoIP alias at an attacker-controlled source URL. The GeoIP importer's process_zip() and process_gzip() routines trust the CSV country_code field when building output filenames under /usr/local/share/GeoIP/alias, so a crafted value traverses out of that directory and writes attacker-controlled files as root; chaining a planted newsyslog fragment with an oversized log file then lets the default hourly root cron job execute the payload, yielding complete firewall compromise (CVSS 9.9, AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). No public exploit code and no confirmed active exploitation were identified at time of analysis, and exploitation requires a non-default alias configuration that the operator must supply.
Authenticated XPath injection in the OPNsense firewall and routing platform (all versions prior to 26.1.10) lets a user holding CA Manager or Certificate Manager privileges recover values stored in config.xml character by character. The Trust module stores attacker-controlled certificate and CA refid values and interpolates them unescaped into XPath queries in CAsField.php and CertificatesField.php; because the resulting refcount/in_use boolean is returned to the requester, it acts as a blind injection oracle for secrets such as password hashes, API credentials, certificate private keys, VPN key material, and high-availability credentials, which in turn can enable privilege escalation and compromise of other security domains. Exploitation is post-authentication, requires those specific trust-management privileges, and is high-complexity and iterative (roughly one boolean leak per request), so this is a genuine but second-tier information-disclosure issue rather than a drive-by remote compromise; no public exploit code has been identified at time of analysis. Vendor-released patch: 26.1.10.
Untrusted-link activation inside an Ionic Capacitor app on Android or iOS can render attacker-controlled HTML at the application's own origin via the internal /_capacitor_http_interceptor_ proxy path, giving that script full same-origin access to storage, cookies and registered Capacitor plugin capabilities. Affected releases are 6.0.0 up to (but not including) 6.2.2, 7.6.9, 8.3.5, 8.4.3 and 8.5.1; exploitation requires the victim to activate an attacker-supplied link in the WebView (UI:R) but no authentication (PR:N) and no non-default feature flag, so apps are exposed even when the CapacitorHttp plugin is disabled because vulnerable builds serve the proxy path regardless of that setting. No public exploit code or confirmed active exploitation was identified at time of analysis, though the high CVSS score of 9.3 (S:C/C:H/I:H) and the broad mobile install base make patch urgency high.
Local privilege escalation in Kiteworks Core lets an attacker who already holds code execution as an unprivileged backend service account invoke a privileged routine that mishandles attacker-influenced input, running arbitrary OS commands as root. The flaw requires a prior local foothold on the appliance - the CVSS vector (AV:L, PR:L, UI:N) confirms it cannot be reached directly over the network and demands an existing initial compromise or misconfiguration to obtain the service account. No public exploit code or active exploitation is identified at time of analysis, and the realistic risk is bounded by how easily that initial service-account access can be obtained on a given deployment; the vendor's advisory is GHSA-658c-86vw-g9hf.
Local privilege escalation in Kiteworks Core lets an attacker who already has code execution as an unprivileged backend service account on the appliance obtain root. A privileged, root-owned routine consumes a filesystem path that the lower-privileged service account can influence, so the attacker can steer that root operation into executing arbitrary commands with full privileges (CWE-59 link-following / unsafe path handling). The attack is local-only (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8) and is a second-stage primitive requiring an existing foothold; no public exploit was identified at time of analysis and the CVE is not reported as confirmed actively exploited (CISA KEV), though the 7.8 severity and availability of a vendor advisory make prompt patching advisable.
Command injection in Kiteworks Core lets an authenticated administrator with elevated privileges run arbitrary operating-system commands as root on the affected appliance node, so an admin-only function can be turned into full host compromise. The flaw is remotely reachable and needs no user interaction (CVSS:3.1/AV:N/AC:L/PR:H/UI:N, base score 7.2), but PR:H is the dominant limiting factor: no unauthenticated or low-privilege path is indicated, so practical exploitation presupposes an insider or stolen high-privilege administrative credentials. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV, keeping real-world urgency moderate and dependent on the value of the credentials required.
Unauthenticated attackers who know a target's email address can take over Kiteworks Core accounts that use locally stored passwords - including administrative accounts - by abusing insufficient parameter validation in the password reset workflow, which lets them bypass the emailed reset-link step and set a new password themselves before authenticating as that user. The flaw is classified CWE-640 (weak password recovery mechanism) and scores CVSS v3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication, no user interaction, and no non-default configuration are required; any internet-reachable Kiteworks Core instance hosting local-password accounts is exploitable. Independent assessment rates this a genuine top-priority issue rather than a high-score-but-low-risk case. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, but the pre-authentication, low-complexity nature warrants urgent action.
OS command execution in Kiteworks Core is possible when the remote-support capability is licensed and enabled and an authenticated System Administrator also possesses the key protecting submitted data, allowing that administrator to redirect the outbound support connection to an attacker-chosen destination that can then execute OS commands with local service account privileges. The CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, so exploitation requires high application privileges plus the additional key-possession condition, and deployments without remote support enabled are not exposed; there is no public exploit identified at time of analysis and no CISA KEV indication. The independent assessment rates real-world priority low-to-medium despite the 7.2 High base score.
Local privilege escalation in Kiteworks Core allows an attacker who already holds a shell under a low-privileged service account to elevate to root on the appliance, gaining complete control of the system and the sensitive content it brokers. The weakness is a link-following issue (CWE-59) in a root-privileged operation, reachable with local access as the service account (CVSS:3.1/AV:L/AC:L/PR:L/UI:N), no user interaction, and no non-default configuration, making it a realistic second-stage escalation after a separate initial-access compromise. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the CVE is not associated with a KEV listing; the primary limiting factor is the prerequisite service-account foothold, while the primary risk is full root compromise of the appliance.
Command injection in Kiteworks Core's internal cluster-management function allows an attacker who already has code execution on one node of a clustered deployment to run operating system commands with elevated privileges on other nodes in the same cluster. The vulnerable function is not reachable from outside the cluster, so the attack path is confined to the internal cluster network and requires a pre-existing foothold on a cluster member; single-node deployments are not exposed. Rated CVSS 8.8 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) with scope change reflecting cross-node impact, and no public exploit identified at time of analysis.
Unauthenticated path traversal in the Kiteworks Core appliance setup interface allows an attacker who can reach that interface to write a file to any location writable by the appliance service account, enabling integrity compromise of the appliance or a denial-of-service condition that persists until an operator intervenes. The exposure is narrow: the setup interface is not reachable on a fully configured appliance in its default configuration, so exploitation is realistically limited to the transient provisioning window of a new appliance or a non-default configuration that leaves setup exposed, which is why AC:H applies despite PR:N and UI:N (CVSS 7.4). No public exploit code and no confirmed active exploitation were identified at time of analysis, and the flaw does not by itself provide code execution.
Sandbox escape in Kiteworks Core's document-conversion feature (CVE-2026-102125, CVSS 8.8) allows code already executing inside the conversion sandbox to break confinement and act with the privileges of the application service account, enabling reads or modifications of application data and configuration or disruption of the service. Exploitation is conditional: the attacker must first get code running inside the sandbox, typically by submitting a crafted document for conversion, and the CVSS vector (AV:L/PR:L/UI:N/S:C) confirms a local, low-privilege prerequisite with no user interaction once that foothold exists. No public exploit code has been identified at time of analysis, making this a genuine but conditional integrity and availability risk rather than a mass-exploitation threat; a vendor-released patch is documented in Kiteworks advisory GHSA-58j2-hj9r-c258.
Stored cross-site scripting in Kiteworks Core allows an administrator holding only a single narrowly scoped delegated permission to plant crafted content that later executes as JavaScript in the authenticated session of a higher-privileged System Administrator, enabling the lower-privileged attacker to escalate to full tenant administrative control and create a new administrative account. The flaw is tracked as CVE-2026-102126 with a vendor CVSS 3.1 score of 8.1 (AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N) and is rated high severity under CWE-79. Exploitation requires an authenticated admin with the delegated permission (PR:H) and depends on the victim System Administrator viewing the affected page (UI:R); no public exploit code has been identified at time of analysis, and the issue is not in CISA KEV.
Privilege escalation in Kiteworks Core allows a delegated administrator whose scope includes role changes to promote an account to full system-administrator through the user-provisioning interface, which fails to verify that the requester is entitled to grant the role being assigned (CWE-266). The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, 7.2 High) confirms the flaw is network-reachable but requires high-privileged, delegated-admin credentials and no user interaction, so anonymous or ordinary-user accounts cannot exploit it and environments without scoped admin roles have no trust boundary to cross. No public exploit identified at time of analysis and no KEV listing; independent assessment rates this a genuine but low-to-medium operational priority rather than a high-urgency issue.
Privilege escalation in Kiteworks Core versions before 9.5.1 allows an authenticated delegated administrator holding only a single narrowly scoped administrative permission to obtain full system administrator privileges by abusing the administrative import function for integration credentials, which fails to verify that the requesting administrator is entitled to create the privileged credential being imported (CVE-2026-102132, CVSS 7.2 High). The attacker must already possess a valid delegated-admin account (PR:H), so this is an insider or lateral privilege-escalation issue rather than an unauthenticated internet-facing takeover, and no action by an existing system administrator is required for the escalation to succeed (UI:N). A vendor patch is available in Kiteworks Core 9.5.1; no public exploit code or confirmed active exploitation has been identified at time of analysis.
Deserialization of untrusted data in Kiteworks Core before 9.5.0 can escalate to remote code execution on the appliance, but only as a secondary, chained weakness rather than a standalone attack. The issue is not exploitable in isolation: an attacker must first obtain a way to influence the data that Core deserializes, which in practice means chaining a separate flaw (for example one of the file-write or injection issues in the same CISA CSAF batch, va-26-274-01) or leveraging an existing foothold. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, and although the base score is 8.1, the local/config-adjacent reachability (AV:L), high attack complexity (AC:H) and the mandatory data-influence precondition materially lower real-world risk; the CVSS vector indicates no privileges are required (PR:N), but exploitation is not remotely self-contained.
Server-side template injection in the Kiteworks Core appliance allows an authenticated System Administrator to store a crafted system-notification template whose embedded template-engine expressions are evaluated when the notification is next rendered, resulting in operating-system command execution on the appliance. Exploitation requires a high-privileged admin account (CVSS vector PR:H, UI:N) and has a timing dependency because the payload only fires when the affected notification is triggered, making this a malicious-insider or compromised-admin scenario rather than a perimeter-reachable RCE. No public exploit code and no confirmed active exploitation were identified at time of analysis; the vendor-assigned CVSS 3.1 score of 7.2 (C:H/I:H/A:H) reflects full compromise of confidentiality, integrity, and availability once the template is rendered.
Stored cross-site scripting in Kiteworks Core before version 9.5.0 allows an authenticated user with only low privileges to submit content that executes arbitrary JavaScript in the browser session of any other user who later views it, potentially enabling full account takeover of higher-privileged users such as administrators. The issue scores 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N = High) because a successful attack crosses the browser privilege boundary into the victim's session, yielding high confidentiality and integrity impact while availability is unaffected. No public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation is constrained by two prerequisites: the attacker must already hold a valid low-privileged account, and a second user must subsequently render the stored payload in the web UI.
Stored cross-site scripting in Kiteworks Core (all versions prior to 9.5.0) enables unauthenticated attackers to persist malicious JavaScript that executes in an administrator's browser session when the poisoned page is viewed. Successful exploitation could grant the attacker full administrative control, including creating new admin accounts, as reflected by the CVSS 9.3 score (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N). The primary limiting factor is the required user interaction-an administrator must actively view the affected page-and no public exploit identified at time of analysis.
OS command injection in Kiteworks Core appliances running versions before 9.5.0 allows an authenticated administrator to upload a configuration package whose contents are not sufficiently validated, resulting in arbitrary operating-system command execution that may run with elevated privileges on the underlying appliance. The attack requires a valid administrator account with access to the configuration-package upload functionality in the administrative interface (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, 7.2 High), so the high-privilege prerequisite is the dominant constraint and the realistic scenario is a malicious, compromised, or coerced administrator rather than opportunistic unauthenticated remote exploitation; the assessed vector is internally consistent and concurred with. No public exploit code and no confirmed active exploitation were identified at time of analysis, and successful exploitation yields full compromise of confidentiality, integrity, and availability on the affected appliance.
Arbitrary file write in Kiteworks Core before 9.5.0 lets a holder of an existing administrative account steer the platform's administrative export feature to write files to any path on the underlying host, which can be chained into command execution on the appliance. The root cause is an improper restriction of a user-supplied file path (CWE-22), scored CVSS v3.1 7.2 with vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, so the flaw is not reachable by unauthenticated or standard users and command execution is a downstream consequence of the write rather than a guaranteed outcome. No public exploit code and no confirmed active exploitation (no CISA KEV listing) were identified at time of analysis; the primary constraint on real-world risk is the high-privilege prerequisite.
Improper privilege management in Kiteworks Core before 9.5.0 allows an authenticated administrative user who holds only limited, non-Sysadmin role-management permissions to grant another account full system-administrator (Sysadmin) rights that the grantor was never authorized to confer. The flaw sits in the role-assignment logic, which fails to constrain grantable privileges to the subset the granting administrator actually possesses, so a single delegated-admin session is enough to escalate a chosen account to the highest privilege level. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, score 7.2) the attack is network-reachable with no user interaction but requires an already-authenticated high-privilege session; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (not in CISA KEV). This is best characterized as a genuine but access-gated integrity risk whose real-world exposure depends on how many delegated administrators exist in a deployment and how tightly their role scopes are managed.
Stored cross-site scripting in Kiteworks Core allows an authenticated user to store crafted content that executes arbitrary JavaScript in another user's authenticated session when that victim previews the shared content, potentially enabling session compromise or account takeover. Affected deployments are Kiteworks Core versions before 9.5.0, and exploitation requires a valid platform account plus victim interaction with the preview rendering path. No public exploit code or CISA KEV listing has been identified at time of analysis, and the independent assessment classifies this as a moderate-priority, contingent-risk finding rather than an urgent one.
Stored SQL injection in Kiteworks Core before 9.5.0 allows an authenticated administrator to read sensitive data from the underlying database and to degrade availability of the service. Exploitation is only reachable through the affected administrative reporting feature and requires an existing, authenticated administrative account (CVSS:3.1/AV:N/AC:L/PR:H/UI:N), so the flaw is not exposed to unauthenticated or low-privileged users; no public exploit code has been identified at time of analysis, and no CISA KEV entry or EPSS score accompanies this CVE. Our independent assessment rates the issue at moderate priority: confidentiality and availability impact are high, but integrity impact is limited (C:H/I:L/A:H), and the mandatory full administrative privilege sharply narrows the realistic attack surface to trusted insiders or attackers who have already compromised an admin session.
Incorrect authorization in Cheshire Cat AI's GET /memory/collections/{collection_id}/points endpoint allows any authenticated user holding MEMORY:READ permission to retrieve episodic memory records belonging to all other users by paginating through the collection via the offset cursor. The route implementation in core/cat/routes/memory/points.py omits per-user scoping when querying the vector store, exposing stored conversation histories and personal data across the entire tenant base. No public exploit or CISA KEV listing has been identified at time of analysis.
OS command injection in Liman server management software (limanmys/core) before version 2.2.2 - 1103 lets an authenticated administrator run arbitrary operating-system commands on the host via the log rotation configuration endpoint. The unsanitized `ip_address` parameter is concatenated into a shell command, allowing single-quote shell-escape to break out and execute attacker-controlled commands. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; it is fixed in 2.2.2 - 1103.
Denial of service in NextAuth.js's getToken() helper allows unauthenticated remote attackers to crash any API route, middleware, or server-side handler that calls getToken() directly by sending a single HTTP request with a malformed Authorization: Bearer header containing invalid percent-encoding. The vulnerability affects next-auth 4.0.6-4.24.14, next-auth 5.0.0-beta.0-5.0.0-beta.31, and @auth/core 0.1.0-0.41.2, and is fixed in next-auth 4.24.15, next-auth 5.0.0-beta.32, and @auth/core 0.41.3. No public exploit code has been identified at time of analysis, but the trigger condition is trivially constructible from the public advisory description alone.
The Home Assistant iOS Companion app silently executes tag-triggered automations when any co-installed untrusted app forwards a crafted tag event via iOS universal links, bypassing physical scan validation entirely. Affected versions are all iOS Companion app releases prior to 2026.5.0; the underlying Home Assistant core CPE (cpe:2.3:a:home-assistant:core:*:*:*:*:*:*:*:*) is also cited. Because automations can control physical devices such as smart locks and alarms, the I:H CVSS metric reflects real-world consequences beyond software state. No public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Silent automation execution in the Home Assistant Android Companion App prior to 2026.8.1 allows any co-installed app on the device to trigger arbitrary HA automations by forwarding a crafted tag URL to an exported Activity without user confirmation. The flaw exists because TagReaderActivity accepted both physical NFC intents and OS-routed deep links identically, with no caller validation or approval prompt before dispatching the tag scan to the Home Assistant server. No public exploit has been identified at time of analysis, but the attack is unattended and can control physical actuators such as locks or alarms.
Unsandboxed Twig template rendering in Bolt CMS allows any user holding an editor-level CMS role to inject arbitrary OS commands via Server-Side Template Injection (SSTI), achieving remote code execution as the web server process. The root cause is that Bolt's Twig environment never registers a SandboxExtension, so the full Twig filter chain - including dangerous filters like `passthru` - is available to content authors. The default out-of-the-box configuration of the 'pages' content type ships with `allow_twig: true`, meaning this is exploitable in a standard Bolt installation without any additional misconfiguration. No public exploit has been independently confirmed, though the CVE description includes a working payload demonstrating command execution.
Remote code execution in REDAXO CMS versions 5.18.2 through 5.21.0 is reachable by authenticated backend users with media upload permissions via a multi-segment filename bypass (e.g., shell.php.any.jpg) that defeats the extension blocklist in rex_mediapool::isAllowedExtension. The flaw is a confirmed regression introduced in PR #6213 (February 2025), which replaced a historically correct str_contains guard with weaker str_ends_with logic, reintroducing a double-extension attack class that the codebase had explicitly defended against since 2018. Exploitation additionally requires the target server to run a multi-extension PHP handler (Apache mod_mime AddHandler or unanchored FilesMatch); no public exploit or CISA KEV listing has been identified at time of analysis, and the vendor-released fix is available in version 5.21.1.
Sensitive token disclosure affects the Home Assistant iOS companion app prior to 2025.5.0, where the app ignores the configured SSID allowlist meant to gate internal-network access. Because the app falls back to the internal URL whenever no other URL is available, it can transmit the user's authentication token to the internal endpoint while the device is connected to an untrusted or insecure Wi-Fi network, enabling interception. No public exploit has been identified at time of analysis, and the issue is not in CISA KEV; vendor advisory GHSA-cm5v-547m-qh5h confirms the fix in 2025.5.0.
Location spoofing in the Home Assistant Android companion app prior to 2026.5.3 allows any co-installed application - even one with zero runtime permissions - to forge the device's reported GPS position by broadcasting a crafted Google Play Services LocationResult to an unprotected exported BroadcastReceiver. The forged coordinates are forwarded to the user's Home Assistant server as the device's real location, defeating Android's developer-mode Mock Location gate and enabling abuse of zone-based automations such as unlocking doors, disarming alarms, or opening garages. No public exploit identified at time of analysis, and the issue is patched in 2026.5.3 by unexporting LocationSensorManager and introducing a thin RequestAccurateLocationReceiver proxy that drops attacker-supplied extras.
Cross-origin JavaScript injection in Home Assistant Companion apps for Android (before 2026.4.4) and iOS (before 2026.4.1) allows a malicious iframe loaded inside the app's WebView to execute arbitrary JavaScript in the Home Assistant frontend's origin and steal the signed-in user's access token. The flaw stems from exposing the native JavaScript bridge (window.externalApp on Android, webkit.messageHandlers.getExternalAuth on iOS) to all frames combined with unsanitized callback identifier interpolation. No public exploit identified at time of analysis, and the issue is not in CISA KEV.
Authentication bypass in UltraDAG Core blockchain allows remote unauthenticated attackers to drain all pocket-derived sub-addresses on smart accounts, completely bypassing vault delays and daily spending limits. The StateEngine fails to resolve pocket addresses to their parent account during policy enforcement, treating virtual pocket addresses as unrestricted accounts. Confirmed actively exploited (CISA KEV). Vendor-released patch: commit fb6ef59 resolves pocket-to-parent mapping before all policy checks. EPSS data unavailable but attack vector is network-accessible with no complexity (CVSS 4.0 AV:N/AC:L/PR:N), making this a critical priority for any UltraDAG deployment using smart account pockets.
LDAP filter injection in OPNsense firewall allows unauthenticated attackers to enumerate valid LDAP usernames and bypass group membership restrictions via the WebGUI login page. Affects OPNsense versions prior to 26.1.6. The vulnerability stems from failure to escape user-supplied input before insertion into LDAP search filters, enabling metacharacter injection. Attackers can authenticate as any LDAP user with known credentials, circumventing Extended Query group membership controls. No public exploit identified at time of analysis.
An access control vulnerability exists in Kiteworks Core versions 9.2.0 and 9.2.1 that allows authenticated users to access unauthorized content within the private data network. With a CVSS score of 8.8 (High), an attacker with low-level authenticated access can potentially access, modify, or delete sensitive data they should not have permissions to view. No public proof-of-concept or active exploitation (KEV listing) has been reported at this time.
A remote code execution vulnerability in MobileIron Core & Connector versions 10.3.0.3 and earlier, 10.4.0.0, 10.4.0.1, 10.4.0.2, 10.4.0.3, 10.5.1.0, 10.5.2.0 and 10.6.0.0; and Sentry versions 9.7.2. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Stored cross-site scripting in OPNsense core prior to 26.1.11 lets a user who holds the page-system-certmanager privilege inject HTML metacharacters into a certificate description field, and that markup is later rendered unescaped in the SSL Certificate selector on System Settings > Administration, executing in the browser session of any other user who opens that page. Exploitation requires a multi-user deployment and deliberate victim interaction (CVSS 3.1 base 5.2, Medium; vendor vector AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N, with the independent assessment treating the impact as scope-changing and limited to low confidentiality/integrity), and the attacker must already be authenticated with a high-privilege account. No confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; the flaw is resolved by upgrading to OPNsense 26.1.11.
Stored cross-site scripting in the NTP GPS configuration page of OPNsense (FreeBSD-based firewall/router platform) lets an authenticated user who holds the page-services-ntp-gps privilege persist a malicious initcmd value that closes the GPS textarea and injects script into the page. The payload executes in the browser session of any user - including an administrator - who later opens that page, letting the script read CSRF material and perform authenticated actions with the victim's privileges, which is why the CVSS vector assigns a changed scope (S:C). Affected are OPNsense core builds prior to 26.1.11; the flaw is fixed in 26.1.11, no public exploit was identified at time of analysis, and exploitation requires both a privileged operator account and a second user (UI:R) visiting the page.
Authenticated OPNsense users who hold at least one affected module privilege can supply a crafted safe-delete token that is interpolated into an XPath query over config.xml, letting them read configuration metadata from modules they are not authorized to access. The flaw, tracked as CVE-2026-58395, affects OPNsense releases prior to 26.1.11 and yields a substring-presence oracle that leaks configuration item names, descriptions, reference paths, and UUIDs, though it cannot modify configuration or delete data. It is a read-only information-disclosure issue rated 4.3 medium; no public exploit code identified at time of analysis, and CISA KEV does not list it.
A path traversal in OPNsense's OpenVPN Client Specific Override (CSO) handling allows an authenticated user holding CSO privileges to store a traversal sequence such as '../' in the common_name field, which openvpn_csc_conf_write() concatenates into the target path /var/etc/openvpn-csc/<vpnid>/<common_name> without normalization or a basename check; when a matching OpenVPN client-connect or authentication event is later processed by client_connect.php or user_pass_verify.php, a generated CSO configuration file is written outside the intended directory. Exploitation is constrained: the attacker must first have operator-level CSO access and must cause a matching common name or username to be processed, and the written content is generated OpenVPN configuration rather than arbitrary attacker-controlled bytes, which limits achievable impact - there is no public exploit identified at time of analysis. The issue is rated medium severity (vendor CVSS 5.9, independent assessment CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L) and is fixed in OPNsense 26.1.11.
Stored cross-site scripting in OPNsense core before 26.1.11 allows a user holding Firewall Categories or Firewall Alias Edit privileges to plant script that executes in the browser session of an administrator or other operator who opens the Firewall Rules or NAT page. The injected code runs with the victim's context, can read CSRF tokens, and can therefore perform authenticated actions on the firewall as that victim. Exploitation is not anonymous - it requires the attacker to already possess category or alias editing rights (PR:L, CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, base 5.4), and the malicious category must be attached to a rule or the alias referenced as a rule source/destination and saved so the tooltip renders; no public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited in CISA KEV. Fixed in OPNsense 26.1.11.
Cheshire Cat AI core through 2.0.23 is affected by a stored cross-site scripting vulnerability in its uploads plugin, which allows any authenticated user to upload HTML files via POST /uploads without type restrictions. A signed-in victim who opens a crafted GET /uploads/{path} link executes attacker-controlled script in the application's origin, potentially exposing the access_token cookie and enabling session hijacking, with administrators at highest risk. The issue requires victim interaction and a valid account; no public exploit code or active exploitation (CISA KEV) has been identified, and the overall risk is assessed as moderate (CVSS 5.1).
An authenticated user of Kiteworks Core can abuse the file-request feature to send a request that appears to originate from a different, trusted account, because the server fails to verify that the requester is authorized to act on behalf of the identity they specify. Exploitation is gated by three conditions that substantially lower real-world risk: the attacker must hold a valid account (PR:L), the file-request feature must be enabled for the attacker's profile, and the targeted recipient must actively act on the spoofed request (UI:R). There is no memory corruption, code execution, or availability impact - the flaw only enables identity misrepresentation to solicit files or information. Consistent with an assessed CVSS of 4.6, a public exploit has not been identified at time of analysis and there is no confirmed active exploitation.
Kiteworks Core appliances that are mid-way through first-time activation expose an unauthenticated setup endpoint which enforces neither authentication (CWE-306) nor its intended state precondition, letting an unauthenticated, network-positioned attacker repeatedly re-trigger the privileged activation routine and drive the appliance into an incompletely configured state. The exposure is confined to the transient initial-activation window before the system is fully configured, so only newly deployed or re-provisioned appliances are at risk and the resulting impact is limited to setup integrity disruption - there is no confidentiality loss, no code execution, and no persistent takeover. No public exploit code or confirmed active exploitation has been identified at time of analysis (no CISA KEV listing), and vendor-supplied patching is available; practical priority is consequently LOW-to-MEDIUM despite the network-reachable, unauthenticated vector.
Kiteworks Core deployments earlier than 9.5.0 allow an authenticated administrator to silently render a security-policy control ineffective by setting its configurable value outside the intended range, while the control continues to appear enabled in the administrative interface and audit log. The assessed impact is correspondingly limited - CVSS 4.9 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N) with no confidentiality or availability impact - because exploitation requires full administrative privileges and produces a masking of enforcement rather than direct system compromise. No public exploit code was identified at time of analysis, and the realistic risk is confined to insider misuse or an already-compromised administrator session; a vendor patch is available.
Kiteworks Core versions below 9.5.1 fail to enforce which roles a shared folder's Manager is allowed to assign, so an authenticated user who already holds the Manager role on a folder can grant the Owner role on that same folder to themselves or to other members. The weakness works in a default configuration, but its impact is bounded: it is an escalation to Owner within that one folder and does not by itself confer tenant-wide or system-administrator rights. Rated CVSS 4.3 (integrity-only, low confidentiality and availability impact), with no public exploit code identified at time of analysis and no CISA KEV entry.
Kiteworks Core appliances running versions before 9.5.0 leave their setup interface reachable without authentication once initial configuration has completed, so any remote attacker with network access to that interface can read and modify a limited set of setup records - specifically the contact name and email address captured during provisioning. The flaw is state-dependent: authentication is enforced during first-run provisioning but the interface remains exposed afterward, and the exposed data is narrow, with no code execution, no broader configuration control, and no availability impact. No public exploit code has been identified at time of analysis, and there is no evidence of active exploitation; the practical risk is gated by whether the appliance's setup or management plane is reachable from untrusted networks.
Command injection in the optional repository-connector feature of Kiteworks Core allows an authenticated system administrator to append shell commands to a user-supplied path, resulting in code execution as the connector's service account and arbitrary file writes within that account's permissions. Only deployments running Kiteworks Core below 9.5.1 that have licensed and enabled the non-default repository connector are exposed, and successful exploitation additionally requires the appliance to be able to reach an attacker-controlled host over the network, as the injected command must pull or deliver content externally. Rated CVSS 6.6 (AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H); there is no public exploit code identified at time of analysis and the vulnerability is not confirmed actively exploited (no CISA KEV listing), so real-world risk is best characterised as LOW-to-MEDIUM despite the high-integrity/high-availability outcome, given the layered prerequisites of admin privilege, a separately licensed feature, and outbound egress.
Kiteworks Core versions before 9.5.1 fail to apply gateway-level API security controls to every request authenticated through the central authentication service, enabling an authenticated attacker to access REST API functionality on an unprotected path even with a revoked or signed-out session. This CWE-420 unprotected alternate channel yields low confidentiality and integrity impact (CVSS 5.4) and requires a valid authenticated session (PR:L). No public exploit code has been identified at time of analysis.
OS command execution on a second appliance node is possible in multi-node (clustered) Kiteworks Core deployments running versions below 9.5.1, but only for an attacker who has already achieved code execution on another node in the same cluster. An unvalidated value submitted through an internal cluster interface is written into the monitoring configuration of a peer node, where it can be interpreted as an OS command running under an unprivileged service account. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); the CVSS 3.1 score of 6.3 (AV:L/PR:L/S:C) reflects the strong prerequisites - local-adjacent access, existing low-privilege foothold, and a multi-node topology.
An authenticated administrator on Kiteworks Core can bypass server-side content validation for administrative file uploads, allowing storage of files with dangerous content. While this alone does not execute code, it could be leveraged in a chained attack with a separate vulnerability. Affected versions are prior to 9.5.1, and a vendor patch is available. The low CVSS score (4.1) reflects the high privilege requirement and complex bypass, and no public exploit has been identified.
Server-side request forgery in Kiteworks Core before 9.5.1 lets an authenticated administrator on a node with the separately licensed gateway role enabled supply a connector URL that the server fetches without adequately validating the URL scheme or destination, causing outbound requests to internal network services. Exploitation requires two prerequisites: a valid administrative session (CVSS PR:H) and an active optional gateway role, which is not a default configuration, and the resulting impact is constrained to limited confidentiality and integrity with no availability effect (CVSS 3.3, AC:H). No public exploit code has been identified at time of analysis and there is no evidence of active exploitation; the vendor has released a fixed version, 9.5.1, and the issue was reported through CISA's coordinated disclosure channel.
Insufficient verification of user-supplied data (CWE-345) in Kiteworks Core before version 9.5.1 allows an authenticated administrator to import a file whose header passes validation while its full contents remain forged or unverified, undermining the integrity of the imported data. The flaw is reachable over the network but requires high privileges (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N), so only attackers holding a Kiteworks Core administrative account and access to the administrative import function can trigger it; there is no confidentiality or availability impact and no user interaction is needed. The CVSS base score of 4.9 (Medium) accurately reflects this constrained, integrity-only issue, and no public exploit code or confirmed active exploitation was identified at time of analysis. Kiteworks has released a fix in Core 9.5.1.
Two cluster-management operations in Kiteworks Core before 9.5.1 fail to validate attacker-supplied file paths, letting an attacker who already holds backend root on one node of a multi-node cluster write files as root onto another node and have them executed there. Exploitation is heavily gated: it is local-only (AV:L), requires pre-existing high privilege (PR:H, backend root), and depends on a software patch being simultaneously pending/staged on the target node to serve as the execution trigger - making this a lateral-movement and privilege-persistence primitive for an already-compromised cluster rather than an initial-access bug. This is a genuine but heavily gated post-compromise flaw, not a top-of-queue emergency; vendor patches are available and no public exploit code has been identified at time of analysis.
Authenticated administrators on Kiteworks Core deployments earlier than 9.5.1 can abuse the administrative interface to make the server issue requests to, and interact with, internal network services that should not be reachable through that interface - a server-side request forgery (SSRF) style weakness with a scope change (S:C) that still carries a moderate 6.6 base score. Exploitation is gated behind high privileges (PR:H) and, as the vendor and our assessment both note, does not by itself achieve remote code execution; meaningful impact would require chaining with a separate flaw. No public exploit has been identified at time of analysis, but a vendor patch is available in Kiteworks Core 9.5.1, so the primary risk is to organizations that expose the admin plane to untrusted networks or allow unrestricted egress from the appliance.
Content injection in the Kiteworks Core PDF viewer in versions before 9.5.1 allows remote attackers to load an attacker-controlled document inside the application's own trusted domain, because a URL parameter used by the viewer is not sufficiently validated (CWE-601). Under the assessed CVSS:3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N (base 4.3), no authentication is required of the attacker, but exploitation depends on a victim clicking a crafted link and then trusting the rendered content; the resulting impact is limited to integrity/content spoofing (I:L) with no reading of Kiteworks data, no code execution, and no availability impact. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; the primary abuse case is raising the credibility of phishing that relies on links embedded in the displayed content. A vendor-released patch exists in Kiteworks Core 9.5.1.
Authenticated REDAXO backend users can exploit improper validation of the 'sort' parameter in rex_list::getSortColumn() (redaxo/core before 5.21.2) to inject unauthorized column names into SQL ORDER BY clauses, enabling error-based enumeration of columns in joined tables and ordering by sensitive fields such as rex_user.password. This low-to-moderate severity information-disclosure issue requires valid backend credentials (PR:L) and yields inference-based leaks-schema enumeration and ordering oracles-rather than direct data dumps. The vendor fixed it in 5.21.2 by validating the requested column against registered sortable columns; no public exploit code or active exploitation is identified at time of analysis.
Provider-confusion in NextAuth.js (next-auth and @auth/core) allows an attacker to link their own OAuth identity at a target provider to a victim's Auth.js user account, granting the attacker persistent unauthorized sign-in. The flaw stems from OAuth anti-CSRF cookies - state, nonce, and PKCE verifier - being stored globally without binding to the originating provider, so a callback for one provider can consume check values minted during a flow initiated with a different provider. No public exploit code or CISA KEV listing exists at time of analysis, but the CVSS 6.8 score with C:H/I:H reflects a full account-takeover outcome when the required multi-condition setup is present.
Open redirect in the Home Assistant Android Companion App (prior to 2026.6.1) enables credential phishing attacks against new users via crafted homeassistant://invite deep links. Because no screen in the invitation or onboarding flow displays the parsed server hostname before the WebView commits to it, an attacker who delivers a malicious invite link can silently redirect the victim's onboarding session to an attacker-controlled server presenting a look-alike login page. No public exploit code has been identified at time of analysis; the CVSS score of 4.3 (C:L) understates real-world impact given that captured credentials yield full smart-home access.
Cross-user attribute structure leakage in API Platform Core's JSON:API and HAL serializers exposes the schema layout of security-gated properties to lower-privileged users through improper cache reuse. Versions from 2.6.0 up to 4.1.29, 4.2.26, and 4.3.12 are affected across the core, hal, and json-api packages. The component structure computed for a higher-privileged user's request can be served from cache to a subsequent lower-privileged user's request, bypassing the per-request evaluation of #[ApiProperty(security: ...)] predicates. No public exploit identified at time of analysis; vendor-released patches are available.
Type confusion in API Platform Core's AbstractItemNormalizer allows authenticated API consumers to corrupt relational data by supplying IRIs pointing to resources of the wrong type during write operations (POST/PUT/PATCH). The root cause is that getResourceFromIri() omits the $operation context when calling IriConverter::getResourceFromIri(), silently bypassing the is_a type guard at IriConverter.php:86. All 4.1.x, 4.2.x, and 4.3.x releases prior to the patched versions are affected; no public exploit or CISA KEV listing has been identified at time of analysis.
Dräger Core 1.0.5 and Dräger M540 Converter Service 1.0.9 contain a denial of service vulnerability that allows network-adjacent attackers to trigger high CPU load by sending specially crafted,. Rated high severity (CVSS 8.7), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This Uncontrolled Resource Consumption vulnerability could allow attackers to cause denial of service by exhausting system resources.
Excessive Data Query Operations in a Large Data Table in GitHub repository pimcore/demo prior to 10.3.0. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.
API Platform Core is the server component of API Platform: hypermedia and GraphQL APIs. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity.
Onlyoffice Document Server v6.0.0 and below and Core 6.1.0.26 and below were discovered to contain a heap overflow via the component DesktopEditor/fontengine/fontconverter/FontFileBase.h. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.
Onlyoffice Document Server v6.0.0 and below and Core 6.1.0.26 and below were discovered to contain a stack overflow via the component DesktopEditor/common/File.cpp. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.
An issue was discovered in Form Tools through 3.0.20. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
An issue was discovered in Form Tools through 3.0.20. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
An issue was discovered in Form Tools through 3.0.20. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
In RACTF before commit f3dc89b, unauthenticated users are able to get the value of sensitive config keys that would normally be hidden to everyone except admins. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. This Exposure of Sensitive Information vulnerability could allow attackers to access sensitive data that should not be disclosed.
An arbitrary file reading vulnerability in MobileIron Core versions 10.3.0.3 and earlier, 10.4.0.0, 10.4.0.1, 10.4.0.2, 10.4.0.3, 10.5.1.0, 10.5.2.0 and 10.6.0.0 that allows remote attackers to read. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
An authentication bypass vulnerability in MobileIron Core & Connector versions 10.3.0.3 and earlier, 10.4.0.0, 10.4.0.1, 10.4.0.2, 10.4.0.3, 10.5.1.0, 10.5.2.0 and 10.6.0.0 that allows remote. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
API Platform version from 2.2.0 to 2.3.5 contains an Incorrect Access Control vulnerability in GraphQL delete mutations that can result in a user authorized to delete a resource can delete any. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.