Authentication bypass in Cisco Identity Services Engine (ISE) and ISE Passive Identity Connector lets an unauthenticated, remote attacker reach a privileged API endpoint and gain unauthorized access to the appliance through its web-based management interface, with no credentials or user interaction required - reflected in a maximum CVSS score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H). Exploitation is confirmed actively exploited (CISA KEV) and publicly available exploit code exists, so any reachable ISE management/API plane should be treated as a top-priority emergency. Affected deployments span ISE 3.1.0 p8 through 3.5 Patch 3 and ISE-PIC 3.4.0 and 3.5.0.
Cisco ISE and Cisco ISE-PIC can be taken over by an unauthenticated, remote attacker who reaches the REST API web service, because that service fails to enforce adequate authorization checks before processing crafted HTTP requests. Successful exploitation grants administrative privileges over the appliance, allowing the attacker to read and modify policy configuration and identity data - a CVSS 10.0 (AV:N/AC:L/PR:N/UI:N/S:C) condition where no credentials or user interaction are required. The only meaningful barrier is network reachability: any ISE node whose REST API port is exposed to an untrusted segment is directly exploitable, so exposure is effectively the exploitability gate. No public exploit code has been identified at time of analysis, and the flaw is not confirmed as actively exploited (no CISA KEV listing), but the assessed impact and the value of ISE as a central identity/network-access control plane make this a top-priority item.
Remote, unauthenticated attackers with network access to Cisco Identity Services Engine (ISE) or ISE Passive Identity Connector (ISE-PIC) can achieve full compromise of the appliance due to multiple injection-class flaws (CWE-74) addressed in a hardening release, as reflected by a maximum CVSS 3.1 score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H). No public exploit code has been identified at time of analysis, and the vendor has not specified the exact triggering feature or protocol path, but the CVSS vector confirms no authentication, no user interaction, and low attack complexity are required. Real-world risk is primarily limited by network exposure, as ISE management and service interfaces are typically deployed on protected management networks.
Improper access control vulnerabilities in Cisco Identity Services Engine (ISE) and ISE Passive Identity Connector (ISE-PIC) allow unauthenticated remote attackers to bypass authentication and gain full control of affected deployments (CVSS 10.0). Cisco addressed these flaws in a software hardening release, and no public exploit has been identified at time of analysis. Affected versions are pre-hardening releases of ISE and ISE-PIC, though the specific triggering components are not disclosed due to the grouped nature of the advisory. This is the most severe member of the Cisco ISE hardening advisory family.
Command injection in Arista EOS-based products lets an authenticated user of the gRPC Network Security Interface (gNSI) Certz service escalate privileges and run arbitrary OS commands as root by sending a crafted Certz Rotate request, resulting in full device compromise; the Bootz service is affected by the same flaw. The issue is a CWE-78 OS command injection reported by Arista and carries a CVSS 4.0 base score of 9.4. There is no public exploit identified at time of analysis and the vulnerability is not listed in CISA KEV.
Sandbox escape in the Avast/AVG/Norton sandbox minifilter driver (aswSnx.sys) on Windows allows an authenticated, low-privileged process already executing inside the sandbox to break file isolation and escalate to SYSTEM (CVSS 8.8, AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, CWE-281). The driver opens the virtualization target with only GENERIC_WRITE and FILE_WRITE_ATTRIBUTES, omitting WRITE_DAC, so every attempt to reapply the original DACL fails silently and virtualized copies of sensitive files are left with permissive permissions; the IRP_MJ_CREATE handler additionally fails to strip WRITE_DAC for sensitive directories, letting a sandboxed process rewrite the security descriptor of a virtualized object, read the virtualized SAM copy, extract local NTLM hashes and run code as SYSTEM. Publicly available exploit code exists (the PrettyPrague proof of concept), the vendor has released patches for the affected Avast, AVG and Norton products, and no CISA KEV entry indicates confirmed active exploitation.
Unauthenticated attackers can coerce changedetection.io through 0.60.6 into fetching arbitrary internal network addresses by abusing the 'Goto URL' action inside a browser step, because the application's SSRF guard is applied only to the main watch URL and never to the browser-step optional_value parameter. Successful exploitation returns the raw response from otherwise unreachable internal services, giving high-confidentiality read access with no write or code-execution impact (independently assessed as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, high confidentiality only, scope unchanged, versus the vendor-scale 8.7 CVSS 4.0 score). Publicly available exploit code exists, and exploitation additionally requires that browser steps be reachable and backed by a configured Playwright/Chrome fetcher; the unauthenticated path applies to default deployments that ship with no access password, while password-protected instances require valid credentials first.
Multi-statement SQL authorization bypass in Manticore Search 27.0.0 through 28.4.3 lets an authenticated read-only user escalate to full administrative control: the server validates permissions only for the first statement in a batch, so appending additional SELECT statements exposes system credential tables and their password hashes, which can be replayed to authenticate as an administrator without cracking any plaintext. No user interaction is required, and publicly available exploit code exists, though no confirmed active exploitation (CISA KEV) has been reported; the only prerequisite is an existing low-privileged account with SQL access over the MySQL-protocol interface. This is a genuine, actionable priority rather than a high-CVSS-but-low-real-risk paper finding.
SIMAC MyPHR 1.1 exposes an insecure direct object reference (IDOR) in its employee-update API that lets any authenticated user with a valid low-privileged account access and modify arbitrary employee records. By sending a PUT request with another employee's identifier and a controlled password value, an attacker can take over target accounts, enumerate employee records, and retrieve sensitive personally identifiable information such as private pay bulletins. Publicly available exploit code exists, and the vulnerability has a CVSS 4.0 base score of 8.7; active exploitation has not been confirmed by CISA KEV status in the provided data.
Denial of service in PocketBase versions prior to 0.22.48 (0.22.x branch) and 0.23.0 through 0.39.6 (0.23.0+ branch) allows an authenticated attacker or server misconfiguration to crash the process by triggering a panic in an internal goroutine that escapes the panic-recovery middleware. The flaw requires a network-reachable instance and low-privilege access (e.g., superuser) for the most directly reachable paths such as backup restore or view creation; public exploit code exists. Impact is limited to availability, causing process termination and requiring a restart, with no data exposure or code execution.
Authenticated users of zlt2000 microservices-platform through 6.0.0 can overwrite the password of any non-administrator account by calling the PUT /users/password endpoint with an arbitrary user id and a new password, because the server never verifies the current password. The flaw is network-reachable, low-complexity, and requires only a low-privilege login session (CVSS 4.0 base 8.7; assessed CVSS 3.1 AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:L), and publicly available exploit code exists. Exploitation is limited to non-administrator accounts and is not possible pre-authentication, but a successful attack yields full credential takeover of the targeted account.
Missing authorization in zlt2000 microservices-platform through 6.0.0 lets any authenticated account - including one with zero assigned roles - invoke administrative APIs for user management, role assignment, password resets by user ID, and Elasticsearch index deletion, because the shipped default of zlt.security.auth.urlPermission.enable is false and suppresses all permission checks once authentication succeeds. Exploitation is not pre-auth: it requires a valid low-privilege session against a deployment running the out-of-the-box configuration, and publicly available exploit code exists (VulnCheck-reported PoC scripts covering role-granting, user enumeration, password reset, and ES index deletion), though no confirmed active exploitation (CISA KEV) has been recorded. Assessed severity is high (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H = 8.8; vendor-published CVSS 4.0 score 8.7) because a zero-role user obtains both read and write access to sensitive administrative functions.
Authorization bypass in Wiki.js through 2.5.314 allows an authenticated user who has been granted access to at least one folder to read and modify unrelated pages whose paths share a literal prefix with that folder (for example, access to '/docs' also exposes '/docs-internal'). The flaw lies in the START/END page-rule engine, which matches path prefixes without requiring a path-segment boundary. Publicly available exploit code exists; no confirmed active exploitation (CISA KEV) at time of analysis. No vendor-released patch version is identified in the available data, and the assessed CVSS 3.1 base score is 8.1 (High).
Insufficient scope validation in GitLab Enterprise Edition lets an authenticated user holding only Developer permissions run security policy test pipelines inside projects in their own group and read protected CI/CD variables that are meant to be restricted to Maintainer or Owner roles. All EE releases from 19.0 up to 19.1.8, 19.2.6 and 19.3.2 are affected, and GitLab shipped fixes in those patch releases. Publicly available exploit code exists (a HackerOne report is referenced), but there is no confirmed active exploitation and no CISA KEV listing.
Arbitrary file write via path traversal in ComfyUI before 0.30.0 lets an attacker place attacker-controlled content anywhere on the host filesystem by supplying a crafted folder_name to the dataset save nodes. According to the vendor vector, no authentication is required (PR:N), but exploitation requires user interaction in the form of the victim loading and running a malicious workflow (UI:P); code execution does not occur immediately and instead follows when the written startup file or package initializer is subsequently loaded. Publicly available exploit code exists (a published PoC walkthrough and a VulnCheck advisory), the affected versions are in default configurations, and the vendor has released a fix in 0.30.0; there is no indication of confirmed active exploitation (CISA KEV), and this is not an unauthenticated remote worm-class flaw despite its 8.5 severity, because the local vector and mandatory workflow-import step constrain delivery.
A high-privileged authenticated attacker can inject and execute arbitrary operating-system commands on the Ruijie RG-EW3000GX router running firmware EW_3.0(1)B11P380, through the user_list_note functionality that manipulates the Name argument resolved from /etc/rg_config/admin. The vulnerability is network-reachable and requires no user interaction, but the CVSS vector (PR:H) confirms it is only exploitable after obtaining administrator credentials for the device management interface, so anonymous internet attackers cannot reach it directly. Publicly available exploit code exists (a GitHub proof-of-concept for the RG-EW3000GX user_list_note flaw), which materially raises the likelihood of post-authentication abuse, particularly on routers whose management plane is exposed to the WAN or protected by weak/default admin passwords; no CISA KEV entry has been reported for this CVE.
OS command injection in the Ruijie RG-EW3000GX router (firmware EW_3.0(1)B11P380) lets an attacker who already holds a valid administrator session execute arbitrary shell commands on the device by injecting metacharacters into the data.url argument of a configChange request handled by the cc_set function in unifyframe-sgi.elf. Exploitation is remote and low-complexity once admin access is obtained, and publicly available exploit code exists (PoC disclosed via GitHub and VulDB), though there is no CISA KEV confirmation of active exploitation. Because the CVSS vector carries PR:H and the independent assessment confirms the configChange/cc_set path is not reachable pre-authentication, this is a real but privilege-gated vulnerability rather than an unauthenticated takeover.
Improper sanitization of user-controlled data in GitLab CE/EE's Markdown JSON table renderer allows crafted content to make a targeted user's browser issue unintended state-changing HTTP requests when the rendered page is viewed, affecting versions from 15.3 through 19.1.7, 19.2.5 and 19.3.1. Exploit details are publicly available through a linked HackerOne report, and the vendor CVSS of 8.2 reflects network reachability, a high attack-complexity rating, required user interaction and a scope change. Vendor-released fixes are 19.1.8, 19.2.6 and 19.3.2.
Cross-site request forgery in djust's Server-Sent-Events transport affects all versions prior to 1.0.7 and allows a cross-origin attacker page to drive a victim's cookie-authenticated SSE session, firing state-changing LiveView event handlers as that victim. Remote attackers need no authentication of their own, but exploitation requires the victim to be lured to an attacker-controlled page while holding an active authenticated djust session and while the SSE transport is enabled (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N - integrity impact only, no confidentiality or availability impact). The flaw is fully fixed in 1.0.7 (Origin validated against ALLOWED_HOSTS with 403 for cross-origin requests, and POST endpoints now requiring Content-Type: application/json with 415 otherwise); no public exploit code was identified at time of analysis and the CVE has not been listed in CISA KEV.
OS command injection in Arista VeloCloud Edge management and configuration workflows allows input supplied through those workflows to be interpreted as an operating-system command, resulting in command execution with elevated privileges on the appliance. Exploitation requires a high-privileged management request or the ability to write a configuration value, so this is primarily a privileged-insider, compromised-admin-account, or post-compromise escalation risk rather than an unauthenticated internet-facing flaw. No public exploit code or active exploitation has been identified at time of analysis, and no EPSS score was supplied with the record.
Unauthenticated denial of service in GitLab CE/EE caused by flawed resource accounting in the GraphQL complexity calculation logic, allowing a crafted query to consume disproportionate server resources. Exploitation affects GitLab 18.4.6 through 19.1.7, 19.2.0 through 19.2.5, and 19.3.0 through 19.3.1 - any Internet- or network-reachable instance with the GraphQL API enabled. Public exploit code exists (a HackerOne report is cited as the source), but there is no CISA KEV listing confirming active in-the-wild exploitation at time of analysis.
Unauthenticated denial of service in GitLab CE/EE (all versions from 18.4.6 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2) allows a remote attacker with no credentials to exhaust server resources through the GraphQL API by submitting queries whose true cost the complexity calculation under-counts. The flaw is an improper resource-allocation limit (CWE-770), scored CVSS 7.5 with the entire impact on availability (A:H) and none on confidentiality or integrity. Publicly available exploit code exists - a HackerOne report is linked from the advisory - but there is no CISA KEV listing, so active in-the-wild exploitation is not confirmed; EPSS data was not supplied with this record.
Path traversal in decap-server's local proxy containment guard allows an unauthenticated attacker to read, write, or delete files outside the intended repository root whenever a sibling directory's name begins with the repository directory's name. Affected is the decap-server package shipped in the decaporg/decap-cms monorepo, confirmed at commit 11f35405cd1a1d1216e97b890173f46436752019, with the CPE wildcard suggesting all tracked versions of decap-server are in scope. Exploitation requires the local proxy backend to be running, victim interaction to drive requests to it, and the presence of a suitably named sibling directory containing the target files; publicly available exploit code exists, but there is no indication of confirmed active exploitation (no CISA KEV listing) at time of analysis, so this reads as a real but tightly scoped issue rather than a mass-exploitation priority.
Revoked users of suitenumerique Docs prior to 5.4.1 can retain real-time read and write access to nested sub-documents, because the server resets collaboration websocket rooms only for the document whose permissions changed and not for its descendants. An attacker who is a previously authorized user (authenticated, PR:L per the CVSS vector) and who already holds an open websocket session to a sub-document keeps that session alive after their access is revoked at the parent level, allowing continued viewing and editing of content they should no longer reach; the impact is bounded by the requirement that a live session already exist at the moment of revocation (AC:H, AT:P), and no KEV-listed active exploitation has been reported, though publicly available exploit code exists. This is an offboarding and session-expiration failure (CWE-613) rather than an unauthenticated intrusion vector, and the assessed CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N) aligns with the high confidentiality and integrity impact described.
Cross-site request forgery in phpList before 3.6.17 allows remote attackers to silently delete and blacklist arbitrary subscriber addresses by inducing a logged-in administrator to load a crafted page, with no attacker credentials required on the target (CVSS 4.0 vector PR:N/UI:P). The vulnerable code path is the mass subscriber removal handler (public_html/lists/admin/massremove.php), which processes removal requests without validating a CSRF token, so the request is executed with the administrator's own session privileges. Rated 7.2 by the CVSS 4.0 vector and scored integrity high with limited availability impact by the independent assessment, the flaw requires the admin to be authenticated and to be lured into visiting an attacker-controlled page while that session is valid - this user-interaction prerequisite is the main limiting factor. Publicly available exploit code exists (referenced by VulnCheck and a public write-up), but there is no indication of confirmed active exploitation (not in CISA KEV).
Arbitrary file deletion in zlt2000 microservices-platform through 6.0.0 allows authenticated attackers to delete any user's files and metadata due to missing ownership validation in the file-center module's DELETE /files/{id} endpoint. Attackers can enumerate file identifiers via GET /files and then delete arbitrary files, bypassing authorization controls (CWE-639); publicly available exploit code exists. Exploitation requires a valid, low-privilege account (PR:L) with access to the file-center REST API, and the impact is limited to integrity and availability (no data disclosure), with a CVSS 4.0 base score of 7.2.
Authenticated token holders can drive the Playwright websocket endpoints of browserless to file:// URLs and read arbitrary files available to the container process, affecting versions 1.44.0 through 2.56.7. The setting intended to prevent this, ALLOW_FILE_PROTOCOL, already defaults to false, but it is simply not enforced on the Playwright path, so exploitation requires no non-default configuration and no user interaction - only a valid token (CVSS vector PR:L) and network reachability to the websocket endpoint. Publicly available exploit code exists, and while the disclosed CVSS of 7.1 reflects high confidentiality impact, practical exposure is bounded to files readable by the container process, so container isolation and minimal secret mounts materially limit the blast radius.
Server-side request forgery in Wiki.js through 2.5.314 lets an authenticated user who holds page-editing permissions force the server to fetch arbitrary URLs on their behalf, including internal services and cloud instance metadata endpoints, with the fetched response returned to the attacker. The flaw sits in the Image Prefetch renderer, which resolves the src of any img element tagged with the prefetch-candidate class without validating protocol, host, or resolved address; publicly available exploit code exists, and the assessed impact is information disclosure only (high confidentiality, no integrity or availability effect). Exploitation is constrained by the need for an account with editing rights and by the server's network reachability to the intended internal or metadata target, making this a genuine but moderate-priority issue rather than a pre-auth or remote-code-execution class bug.
Harbor through 2.15.2 can disclose scanner adapter AccessCredential secrets to an authenticated project administrator who abuses fuzzy q-parameter filtering and observes response row counts one character at a time. This is a privilege-gated confidentiality issue rather than a critical remote-takeover flaw: the attacker must already hold a project-admin role and must issue many sequential API requests, with no user interaction and no special feature toggle required in default configurations. Publicly available exploit code exists, and the supplied data does not confirm active exploitation by CISA KEV.
Mass assignment in djust, a Django library providing Phoenix LiveView-style reactive server-side rendering, allows any client with an established WebSocket session to overwrite arbitrary public attributes on a LiveView instance through the framework's default `update_model` event handler. The handler ships in `djust.mixins.model_binding.ModelBindingMixin`, which sits in the LiveView base MRO and is therefore exposed by every view, and it `setattr`s a view attribute whose name is supplied entirely by the client - gated only by a 14-entry framework-internal denylist, an underscore-prefix rejection, and an opt-in `allowed_model_fields` allowlist that defaults to `None` (allow all). Affected deployments are djust versions prior to 1.0.7 that leave the allowlist unset and keep authorization, ownership, or business state such as `self.account_id`, `self.is_admin`, or `self.total_price` as public view attributes; the advisory's own reproducer set all three without any `dj-model` binding. Exploitation yields state tampering that can escalate to authorization-flag manipulation or IDOR when downstream handlers act on the tampered attributes without re-authorizing, giving a High integrity impact with no confidentiality or availability impact (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N); no public exploit code was identified at time of analysis and there is no CISA KEV entry, though the vendor retained a private reproducer.
Authenticated attackers can read arbitrary Elasticsearch indices in zlt2000 microservices-platform through 6.0.0 by supplying any index name in the POST /search/{indexName} or GET /agg/requestStat/{indexName}/{routing} endpoints, bypassing authorization checks. This exposes sensitive data such as the sys_user index containing user records and password hashes; the vulnerability has a CVSS 4.0 base score of 7.1 and an assessed CVSS 3.1 vector of AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, meaning high confidentiality impact with no integrity or availability effect. Publicly available exploit code exists (no CISA KEV confirmation), and exploitation requires only a valid low-privilege session on a network-reachable search-center service.
Authenticated back-office users of yshop-crm through 2.1.3 can enumerate the complete user directory via GET /admin-api/system/user/page because the endpoint's @PreAuthorize('system:user:list') gate is commented out in UserController.java. The flaw is a broken-access-control issue (CWE-862) that requires valid admin-panel credentials plus a role configured with data scope ALL; without that scope the query returns little of value, but with it an attacker can harvest login names, nicknames, departments, emails, mobile numbers, and last-login metadata. Publicly available exploit code exists (a Python enumeration PoC), and no CISA KEV entry confirms active exploitation at time of analysis. The independent assessment rates this CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, meaning authenticated remote confidentiality loss only - no integrity or availability impact.
Missing authorization in yshop-crm 2.1.3 and earlier lets any authenticated back-office (admin-api) user delete arbitrary approval-workflow steps via DELETE /admin-api/crm/flow/delete-step, bypassing the permission check that should restrict this to workflow administrators. The result is an integrity-only compromise of the approval chains that gate contract, receivable, and invoice finalization; there is no confidentiality or availability impact, and the CVE record's CVSS 4.0 score of 7.1 maps to an independent CVSS 3.1 assessment of AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N, i.e. a genuine but moderate-priority missing-authorization flaw rather than a critical takeover. Publicly available exploit code exists (a Python PoC against the delete-step endpoint); no CISA KEV listing or other confirmation of active in-the-wild exploitation was present in the supplied data.
Missing authorization in yshop-crm through 2.1.3 allows any authenticated back-office user - including low-privilege operators - to read the installation-wide audit trail by calling GET /admin-api/crm/operatelog/page, exposing operator names, display nicknames, client IP addresses, User-Agent strings, request URLs, action details, and customer identifiers. Publicly available exploit code exists (a PoC script that queries the endpoint), and although exploitation requires a valid back-office session with network reach to the admin API, no elevated role or user interaction is needed, so the realistic threat is a malicious insider or anyone who has reused or stolen an operator credential. The vulnerability is broken access control (CWE-862) with high confidentiality impact only; it does not permit data modification, service disruption, or pre-authentication compromise.
Missing authorization in yshop-crm through 2.1.3 allows any authenticated back-office user to claim and reassign sales leads belonging to other employees by invoking the CrmCluesController receiveCustomer lead-claim endpoint with a manipulated ownerUserId value. The flaw is a broken access control (CWE-862) issue that requires only a valid low-privilege staff login and no administrative role, feature toggle, or user interaction, with the practical impact limited to integrity of lead ownership data (no confidentiality or availability impact). Publicly available exploit code exists in the form of a Python proof-of-concept targeting the endpoint, and the absence of access logging or quota validation on the operation removes any built-in brake on bulk lead theft, though no confirmed active exploitation (CISA KEV) has been observed at time of analysis.
Missing authorization in yshop-crm through 2.1.3 allows any authenticated back-office user to issue arbitrary invoices by calling the PUT /admin-api/crm/invoice/issue endpoint, which performs no permission check on the caller. An attacker holding low-privileged back-office credentials can set an invoice's status, overwrite contract invoiced amounts with attacker-chosen values, and trigger invoice emails to arbitrary recipient addresses - a pure integrity impact with no confidentiality or availability loss. Publicly available exploit code exists (a Python PoC in the LinYuanyi1 cve-request-poc repository), but there is no evidence of confirmed active exploitation (CISA KEV).
Missing authorization in yshop-crm through 2.1.3 lets any authenticated back-office user, regardless of role or privilege level, invoke the saveRedisSet and getRedisSet endpoints in CrmCustomerController and rewrite the installation-wide Redis keys that drive lead allocation and customer auto-recycling. Because the scheduled CustomerAutoJob consumes those same keys, a low-privilege staff account can disable recycling, block customer creation, or trigger mass customer deletion across the deployment; publicly available exploit code exists (the VulnCheck-referenced CVE request PoC on GitHub), while no active exploitation has been confirmed and the CVE is not listed in CISA KEV. This is a genuine but bounded-priority issue: exploitation requires a valid CRM account (assessed CVSS PR:L, so unauthenticated remote abuse is not possible), and the assessed impact is high integrity loss to shared policy state (I:H) with a limited availability effect (A:L) and no confidentiality loss (C:N - the readable values are configuration/policy keys, not customer records).
Socket and memory exhaustion in node-opcua clients (packages node-opcua, node-opcua-client and node-opcua-transport, versions 2.0.0 through 2.169.x) can terminate the Node.js process or container via OOM kill when the client is configured with the default keepSessionAlive: true and connects to an OPC UA server whose clock is skewed well beyond the server's RequestHeader timestamp tolerance. Two compounding defects cause this: the keepalive manager misclassifies the server's BadInvalidTimestamp status code as a network outage and forces a full transport reconnection on every keepalive cycle, while the HEL/ACK failure handler calls socket.end() instead of socket.destroy(), leaving each abandoned connection in FIN-WAIT-2 so leaked sockets accumulate roughly once per keepAliveInterval (about 1,200 per hour at the default 3-second interval). The vector is network-reachable and unauthenticated (PR:N), but exploitation is high-complexity and conditional on clock skew plus a peer that never completes the TCP close; no public exploit code or confirmed active exploitation was identified at time of analysis, and impact is confined to availability of the affected client process (C:N/I:N/A:H).
Server-side request forgery in Metabase through 0.63.18 lets an attacker bypass GeoJSON URL validation by saving a custom GeoJSON entry that points at the unspecified address 0.0.0.0, which resolves to loopback and causes the Metabase server to fetch from services bound to localhost and return their responses to the caller. Note a conflict in the source data: vendor scoring (CVSS 4.0 with PR:H) requires high-privileged, authenticated access to persist the malicious GeoJSON entry, while the CVE description asserts that the triggered read is returned to unauthenticated callers - the authentication bar for triggering and reading should be verified against the vendor advisory. Publicly available exploit code exists (VulnCheck advisory and a public write-up), there is no CISA KEV listing indicating confirmed active exploitation at time of analysis, and impact is confidentiality-only, since only response data is exposed with no integrity or availability effect.
Token generation in EspoCRM through 10.0.8 relies on PHP's non-cryptographic rand() function, producing roughly 31-bit identifiers for lead-capture opt-in links, event invitations, and campaign URLs. Remote unauthenticated attackers who can reach those public endpoints can guess or enumerate valid tokens, allowing them to confirm opt-ins, accept or decline event invitations on behalf of other contacts, and read event details. Publicly available exploit code exists (a vendor commit and a public write-up), but there is no evidence of confirmed active exploitation in the wild, and the CVSS 6.3 rating reflects high attack complexity and only low confidentiality/integrity impact.
Arbitrary code execution in Arista EOS with the gRPC Network Packet Sampling Interface (gNPSI) enabled allows an unauthenticated gNPSI client to craft a malicious request that executes code on the switch, yielding full administrative control of the device. The exploit path is gated by a hard precondition: gNPSI is not enabled by default and the gRPC endpoint must be network-reachable, which the vendor vector captures as AT:P and the advisory describes as 'under certain circumstances'; given that condition, no authentication (PR:N) or user interaction (UI:N) is needed. The vulnerability is rated critical (CVSS 4.0 base 9.2, independent 3.1 assessment AV:N/AC:H/PR:N/UI:N with high confidentiality, integrity, and availability impact), and no public exploit code has been identified at time of analysis, so realistic risk is concentrated on switches where gNPSI has been turned on and exposed to untrusted network segments.
Server-side request forgery in the UnifiedLogin service of on-premises Altium Enterprise Server lets an unauthenticated network attacker force the server to issue outbound HTTP requests to arbitrary destinations, including internal-only services. By targeting an internal configuration endpoint that exposes credential material without authentication (relying solely on the request originating locally), the attacker inherits that trusted locality, steals stored credentials, and uses them to obtain an administrative session, resulting in full compromise of the server and its services. Altium 365 cloud deployments are not affected because the vulnerable endpoint is disabled in cloud mode; no public exploit code has been identified at time of analysis, though the assessed severity is maximum (CVSS 10.0 / 3.1 base 10.0).
Unauthenticated remote code execution in Dell ObjectScale affects all versions prior to 4.4.0.0, where deserialization of untrusted data (CWE-502) can let a network-reachable attacker execute arbitrary code on the appliance. Both the vendor/NVD vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) and our independent assessment score the issue 10.0, reflecting low-complexity, pre-auth exploitation with full confidentiality, integrity, and availability impact and no user interaction; the practical limiting factor is exposure, since instances not reachable from the attacker's position are not exploitable. No public exploit code has been identified at time of analysis and the vulnerability is not confirmed actively exploited (no CISA KEV listing), and a vendor patch is available in ObjectScale 4.4.0.0.
Authentication bypass in Pepperl+Fuchs ICE2/ICE3-series IO-Link masters (and OEM-equivalent Phoenix Contact IOL-MA8 modules) lets a remote unauthenticated attacker reach the _account_log function and authenticate as administrator, even on devices where accounts are correctly provisioned. The flaw grants full administrative control of the device management interface with no credentials. Reported by CERT@VDE; no public exploit code and no active-exploitation evidence are present in the available data, though the CVSS 9.8 rating reflects trivial exploitability.
Root-level remote code execution affects Pepperl+Fuchs ICE2/ICE3-series and Phoenix Contact IOL-MA8 IO-Link master gateways, where an unauthenticated attacker uploads a crafted IODD (IO Device Description) file that drops and executes an arbitrary shell script as root. The injected script survives reboot, granting persistent full control of the industrial device. No public exploit is identified at time of analysis and the CVE is not in CISA KEV, but the CVSS 9.8 rating reflects trivial network reachability and complete device compromise.
Improper access control defects in Cisco Secure Firewall ASA, FTD, and FMC software allow an authenticated, low-privileged attacker with network reachability to escalate privileges and achieve a full loss of confidentiality, integrity, and availability, with a scope change that extends the impact beyond the vulnerable component itself (CVSS 3.1 base 9.9, Critical). The issues were uncovered during Cisco's internal security review and are shipped as a grouped hardening fix rather than tied to one named feature, so no single vulnerable configuration toggle is disclosed. No public exploit code and no confirmed active exploitation were identified at time of analysis, but the very broad affected version range (ASA 9.16 through 9.24, FTD 7.0 through 10.0.0, FMC 7.0 through 10.0.1) means unpatched appliances remain exposed to any attacker who already holds valid low-privileged credentials.
Authenticated remote code execution as root affects Cisco Secure Firewall Management Center (FMC) software. An attacker who possesses valid user credentials on the FMC - or who can hijack an established sftunnel peer connection - can send a crafted sftunnel command that writes a malicious file to any location on the device, and that file is then executed with root privileges (CVSS 9.9, CWE-862). Authentication is required (CVSS vector PR:L), no user interaction is needed, and the sftunnel path is normally used between FMC and managed firewall devices rather than being exposed to arbitrary internet clients; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV.
Command injection (CWE-77) in Cisco Nexus Dashboard allows a remote, authenticated attacker holding low-privilege credentials to inject and execute arbitrary commands, carrying a vendor-assigned CVSS of 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) with high confidentiality, integrity, and availability impact and a Scope:Changed rating. The flaw was disclosed as one of multiple issues fixed in a grouped Cisco internal 'hardening release' advisory (cisco-sa-hardening-ndw1-psFvnrg) rather than a single externally reported CVE, so specific exploit prerequisites and exact affected version boundaries should be confirmed against that advisory's fixed-release table. Authentication is the primary limiting factor - the attacker must already possess valid low-privilege credentials or a session on the management interface - and no public exploit code or confirmed active exploitation was identified at time of analysis.
Multiple improper neutralization flaws in Cisco Secure Firewall ASA, Threat Defense (FTD), and Management Center (FMC) software can let a low-privilege, authenticated remote attacker cause high-impact confidentiality, integrity, and availability effects on affected appliances, with information disclosure flagged among the affected weaknesses. Cisco scores the bundled issues 9.9 under CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, where the scope change (S:C) and complete C/I/A impact push the rating into critical territory despite requiring a valid low-privilege credential and no user interaction. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; the fixes were produced through an internal hardening review rather than in response to observed attacks, so real-world urgency cannot be confirmed from the available signals.
Improper access control in Cisco Nexus Dashboard, Cisco's data-center orchestration and management appliance, allows a network-positioned attacker who already holds a valid low-privileged account to exceed their intended permissions, with the scope-change (S:C) scoring producing full confidentiality, integrity, and availability impact. Cisco rates the flaw CVSS 9.9 (Critical) under vector AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H; because PR:L is required, this is explicitly an authenticated flaw - a legitimate or stolen operator-level credential is a prerequisite, and it is not unauthenticated. The issue was discovered during Cisco's internal security review and shipped in a hardening release, so no public exploit code exists and there is no confirmed active exploitation (no CISA KEV listing) at time of analysis; reachability is further limited because Nexus Dashboard is typically deployed on internal management networks rather than exposed to the internet.