Unauthenticated remote code execution in Rejetto HFS2 (HTTP File Server) through version 2.4.0 lets an attacker execute arbitrary commands on the underlying host by hiding server-side template syntax inside the filename of a multipart file upload. The crafted filename closes the template quoting context and injects an exec macro, which bypasses the dispatcher's authorization check, so no credentials or user interaction are required (assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; vendor score 10.0). Publicly available exploit code exists and an advisory with a proof-of-concept walkthrough is referenced by VulnCheck, but no KEV entry was provided, so this is not confirmed as actively exploited; the practical limiting factor is whether the multipart upload endpoint is reachable from the attacker's network.
Unauthenticated arbitrary file read, write, append, and delete in Rejetto HFS2 up to and including 2.4.0 allows remote attackers to compromise the confidentiality, integrity, and availability of the host filesystem. The vulnerability arises because the template engine's macro dispatcher performs no authorization check and the path resolver fails to confine absolute paths to the shared folder, letting attackers manipulate macros to access files anywhere the HFS service account has permissions. Public exploit code exists, and exploitation works against default configurations; the legacy 2.x branch is affected, while HFS 3.x is a separate codebase.
Unauthenticated local file inclusion in the Visual Composer Website Builder plugin for WordPress (all versions up to and including 45.16.0) lets remote attackers supply the vcv-template request parameter to force the server to include and execute files of their choosing. Because the vulnerable code path is reachable without authentication (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), attackers can directly bypass access controls and read sensitive files on the host; full PHP code execution is achievable only where the attacker can also plant an includable file (for example an uploaded image or other supposedly 'safe' file type) on the server. At time of analysis there is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified, though the Wordfence advisory and the plugin's own Trac changeset confirm an upstream fix has been committed.
Unauthenticated privilege escalation in the Paytium: Mollie payment forms & donations WordPress plugin (all versions up to and including 5.0.3) allows an attacker to create a brand-new WordPress user with the administrator role and take over the site. The flaw lives in the unsigned pt_cf_checkout_meta() filter on the pt_meta_values hook, which copies attacker-supplied $_POST['pt_form_field'] keys, including pt-user-role, straight into payment meta and ultimately into wp_insert_user(); exploitation requires a publicly reachable [paytium] shortcode form and completion of an actual Mollie payment so the malicious role meta is persisted, after which the attacker claims the new admin account via the standard lost-password flow. No public exploit code was identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV), though the vendor-published Wordfence advisory and the 9.8 CVSS rating (AV:N/AC:L/PR:N/UI:N) make this a high-priority unauthenticated issue for any site running the affected versions with a public Paytium form.
XML External Entity (XXE) injection in http4s-scala-xml's EntityDecoder for scala.xml.Elem (all versions before 0.24.1 and 1.0.0-M39) allows unauthenticated remote attackers who can supply XML message bodies to disclose files readable by the service process, perform server-side request forgery (SSRF) against internal network resources, or trigger denial of service via entity expansion. The decoders obtain a javax.xml.parsers.SAXParserFactory through SAXParserFactory.newInstance without configuring secure-processing features, so JDK default behavior resolves DOCTYPE declarations, external general and parameter entities, and external DTDs. Vendor-released fixes are 0.24.1 and 1.0.0-M39; no public exploit code has been identified at time of analysis, and reachability depends on an application actually using these decoders against untrusted XML.
Unauthenticated MCP tool invocation in DBHub versions prior to 0.22.5 allows a malicious website to reach the HTTP transport endpoint and dispatch database tool calls against connected Postgres, MySQL, SQL Server, Oracle, MariaDB, or SQLite databases, because the server's Origin-equals-Host check is defeated by DNS rebinding. The flaw applies only when DBHub is launched in the non-default HTTP transport mode (for example --transport http --port 8080); the default stdio transport is unaffected, and exploitation requires a victim's browser to load attacker-controlled content and successfully complete the rebind window, per the independent assessment. No public exploit has been identified at time of analysis, and while the CVSS 4.0 vector scores 9.3, the assessed real-world severity is lower (CVSS 3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L), with impact bounded by DBHub's configured tool permissions and database credentials - read-only configurations limit exposure to disclosure.
Improper firmware authenticity verification in the Botslab G980H dash camera allows an attacker who can intercept the device's firmware download or supply a crafted update package to install modified firmware and execute unauthorized code on the device. The update process fetches firmware over an unprotected connection and validates only an integrity value delivered alongside the payload rather than a trusted cryptographic signature, so anyone who controls the delivered bytes and recomputes that value defeats the check. The assessed CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) rates this as high severity but with a harder attack path than the vendor-published CVSS 4.0 score of 9.2 suggests, since the attacker needs either an on-path network position between camera and update source or authenticated update-submission access; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the intelligence signals around this advisory remain thin.
Decepticon versions prior to 1.1.17 fail to neutralize ChatML-style special-token literals (e.g. <|im_start|>, <|eot_id|>, <start_of_turn>, [INST], <<SYS>>) embedded in web crawl results returned by agent reconnaissance, so an attacker who plants such a string on a crawled page can forge an authoritative operator turn that the model acts on, bypassing Decepticon's agent guardrails and achieving arbitrary command execution inside the Kali Linux sandbox. Exploitation is unauthenticated (PR:N) but conditional: it requires the BYOK deployment model with a self-hosted or OpenAI-compatible backend (vLLM, SGLang, TGI, Ollama, LM Studio, text-generation-webui) whose tokenizer preserves special-token IDs, and the operator must actually crawl attacker-controlled or attacker-compromised content - both normal for a red-team tool. Deployments using hosted providers such as OpenAI or Anthropic are not vulnerable because those strip special tokens server-side; no public exploit code has been identified at time of analysis, and the advisory ships with a vendor fix in 1.1.17.
Command injection in Dokploy before 0.29.13 lets an authenticated organization member with service:read permission execute arbitrary commands as root inside the Dokploy container by injecting shell metacharacters into the repoPath parameter of the patch.readRepoDirectories tRPC procedure. Because the standard deployment mounts /var/run/docker.sock, successful exploitation can pivot to control Docker and compromise the host and its managed applications; the vendor fix is available in 0.29.13, and no public exploit identified at time of analysis. The vulnerability is rated CVSS 9.9 with scope change and high confidentiality, integrity, and availability impact.
Privilege escalation in Rapid7 Velociraptor allows an authenticated user holding only the 'investigator' role to execute arbitrary VQL statements with administrator privileges on the Velociraptor server by populating the internal 'compiled_collector_args' field when submitting a hunt-creation/scheduling API request. Because the server accepts this internal field from the caller, the attacker-supplied pre-compiled VQL is trusted and the ACL checks that normally gate artifact compilation are skipped (CVSS 9.9, AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). Exploitation requires a valid investigator-or-higher account that can schedule hunts, making this an insider/privilege-escalation path rather than an unauthenticated remote compromise; no public exploit identified at time of analysis, and no confirmed actively exploited (CISA KEV) status was provided. The vendor advisory is published at https://docs.velociraptor.app/announcements/advisories/cve-2026-19072/.
Use-after-free in the Linux kernel's server-side SUNRPC RPCSEC_GSS credential decoder (svcauth_gss_decode_credbody) leaves the pooled per-request credential (svcdata->clcred in gss_svc_data) holding a dangling gc_ctx.data inline pointer into a released request XDR page while gc_ctx.len still carries a stale length from an earlier request, so a downstream length-driven consumer such as gss_svc_searchbyctx() walks freed memory. Exposure is limited to hosts running an NFS server with RPCSEC_GSS/Kerberos security enabled (exports mounted with sec=krb5, krb5i, or krb5p); systems using only AUTH_SYS or running no NFS server are not affected. A remote, unauthenticated attacker who can reach the GSS-enabled service and craft a credential body that fails XDR decode can trigger the fault, but reliability is limited because the dangling state depends on residue from a prior request and on the request pages being released, so denial of service with limited information disclosure is the realistic outcome rather than assured code execution; no public exploit identified at time of analysis, and vendor patches are available for the affected stable trees.
Out-of-bounds memory access in the Linux kernel's RDMA RTRS server (rtrs-srv) module, used by RNBD remote block devices, is reachable by an unauthenticated remote attacker (CVSS vector PR:N) who can open an rtrs client session over an RDMA/RoCE/InfiniBand fabric and send a process_read or process_write message whose network-supplied usr_len field exceeds off. The unchecked subtraction data_len = off - usr_len underflows to a huge size_t that is then handed to the rdma_ev callback as a memory length, producing the out-of-bounds access. The independent assessment rates this AV:N/AC:L/PR:N/UI:N/S:U with Low confidentiality and integrity impact and High availability impact (substantially below the vendor's 9.8), and practical exposure is narrowed because rtrs-srv is not present on general-purpose systems and requires RDMA-fabric reachability rather than ordinary IP routing; no public exploit code identified at time of analysis.
Improper authentication in Delta Electronics DIAEnergie before 1.11.00.022 allows authentication bypass, enabling remote attackers to reach protected functionality without valid credentials. The flaw carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires no authentication, no user interaction, and no non-default configuration - only network reachability to the DIAEnergie service. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); the practical exposure is limited chiefly by the product's footprint, as DIAEnergie is a niche ICS energy-management platform typically deployed on operational or enterprise networks rather than the public internet.
A credential-isolation flaw in geelen mcp-remote 0.1.16 through 0.1.38 allows a remote attacker who controls or can predict the MCP server URL a victim configures to cause MD5-derived credential-store paths to collide or match, potentially exposing or overwriting another server's cached OAuth tokens via the getServerUrlHash function in src/lib/utils.ts. The package is an npm bridge that connects local MCP clients to remote MCP servers, so practical exploitation depends on the victim adding the attacker's server URL and on the OAuth credential-persistence feature being in use (user interaction), which is inconsistent with the no-interaction AV:N/AC:L/PR:N/UI:N profile of the 9.8 headline score. No public exploit code was identified at time of analysis and EPSS is low (0.29%, 19th percentile), so the CWE-94 arbitrary-code-execution framing should be treated as unverified rather than confirmed remote code execution.
Session fixation in the HTTP management interface of Apache Qpid Broker-J through 10.1.0 lets remote, unauthenticated attackers hijack an administrator's authenticated management session by reusing a session identifier that is retained across successful authentication, yielding full confidentiality, integrity, and availability impact (C:H/I:H/A:H) over the broker's management functions. Exploitation requires the HTTP management interface to be reachable by the attacker and, critically, requires a legitimate management user - typically an administrator - to authenticate using a session identifier the attacker has planted, fixed, or otherwise obtained before login, so the assessed vector is AV:N/AC:H/PR:N/UI:R rather than the NVD-published 9.8 CRITICAL (AC:L/UI:N), which is inconsistent with the session-fixation class. There is no public exploit identified at time of analysis, and brokers are only exposed where management access is not otherwise restricted; upgrading to 10.1.1 addresses the flaw.
Heap out-of-bounds write in QuickJS's bytecode deserializer (JS_ReadFunctionTag) lets a crafted serialized blob corrupt heap memory, giving an attacker the potential for arbitrary code execution in the context of the host process. The flaw is only reachable when the embedding application calls JS_ReadObject with the JS_READ_OBJ_BYTECODE flag on attacker-controlled input - not the default pattern of executing JavaScript source - so exposure is confined to plugin, cache, or IPC loaders that treat serialized bytecode as untrusted data; where that path is exposed, the flaw is remotely triggerable by an unauthenticated attacker (CVSS vector PR:N) with a single malformed blob and no user interaction. Public exploit code has not been identified at time of analysis (EPSS 0.17%, 5th percentile), and while the vendor score is 9.8 with AC:L, an independent assessment rates attack complexity as high (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) because exploitation depends on a non-default deserialization path in the hosting application.
Integer overflow in minimp3's mp3dec_skip_id3v1() tag-parsing routine allows a crafted APEv2 tag-size field inside an MP3 file to corrupt internal size arithmetic, which can lead to memory corruption in any application that decodes untrusted audio with a build at or around commit ea99364f. The CVSS vector supplied with the record is 9.8 (AV:N/AC:L/PR:N/UI:N), but our assessment lowers user interaction to UI:R: minimp3 is a passive single-header decoder library, so a victim or automated ingestion pipeline must open or feed the malicious file before the overflow is reachable, and there is no direct network attack surface in the library itself. No public exploit code has been identified at time of analysis, EPSS is low at 0.15% (3rd percentile), and the CVE is not listed in CISA KEV, so exploitation is unconfirmed and real-world risk depends on whether the consuming application processes hostile media.
Heap-buffer-overflow in MPack 1.1.1's Node (tree) parsing API on 32-bit platforms lets remote, unauthenticated attackers corrupt memory and crash the host application by delivering a MessagePack array32 or map32 header that declares an oversized element count. The declared count overflows the size_t arithmetic used to size an internal page allocation in mpack_tree_parse_children(), producing an undersized heap buffer that is then written past its end with mpack_node_data_t records. Exploitation is constrained to 32-bit builds that call the tree/Node API on attacker-supplied data: on 64-bit builds the overflow is effectively unreachable, and applications using only the streaming Expect/Reader API are not affected. EPSS is 0.14% (3rd percentile), there is no CISA KEV listing, and no public exploit code has been identified at time of analysis; NVD scores this 9.8, while independent assessment rates it lower (C:L/I:L/A:H) because of the 32-bit-only deployment prerequisite.
The Perl CPAN distribution IO::Socket::SSL::SelfCertificate version 1.00 is itself the attack artifact: its generate_certificate() routine writes a Python script disguised as a certificate file and executes it, causing base64-obfuscated code to be fetched from a hardcoded HTTP URL and run in memory without ever dropping a script to disk. Anyone who installs the 1.00 tarball and calls that function is exposed - a local, unauthenticated action requiring user interaction (assessed CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), rather than the remote pre-authentication scenario implied by the CNA's 9.8 network vector - and outbound HTTP egress must be reachable for the payload to be retrieved. The advisory notes there are no test scripts or build hooks, so nothing fires automatically at install time and the payload must be manually triggered; no public exploit code beyond the malicious package itself has been identified at time of analysis, EPSS is negligible at 0.12% (1st percentile), and the nearly identical CVE-2026-95831 covers the sibling Crypt::SelfCertificate module.
Unauthenticated remote code execution in Honeywell PD45 Industrial Printer firmware F10.19.010040 lets any network-reachable attacker upload attacker-controlled files through the web management interface and execute them as malicious files and commands. The CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H) reflects the complete absence of authentication or user interaction required, consistent with CWE-306 missing authentication for a critical function, so a single unauthenticated HTTP request path is enough to gain code execution on the device. Honeywell has released fixed firmware F10.22.030745; no public exploit code has been identified at time of analysis, but exposure is constrained mainly by the fact that these industrial printers typically sit on internal warehouse or manufacturing networks rather than the public internet, meaning an attacker usually needs an existing network foothold or adjacent access first.
Out-of-bounds write in the rp-l2tp component of D-Link DIR-825 firmware 3.00b32 allows a remote, unauthenticated attacker to corrupt memory by sending a crafted L2TP Host-Name AVP, with the CVSS 4.0 base score of 9.3 reflecting high confidentiality, integrity, and availability impact. The flaw resides in tunnel_set_params() in tunnel.c, where the peer_hostname argument is copied without adequate bounds validation, so an oversized or malformed value overwrites adjacent memory; because the vulnerable code sits in the L2TP tunnel setup path, an attacker only needs network reachability to the router's L2TP service and no credentials or user interaction. No public exploit code and no confirmed active exploitation have been identified at time of analysis, but the severity and low attack complexity make the exposure significant for any deployment that leaves L2TP enabled on a WAN-facing interface.
Authorization bypass in the ixo Blockchain x/bonds module (all versions before v8.0.0) lets any unauthenticated remote account move another user's token balance into an attacker-controlled bond by simply adding the victim's blockchain address as a verification method on a DID the attacker owns - no victim keys, signatures, consent, or prior system compromise are required. The flaw affects the MsgMakeOutcomePayment, MsgBuy, MsgSell, MsgSwap and MsgWithdrawShare handlers plus the bonds batch order processor and its EndBlocker, and the vendor advisory reports the technique was exploited on ixo mainnet (ixo-5) on 2026-06-20, with the proceeds later withdrawn and bridged off-chain. With a CVSS 9.3 rating, PR:N/UI:N reachability, and every account holding a balance in a bond-usable token in scope, this is a genuine top-priority issue rather than a high-score-but-low-real-risk case.
Improper TLS certificate validation in the eufy Omni C20 robot vacuum allows an attacker who has already obtained a man-in-the-middle position on the device's network path to present a forged certificate, hijack the connection, and ultimately execute arbitrary code on the device. The flaw carries a vendor/NVD CVSS 4.0 score of 9.3 (AV:N/AC:L/AT:N/PR:N/UI:N), but the independent assessment re-rates it as CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L because exploitation is unauthenticated and requires no user interaction yet is gated on a privileged network position - hostile or shared Wi-Fi, a rogue access point, or ARP/DNS spoofing on the LAN path - meaning a purely off-path remote attacker cannot trigger it. Reported through CISA ICS-CERT (ICSA-26-267-02); no public exploit code has been identified at time of analysis and there is no confirmed actively exploited (CISA KEV) status. Devices that only ever connect to trusted, isolated home networks face substantially lower exposure than those on public, guest, or shared networks.
Missing authorization in the ServiceNow AI Platform lets unauthenticated remote attackers, under certain vendor-undisclosed instance conditions, read instance data beyond the intended scope and escalate privileges. ServiceNow has remediated the flaw on its hosted instances and distributed the fix to partners and self-hosted customers, but no public exploit code or active exploitation has been reported and no EPSS score was supplied with the source data. The vendor CVSS 4.0 rating is Critical (9.3), while the independent assessment is lower and treats exploitation as conditional, so unpatched self-hosted or partner-managed instances should still be prioritized given the data-exposure and privilege-escalation potential.
Unauthenticated SQL injection in the ServiceNow AI Platform allows remote attackers to execute arbitrary SQL statements against an instance's underlying database, potentially reading or altering instance data beyond its intended scope. ServiceNow has already remediated its hosted instances and shipped the update to partners and self-hosted customers, so residual exposure is confined to self-hosted or partner-managed deployments that have not yet moved to the patched release described in KB3159623. No public exploit code has been identified and the vendor states it is not aware of malicious exploitation at time of analysis, but the 9.3 CVSS 4.0 rating - along with a more conservative independent assessment that raises attack complexity to High and lowers availability impact - makes prompt patching of any remaining unpatched instance the priority.
Improper JWT signature verification in Dashbit's nimble_zta (0.1.2 up to but not including 0.1.3) lets an unauthenticated remote attacker bypass authentication and impersonate an arbitrary Cloudflare service token in applications using the Cloudflare Zero Trust service-token strategy. Because verify_token/2 pattern-matches the {_, token, _s} tuple returned by JOSE.JWT.verify/2, the boolean signature-verification result is discarded and a forged JWT sent in the cf-access-jwt-assertion header is accepted as authenticated identity; the attacker only needs the expected iss claim plus the seven service-token claims (aud, common_name, exp, iat, iss, sub, type). No public exploit code has been identified at time of analysis, but the flaw is remotely reachable with no authentication or user interaction (assessed CVSS 3.1 base 9.3, scope changed) and is fixed in nimble_zta 0.1.3.
Session token forgery in SigNoz v0.8.0 through v0.142.x allows unauthenticated attackers to impersonate any user, including administrators, when the default JWT tokenizer provider runs without a configured signing secret. The application defaults the JWT HMAC key to an empty string and fails to reject this in Config.Validate(), so tokens are both signed and verified with an empty key; an attacker who knows a target user ID can forge valid access and refresh tokens, and the refresh token can be rotated at /api/v2/sessions/rotate and cannot be revoked. No public exploit identified at time of analysis; deployments that explicitly set a secret or use the opaque provider are not affected, and v0.143.0 eliminates the exposure.
Authentication bypass in OpenStack Zaqar before 22.0.2 allows an unauthenticated remote attacker who knows a target project's UUID to send a request carrying an empty URL-Signature header and defeat both Keystone authentication and pre-signed URL verification, gaining the ability to read, enumerate, create, and delete that project's queues, messages, claims, and subscriptions. Only deployments using the WSGI transport with an authentication strategy configured are exposed; the websocket transport is explicitly not affected, and escalation to administrative operations such as managing pools and flavors additionally requires an admin_mode deployment in which the attacker asserts an administrative role. The issue is rated CVSS 4.0 base 9.2, while independent assessment scores it CVSS 3.1 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) with the AC:H component reflecting the prerequisite knowledge of the victim project UUID; no public exploit code or confirmed active exploitation was identified at time of analysis.
Authentication bypass in PortSwigger Burp Suite DAST (formerly Burp Suite Enterprise Edition) before 2026.8 allows unauthenticated remote attackers to reach restricted functionality through an alternate path or channel, yielding high confidentiality, integrity and availability impact on the scanning platform. The CVSS 4.0 base score of 9.2 and CISA SSVC technical impact rating of 'total' reflect complete compromise of the affected management interface, although an undisclosed attack precondition (AT:P) must be satisfied and the product is normally deployed on segmented internal networks rather than being internet-facing. No public exploit identified at time of analysis, and SSVC exploitation is rated 'none', so this is a serious but not currently imminent priority. Authentication requirements are confirmed unauthenticated by the CVSS vector (PR:N, UI:N). Vendor-released patch: 2026.8.
Linux kernel NFS/RDMA servers using svcrdma accept RPC-over-RDMA Write and Reply chunks whose segcount field is zero, because xdr_check_write_chunk() only rejects segcount values above rc_maxpages and xdr_inline_decode(stream, 0) succeeds without advancing the cursor, causing pcl_alloc_write() to link a struct svc_rdma_chunk with ch_segcount == 0 onto the rc_write_pcl or rc_reply_pcl parsed-chunk lists even though RFC 8166 assigns no meaning to a chunk describing no remote buffer. The vulnerable path is reachable only on NFS servers configured with the RDMA transport over InfiniBand, RoCE, or iWARP, so an attacker must already be an RDMA peer able to send Write or Reply chunks to the server, and the independent assessment rates the realistic impact as availability-only (CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) rather than the 9.1 input score, because an earlier patch in the same series already made pcl_for_each_segment() safe for ch_segcount == 0. No public exploit code and no confirmed active exploitation are identified at time of analysis, and vendor-released patches are available in 6.12.111, 6.18.50, 7.2.4, and mainline 7.3-rc1.
Command injection in Termix 2.4.1 through 2.5.0 lets an authenticated administrator execute arbitrary operating-system commands as the Termix backend process by storing crafted domain and email values via PATCH /users/acme-ssl-settings and then triggering their interpolation into a certbot shell invocation through POST /users/acme-ssl-request. Successful exploitation exposes Termix databases, process secrets, stored credentials, and the backend's network reachability, with both HTTP-webroot and DNS-Cloudflare challenge modes affected. The issue is fixed in 2.5.1; no public exploit code has been identified at time of analysis, and the practical risk is bounded by the requirement for a high-privileged (administrator) account rather than being reachable pre-authentication.
Path traversal in Delta Electronics DIAEnergie before 1.11.00.022 allows unauthenticated remote attackers to manipulate file paths on the host, with the CVSS vector indicating high integrity and availability impact but no confidentiality impact, which is consistent with arbitrary file writing, overwriting, or deletion rather than file disclosure. Exploitation is rated CVSS 9.1 (AV:N/AC:L/PR:N/UI:N) and requires only network reachability to the DIAEnergie web application - no credentials, user interaction, or non-default configuration are prerequisites. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, so current risk is driven by intrinsic severity and exposure rather than observed exploitation in the wild. The practical threat hinges on exposure: DIAEnergie is a niche industrial energy-management platform typically deployed on segmented OT/enterprise networks, so internet-facing or broadly reachable management interfaces carry the highest risk.
Server-side request forgery in mcp-remote 0.1.32 through 0.1.38 allows an unauthenticated remote attacker who controls or compromises the remote MCP server the victim connects to to make the client fetch attacker-chosen internal or metadata URLs during OAuth discovery. The victim must initiate the connection (UI:R), and the attacker supplies a malicious WWW-Authenticate header whose resource_metadata URL is not validated by the client. No public exploit or KEV activity was identified at time of analysis and EPSS is low at 0.17% (5th percentile); our independent assessment rates the issue CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, requiring user interaction and limiting impact to confidentiality, rather than the reported UI:N and integrity impact.
Command injection in the pairing process of eufy Omni C20 and Omni X10 Pro robot vacuums lets an unauthenticated attacker on an adjacent network or within wireless proximity run arbitrary system commands on the device during pairing. The vendor rates this CRITICAL at CVSS 4.0 9.0 (AV:A/AC:H/AT:P/PR:N/UI:N, all-high impact including subsequent-system impact), and CISA ICS published advisory ICSA-26-267-02; the practical bar is higher than the score suggests because the attacker must be radio/local-adjacent and catch the device inside an active pairing window. No public exploit code was identified at time of analysis, and the flaw is not confirmed actively exploited (not in CISA KEV).