RCE
Monthly
Arbitrary code execution in Adobe Dimension 4.1.8 and earlier occurs through a CWE-426 untrusted search path flaw where a local attacker can pre-stage a malicious DLL or shared library in a directory the application searches ahead of the trusted location, which is then loaded when a victim launches Dimension. Exploitation requires local file-write access and user interaction, and no public exploit or CISA KEV listing has been identified at time of analysis. The vendor CVSS base score is 8.6 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), indicating high impact despite the local and interaction prerequisites.
Arbitrary code execution in Adobe Dimension 4.1.8 and earlier is possible when a user opens a crafted project or asset file containing improperly neutralized input that is then processed during the application's page/content generation (CWE-79). The attack surface is local only: an attacker must first place malicious content on the victim's machine and persuade them to launch Dimension, but success yields full confidentiality, integrity, and availability impact with a changed scope, meaning the resulting code execution can affect resources beyond Dimension's own boundary. The issue is scored CVSS 3.1 base 8.6 (AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Arbitrary code execution in Adobe Dimension (all versions from 0 through 4.1.8 inclusive) is possible because the application loads libraries/DLLs from an uncontrolled search path, allowing a local attacker to plant a malicious file that Dimension resolves and loads. Exploitation yields code execution in the context of the current user and requires the victim to launch the application (UI:R) after a local attacker with user-level write access has staged the malicious element in an attacker-influenceable directory; the scope-changed CVSS vector (AV:L/PR:N/UI:R/S:C) means no prior privileges are needed but local access and user interaction are. No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); Adobe PSIRT published advisory apsb26-171 for tracking.
An out-of-bounds write (CWE-787) in Adobe Dimension 4.1.8 and earlier allows arbitrary code execution at the privilege level of the user who opens a specially crafted file, such as a malicious Dimension project or imported 3D asset. Exploitation is local and depends entirely on victim interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8) - the attacker must deliver a file the user then opens, so this is not a remotely triggerable, wormable flaw; no public exploit code identified at time of analysis and the CVE is not in CISA KEV. The practical risk is genuine but operationally constrained by the mandatory user action, the local delivery requirement, and the shrinking installed base of what our assessment describes as a discontinued product.
Arbitrary code execution is possible in Adobe Substance 3D Stager 3.1.8 and earlier, where a use-after-free (CWE-416) is triggered while the application processes a crafted file. The CVSS v3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (7.8 High) shows no authentication is required, but the attacker must deliver the malicious file locally and convince the victim to open it, after which code runs only with the privileges of the current user. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, so the practical risk is driven by social-engineering delivery and by the fact that a crash (denial of service) is also achievable from the same corrupting file.
Arbitrary code execution in Adobe Substance 3D Stager 3.1.8 and earlier is possible via an out-of-bounds write (CWE-787) triggered when a victim opens a maliciously crafted file, such as a 3D asset or project file, in the application. The flaw carries a CVSS 3.1 base score of 7.8 (HIGH, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H): the attack is local-only with no network path, requires victim user interaction to open the file, and needs no prior privileges, but grants full confidentiality, integrity, and availability impact through code execution in the context of the current user. There is no public exploit identified at time of analysis (not in CISA KEV, no POC referenced), so the practical risk depends on an attacker's ability to socially engineer a designer or artist into opening a booby-trapped asset.
Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier allows arbitrary code execution in the context of the current user when a victim opens a malicious file. This local, user-interaction-required flaw (CVSS 7.8) stems from improper memory handling (CWE-787) during file/asset parsing; no public exploit code has been identified at time of analysis, and exploitation requires the attacker to deliver a crafted file to the target workstation. Successful exploitation grants code execution with the privileges of the Stager user, with high impact to confidentiality, integrity, and availability.
Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier permits arbitrary code execution in the context of the current user when a victim opens a crafted file. The flaw is local (AV:L), requires user interaction (UI:R), and needs no privileges (PR:N), so exploitation depends on social engineering rather than remote autonomous triggering. No public exploit or confirmed active exploitation (CISA KEV) is identified at time of analysis, making this a high-priority patch item but not an emergency per the independent assessment.
Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier allows arbitrary code execution in the context of the user who opens a crafted file, and Adobe's PSIRT has published advisory APSB26-170 covering the issue. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) scores 7.8 High on the strength of full confidentiality, integrity and availability impact, but the attack is not remotely triggerable: the attacker must deliver a malicious file and convince a victim to open it, and any resulting code runs only with that user's privileges, with no privilege escalation beyond the current user. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV); exploitation is neither automatable nor network-reachable, so risk concentrates on targeted file-delivery campaigns against individual Stager users.
Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier allows arbitrary code execution in the context of the current user when the victim opens a maliciously crafted 3D project or asset file. The attack path is local and requires user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8), with no network-facing trigger and no privilege escalation beyond the rights of the user who opens the file. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis; this is a genuine but not emergency-grade priority, where the practical risk is driven by social engineering that convinces a Stager user to open attacker-supplied content.
Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier allows arbitrary code execution in the context of the current user when a victim opens a crafted 3D asset or scene file. The flaw is a client-side file-parsing issue (CWE-787) with a local attack vector and required user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 7.8); no public exploit identified at time of analysis, and no confirmed active exploitation (CISA KEV). Attackers must deliver a malicious file to the target and induce the user to open it, which limits exposure to systems where untrusted Stager files are processed.
An out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier lets an attacker achieve arbitrary code execution in the context of the current user when a victim opens a specially crafted 3D project or asset file. The attack is local in nature (AV:L) and depends entirely on user interaction (UI:R) - the victim must be socially engineered into opening the malicious file - and the resulting code runs with the victim's own privileges rather than elevated rights (no privileges are required per PR:N). At time of analysis there is no public exploit identified and the issue is not listed in CISA KEV, so this is assessed as a moderate-priority, not emergency, memory-corruption flaw whose primary risk is targeted, file-based social engineering against individual Substance 3D Stager workstations.
Arbitrary code execution in Adobe Substance 3D Stager 3.1.8 and earlier is achievable when a user is persuaded to open a maliciously crafted file, allowing an unauthenticated attacker to corrupt memory out of bounds and run code in the context of the current user. The CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects a local, file-based flaw with no network attack surface, where the mandatory user interaction of opening an untrusted file is the principal limiting factor; impact is confined to the victim user's privileges rather than the whole system. No public exploit code has been identified at time of analysis, and there is no CISA KEV entry indicating confirmed active exploitation.
Opening a crafted file in Adobe Substance 3D Stager 3.1.8 or earlier can trigger a stack-based buffer overflow that leads to arbitrary code execution in the context of the current user. The attack is local in nature (AV:L) and requires the victim to open an attacker-supplied file (UI:R), while requiring no privileges on the target (PR:N), so practical exploitation depends on socially engineering a user into opening a malicious asset rather than on any remotely reachable network service. There is no public exploit identified at time of analysis and nothing in the supplied intelligence indicates confirmed active exploitation, so this is a genuine but not emergency-priority issue at a CVSS 3.1 base score of 7.8, with impact bounded by the privileges of the user who opens the file.
Local privilege escalation in Windows Assigned Access (kiosk mode) allows an authenticated, low-privileged local user to inject and execute code in a higher-integrity context, yielding full loss of confidentiality, integrity, and availability on the affected host (CVSS 3.1 base 7.8). Exploitation is constrained: the attacker must already hold authorized local logon (PR:L), the host must be one where an administrator has explicitly configured Assigned Access, and there is no network vector and no victim interaction (AV:L/UI:N). No public exploit code has been identified at time of analysis, no active exploitation is confirmed, and Microsoft has shipped fixed builds, so this is a credible but not emergency-level priority.
Unauthenticated remote code execution in the Windows Routing and Remote Access Service (RRAS) allows a network attacker to run arbitrary code in the context of the RRAS service on any host where the RRAS role is installed and its listener is reachable, yielding full compromise of confidentiality, integrity and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-122 heap overflow, with an authentication-bypass component implied by the pre-auth reachability of the flaw). Exposure is severely gated by configuration rather than by exploit difficulty: RRAS is not enabled by default on Windows, so only machines acting as VPN, dial-up or routing gateways - across Windows 10/11 and Windows Server 2012 through 2025 builds older than the patched build numbers - are realistically at risk. No public exploit code has been identified at time of analysis, CISA SSVC records Exploitation: none alongside Automatable: yes and Technical Impact: total, and Microsoft has released fixes, so this should be treated as a high-priority patch item rather than an active emergency.
Remote code execution in the Windows Routing and Remote Access Service (RRAS) affects Windows 10 and Windows 11 builds from 1607 through 26H1/26H2 as well as Windows Server 2012 through 2025, including Server Core installations, but only on hosts where the RRAS role is actually installed and enabled. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) indicates an unauthenticated, remotely reachable attacker who requires neither credentials nor user interaction can corrupt memory in the service and gain full impact to confidentiality, integrity, and availability. Because RRAS is not a default role, exposure is limited to systems deployed as VPN, dial-up, NAT, or LAN/WAN routing gateways; a vendor patch is available and no public exploit identified at time of analysis.
Remote code execution in Microsoft's Windows Routing and Remote Access Service (RRAS) lets a remote, unauthenticated attacker corrupt heap memory and execute code on affected hosts, though exploitation requires the victim to perform an action (UI:R) such as initiating or accepting a connection to attacker-controlled remote-access traffic. The Routing and Remote Access Service is an optional Windows role that is not installed by default, which sharply limits the exposed population to systems explicitly configured as VPN or dial-up servers. No public exploit code has been identified at time of analysis and the CISA SSVC assessment records exploitation as 'none'; Microsoft has released fixes, and all Windows 10/11 and Windows Server 2012 through 2025 builds below the fixed revisions listed by EUVD are affected.
Code injection in the Windows Encrypting File System (EFS) allows an authenticated attacker holding only low-level privileges (PR:L) to execute arbitrary code over the network against unpatched Windows hosts, with high impact across confidentiality, integrity, and availability (CVSS 8.8). Every supported Windows branch is in scope, including Windows 10 1607 through 22H2, Windows 11 23H2/24H2/25H2/26H1/26H2, and Windows Server 2016, 2019, 2022, and 2025 (Server Core included), and exploitation requires network reachability to the EFS component rather than any user interaction. Microsoft has published patched builds for each affected branch, and at time of analysis there is no CISA KEV listing, no public exploit code identified, and CISA's SSVC assessment records exploitation as 'none' with automatable set to 'no'.
Remote code execution in the Windows Routing and Remote Access Service (RRAS) affects Windows 10, Windows 11 and Windows Server 2012 through 2025 hosts on which the RRAS role is installed, with the CVSS 3.1 vector (8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicating a network-reachable attacker who already holds a low-privilege authenticated position, requires no user interaction, and can achieve full confidentiality, integrity and availability impact. The defect is a double free (CWE-415) memory-corruption condition in the service, which Microsoft has addressed in its monthly update with fixed builds published for each supported branch. There is no public exploit identified at time of analysis and no confirmed actively exploited (CISA KEV) status, and real-world exposure is materially narrowed because RRAS is not enabled by default on standard Windows installations.
Command-approval bypass in Roo Code through 3.54.0 lets attacker-influenced input cause the agent to execute arbitrary shell commands without the normal user confirmation prompt. The flaw lives in parseCommandLine(), which validates only the first token of a command against the auto-approval allowlist, so a payload such as $(echo touch /tmp/x) placed in command position passes the echo allowlist check while the shell substitutes and runs the embedded command. Exploitation is unauthenticated in the sense that no Roo Code credentials are required (CVSS 4.0 PR:N), but it depends on attack requirements and passive user interaction (AT:P/UI:P): the victim must run a vulnerable build with command auto-approval enabled and at least one allowlisted command, and must direct the agent at attacker-controlled content (web pages, repository files, issues or dependency docs) that carries an indirect prompt injection. Vendor CVSS 4.0 base is 7.7 (High) with full confidentiality, integrity and availability impact on the local host; no scope change to downstream systems, and no public exploit identified at time of analysis - no confirmed actively exploited (CISA KEV) status was reported. The independent assessment rates the flaw CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, emphasizing that the non-default auto-approval/allowlist configuration and the need for the developer to actively operate the agent on hostile content are the primary constraints on real-world exposure.
Privilege escalation leading to remote code execution in Xen Orchestra deployments before 6.9.0 lets any authenticated account, regardless of how few permissions it holds, obtain global administrator rights. The vm.importFromEsxi and vm.importMultipleFromEsxi methods lack access-control checks, so an authenticated remote attacker who can make xo-server import from an attacker-controlled ESXi host serving a crafted .vmx file containing a __proto__.permission property pollutes Object.prototype; every permission-less account then inherits admin rights, and that administrative foothold enables remote code execution. The flaw is rated 7.7 (CVSS 4.0, AV:N/AC:H/PR:L) and assessed as CVSS 3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H; exploitation requires a valid low-privileged Xen Orchestra account plus control of the ESXi endpoint xo-server connects to, and no public exploit code was identified at time of analysis.
An out-of-bounds write (CWE-787) in Adobe FrameMaker allows an attacker to corrupt memory and potentially execute arbitrary code with the privileges of the user who opens a maliciously crafted document. Affected builds are FrameMaker 2026 at or below 18.0.0.206 and FrameMaker 2022 at or below 17.0.9.866. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8) confirms there is no network or unauthenticated trigger: exploitation depends on social engineering a victim into opening a booby-trapped file, and any code that runs is confined to the current user's rights with no privilege escalation. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, making this a credible but not emergency-tier patching priority.
Arbitrary code execution in Adobe FrameMaker is possible via a heap-based buffer overflow (CWE-122) that is triggered when the victim opens a specially crafted file. The CVSS:3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score 7.8) indicates the flaw is local to the desktop application, requires user interaction, needs no prior authentication, and gives the attacker only the privileges of the user who opens the document. No public exploit was identified at time of analysis, and there is no CISA KEV confirmation of active exploitation; the main risk is social engineering against FrameMaker users.
Arbitrary code execution in Adobe FrameMaker is possible when a user opens a maliciously crafted file, due to a use-after-free (CWE-416) memory corruption flaw. The vulnerability requires user interaction (UI:R) and is local (AV:L), meaning an attacker must deliver the file to the victim, who then opens it; no authentication is needed (PR:N). While no public exploit code has been identified, the issue is rated CVSS 7.8 and is considered a genuine but not emergency-grade priority; Adobe has published a security bulletin (APSB26-172) with remediation guidance.
Out-of-bounds write in Adobe FrameMaker allows arbitrary code execution in the context of the current user when a victim opens an attacker-crafted document. Rated CVSS 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-787), the flaw is reached locally and requires user interaction, so exploitation depends on social engineering to deliver a malicious file that the target then opens; no authentication is required of the attacker and no non-default configuration is implicated, meaning any installation that opens the file is affected. Impact is bounded by the privileges of the user running FrameMaker (S:U), and there is no public exploit code or confirmed active exploitation identified at time of analysis.
Heap-based buffer overflow in Adobe FrameMaker (CWE-122) lets an attacker achieve arbitrary code execution in the context of the user who opens a crafted FrameMaker document. The flaw is rated CVSS 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), meaning no prior authentication or privileges are needed, but exploitation depends on the victim opening an attacker-supplied file, and code runs only with that user's rights due to unchanged scope. Impact is therefore bounded by the victim's privilege level and by successful social engineering; there is no public exploit identified at time of analysis and the issue is not confirmed as actively exploited.
An out-of-bounds write (CWE-787) in Adobe FrameMaker allows arbitrary code execution in the context of the current user when a victim opens a crafted FrameMaker document. Exploitation is file-based and requires user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base score 7.8 HIGH): the attacker must socially engineer the target into opening malicious content, and the resulting code runs with only that user's privileges rather than gaining system-level control. No confirmed active exploitation or publicly available exploit code was identified at time of analysis, but the full confidentiality, integrity, and availability impact makes prompt patching important for engineering and technical-publishing environments that routinely exchange FrameMaker files.
Heap-based buffer overflow in Adobe FrameMaker enables arbitrary code execution in the context of the current user when a victim opens a maliciously crafted file. The provided CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8 HIGH) confirms the attack is local and requires user interaction, with no privileges needed to trigger the flaw but no remote or automatable path either. No public exploit was identified at time of analysis, exploitation is bounded to systems where FrameMaker is installed and used to open untrusted documents, and code runs only with the current user's privileges - there is no automatic elevation of privilege.
Code injection in SQL Server Management Studio and Visual Studio Tools for Applications hosts allows remote, unauthenticated attackers to execute arbitrary code in the security context of the user who opens a crafted project, script, or database object. Rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), exploitation is gated by user interaction, so it depends on social-engineering a developer or DBA into opening attacker-supplied content rather than a zero-click or server-side trigger. No public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation; the risk profile makes this a credible patch priority rather than an emergency.
Remote code execution in ASP.NET Core via a code-injection flaw (CWE-94) allows an unauthenticated, network-based attacker to execute arbitrary code when a victim user interacts with crafted content (CVSS 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploitation requires an ASP.NET Core application that routes attacker-controlled input through a dynamic code-generation or evaluation path; the user interaction requirement (UI:R) is a significant limiting factor, preventing fully autonomous or wormable exploitation. No public exploit code was identified at the time of analysis, and the specific framework API or configuration exposing the injectable path is not described in the available data and should be confirmed against the Microsoft MSRC advisory.
Authenticated code injection in Microsoft SharePoint (CVSS 3.1 base 8.8) allows a remote attacker holding a valid low-privileged SharePoint account to run code in the server's context and elevate privileges, with low attack complexity and no user interaction required. The flaw is rooted in improper control of code generation (CWE-94) inside SharePoint, and the assessed vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms that the authentication prerequisite is the primary barrier - an outside attacker must first obtain or compromise a low-privileged credential, after which confidentiality, integrity, and availability are all fully impacted. No confirmed active exploitation (CISA KEV) and no public exploit code were identified at time of analysis, so this should be treated as a high-priority patch item rather than an actively exploited emergency; the specific vulnerable endpoint is not named in the description and should be confirmed against the Microsoft MSRC advisory.
Arbitrary code execution in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source is reachable by an attacker who already holds a high-privilege administrator-level account, exploiting an improperly validated input path to run code in the context of the current user with no victim interaction required. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) rates confidentiality, integrity, and availability impact as high with a changed scope, meaning the effect is not contained within the vulnerable component; the governing limitation is the PR:H precondition, which keeps the realistic attacker set to insiders, holders of compromised admin credentials, or post-authentication attack chains rather than anonymous or low-privileged users. No public exploit code was identified and there is no confirmed active exploitation (CISA KEV) at time of analysis, so this should be treated as a high-value post-authentication target rather than an opportunistically exploited one.
Unauthenticated remote code execution affects Adobe Commerce, Adobe Commerce B2B, and Magento Open Source through improper neutralization of special elements used in a template engine (CWE-1336, server-side template injection). Per the vendor CVSS vector (AV:N/AC:L/PR:N/UI:N/S:C), an attacker can reach the vulnerable template-processing surface over the network without credentials and without any victim interaction, and the scope change (S:C) indicates compromise can extend beyond the vulnerable component into the surrounding account or session context. The score is the maximum possible (10.0) and Adobe has published remediation guidance in APSB26-153; no public exploit code or confirmed active exploitation was identified at time of analysis, so the risk is driven by severity and ease of reachability rather than observed attacks.
Arbitrary code execution is achievable in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source by an attacker who already holds a high-privilege backend account, exploiting an improper input validation flaw (CWE-20) that a single crafted, network-delivered request can trigger without any user interaction. The CVSS 3.1 base score of 9.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) reflects complete compromise of confidentiality, integrity, and availability with a changed scope, but the PR:H metric means the attacker must first obtain administrative or equivalently privileged credentials - stolen admin or API credentials, or a pre-existing privileged foothold. Adobe reported the issue directly (APSB26-153); no public exploit code has been identified and there is no confirmed active exploitation (not in CISA KEV) at time of analysis, so the practical risk is concentrated in organizations whose admin panels are internet-exposed with weak credential controls.
Remote, low-complexity code execution is possible in Adobe Commerce, Adobe Commerce B2B and Magento Open Source through an incorrect authorization flaw (CWE-863) rated CVSS 9.8, allowing an attacker to act with the privileges of the current request context and escalate to arbitrary code execution without user interaction. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) describes network-reachable exploitation requiring no prior privileges, which is the strongest signal in the available data. No public exploit code and no CISA KEV entry were identified at time of analysis, and Adobe's only provided reference is advisory APSB26-153; defenders should note Adobe's wording about 'the context of the current user,' which may indicate an existing session or request context is required even though the vector claims PR:N.
Code injection in dataclasses-avroschema versions 0.38.0 through 0.70.5 lets an attacker who controls the Avro schema consumed by the library's model-generator classes inject arbitrary statements into the generated Python source, because enum symbols are used as generated enum member names after case conversion without being validated as Python identifiers. Exploitation is not on the library's default runtime serialization path: it requires an application to invoke the generator classes directly (BaseGenerator.parse_enum / EnumRepresentation.render_symbols) on an attacker-supplied schema and then import or execute the emitted module, which is why the assessed vector carries UI:R despite being network-reachable and unauthenticated (PR:N). Impact when the chain is completed is code execution and namespace modification in the importing process with high confidentiality, integrity, and availability consequences (CVSS 8.8); no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis. Version 0.70.6 fixes the issue by validating every enum symbol as a name.
Arbitrary code execution in dataclasses-avroschema versions 0.38.0 through 0.70.5, where BaseGenerator.parse_fixed writes a fixed type's 'aliases' value straight into the generated types.confixed annotation: a bare string alias (instead of a JSON list) is emitted as an unquoted Python expression and evaluated the moment the generated module is imported. Exploitation is not automatic - it requires a developer to run the library's Avro-schema-to-Python code generation over an attacker-influenced schema and then import the resulting module, which is why the vector carries UI:R despite PR:N and network-level delivery of the malicious schema. The flaw is a genuine CWE-94 code-injection issue with high confidentiality, integrity and availability impact under our assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H; no public exploit code has been identified at time of analysis and it is not in CISA KEV. Version 0.70.6 fixes it by rejecting any 'aliases' value that is not a list.
Code injection in dataclasses-avroschema 0.38.0 through 0.70.5 allows an attacker who supplies a crafted Avro schema to the library's Avro-to-Python code generator (model_generator) to embed arbitrary Python statements into the generated module via an enum field default, and those statements execute when the generated module is imported, either modifying the module namespace or preventing it from loading (CVSS 3.1 8.8, CWE-94). The CVSS vector (AV:N/AC:L/PR:N/UI:R) indicates the flaw is unauthenticated but requires user interaction: a victim must run the generator against the attacker-controlled schema and then import the resulting module, so environments that only generate code from their own trusted models or never load attacker-influenced generated code are not exposed. The maintainer confirmed and patched the issue in 0.70.6 by validating enum defaults as names; no public exploit code has been identified at time of analysis, and no active exploitation is confirmed (CISA KEV) at the time of writing.
Arbitrary code execution is possible in JFrog CLI when specific, non-default configurations are combined with an argument-injection weakness (CWE-88) that allows attacker-influenced input to be incorporated into arguments passed to an underlying command. The flaw carries a 9.0 base score with the vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, meaning the vector formally allows unauthenticated, no-interaction network exploitation, but the High attack complexity reflects the configuration preconditions that gate it rather than ease of use. Only environments running JFrog CLI are in scope - typically developer workstations and CI/CD pipelines that interact with JFrog Artifactory/Platform - and no public exploit has been identified at time of analysis.
Python code injection in dataclasses-avroschema versions 0.38.0 through 0.70.5 lets an attacker with control over Avro schema content smuggle arbitrary Python statements into the enum class body that the library emits, so simply importing the generated module executes the attacker's code. The flaw sits in EnumRepresentation.render_symbols, which wraps each schema-supplied enum symbol in double quotes without escaping it, allowing a quote character to close the literal and append attacker-chosen Python. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8, CWE-94) indicates no privileges are required but that user interaction is essential, since the victim must run the import of the generated file; no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, and version 0.70.6 fixes it by escaping enum symbol values before rendering.
Arbitrary Python code execution in dataclasses-avroschema versions 0.44.0 through 0.70.5 occurs because the Pydantic and AvroDantic model generators embed an Avro schema field's pydantic-class value directly into a generated field annotation after the literal prefix 'pydantic.', without sanitizing the expression. When a victim runs the code-generation path (ModelGenerator) on an attacker-influenced schema and then imports the generated Python module, the injected annotation is evaluated at import time and the payload executes with the privileges of that process, giving full confidentiality and integrity impact (CVSS 8.8, AV:C:N/AC:L/PR:N/UI:R). Exploitation is unauthenticated from the network perspective (CVSS PR:N) but requires the victim to generate and import the code, and no public exploit code or CISA KEV entry was identified at time of analysis; version 0.70.6 restricts the value to a bare name or a call to a bare name with literal arguments.
Arbitrary Python code execution is possible in dataclasses-avroschema versions 0.65.9 through 0.70.5 when the library's Pydantic or AvroDantic model-generation path is run over an Avro schema the attacker controls: the schema field's 'doc' value is interpolated unescaped between the quotes of a generated pydantic.Field(description="...") argument, so a crafted quote can close the string and inject a Python expression that is evaluated when the generated class is defined (CWE-94). The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (8.8), reflecting high confidentiality and integrity impact with user interaction required because a developer or build process must actively generate models from the malicious schema; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV, and urgency is further moderated because only the Pydantic/AvroDantic generators are affected and only versions 0.65.9-0.70.5 are vulnerable.
Code injection in dataclasses-avroschema 0.38.0 through 0.70.5 lets an attacker-influenced Avro schema execute arbitrary Python when the library's model generator renders a 'fixed' type's namespace into generated source. BaseGenerator.parse_fixed interpolates the namespace between quotes inside a generated types.confixed annotation without escaping, so a namespace containing a quote character terminates the string literal and turns the remainder into live Python that runs when the generated class is defined or the generated module is imported; the assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (8.8), unauthenticated over the network but requiring the victim to run code generation on the crafted schema and then import the result. The flaw is fixed in 0.70.6, which enforces that namespaces are dot-separated sequences of valid Avro names; no public exploit code was identified at time of analysis and the issue is not in CISA KEV, but the high CVSS score, confirmed GHSA-h9q3-f96w-f88j advisory, and availability of a vendor fix commit make prompt upgrading advisable for anyone generating code from externally sourced schemas.
Code injection in dataclasses-avroschema versions 0.40.0 through 0.70.5 lets an attacker who controls the `doc` value of an Avro schema record close the generated class docstring and inject arbitrary Python statements into the emitted class body, achieving code execution when the generated module is imported. The CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) rates the flaw as network-reachable, low-complexity and unauthenticated with high confidentiality and integrity impact, but exploitation is gated by user interaction: a developer or CI pipeline must both run the library's model generator against the attacker-influenced schema and import the resulting Python file. No public exploit code has been identified at time of analysis, and the vendor released a fix in 0.70.6.
Authenticated OS command injection in the odt2spip plugin for SPIP before 4.4.0 allows author-level users to execute arbitrary commands as the web-server user by uploading a document with a crafted non-.odt filename through the document import form. The flaw survives sanitization in odt2spip_deplacer_fichier_upload() and LibreOffice::createCommand(), then triggers during LibreOffice conversion; exploitation requires a working LibreOffice backend and an author account. No public exploit was identified at time of analysis.
Code injection in dataclasses-avroschema 0.62.3 through 0.70.5 allows an attacker-supplied Avro record name to break out of the quoted Meta.schema_name string literal and inject arbitrary Python statements into the generated model's class body, which then execute when that generated module is imported. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R) means no authentication is required but a victim must run the Avro-to-Python code generator on an untrusted or tainted schema and subsequently import the generated file; generating Avro schemas from trusted local dataclasses does not trigger it. Vendor-released patch: 0.70.6. No public exploit identified at time of analysis, and the issue is not confirmed actively exploited (no CISA KEV entry).
Unauthenticated remote attackers can write arbitrary files on servers running Risesoft-y9 Digital-Infrastructure 9.6.5 through 9.6.11 by abusing a path traversal flaw in the fileManager module's storeFile endpoint; a single crafted POST to /rest/storeFile with attacker-controlled fullPath and fileName parameters lets the service account create or overwrite files anywhere it has write permission, which can escalate to code execution if a writable path is later executed or parsed. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H (8.8, matching the published CVSS 4.0 score), reflecting high integrity and availability impact with no confidentiality impact, and no KEV listing, so there is no confirmed active exploitation (no public exploit identified at time of analysis), though the presence of a public technical writeup and a VulnCheck advisory makes weaponization plausible. Real-world impact is bounded by the service account's write permissions and by whether the vulnerable fileManager endpoint is reachable from the attacker's network position rather than internal-only; this is a credible high-priority issue rather than a high-CVSS-but-low-risk paper cut.
Code injection in dataclasses-avroschema versions 0.38.0 through 0.70.5 allows remote, unauthenticated attackers who supply a crafted Avro schema to inject constrained Python statements into the module produced by the schema-to-code generator; the injected code executes when that generated module is imported. Exploitation requires the victim to deliberately process an untrusted schema through the avro-to-code path and then import the resulting module (the UI:R gate), which limits exposure to pipelines that ingest third-party schemas. CVSS 3.1 base score is 8.8 (High) with vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H; no public exploit identified at time of analysis, and version 0.70.6 fixes the flaw by validating enum defaults as names.
Arbitrary code execution in dataclasses-avroschema 0.38.0 through 0.70.5 occurs when the library's Avro-to-Python model generator processes a schema containing a fixed type whose 'aliases' value is a bare string instead of a list; the value is interpolated unquoted into a generated 'types.confixed' annotation and evaluated when the generated module is imported, giving an attacker code execution in the victim's Python process. Exploitation is unauthenticated from the network perspective (CVSS:3.1/AV:N/AC:L/PR:N/UI:R) but gated on victim interaction: someone must run the schema-to-code generation path on attacker-controlled schema content and then import the resulting module. There is no public exploit code identified at time of analysis and no confirmed active exploitation (CISA KEV), so this is a high-severity but precondition-gated code-injection flaw; the vendor released 0.70.6, which rejects non-list aliases.
FearlessCMS 0.1.2b and earlier lets an authenticated administrator supply an arbitrary Git repository URL to the dashboard updater (admin/updater-handler.php → perform_update → update.sh), which clones the repository and overwrites the live plugins/, admin/, and includes/ directories without validating the repository's identity, signatures, or contents. Because router.php allows existing PHP files under plugins/ to be executed by the PHP built-in development server - the project's documented run mode - the injected update content runs as arbitrary PHP under the web server account and can persist as a backdoor, yielding full compromise of confidentiality, integrity, and availability. Exploitation is gated on high-privilege (administrator) authentication and affects only versions at or below 0.1.2b; no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and no EPSS score was provided.
Code injection in the Salty Docs documentation build pipeline (saltyorg/docs) lets an attacker-controlled fork pull request execute arbitrary code in the privileged base-repository GitHub Actions workflow that has repository secrets in scope, resulting in disclosure of CF_API_TOKEN, GH_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY and a write-capable GITHUB_TOKEN and enabling follow-on compromise of the docs.saltbox.dev deployment. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (10.0) and, per the independent assessment, exploitation is confined to repositories running this specific pre-fix workflow pair - the trigger-pr-build.yml workflow records an untrusted fork commit SHA in the pr_info artifact and build-pr.yml's workflow_run job checks that SHA out before running 'pip install -r requirements.txt'. No public exploit code identified at time of analysis and the issue is not in CISA KEV, but the code path is a genuine CI/CD supply-chain flaw rather than a CVSS-inflated paper risk, so the risk is high for unpatched users of this template. Practical exploitation still requires an attacker to control fork content (malicious setup.py or PEP 517 build hook) rather than merely tampering with artifact metadata, and submitting a fork PR requires a GitHub account even though the vector scores PR:N.
A double-free in Dragonfly's RDB stream loader (OpaqueObjLoader::CreateStream in src/server/rdb_load.cc) lets a remote, unauthenticated attacker corrupt the allocator, crash the server, and potentially execute code as the Dragonfly service account by sending a crafted serialized stream to the RESTORE command. All Dragonfly builds prior to the 1.40 fix are affected, and exposure is highest because Dragonfly ships with authentication disabled by default (no requirepass or ACLs), so network reachability to the client port is the only real precondition (assessed as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; the upstream advisory scores it 9.6 with an AV:A/S:C vector). No public exploit code was identified at time of analysis and the issue is not tied to a CISA KEV entry, but the trigger is a single crafted RESTORE payload and the upstream fix has not yet been mapped to a published release, so unpatched, internet-reachable instances should be considered urgent.
Arbitrary file overwrite in Wazuh Manager (3.9.0 through versions prior to 4.14.8) lets an attacker who already controls an enrolled cluster worker node corrupt protected master-side files - including ossec.conf and agent.conf - by abusing a trailing-slash basename path-validation bypass and the lack of extra_valid enforcement in MasterHandler.process_files_from_worker. Because the manager runs as root and pushes configuration out to its fleet, the overwritten files escalate into root-level remote code execution on the manager and on every connected agent, which is why the vulnerability carries a CVSS 4.0 base score of 9.4 (independent CVSS 3.1 assessment: AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H). The PR:H prerequisite is the key limiter: the attacker must already control a worker node that is enrolled and syncing with the master, so this is not anonymously reachable from the internet, standalone (non-clustered) managers do not expose the vulnerable path, and no public exploit code had been identified at time of analysis.
Remote code execution in Wazuh agents 4.3.0 through 4.14.7 (not including 4.14.8) allows an attacker who already holds manager-level control over a Wazuh deployment to run arbitrary SCA policy command checks as root on every enrolled agent. The root cause is that the SCA subsystem decides whether a policy is trusted by its file path rather than by its configuration source or signature, so an unsigned policy file planted in var/incoming through the agent upgrade channel is honored and its checks execute with root privileges. The vendor CVSS 4.0 base score is 8.6 (High) - network vector, low complexity, no user interaction (PR:H), with high confidentiality, integrity and availability impact on the agent - and represents a fleet-wide escalation that only applies after a manager has already been compromised. No public exploit code and no confirmed active exploitation were identified at time of analysis; the vendor released a fix in Wazuh v4.14.8.
Unsafe deserialization in NVIDIA Megatron-LM's checkpoint-loading routine allows an attacker to execute arbitrary code, escalate privileges, disclose information, and tamper with data by convincing a user to load a maliciously crafted checkpoint or model file into the framework. The flaw is rated CVSS 7.8 (High) and is reachable only when a victim actually opens an attacker-supplied checkpoint, so organizations that load checkpoints exclusively from trusted internal sources are not realistically exposed; the vulnerable path is local (AV:L) and depends on user interaction per our assessment, with no network service or authentication bypass involved. No public exploit code has been identified at time of analysis and the vulnerability is not in CISA KEV, though the availability of proof-of-concept tooling for pickle-based deserialization attacks in ML frameworks makes this class of issue practically exploitable once a crafted checkpoint is delivered.
Path traversal in the NVIDIA AIStore for Linux dSort archive extraction component allows a remote attacker to write files outside the intended extraction directory by submitting a dSort job that references an archive (e.g., tar/zip) whose member names contain crafted traversal sequences, yielding arbitrary file creation or overwrite and potentially code execution, information disclosure, data tampering, and denial of service. The vulnerability carries a CVSS 3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) per the assessed vector, indicating remote reachability and no authentication requirement, but a high attack-complexity rating that reflects the difficulty of reliably crafting the malicious archive and triggering the flaw. There is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis; the practical gating factor is network access to the AIStore dSort/API endpoint, which in typical deployments is confined to a trusted ML/training cluster or private network rather than being internet-facing. Because the dSort job-submission path is the attack surface, exposure is primarily amplified where AIStore's API is reachable from untrusted networks, and no user interaction is required.
Unauthenticated remote attackers can achieve code execution and privilege escalation against NVIDIA AIStore for Linux by injecting arbitrary Kubernetes host-namespace and container security settings into the legacy ETL Kubernetes PodSpec initialization API, rated CVSS 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) because the impact escapes the AIStore workload and extends to the underlying Kubernetes node and cluster. The vector confirms the attack is network-reachable with no privileges or user interaction required, though practical exploitation depends on the legacy ETL/transformation feature being enabled and the ETL API being exposed, and on Kubernetes RBAC and PodSecurity admission being permissive enough for AIStore to actually schedule host-namespaced or privileged pods. At time of analysis there is no confirmed active exploitation (CISA KEV) and no public exploit code identified, but the vendor-reported severity, the scope-changed impact, and CWE-250 (execution with unnecessary privileges) place this in top-priority territory for any cluster running an exposed AIStore ETL endpoint.
Deserialization of untrusted data in the NVIDIA Megatron-LM checkpoint-loading path allows code execution, privilege escalation, information disclosure, and data tampering when a user is convinced to load a maliciously crafted checkpoint file. NVIDIA PSIRT scores this CVSS 7.8 (High) and both the vendor and the independent assessment agree on full confidentiality, integrity, and availability impact; the assessments differ on prerequisites, with the vendor vector indicating low privileges and no user interaction (PR:L/UI:N) while the independent assessment models it as no privileges with required victim interaction (PR:N/UI:R). No public exploit code or CISA KEV entry was identified at time of analysis, and only environments that actually load untrusted checkpoints are exposed; code runs with the privileges of the loading user or process, not inherently as root.
Unauthenticated path traversal in the target-side object rename handler of NVIDIA AIStore on Linux allows a remote attacker who can reach a target (storage) node directly to write files outside the intended storage directory by supplying a crafted rename destination, resulting in arbitrary file creation or overwrite. NVIDIA rates the issue CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-22), with downstream consequences that could include code execution, privilege escalation, information disclosure, data tampering, and denial of service depending on what the overwritten path controls. Exploitation is constrained rather than trivial: the attacker needs network reachability to a target node - not merely the front-end proxy - and must build a traversal payload the rename handler accepts, so exposure is greatest in flat cluster networks or environments where target ports are directly reachable; no public exploit code and no CISA KEV entry were identified at time of analysis.
Guest-to-host privilege escalation in Xen's tapdisk (blktap) userspace xen-blkback backend lets a malicious or buggy guest VM crash or potentially execute code as host root: all versions of tapdisk are affected because the device-connect path performs no boundary check on the multi-page ring size requested by the frontend. Exploitation requires only that the host runs the XAPI toolstack with tapdisk as the block backend and that the attacker already controls a guest VM attached to it (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), with no user interaction on the host side; the vulnerability is reachable under default configurations, and the Xen Security Advisory states there are no mitigations. No public exploit code or active exploitation has been identified at time of analysis, and the fix is an upstream patch (xsa521.patch) for blktap master rather than a named released version.
Stack-based buffer overflow in NVIDIA DALI lets a locally authenticated, low-privileged user who can get a crafted input file processed through a DALI pipeline corrupt memory and potentially achieve code execution, information disclosure, data tampering, or denial of service. Per the assessed CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, base 7.3 High), exploitation is not remotely reachable: it requires an existing local foothold with at least low privileges plus some form of user interaction, which in practice means a victim or automated process must load attacker-controlled data. There is no public exploit identified at time of analysis and the flaw has not been added to CISA KEV; the practical risk concentrates on multi-tenant or pipeline-automation GPU hosts where untrusted files are routinely fed into DALI. Exact affected versions are unconfirmed because the CPE is a wildcard, so defenders must verify their deployed DALI build against the NVIDIA advisory.
Eval injection in NVIDIA Isaac Lab allows a local attacker who can supply crafted input - such as a malicious experiment configuration, task/environment definition, or command-line parameter - to achieve arbitrary code execution, information disclosure, data tampering, and denial of service once a user opens, loads, or runs the content. The flaw is rated CVSS 7.8 (HIGH) with vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H: no privileges are required (PR:N) but the victim must interact with the malicious input (UI:R), the attack path is local (AV:L), and impact is scoped to the invoking user (S:U), so no privilege escalation is implied. The CPE entry is a wildcard with no version boundary and no fixed version is published in the available data, so all Isaac Lab releases should be treated as potentially affected; no public exploit code and no confirmed active exploitation have been identified at time of analysis.
Siemens Industrial Edge App Publisher versions below V1.27.9 fails to sanitize or escape data received from the backend before rendering it in its integrated Node.js front end, enabling injected JavaScript to execute with the client's privileges and escalate to remote code execution on the victim's machine. Exploitation requires an attacker to control or influence backend-delivered data and a victim to actively view that data in the vulnerable client, making this a targeted threat rather than opportunistic mass exploitation. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the vendor has released a patch in V1.27.9.
Local capability escalation in the macOS build of the DigiD app (Logius) lets an attacker who already holds user-level code execution on the same Mac inject an arbitrary dynamic library into the DigiD process and run code under the app's identity, reaching DigiD data and cryptographic operations the process would not normally expose - CVSS 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). The root cause is that the app binary is not signed with the Hardened Runtime flag, so the loader still honours DYLD_INSERT_LIBRARIES; this is a post-compromise escalation primitive, not a remote or initial-access bug, and it grants no privilege beyond the app's own context (S:U) and no availability impact. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV); a Hardened-Runtime-signed build blocks the injection path and is available per the vendor advisory pointing at the Mac App Store listing.
Unauthorized SCIM API access in Perforce Helix Authentication Service (HAS) versions 2022.1 through 2025.2 arises from a shipped default bearer token that the installer and configuration script fail to rotate, enabling remote, unauthenticated attackers who know the token to perform user and group provisioning operations. Chaining this with CVE-2026-61834 in the scim-patch dependency allows server-side prototype pollution and, under Node.js 24/Express with specific gadget chains, remote code execution. The underlying defect is removed in HAS 2026.1; no public exploit code has been identified at time of analysis.
Opening a crafted S-102 bathymetric surface HDF5 file in OpenS100 through commit daaa35b can trigger a 32-bit integer overflow that under-allocates a heap buffer and lets attacker-controlled data be written out of bounds, resulting in an application crash or potential arbitrary code execution. The flaw lives in S102_VG_BathymetryCoverage::Read(), where the product of the numPointsLatitudinal and numPointsLongitudinal grid dimensions wraps around before the buffer size is computed. Exploitation is unauthenticated (PR:N) but constrained: no network-reachable path exists (local vector) and the victim must actively open a malicious file, and while publicly available exploit code exists, EPSS is low at roughly 0.20% (10th percentile), the issue is not in CISA KEV, and the overall signal is a real but low-priority issue rather than an urgent threat.
Remote code execution in GitLab CE/EE (all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2) allows an unauthenticated attacker to execute arbitrary code on the GitLab server by supplying a specially crafted regular expression in a CI/CD configuration that passes insufficient regex validation; the defect is tracked as CWE-190 (integer overflow) and the vendor scores it 10.0 with scope change (S:C). Publicly available exploit code exists, referenced through HackerOne reports cited in the CVE record, but there is no CISA KEV entry and no confirmed active exploitation at time of analysis. Our independent assessment retains the same impact (C:H/I:H/A:H) but raises attack complexity to AC:H, because the vendor states the regex-validation path is reached by an unauthenticated user only 'under certain conditions' that are not detailed publicly and should be confirmed with GitLab; patched instances (19.4.2, 19.3.5, 19.2.8 or later) are not affected.
Remote code execution in SAP S/4HANA's Manage Substitution/Validation Rules allows an authenticated attacker who already holds rule-maintenance business authorizations to submit crafted rule definitions that the rule-processing logic interprets as executable ABAP, resulting in full compromise of the affected system with high impact to confidentiality, integrity and availability (CVSS 9.9, Scope:Changed). Reaching the vulnerable code path requires an account provisioned with substitution/validation rule creation or maintenance privileges, so the practical barrier is authorization scope rather than authentication alone. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but the vendor advisory (SAP Security Note 3805589) should be treated as urgent given the code-injection primitive and the privileged business role required.
Unauthenticated remote code execution affects the SKYWORTH SK-WR6640X (AX1800M) Wi-Fi 6 dual-band fiber router running firmware V1.0.3, allowing a network-reachable attacker to run arbitrary code with full confidentiality, integrity and availability impact (CVSS 9.8, AV:N/AC:L/PR:N/UI:N). Because the name of the vulnerable endpoint, protocol or feature is not disclosed, the practical limiting factor is reachability rather than credentials: on typical home deployments the affected service is LAN-facing, and only internet-facing management, a port-forward, or an exposed management interface would place it within reach of a remote attacker. Assessment signals are mixed - a maximum-severity score and a public disclosure write-up from the PRISMI-Team coexist with a low EPSS of 0.24% (14th percentile), no confirmed actively exploited (CISA KEV) status, and no public exploit code identified at time of analysis.
Arbitrary code execution in mp4v2 2.0.0 can be triggered when a victim or application opens a specially crafted MP4 file containing an undersized RTP ('rtp ') atom; MP4RtpAtom::ReadHntiType() performs an unchecked offset subtraction that underflows to a near-2^64 allocation size, leading to memory corruption and potential code execution. The assessed vector is local with user interaction required (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), so the malicious file must be parsed on the target system rather than delivered to a listening network service. No public exploit identified at time of analysis; EPSS is 0.18% (7th percentile), and the upstream fix is available as a PR/commit but no released patched version is independently confirmed.
Directory traversal in the iKuai8 management interface shipped on the IK-Q3000 Enterprise-grade Wi-Fi 6 router lets an attacker escape the intended file path and execute arbitrary code on the device; affected builds are Enterprise Edition <= iKuai8_3.7.23_Enterprise Build 202606021825 and Free Edition <= iKuai 8_4.0.304-beta. The CVE record scores this 9.8 with a PR:N vector (unauthenticated), but the public disclosure is explicitly titled 'authorized' path traversal and our independent assessment rates it PR:L, so a valid authenticated management session is most likely a prerequisite and is the key factor limiting real-world exploitation. There is no CISA KEV entry and no public exploit identified at time of analysis, and EPSS is low at 0.45% (38th percentile); exposure is further gated by network reachability to the router's administrative web service, so units with management bound to an internal/LAN interface are materially less exposed.
Remote code execution and sensitive-information disclosure in IBM i 7.3, 7.4, 7.5, and 7.6 stem from improper data sanitization by the HTTP Server Administration web application (CWE-94 code injection). An authenticated attacker with only low privileges who can reach that administration interface over the network can inject and execute arbitrary code or read sensitive data, with the scope change (S:C) driving Confidentiality, Integrity, and Availability impacts all High for a CVSS 3.1 base score of 9.9. Exploitation is not unauthenticated and is not possible against systems that do not run the HTTP Server Administration interface, or that expose it only to a trusted management network; no public exploit has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation, though IBM has published a vendor patch.
Authenticated remote code execution in IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 arises from improper validation of file paths inside archives the platform extracts, allowing an attacker with a valid account to write files to arbitrary locations and execute code under the privileges of the TRIRIGA service (CVSS 3.1: 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack is network-reachable with no user interaction and low complexity, but the PR:L vector gates it behind an existing authenticated session, confining realistic exploitation to insiders or attackers who have already obtained platform credentials. No public exploit identified at time of analysis, and IBM has published a vendor patch advisory covering the affected 5.0.0-5.0.8 range.
Authenticated remote code execution in IBM Planning Analytics 2.0 and 2.1 stems from a stack-based buffer overflow (CWE-121) that allows a remote attacker holding valid low-privilege credentials to corrupt stack memory and execute arbitrary code. IBM assigns a CVSS 3.1 base score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), and the independent assessment raises the availability impact to High, indicating a successful exploit may also crash or destabilize the affected service. No public exploit code has been identified at time of analysis and the vulnerability is not listed in CISA KEV; vendor patches are available via IBM support node 7291604.
Authenticated path traversal in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote attacker holding a valid platform account to bypass intended directory restrictions and execute arbitrary code. Exploitation requires only low-privileged credentials (CVSS PR:L), needs no user interaction, and is network-reachable with low complexity, which is why the vector scores 9.9 Critical with a scope change (S:C) reflecting impact that can extend beyond the vulnerable component. Despite the high score, the practical risk picture is more moderate: EPSS is only 0.49% (40th percentile), CISA SSVC rates exploitation as none with automatable set to no, there is no public exploit code identified at time of analysis and no KEV listing, and the vendor has published a patch, so remediation is available rather than dependent on compensating controls alone.
Authenticated remote code execution in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows an attacker who already holds valid low-privilege credentials (CVSS PR:L, AV:N, UI:N) to run arbitrary operating system commands on the underlying host, resulting in high confidentiality, integrity, and availability impact (CVSS 8.8). The root cause is improper neutralization of special elements used in an OS command (CWE-94), meaning user-supplied input reaches a shell command without adequate sanitization. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV), but a vendor patch is available per IBM's advisory, so unpatched 5.4.0.0 deployments exposed to multi-tenant users or broadly provisioned accounts should be prioritized for upgrade.
Remote code execution in IBM Maximo AI Service 9.1.0 and 9.2.0 lets an unauthenticated remote attacker execute arbitrary code on an affected deployment by abusing improper control of code generation (CWE-94). With 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), the flaw requires no authentication, no user interaction, and no special conditions beyond network reachability of the vulnerable instance. No public exploit code has been identified at time of analysis, and there is no KEV listing; IBM has published an advisory with a vendor fix, so the practical priority is identifying and patching internet- or network-exposed Maximo AI Service 9.1.0/9.2.0 instances.
Local code execution in IBM Power Systems firmware (FW1060.00 through FW1060.81) lets an attacker who already holds authenticated service-level access to the Flexible Service Processor (FSP) send a crafted service processor mailbox message that overflows host firmware runtime attribute storage, compromising the managed system's memory and hardware interfaces. The CVSS 3.1 vector AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H (base 8.2) is internally consistent with that description: the flaw is local, requires high-privilege service-plane credentials, needs no user interaction, and its scope change reflects a jump across the trust boundary from the service processor into the host firmware runtime with high confidentiality, integrity and availability impact. No public exploit code has been identified at time of analysis and there is no CISA KEV entry; IBM published the vendor advisory at https://www.ibm.com/support/pages/node/7290126.
Arbitrary code execution on the host system is possible in IBM Power Systems firmware versions FW1120.00 through FW1120.01, FW1110.00 through FW1110.31, and FW1060.00 through FW1060.81, due to a stack-based buffer overflow (CWE-121) in the host firmware boot process image validation path. An attacker with high-privileged service access to the service processor (PR:H, AV:L) can supply a maliciously crafted code update image to execute arbitrary code on the host system, resulting in full confidentiality, integrity, and availability impact (CVSS 3.1 base score 8.2, High). No public exploit has been identified at time of analysis, and exploitation requires local/service-level access and high privileges, substantially limiting real-world risk.
Arbitrary code execution in the host firmware runtime of IBM Power Systems is possible via the service processor mailbox interface, affecting firmware levels FW1060.00 through FW1060.81. An attacker with authenticated service-level access to the Flexible Service Processor (FSP) can send a crafted mailbox message that overflows host firmware runtime attribute storage (CWE-121), gaining full access to the managed system's memory and hardware interfaces. This is a high-severity local/management-plane issue (CVSS 8.2) requiring high privileges; no public exploit has been identified at time of analysis, and while it is not a mass-exploitation priority, isolation of the FSP network and limiting service accounts are recommended.
Authenticated users of Nginx UI (0xJacky/Nginx-UI) prior to 2.4.1 can bypass the built-in nginx directive validation and write arbitrary nginx configuration through the MCP tool nginx_config_add, which reloads nginx with the injected directives. Where nginx is built with the njs or perl module (as in the official Docker image), an attacker - or an MCP-enabled AI agent steered by prompt injection - can achieve code execution on the nginx host with the privileges of the nginx worker process. The CVSS score of 8.8 reflects a network-reachable, low-complexity path requiring only authenticated MCP access (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), making this a credible, actionable priority rather than a paper-high CVSS; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing).
Code injection in the IBM Maximo Application Suite Location Service for Esri component (versions 9.0, 9.1 and 9.2) allows an attacker who already holds high-privilege control over the Kubernetes operator's configuration input - specifically the container image reference consumed from an operator template - to inject a code path that the operator then acts on, resulting in a scope-changing compromise of workloads beyond the operator's own authority (CVSS 3.1 8.7, AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N, CWE-94). The injected image reference can cause attacker-influenced containers to be deployed under the operator's service account, which is why the impact is rated high for confidentiality and integrity even though the attack is not reachable by an unauthenticated outsider against a default deployment. Exploitation is gated by PR:H - the adversary must be able to modify the Location Service for Esri operator's template or custom resource values - no user interaction is required, and there is no public exploit identified at time of analysis.
Arbitrary local program execution is possible in EdgeEver Desktop 1.92.0 through 1.112.0 because the desktop:acp-probe IPC handler performs no sender validation and spawns whatever executable path is supplied in the caller's input.path, running it with the victim user's privileges. This is not a standalone network RCE: an attacker must first land stored cross-site scripting in a renderer through the template-preview or drag-preview feature, and the victim must then preview that attacker-controlled content so the renderer script can invoke probeAcpAdapter (CVSS v4.0 7.3; independent assessment CVSS v3.1 AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H). No public exploit code and no CISA KEV listing were identified at time of analysis; an upstream fix commit has been referenced, but no patched release version has been independently confirmed.
Configuration-validation bypass in Nginx UI (versions 2.0.0-rc.6 through 2.4.0) lets an authenticated low-privilege user write arbitrary nginx configuration directives through the MCP tool nginx_config_add, which persists the file and triggers an nginx reload without ever calling config.ValidateConfigFile - the guard the REST endpoint POST /api/configs does invoke. Because blocked directives such as perl, js_import, load_module and user root can therefore be injected, an attacker on a host with the nginx Perl, njs or Lua module loaded can escalate this into post-authentication remote code execution; on hosts without a scripting module the effect is arbitrary config tampering and reload. The issue is fixed in Nginx UI 2.4.1, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Remote code execution in NetEase Cloud Music for Windows 3.1.38 and 3.1.39.205426 allows an attacker with an active adversary-in-the-middle position to forge the /pc/upgrade/get upgrade-check response using a publicly known AES key over an unvalidated TLS connection, inject renderer content, and invoke the os.navigateExternal IPC bridge with a file:// URL to execute arbitrary local binaries under the logged-in user. The vendor CVSS 4.0 score is 9.2, and the independent assessment retains high confidentiality, integrity, and availability impact with no privileges or user interaction required, though AC:H reflects the network-position prerequisite; no public exploit identified at time of analysis and no CISA KEV active exploitation is indicated.
Authenticated privilege escalation in Progress MarkLogic Server lets an attacker who already holds query-execution access invoke an XQuery evaluation function without the additional evaluation privilege that function requires, so the query is evaluated with elevated permissions and can lead to server-side code execution in the server's security context. Affected deployments are 12.x releases before 12.1.0 and 11.x releases before 11.3.7; the vulnerability is rated CVSS 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), with the scope change and full confidentiality, integrity, and availability impact reflecting what is possible once the missing privilege check is bypassed. Exploitation requires a pre-existing account with query-execution access rather than anonymous reachability, and no public exploit code has been identified at time of analysis; there is no confirmed active exploitation (CISA KEV) reported for this issue.
Remote code execution in Project MONAI 0.4.0 through 1.6.0 requires an on-path attacker to tamper with SENet pretrained weights fetched over plaintext HTTP, causing construction of SEResNet50 or another SENet model with pretrained=True to unpickle a crafted .pth file because load_state_dict_from_url is used without weights_only=True. The issue is unauthenticated but requires user interaction and a man-in-the-middle position; no public exploit identified at time of analysis. The CVE record rates it CVSS 7.7, though the assessed precondition set makes real-world urgency conditional rather than broadly exploitable.
Remote code execution in Adminer before 6.1.1 allows authenticated users with SQLite access to bypass ATTACH and VACUUM INTO restrictions by prefixing SQL statements with a UTF-8 byte-order mark. An attacker can then attach a database file at a PHP-served path and create a table named with PHP code, which executes as the web server user. No public exploit identified at time of analysis; exploitation requires valid credentials, SQLite usage, and a web-accessible writable PHP-executing path.
Authenticated code injection in Craft CMS 4.x and 5.x allows a control panel user holding the performUpdates permission (or access to the Updates utility) to execute arbitrary code on the server by submitting a crafted 'updates' request to AppController::actionCacheUpdates. The endpoint forwards the raw request parameter into UpdatesModel without applying Component::cleanseConfig(), so an attacker can inject Yii behavior and event-handler configuration keys such as 'as' or 'on' - for example an AttributeTypecastBehavior gadget - and achieve remote code execution. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (High, 8.7 in the vendor's CVSS 4.0 scoring), and no public exploit code was identified at time of analysis; the practical barrier is the privileged-account requirement, which limits realistic exposure to malicious insiders, over-provisioned admin accounts, or environments where a control panel credential has already been compromised.
Arbitrary code execution in Adobe Dimension 4.1.8 and earlier occurs through a CWE-426 untrusted search path flaw where a local attacker can pre-stage a malicious DLL or shared library in a directory the application searches ahead of the trusted location, which is then loaded when a victim launches Dimension. Exploitation requires local file-write access and user interaction, and no public exploit or CISA KEV listing has been identified at time of analysis. The vendor CVSS base score is 8.6 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), indicating high impact despite the local and interaction prerequisites.
Arbitrary code execution in Adobe Dimension 4.1.8 and earlier is possible when a user opens a crafted project or asset file containing improperly neutralized input that is then processed during the application's page/content generation (CWE-79). The attack surface is local only: an attacker must first place malicious content on the victim's machine and persuade them to launch Dimension, but success yields full confidentiality, integrity, and availability impact with a changed scope, meaning the resulting code execution can affect resources beyond Dimension's own boundary. The issue is scored CVSS 3.1 base 8.6 (AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Arbitrary code execution in Adobe Dimension (all versions from 0 through 4.1.8 inclusive) is possible because the application loads libraries/DLLs from an uncontrolled search path, allowing a local attacker to plant a malicious file that Dimension resolves and loads. Exploitation yields code execution in the context of the current user and requires the victim to launch the application (UI:R) after a local attacker with user-level write access has staged the malicious element in an attacker-influenceable directory; the scope-changed CVSS vector (AV:L/PR:N/UI:R/S:C) means no prior privileges are needed but local access and user interaction are. No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); Adobe PSIRT published advisory apsb26-171 for tracking.
An out-of-bounds write (CWE-787) in Adobe Dimension 4.1.8 and earlier allows arbitrary code execution at the privilege level of the user who opens a specially crafted file, such as a malicious Dimension project or imported 3D asset. Exploitation is local and depends entirely on victim interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8) - the attacker must deliver a file the user then opens, so this is not a remotely triggerable, wormable flaw; no public exploit code identified at time of analysis and the CVE is not in CISA KEV. The practical risk is genuine but operationally constrained by the mandatory user action, the local delivery requirement, and the shrinking installed base of what our assessment describes as a discontinued product.
Arbitrary code execution is possible in Adobe Substance 3D Stager 3.1.8 and earlier, where a use-after-free (CWE-416) is triggered while the application processes a crafted file. The CVSS v3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (7.8 High) shows no authentication is required, but the attacker must deliver the malicious file locally and convince the victim to open it, after which code runs only with the privileges of the current user. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, so the practical risk is driven by social-engineering delivery and by the fact that a crash (denial of service) is also achievable from the same corrupting file.
Arbitrary code execution in Adobe Substance 3D Stager 3.1.8 and earlier is possible via an out-of-bounds write (CWE-787) triggered when a victim opens a maliciously crafted file, such as a 3D asset or project file, in the application. The flaw carries a CVSS 3.1 base score of 7.8 (HIGH, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H): the attack is local-only with no network path, requires victim user interaction to open the file, and needs no prior privileges, but grants full confidentiality, integrity, and availability impact through code execution in the context of the current user. There is no public exploit identified at time of analysis (not in CISA KEV, no POC referenced), so the practical risk depends on an attacker's ability to socially engineer a designer or artist into opening a booby-trapped asset.
Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier allows arbitrary code execution in the context of the current user when a victim opens a malicious file. This local, user-interaction-required flaw (CVSS 7.8) stems from improper memory handling (CWE-787) during file/asset parsing; no public exploit code has been identified at time of analysis, and exploitation requires the attacker to deliver a crafted file to the target workstation. Successful exploitation grants code execution with the privileges of the Stager user, with high impact to confidentiality, integrity, and availability.
Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier permits arbitrary code execution in the context of the current user when a victim opens a crafted file. The flaw is local (AV:L), requires user interaction (UI:R), and needs no privileges (PR:N), so exploitation depends on social engineering rather than remote autonomous triggering. No public exploit or confirmed active exploitation (CISA KEV) is identified at time of analysis, making this a high-priority patch item but not an emergency per the independent assessment.
Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier allows arbitrary code execution in the context of the user who opens a crafted file, and Adobe's PSIRT has published advisory APSB26-170 covering the issue. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) scores 7.8 High on the strength of full confidentiality, integrity and availability impact, but the attack is not remotely triggerable: the attacker must deliver a malicious file and convince a victim to open it, and any resulting code runs only with that user's privileges, with no privilege escalation beyond the current user. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV); exploitation is neither automatable nor network-reachable, so risk concentrates on targeted file-delivery campaigns against individual Stager users.
Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier allows arbitrary code execution in the context of the current user when the victim opens a maliciously crafted 3D project or asset file. The attack path is local and requires user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8), with no network-facing trigger and no privilege escalation beyond the rights of the user who opens the file. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis; this is a genuine but not emergency-grade priority, where the practical risk is driven by social engineering that convinces a Stager user to open attacker-supplied content.
Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier allows arbitrary code execution in the context of the current user when a victim opens a crafted 3D asset or scene file. The flaw is a client-side file-parsing issue (CWE-787) with a local attack vector and required user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 7.8); no public exploit identified at time of analysis, and no confirmed active exploitation (CISA KEV). Attackers must deliver a malicious file to the target and induce the user to open it, which limits exposure to systems where untrusted Stager files are processed.
An out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier lets an attacker achieve arbitrary code execution in the context of the current user when a victim opens a specially crafted 3D project or asset file. The attack is local in nature (AV:L) and depends entirely on user interaction (UI:R) - the victim must be socially engineered into opening the malicious file - and the resulting code runs with the victim's own privileges rather than elevated rights (no privileges are required per PR:N). At time of analysis there is no public exploit identified and the issue is not listed in CISA KEV, so this is assessed as a moderate-priority, not emergency, memory-corruption flaw whose primary risk is targeted, file-based social engineering against individual Substance 3D Stager workstations.
Arbitrary code execution in Adobe Substance 3D Stager 3.1.8 and earlier is achievable when a user is persuaded to open a maliciously crafted file, allowing an unauthenticated attacker to corrupt memory out of bounds and run code in the context of the current user. The CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects a local, file-based flaw with no network attack surface, where the mandatory user interaction of opening an untrusted file is the principal limiting factor; impact is confined to the victim user's privileges rather than the whole system. No public exploit code has been identified at time of analysis, and there is no CISA KEV entry indicating confirmed active exploitation.
Opening a crafted file in Adobe Substance 3D Stager 3.1.8 or earlier can trigger a stack-based buffer overflow that leads to arbitrary code execution in the context of the current user. The attack is local in nature (AV:L) and requires the victim to open an attacker-supplied file (UI:R), while requiring no privileges on the target (PR:N), so practical exploitation depends on socially engineering a user into opening a malicious asset rather than on any remotely reachable network service. There is no public exploit identified at time of analysis and nothing in the supplied intelligence indicates confirmed active exploitation, so this is a genuine but not emergency-priority issue at a CVSS 3.1 base score of 7.8, with impact bounded by the privileges of the user who opens the file.
Local privilege escalation in Windows Assigned Access (kiosk mode) allows an authenticated, low-privileged local user to inject and execute code in a higher-integrity context, yielding full loss of confidentiality, integrity, and availability on the affected host (CVSS 3.1 base 7.8). Exploitation is constrained: the attacker must already hold authorized local logon (PR:L), the host must be one where an administrator has explicitly configured Assigned Access, and there is no network vector and no victim interaction (AV:L/UI:N). No public exploit code has been identified at time of analysis, no active exploitation is confirmed, and Microsoft has shipped fixed builds, so this is a credible but not emergency-level priority.
Unauthenticated remote code execution in the Windows Routing and Remote Access Service (RRAS) allows a network attacker to run arbitrary code in the context of the RRAS service on any host where the RRAS role is installed and its listener is reachable, yielding full compromise of confidentiality, integrity and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-122 heap overflow, with an authentication-bypass component implied by the pre-auth reachability of the flaw). Exposure is severely gated by configuration rather than by exploit difficulty: RRAS is not enabled by default on Windows, so only machines acting as VPN, dial-up or routing gateways - across Windows 10/11 and Windows Server 2012 through 2025 builds older than the patched build numbers - are realistically at risk. No public exploit code has been identified at time of analysis, CISA SSVC records Exploitation: none alongside Automatable: yes and Technical Impact: total, and Microsoft has released fixes, so this should be treated as a high-priority patch item rather than an active emergency.
Remote code execution in the Windows Routing and Remote Access Service (RRAS) affects Windows 10 and Windows 11 builds from 1607 through 26H1/26H2 as well as Windows Server 2012 through 2025, including Server Core installations, but only on hosts where the RRAS role is actually installed and enabled. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) indicates an unauthenticated, remotely reachable attacker who requires neither credentials nor user interaction can corrupt memory in the service and gain full impact to confidentiality, integrity, and availability. Because RRAS is not a default role, exposure is limited to systems deployed as VPN, dial-up, NAT, or LAN/WAN routing gateways; a vendor patch is available and no public exploit identified at time of analysis.
Remote code execution in Microsoft's Windows Routing and Remote Access Service (RRAS) lets a remote, unauthenticated attacker corrupt heap memory and execute code on affected hosts, though exploitation requires the victim to perform an action (UI:R) such as initiating or accepting a connection to attacker-controlled remote-access traffic. The Routing and Remote Access Service is an optional Windows role that is not installed by default, which sharply limits the exposed population to systems explicitly configured as VPN or dial-up servers. No public exploit code has been identified at time of analysis and the CISA SSVC assessment records exploitation as 'none'; Microsoft has released fixes, and all Windows 10/11 and Windows Server 2012 through 2025 builds below the fixed revisions listed by EUVD are affected.
Code injection in the Windows Encrypting File System (EFS) allows an authenticated attacker holding only low-level privileges (PR:L) to execute arbitrary code over the network against unpatched Windows hosts, with high impact across confidentiality, integrity, and availability (CVSS 8.8). Every supported Windows branch is in scope, including Windows 10 1607 through 22H2, Windows 11 23H2/24H2/25H2/26H1/26H2, and Windows Server 2016, 2019, 2022, and 2025 (Server Core included), and exploitation requires network reachability to the EFS component rather than any user interaction. Microsoft has published patched builds for each affected branch, and at time of analysis there is no CISA KEV listing, no public exploit code identified, and CISA's SSVC assessment records exploitation as 'none' with automatable set to 'no'.
Remote code execution in the Windows Routing and Remote Access Service (RRAS) affects Windows 10, Windows 11 and Windows Server 2012 through 2025 hosts on which the RRAS role is installed, with the CVSS 3.1 vector (8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicating a network-reachable attacker who already holds a low-privilege authenticated position, requires no user interaction, and can achieve full confidentiality, integrity and availability impact. The defect is a double free (CWE-415) memory-corruption condition in the service, which Microsoft has addressed in its monthly update with fixed builds published for each supported branch. There is no public exploit identified at time of analysis and no confirmed actively exploited (CISA KEV) status, and real-world exposure is materially narrowed because RRAS is not enabled by default on standard Windows installations.
Command-approval bypass in Roo Code through 3.54.0 lets attacker-influenced input cause the agent to execute arbitrary shell commands without the normal user confirmation prompt. The flaw lives in parseCommandLine(), which validates only the first token of a command against the auto-approval allowlist, so a payload such as $(echo touch /tmp/x) placed in command position passes the echo allowlist check while the shell substitutes and runs the embedded command. Exploitation is unauthenticated in the sense that no Roo Code credentials are required (CVSS 4.0 PR:N), but it depends on attack requirements and passive user interaction (AT:P/UI:P): the victim must run a vulnerable build with command auto-approval enabled and at least one allowlisted command, and must direct the agent at attacker-controlled content (web pages, repository files, issues or dependency docs) that carries an indirect prompt injection. Vendor CVSS 4.0 base is 7.7 (High) with full confidentiality, integrity and availability impact on the local host; no scope change to downstream systems, and no public exploit identified at time of analysis - no confirmed actively exploited (CISA KEV) status was reported. The independent assessment rates the flaw CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, emphasizing that the non-default auto-approval/allowlist configuration and the need for the developer to actively operate the agent on hostile content are the primary constraints on real-world exposure.
Privilege escalation leading to remote code execution in Xen Orchestra deployments before 6.9.0 lets any authenticated account, regardless of how few permissions it holds, obtain global administrator rights. The vm.importFromEsxi and vm.importMultipleFromEsxi methods lack access-control checks, so an authenticated remote attacker who can make xo-server import from an attacker-controlled ESXi host serving a crafted .vmx file containing a __proto__.permission property pollutes Object.prototype; every permission-less account then inherits admin rights, and that administrative foothold enables remote code execution. The flaw is rated 7.7 (CVSS 4.0, AV:N/AC:H/PR:L) and assessed as CVSS 3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H; exploitation requires a valid low-privileged Xen Orchestra account plus control of the ESXi endpoint xo-server connects to, and no public exploit code was identified at time of analysis.
An out-of-bounds write (CWE-787) in Adobe FrameMaker allows an attacker to corrupt memory and potentially execute arbitrary code with the privileges of the user who opens a maliciously crafted document. Affected builds are FrameMaker 2026 at or below 18.0.0.206 and FrameMaker 2022 at or below 17.0.9.866. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8) confirms there is no network or unauthenticated trigger: exploitation depends on social engineering a victim into opening a booby-trapped file, and any code that runs is confined to the current user's rights with no privilege escalation. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, making this a credible but not emergency-tier patching priority.
Arbitrary code execution in Adobe FrameMaker is possible via a heap-based buffer overflow (CWE-122) that is triggered when the victim opens a specially crafted file. The CVSS:3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score 7.8) indicates the flaw is local to the desktop application, requires user interaction, needs no prior authentication, and gives the attacker only the privileges of the user who opens the document. No public exploit was identified at time of analysis, and there is no CISA KEV confirmation of active exploitation; the main risk is social engineering against FrameMaker users.
Arbitrary code execution in Adobe FrameMaker is possible when a user opens a maliciously crafted file, due to a use-after-free (CWE-416) memory corruption flaw. The vulnerability requires user interaction (UI:R) and is local (AV:L), meaning an attacker must deliver the file to the victim, who then opens it; no authentication is needed (PR:N). While no public exploit code has been identified, the issue is rated CVSS 7.8 and is considered a genuine but not emergency-grade priority; Adobe has published a security bulletin (APSB26-172) with remediation guidance.
Out-of-bounds write in Adobe FrameMaker allows arbitrary code execution in the context of the current user when a victim opens an attacker-crafted document. Rated CVSS 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-787), the flaw is reached locally and requires user interaction, so exploitation depends on social engineering to deliver a malicious file that the target then opens; no authentication is required of the attacker and no non-default configuration is implicated, meaning any installation that opens the file is affected. Impact is bounded by the privileges of the user running FrameMaker (S:U), and there is no public exploit code or confirmed active exploitation identified at time of analysis.
Heap-based buffer overflow in Adobe FrameMaker (CWE-122) lets an attacker achieve arbitrary code execution in the context of the user who opens a crafted FrameMaker document. The flaw is rated CVSS 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), meaning no prior authentication or privileges are needed, but exploitation depends on the victim opening an attacker-supplied file, and code runs only with that user's rights due to unchanged scope. Impact is therefore bounded by the victim's privilege level and by successful social engineering; there is no public exploit identified at time of analysis and the issue is not confirmed as actively exploited.
An out-of-bounds write (CWE-787) in Adobe FrameMaker allows arbitrary code execution in the context of the current user when a victim opens a crafted FrameMaker document. Exploitation is file-based and requires user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base score 7.8 HIGH): the attacker must socially engineer the target into opening malicious content, and the resulting code runs with only that user's privileges rather than gaining system-level control. No confirmed active exploitation or publicly available exploit code was identified at time of analysis, but the full confidentiality, integrity, and availability impact makes prompt patching important for engineering and technical-publishing environments that routinely exchange FrameMaker files.
Heap-based buffer overflow in Adobe FrameMaker enables arbitrary code execution in the context of the current user when a victim opens a maliciously crafted file. The provided CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8 HIGH) confirms the attack is local and requires user interaction, with no privileges needed to trigger the flaw but no remote or automatable path either. No public exploit was identified at time of analysis, exploitation is bounded to systems where FrameMaker is installed and used to open untrusted documents, and code runs only with the current user's privileges - there is no automatic elevation of privilege.
Code injection in SQL Server Management Studio and Visual Studio Tools for Applications hosts allows remote, unauthenticated attackers to execute arbitrary code in the security context of the user who opens a crafted project, script, or database object. Rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), exploitation is gated by user interaction, so it depends on social-engineering a developer or DBA into opening attacker-supplied content rather than a zero-click or server-side trigger. No public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation; the risk profile makes this a credible patch priority rather than an emergency.
Remote code execution in ASP.NET Core via a code-injection flaw (CWE-94) allows an unauthenticated, network-based attacker to execute arbitrary code when a victim user interacts with crafted content (CVSS 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploitation requires an ASP.NET Core application that routes attacker-controlled input through a dynamic code-generation or evaluation path; the user interaction requirement (UI:R) is a significant limiting factor, preventing fully autonomous or wormable exploitation. No public exploit code was identified at the time of analysis, and the specific framework API or configuration exposing the injectable path is not described in the available data and should be confirmed against the Microsoft MSRC advisory.
Authenticated code injection in Microsoft SharePoint (CVSS 3.1 base 8.8) allows a remote attacker holding a valid low-privileged SharePoint account to run code in the server's context and elevate privileges, with low attack complexity and no user interaction required. The flaw is rooted in improper control of code generation (CWE-94) inside SharePoint, and the assessed vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms that the authentication prerequisite is the primary barrier - an outside attacker must first obtain or compromise a low-privileged credential, after which confidentiality, integrity, and availability are all fully impacted. No confirmed active exploitation (CISA KEV) and no public exploit code were identified at time of analysis, so this should be treated as a high-priority patch item rather than an actively exploited emergency; the specific vulnerable endpoint is not named in the description and should be confirmed against the Microsoft MSRC advisory.
Arbitrary code execution in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source is reachable by an attacker who already holds a high-privilege administrator-level account, exploiting an improperly validated input path to run code in the context of the current user with no victim interaction required. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) rates confidentiality, integrity, and availability impact as high with a changed scope, meaning the effect is not contained within the vulnerable component; the governing limitation is the PR:H precondition, which keeps the realistic attacker set to insiders, holders of compromised admin credentials, or post-authentication attack chains rather than anonymous or low-privileged users. No public exploit code was identified and there is no confirmed active exploitation (CISA KEV) at time of analysis, so this should be treated as a high-value post-authentication target rather than an opportunistically exploited one.
Unauthenticated remote code execution affects Adobe Commerce, Adobe Commerce B2B, and Magento Open Source through improper neutralization of special elements used in a template engine (CWE-1336, server-side template injection). Per the vendor CVSS vector (AV:N/AC:L/PR:N/UI:N/S:C), an attacker can reach the vulnerable template-processing surface over the network without credentials and without any victim interaction, and the scope change (S:C) indicates compromise can extend beyond the vulnerable component into the surrounding account or session context. The score is the maximum possible (10.0) and Adobe has published remediation guidance in APSB26-153; no public exploit code or confirmed active exploitation was identified at time of analysis, so the risk is driven by severity and ease of reachability rather than observed attacks.
Arbitrary code execution is achievable in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source by an attacker who already holds a high-privilege backend account, exploiting an improper input validation flaw (CWE-20) that a single crafted, network-delivered request can trigger without any user interaction. The CVSS 3.1 base score of 9.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) reflects complete compromise of confidentiality, integrity, and availability with a changed scope, but the PR:H metric means the attacker must first obtain administrative or equivalently privileged credentials - stolen admin or API credentials, or a pre-existing privileged foothold. Adobe reported the issue directly (APSB26-153); no public exploit code has been identified and there is no confirmed active exploitation (not in CISA KEV) at time of analysis, so the practical risk is concentrated in organizations whose admin panels are internet-exposed with weak credential controls.
Remote, low-complexity code execution is possible in Adobe Commerce, Adobe Commerce B2B and Magento Open Source through an incorrect authorization flaw (CWE-863) rated CVSS 9.8, allowing an attacker to act with the privileges of the current request context and escalate to arbitrary code execution without user interaction. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) describes network-reachable exploitation requiring no prior privileges, which is the strongest signal in the available data. No public exploit code and no CISA KEV entry were identified at time of analysis, and Adobe's only provided reference is advisory APSB26-153; defenders should note Adobe's wording about 'the context of the current user,' which may indicate an existing session or request context is required even though the vector claims PR:N.
Code injection in dataclasses-avroschema versions 0.38.0 through 0.70.5 lets an attacker who controls the Avro schema consumed by the library's model-generator classes inject arbitrary statements into the generated Python source, because enum symbols are used as generated enum member names after case conversion without being validated as Python identifiers. Exploitation is not on the library's default runtime serialization path: it requires an application to invoke the generator classes directly (BaseGenerator.parse_enum / EnumRepresentation.render_symbols) on an attacker-supplied schema and then import or execute the emitted module, which is why the assessed vector carries UI:R despite being network-reachable and unauthenticated (PR:N). Impact when the chain is completed is code execution and namespace modification in the importing process with high confidentiality, integrity, and availability consequences (CVSS 8.8); no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis. Version 0.70.6 fixes the issue by validating every enum symbol as a name.
Arbitrary code execution in dataclasses-avroschema versions 0.38.0 through 0.70.5, where BaseGenerator.parse_fixed writes a fixed type's 'aliases' value straight into the generated types.confixed annotation: a bare string alias (instead of a JSON list) is emitted as an unquoted Python expression and evaluated the moment the generated module is imported. Exploitation is not automatic - it requires a developer to run the library's Avro-schema-to-Python code generation over an attacker-influenced schema and then import the resulting module, which is why the vector carries UI:R despite PR:N and network-level delivery of the malicious schema. The flaw is a genuine CWE-94 code-injection issue with high confidentiality, integrity and availability impact under our assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H; no public exploit code has been identified at time of analysis and it is not in CISA KEV. Version 0.70.6 fixes it by rejecting any 'aliases' value that is not a list.
Code injection in dataclasses-avroschema 0.38.0 through 0.70.5 allows an attacker who supplies a crafted Avro schema to the library's Avro-to-Python code generator (model_generator) to embed arbitrary Python statements into the generated module via an enum field default, and those statements execute when the generated module is imported, either modifying the module namespace or preventing it from loading (CVSS 3.1 8.8, CWE-94). The CVSS vector (AV:N/AC:L/PR:N/UI:R) indicates the flaw is unauthenticated but requires user interaction: a victim must run the generator against the attacker-controlled schema and then import the resulting module, so environments that only generate code from their own trusted models or never load attacker-influenced generated code are not exposed. The maintainer confirmed and patched the issue in 0.70.6 by validating enum defaults as names; no public exploit code has been identified at time of analysis, and no active exploitation is confirmed (CISA KEV) at the time of writing.
Arbitrary code execution is possible in JFrog CLI when specific, non-default configurations are combined with an argument-injection weakness (CWE-88) that allows attacker-influenced input to be incorporated into arguments passed to an underlying command. The flaw carries a 9.0 base score with the vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, meaning the vector formally allows unauthenticated, no-interaction network exploitation, but the High attack complexity reflects the configuration preconditions that gate it rather than ease of use. Only environments running JFrog CLI are in scope - typically developer workstations and CI/CD pipelines that interact with JFrog Artifactory/Platform - and no public exploit has been identified at time of analysis.
Python code injection in dataclasses-avroschema versions 0.38.0 through 0.70.5 lets an attacker with control over Avro schema content smuggle arbitrary Python statements into the enum class body that the library emits, so simply importing the generated module executes the attacker's code. The flaw sits in EnumRepresentation.render_symbols, which wraps each schema-supplied enum symbol in double quotes without escaping it, allowing a quote character to close the literal and append attacker-chosen Python. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8, CWE-94) indicates no privileges are required but that user interaction is essential, since the victim must run the import of the generated file; no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, and version 0.70.6 fixes it by escaping enum symbol values before rendering.
Arbitrary Python code execution in dataclasses-avroschema versions 0.44.0 through 0.70.5 occurs because the Pydantic and AvroDantic model generators embed an Avro schema field's pydantic-class value directly into a generated field annotation after the literal prefix 'pydantic.', without sanitizing the expression. When a victim runs the code-generation path (ModelGenerator) on an attacker-influenced schema and then imports the generated Python module, the injected annotation is evaluated at import time and the payload executes with the privileges of that process, giving full confidentiality and integrity impact (CVSS 8.8, AV:C:N/AC:L/PR:N/UI:R). Exploitation is unauthenticated from the network perspective (CVSS PR:N) but requires the victim to generate and import the code, and no public exploit code or CISA KEV entry was identified at time of analysis; version 0.70.6 restricts the value to a bare name or a call to a bare name with literal arguments.
Arbitrary Python code execution is possible in dataclasses-avroschema versions 0.65.9 through 0.70.5 when the library's Pydantic or AvroDantic model-generation path is run over an Avro schema the attacker controls: the schema field's 'doc' value is interpolated unescaped between the quotes of a generated pydantic.Field(description="...") argument, so a crafted quote can close the string and inject a Python expression that is evaluated when the generated class is defined (CWE-94). The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (8.8), reflecting high confidentiality and integrity impact with user interaction required because a developer or build process must actively generate models from the malicious schema; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV, and urgency is further moderated because only the Pydantic/AvroDantic generators are affected and only versions 0.65.9-0.70.5 are vulnerable.
Code injection in dataclasses-avroschema 0.38.0 through 0.70.5 lets an attacker-influenced Avro schema execute arbitrary Python when the library's model generator renders a 'fixed' type's namespace into generated source. BaseGenerator.parse_fixed interpolates the namespace between quotes inside a generated types.confixed annotation without escaping, so a namespace containing a quote character terminates the string literal and turns the remainder into live Python that runs when the generated class is defined or the generated module is imported; the assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (8.8), unauthenticated over the network but requiring the victim to run code generation on the crafted schema and then import the result. The flaw is fixed in 0.70.6, which enforces that namespaces are dot-separated sequences of valid Avro names; no public exploit code was identified at time of analysis and the issue is not in CISA KEV, but the high CVSS score, confirmed GHSA-h9q3-f96w-f88j advisory, and availability of a vendor fix commit make prompt upgrading advisable for anyone generating code from externally sourced schemas.
Code injection in dataclasses-avroschema versions 0.40.0 through 0.70.5 lets an attacker who controls the `doc` value of an Avro schema record close the generated class docstring and inject arbitrary Python statements into the emitted class body, achieving code execution when the generated module is imported. The CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) rates the flaw as network-reachable, low-complexity and unauthenticated with high confidentiality and integrity impact, but exploitation is gated by user interaction: a developer or CI pipeline must both run the library's model generator against the attacker-influenced schema and import the resulting Python file. No public exploit code has been identified at time of analysis, and the vendor released a fix in 0.70.6.
Authenticated OS command injection in the odt2spip plugin for SPIP before 4.4.0 allows author-level users to execute arbitrary commands as the web-server user by uploading a document with a crafted non-.odt filename through the document import form. The flaw survives sanitization in odt2spip_deplacer_fichier_upload() and LibreOffice::createCommand(), then triggers during LibreOffice conversion; exploitation requires a working LibreOffice backend and an author account. No public exploit was identified at time of analysis.
Code injection in dataclasses-avroschema 0.62.3 through 0.70.5 allows an attacker-supplied Avro record name to break out of the quoted Meta.schema_name string literal and inject arbitrary Python statements into the generated model's class body, which then execute when that generated module is imported. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R) means no authentication is required but a victim must run the Avro-to-Python code generator on an untrusted or tainted schema and subsequently import the generated file; generating Avro schemas from trusted local dataclasses does not trigger it. Vendor-released patch: 0.70.6. No public exploit identified at time of analysis, and the issue is not confirmed actively exploited (no CISA KEV entry).
Unauthenticated remote attackers can write arbitrary files on servers running Risesoft-y9 Digital-Infrastructure 9.6.5 through 9.6.11 by abusing a path traversal flaw in the fileManager module's storeFile endpoint; a single crafted POST to /rest/storeFile with attacker-controlled fullPath and fileName parameters lets the service account create or overwrite files anywhere it has write permission, which can escalate to code execution if a writable path is later executed or parsed. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H (8.8, matching the published CVSS 4.0 score), reflecting high integrity and availability impact with no confidentiality impact, and no KEV listing, so there is no confirmed active exploitation (no public exploit identified at time of analysis), though the presence of a public technical writeup and a VulnCheck advisory makes weaponization plausible. Real-world impact is bounded by the service account's write permissions and by whether the vulnerable fileManager endpoint is reachable from the attacker's network position rather than internal-only; this is a credible high-priority issue rather than a high-CVSS-but-low-risk paper cut.
Code injection in dataclasses-avroschema versions 0.38.0 through 0.70.5 allows remote, unauthenticated attackers who supply a crafted Avro schema to inject constrained Python statements into the module produced by the schema-to-code generator; the injected code executes when that generated module is imported. Exploitation requires the victim to deliberately process an untrusted schema through the avro-to-code path and then import the resulting module (the UI:R gate), which limits exposure to pipelines that ingest third-party schemas. CVSS 3.1 base score is 8.8 (High) with vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H; no public exploit identified at time of analysis, and version 0.70.6 fixes the flaw by validating enum defaults as names.
Arbitrary code execution in dataclasses-avroschema 0.38.0 through 0.70.5 occurs when the library's Avro-to-Python model generator processes a schema containing a fixed type whose 'aliases' value is a bare string instead of a list; the value is interpolated unquoted into a generated 'types.confixed' annotation and evaluated when the generated module is imported, giving an attacker code execution in the victim's Python process. Exploitation is unauthenticated from the network perspective (CVSS:3.1/AV:N/AC:L/PR:N/UI:R) but gated on victim interaction: someone must run the schema-to-code generation path on attacker-controlled schema content and then import the resulting module. There is no public exploit code identified at time of analysis and no confirmed active exploitation (CISA KEV), so this is a high-severity but precondition-gated code-injection flaw; the vendor released 0.70.6, which rejects non-list aliases.
FearlessCMS 0.1.2b and earlier lets an authenticated administrator supply an arbitrary Git repository URL to the dashboard updater (admin/updater-handler.php → perform_update → update.sh), which clones the repository and overwrites the live plugins/, admin/, and includes/ directories without validating the repository's identity, signatures, or contents. Because router.php allows existing PHP files under plugins/ to be executed by the PHP built-in development server - the project's documented run mode - the injected update content runs as arbitrary PHP under the web server account and can persist as a backdoor, yielding full compromise of confidentiality, integrity, and availability. Exploitation is gated on high-privilege (administrator) authentication and affects only versions at or below 0.1.2b; no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and no EPSS score was provided.
Code injection in the Salty Docs documentation build pipeline (saltyorg/docs) lets an attacker-controlled fork pull request execute arbitrary code in the privileged base-repository GitHub Actions workflow that has repository secrets in scope, resulting in disclosure of CF_API_TOKEN, GH_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY and a write-capable GITHUB_TOKEN and enabling follow-on compromise of the docs.saltbox.dev deployment. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (10.0) and, per the independent assessment, exploitation is confined to repositories running this specific pre-fix workflow pair - the trigger-pr-build.yml workflow records an untrusted fork commit SHA in the pr_info artifact and build-pr.yml's workflow_run job checks that SHA out before running 'pip install -r requirements.txt'. No public exploit code identified at time of analysis and the issue is not in CISA KEV, but the code path is a genuine CI/CD supply-chain flaw rather than a CVSS-inflated paper risk, so the risk is high for unpatched users of this template. Practical exploitation still requires an attacker to control fork content (malicious setup.py or PEP 517 build hook) rather than merely tampering with artifact metadata, and submitting a fork PR requires a GitHub account even though the vector scores PR:N.
A double-free in Dragonfly's RDB stream loader (OpaqueObjLoader::CreateStream in src/server/rdb_load.cc) lets a remote, unauthenticated attacker corrupt the allocator, crash the server, and potentially execute code as the Dragonfly service account by sending a crafted serialized stream to the RESTORE command. All Dragonfly builds prior to the 1.40 fix are affected, and exposure is highest because Dragonfly ships with authentication disabled by default (no requirepass or ACLs), so network reachability to the client port is the only real precondition (assessed as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; the upstream advisory scores it 9.6 with an AV:A/S:C vector). No public exploit code was identified at time of analysis and the issue is not tied to a CISA KEV entry, but the trigger is a single crafted RESTORE payload and the upstream fix has not yet been mapped to a published release, so unpatched, internet-reachable instances should be considered urgent.
Arbitrary file overwrite in Wazuh Manager (3.9.0 through versions prior to 4.14.8) lets an attacker who already controls an enrolled cluster worker node corrupt protected master-side files - including ossec.conf and agent.conf - by abusing a trailing-slash basename path-validation bypass and the lack of extra_valid enforcement in MasterHandler.process_files_from_worker. Because the manager runs as root and pushes configuration out to its fleet, the overwritten files escalate into root-level remote code execution on the manager and on every connected agent, which is why the vulnerability carries a CVSS 4.0 base score of 9.4 (independent CVSS 3.1 assessment: AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H). The PR:H prerequisite is the key limiter: the attacker must already control a worker node that is enrolled and syncing with the master, so this is not anonymously reachable from the internet, standalone (non-clustered) managers do not expose the vulnerable path, and no public exploit code had been identified at time of analysis.
Remote code execution in Wazuh agents 4.3.0 through 4.14.7 (not including 4.14.8) allows an attacker who already holds manager-level control over a Wazuh deployment to run arbitrary SCA policy command checks as root on every enrolled agent. The root cause is that the SCA subsystem decides whether a policy is trusted by its file path rather than by its configuration source or signature, so an unsigned policy file planted in var/incoming through the agent upgrade channel is honored and its checks execute with root privileges. The vendor CVSS 4.0 base score is 8.6 (High) - network vector, low complexity, no user interaction (PR:H), with high confidentiality, integrity and availability impact on the agent - and represents a fleet-wide escalation that only applies after a manager has already been compromised. No public exploit code and no confirmed active exploitation were identified at time of analysis; the vendor released a fix in Wazuh v4.14.8.
Unsafe deserialization in NVIDIA Megatron-LM's checkpoint-loading routine allows an attacker to execute arbitrary code, escalate privileges, disclose information, and tamper with data by convincing a user to load a maliciously crafted checkpoint or model file into the framework. The flaw is rated CVSS 7.8 (High) and is reachable only when a victim actually opens an attacker-supplied checkpoint, so organizations that load checkpoints exclusively from trusted internal sources are not realistically exposed; the vulnerable path is local (AV:L) and depends on user interaction per our assessment, with no network service or authentication bypass involved. No public exploit code has been identified at time of analysis and the vulnerability is not in CISA KEV, though the availability of proof-of-concept tooling for pickle-based deserialization attacks in ML frameworks makes this class of issue practically exploitable once a crafted checkpoint is delivered.
Path traversal in the NVIDIA AIStore for Linux dSort archive extraction component allows a remote attacker to write files outside the intended extraction directory by submitting a dSort job that references an archive (e.g., tar/zip) whose member names contain crafted traversal sequences, yielding arbitrary file creation or overwrite and potentially code execution, information disclosure, data tampering, and denial of service. The vulnerability carries a CVSS 3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) per the assessed vector, indicating remote reachability and no authentication requirement, but a high attack-complexity rating that reflects the difficulty of reliably crafting the malicious archive and triggering the flaw. There is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis; the practical gating factor is network access to the AIStore dSort/API endpoint, which in typical deployments is confined to a trusted ML/training cluster or private network rather than being internet-facing. Because the dSort job-submission path is the attack surface, exposure is primarily amplified where AIStore's API is reachable from untrusted networks, and no user interaction is required.
Unauthenticated remote attackers can achieve code execution and privilege escalation against NVIDIA AIStore for Linux by injecting arbitrary Kubernetes host-namespace and container security settings into the legacy ETL Kubernetes PodSpec initialization API, rated CVSS 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) because the impact escapes the AIStore workload and extends to the underlying Kubernetes node and cluster. The vector confirms the attack is network-reachable with no privileges or user interaction required, though practical exploitation depends on the legacy ETL/transformation feature being enabled and the ETL API being exposed, and on Kubernetes RBAC and PodSecurity admission being permissive enough for AIStore to actually schedule host-namespaced or privileged pods. At time of analysis there is no confirmed active exploitation (CISA KEV) and no public exploit code identified, but the vendor-reported severity, the scope-changed impact, and CWE-250 (execution with unnecessary privileges) place this in top-priority territory for any cluster running an exposed AIStore ETL endpoint.
Deserialization of untrusted data in the NVIDIA Megatron-LM checkpoint-loading path allows code execution, privilege escalation, information disclosure, and data tampering when a user is convinced to load a maliciously crafted checkpoint file. NVIDIA PSIRT scores this CVSS 7.8 (High) and both the vendor and the independent assessment agree on full confidentiality, integrity, and availability impact; the assessments differ on prerequisites, with the vendor vector indicating low privileges and no user interaction (PR:L/UI:N) while the independent assessment models it as no privileges with required victim interaction (PR:N/UI:R). No public exploit code or CISA KEV entry was identified at time of analysis, and only environments that actually load untrusted checkpoints are exposed; code runs with the privileges of the loading user or process, not inherently as root.
Unauthenticated path traversal in the target-side object rename handler of NVIDIA AIStore on Linux allows a remote attacker who can reach a target (storage) node directly to write files outside the intended storage directory by supplying a crafted rename destination, resulting in arbitrary file creation or overwrite. NVIDIA rates the issue CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-22), with downstream consequences that could include code execution, privilege escalation, information disclosure, data tampering, and denial of service depending on what the overwritten path controls. Exploitation is constrained rather than trivial: the attacker needs network reachability to a target node - not merely the front-end proxy - and must build a traversal payload the rename handler accepts, so exposure is greatest in flat cluster networks or environments where target ports are directly reachable; no public exploit code and no CISA KEV entry were identified at time of analysis.
Guest-to-host privilege escalation in Xen's tapdisk (blktap) userspace xen-blkback backend lets a malicious or buggy guest VM crash or potentially execute code as host root: all versions of tapdisk are affected because the device-connect path performs no boundary check on the multi-page ring size requested by the frontend. Exploitation requires only that the host runs the XAPI toolstack with tapdisk as the block backend and that the attacker already controls a guest VM attached to it (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), with no user interaction on the host side; the vulnerability is reachable under default configurations, and the Xen Security Advisory states there are no mitigations. No public exploit code or active exploitation has been identified at time of analysis, and the fix is an upstream patch (xsa521.patch) for blktap master rather than a named released version.
Stack-based buffer overflow in NVIDIA DALI lets a locally authenticated, low-privileged user who can get a crafted input file processed through a DALI pipeline corrupt memory and potentially achieve code execution, information disclosure, data tampering, or denial of service. Per the assessed CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, base 7.3 High), exploitation is not remotely reachable: it requires an existing local foothold with at least low privileges plus some form of user interaction, which in practice means a victim or automated process must load attacker-controlled data. There is no public exploit identified at time of analysis and the flaw has not been added to CISA KEV; the practical risk concentrates on multi-tenant or pipeline-automation GPU hosts where untrusted files are routinely fed into DALI. Exact affected versions are unconfirmed because the CPE is a wildcard, so defenders must verify their deployed DALI build against the NVIDIA advisory.
Eval injection in NVIDIA Isaac Lab allows a local attacker who can supply crafted input - such as a malicious experiment configuration, task/environment definition, or command-line parameter - to achieve arbitrary code execution, information disclosure, data tampering, and denial of service once a user opens, loads, or runs the content. The flaw is rated CVSS 7.8 (HIGH) with vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H: no privileges are required (PR:N) but the victim must interact with the malicious input (UI:R), the attack path is local (AV:L), and impact is scoped to the invoking user (S:U), so no privilege escalation is implied. The CPE entry is a wildcard with no version boundary and no fixed version is published in the available data, so all Isaac Lab releases should be treated as potentially affected; no public exploit code and no confirmed active exploitation have been identified at time of analysis.
Siemens Industrial Edge App Publisher versions below V1.27.9 fails to sanitize or escape data received from the backend before rendering it in its integrated Node.js front end, enabling injected JavaScript to execute with the client's privileges and escalate to remote code execution on the victim's machine. Exploitation requires an attacker to control or influence backend-delivered data and a victim to actively view that data in the vulnerable client, making this a targeted threat rather than opportunistic mass exploitation. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the vendor has released a patch in V1.27.9.
Local capability escalation in the macOS build of the DigiD app (Logius) lets an attacker who already holds user-level code execution on the same Mac inject an arbitrary dynamic library into the DigiD process and run code under the app's identity, reaching DigiD data and cryptographic operations the process would not normally expose - CVSS 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). The root cause is that the app binary is not signed with the Hardened Runtime flag, so the loader still honours DYLD_INSERT_LIBRARIES; this is a post-compromise escalation primitive, not a remote or initial-access bug, and it grants no privilege beyond the app's own context (S:U) and no availability impact. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV); a Hardened-Runtime-signed build blocks the injection path and is available per the vendor advisory pointing at the Mac App Store listing.
Unauthorized SCIM API access in Perforce Helix Authentication Service (HAS) versions 2022.1 through 2025.2 arises from a shipped default bearer token that the installer and configuration script fail to rotate, enabling remote, unauthenticated attackers who know the token to perform user and group provisioning operations. Chaining this with CVE-2026-61834 in the scim-patch dependency allows server-side prototype pollution and, under Node.js 24/Express with specific gadget chains, remote code execution. The underlying defect is removed in HAS 2026.1; no public exploit code has been identified at time of analysis.
Opening a crafted S-102 bathymetric surface HDF5 file in OpenS100 through commit daaa35b can trigger a 32-bit integer overflow that under-allocates a heap buffer and lets attacker-controlled data be written out of bounds, resulting in an application crash or potential arbitrary code execution. The flaw lives in S102_VG_BathymetryCoverage::Read(), where the product of the numPointsLatitudinal and numPointsLongitudinal grid dimensions wraps around before the buffer size is computed. Exploitation is unauthenticated (PR:N) but constrained: no network-reachable path exists (local vector) and the victim must actively open a malicious file, and while publicly available exploit code exists, EPSS is low at roughly 0.20% (10th percentile), the issue is not in CISA KEV, and the overall signal is a real but low-priority issue rather than an urgent threat.
Remote code execution in GitLab CE/EE (all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2) allows an unauthenticated attacker to execute arbitrary code on the GitLab server by supplying a specially crafted regular expression in a CI/CD configuration that passes insufficient regex validation; the defect is tracked as CWE-190 (integer overflow) and the vendor scores it 10.0 with scope change (S:C). Publicly available exploit code exists, referenced through HackerOne reports cited in the CVE record, but there is no CISA KEV entry and no confirmed active exploitation at time of analysis. Our independent assessment retains the same impact (C:H/I:H/A:H) but raises attack complexity to AC:H, because the vendor states the regex-validation path is reached by an unauthenticated user only 'under certain conditions' that are not detailed publicly and should be confirmed with GitLab; patched instances (19.4.2, 19.3.5, 19.2.8 or later) are not affected.
Remote code execution in SAP S/4HANA's Manage Substitution/Validation Rules allows an authenticated attacker who already holds rule-maintenance business authorizations to submit crafted rule definitions that the rule-processing logic interprets as executable ABAP, resulting in full compromise of the affected system with high impact to confidentiality, integrity and availability (CVSS 9.9, Scope:Changed). Reaching the vulnerable code path requires an account provisioned with substitution/validation rule creation or maintenance privileges, so the practical barrier is authorization scope rather than authentication alone. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but the vendor advisory (SAP Security Note 3805589) should be treated as urgent given the code-injection primitive and the privileged business role required.
Unauthenticated remote code execution affects the SKYWORTH SK-WR6640X (AX1800M) Wi-Fi 6 dual-band fiber router running firmware V1.0.3, allowing a network-reachable attacker to run arbitrary code with full confidentiality, integrity and availability impact (CVSS 9.8, AV:N/AC:L/PR:N/UI:N). Because the name of the vulnerable endpoint, protocol or feature is not disclosed, the practical limiting factor is reachability rather than credentials: on typical home deployments the affected service is LAN-facing, and only internet-facing management, a port-forward, or an exposed management interface would place it within reach of a remote attacker. Assessment signals are mixed - a maximum-severity score and a public disclosure write-up from the PRISMI-Team coexist with a low EPSS of 0.24% (14th percentile), no confirmed actively exploited (CISA KEV) status, and no public exploit code identified at time of analysis.
Arbitrary code execution in mp4v2 2.0.0 can be triggered when a victim or application opens a specially crafted MP4 file containing an undersized RTP ('rtp ') atom; MP4RtpAtom::ReadHntiType() performs an unchecked offset subtraction that underflows to a near-2^64 allocation size, leading to memory corruption and potential code execution. The assessed vector is local with user interaction required (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), so the malicious file must be parsed on the target system rather than delivered to a listening network service. No public exploit identified at time of analysis; EPSS is 0.18% (7th percentile), and the upstream fix is available as a PR/commit but no released patched version is independently confirmed.
Directory traversal in the iKuai8 management interface shipped on the IK-Q3000 Enterprise-grade Wi-Fi 6 router lets an attacker escape the intended file path and execute arbitrary code on the device; affected builds are Enterprise Edition <= iKuai8_3.7.23_Enterprise Build 202606021825 and Free Edition <= iKuai 8_4.0.304-beta. The CVE record scores this 9.8 with a PR:N vector (unauthenticated), but the public disclosure is explicitly titled 'authorized' path traversal and our independent assessment rates it PR:L, so a valid authenticated management session is most likely a prerequisite and is the key factor limiting real-world exploitation. There is no CISA KEV entry and no public exploit identified at time of analysis, and EPSS is low at 0.45% (38th percentile); exposure is further gated by network reachability to the router's administrative web service, so units with management bound to an internal/LAN interface are materially less exposed.
Remote code execution and sensitive-information disclosure in IBM i 7.3, 7.4, 7.5, and 7.6 stem from improper data sanitization by the HTTP Server Administration web application (CWE-94 code injection). An authenticated attacker with only low privileges who can reach that administration interface over the network can inject and execute arbitrary code or read sensitive data, with the scope change (S:C) driving Confidentiality, Integrity, and Availability impacts all High for a CVSS 3.1 base score of 9.9. Exploitation is not unauthenticated and is not possible against systems that do not run the HTTP Server Administration interface, or that expose it only to a trusted management network; no public exploit has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation, though IBM has published a vendor patch.
Authenticated remote code execution in IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 arises from improper validation of file paths inside archives the platform extracts, allowing an attacker with a valid account to write files to arbitrary locations and execute code under the privileges of the TRIRIGA service (CVSS 3.1: 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack is network-reachable with no user interaction and low complexity, but the PR:L vector gates it behind an existing authenticated session, confining realistic exploitation to insiders or attackers who have already obtained platform credentials. No public exploit identified at time of analysis, and IBM has published a vendor patch advisory covering the affected 5.0.0-5.0.8 range.
Authenticated remote code execution in IBM Planning Analytics 2.0 and 2.1 stems from a stack-based buffer overflow (CWE-121) that allows a remote attacker holding valid low-privilege credentials to corrupt stack memory and execute arbitrary code. IBM assigns a CVSS 3.1 base score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), and the independent assessment raises the availability impact to High, indicating a successful exploit may also crash or destabilize the affected service. No public exploit code has been identified at time of analysis and the vulnerability is not listed in CISA KEV; vendor patches are available via IBM support node 7291604.
Authenticated path traversal in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote attacker holding a valid platform account to bypass intended directory restrictions and execute arbitrary code. Exploitation requires only low-privileged credentials (CVSS PR:L), needs no user interaction, and is network-reachable with low complexity, which is why the vector scores 9.9 Critical with a scope change (S:C) reflecting impact that can extend beyond the vulnerable component. Despite the high score, the practical risk picture is more moderate: EPSS is only 0.49% (40th percentile), CISA SSVC rates exploitation as none with automatable set to no, there is no public exploit code identified at time of analysis and no KEV listing, and the vendor has published a patch, so remediation is available rather than dependent on compensating controls alone.
Authenticated remote code execution in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows an attacker who already holds valid low-privilege credentials (CVSS PR:L, AV:N, UI:N) to run arbitrary operating system commands on the underlying host, resulting in high confidentiality, integrity, and availability impact (CVSS 8.8). The root cause is improper neutralization of special elements used in an OS command (CWE-94), meaning user-supplied input reaches a shell command without adequate sanitization. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV), but a vendor patch is available per IBM's advisory, so unpatched 5.4.0.0 deployments exposed to multi-tenant users or broadly provisioned accounts should be prioritized for upgrade.
Remote code execution in IBM Maximo AI Service 9.1.0 and 9.2.0 lets an unauthenticated remote attacker execute arbitrary code on an affected deployment by abusing improper control of code generation (CWE-94). With 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), the flaw requires no authentication, no user interaction, and no special conditions beyond network reachability of the vulnerable instance. No public exploit code has been identified at time of analysis, and there is no KEV listing; IBM has published an advisory with a vendor fix, so the practical priority is identifying and patching internet- or network-exposed Maximo AI Service 9.1.0/9.2.0 instances.
Local code execution in IBM Power Systems firmware (FW1060.00 through FW1060.81) lets an attacker who already holds authenticated service-level access to the Flexible Service Processor (FSP) send a crafted service processor mailbox message that overflows host firmware runtime attribute storage, compromising the managed system's memory and hardware interfaces. The CVSS 3.1 vector AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H (base 8.2) is internally consistent with that description: the flaw is local, requires high-privilege service-plane credentials, needs no user interaction, and its scope change reflects a jump across the trust boundary from the service processor into the host firmware runtime with high confidentiality, integrity and availability impact. No public exploit code has been identified at time of analysis and there is no CISA KEV entry; IBM published the vendor advisory at https://www.ibm.com/support/pages/node/7290126.
Arbitrary code execution on the host system is possible in IBM Power Systems firmware versions FW1120.00 through FW1120.01, FW1110.00 through FW1110.31, and FW1060.00 through FW1060.81, due to a stack-based buffer overflow (CWE-121) in the host firmware boot process image validation path. An attacker with high-privileged service access to the service processor (PR:H, AV:L) can supply a maliciously crafted code update image to execute arbitrary code on the host system, resulting in full confidentiality, integrity, and availability impact (CVSS 3.1 base score 8.2, High). No public exploit has been identified at time of analysis, and exploitation requires local/service-level access and high privileges, substantially limiting real-world risk.
Arbitrary code execution in the host firmware runtime of IBM Power Systems is possible via the service processor mailbox interface, affecting firmware levels FW1060.00 through FW1060.81. An attacker with authenticated service-level access to the Flexible Service Processor (FSP) can send a crafted mailbox message that overflows host firmware runtime attribute storage (CWE-121), gaining full access to the managed system's memory and hardware interfaces. This is a high-severity local/management-plane issue (CVSS 8.2) requiring high privileges; no public exploit has been identified at time of analysis, and while it is not a mass-exploitation priority, isolation of the FSP network and limiting service accounts are recommended.
Authenticated users of Nginx UI (0xJacky/Nginx-UI) prior to 2.4.1 can bypass the built-in nginx directive validation and write arbitrary nginx configuration through the MCP tool nginx_config_add, which reloads nginx with the injected directives. Where nginx is built with the njs or perl module (as in the official Docker image), an attacker - or an MCP-enabled AI agent steered by prompt injection - can achieve code execution on the nginx host with the privileges of the nginx worker process. The CVSS score of 8.8 reflects a network-reachable, low-complexity path requiring only authenticated MCP access (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), making this a credible, actionable priority rather than a paper-high CVSS; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing).
Code injection in the IBM Maximo Application Suite Location Service for Esri component (versions 9.0, 9.1 and 9.2) allows an attacker who already holds high-privilege control over the Kubernetes operator's configuration input - specifically the container image reference consumed from an operator template - to inject a code path that the operator then acts on, resulting in a scope-changing compromise of workloads beyond the operator's own authority (CVSS 3.1 8.7, AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N, CWE-94). The injected image reference can cause attacker-influenced containers to be deployed under the operator's service account, which is why the impact is rated high for confidentiality and integrity even though the attack is not reachable by an unauthenticated outsider against a default deployment. Exploitation is gated by PR:H - the adversary must be able to modify the Location Service for Esri operator's template or custom resource values - no user interaction is required, and there is no public exploit identified at time of analysis.
Arbitrary local program execution is possible in EdgeEver Desktop 1.92.0 through 1.112.0 because the desktop:acp-probe IPC handler performs no sender validation and spawns whatever executable path is supplied in the caller's input.path, running it with the victim user's privileges. This is not a standalone network RCE: an attacker must first land stored cross-site scripting in a renderer through the template-preview or drag-preview feature, and the victim must then preview that attacker-controlled content so the renderer script can invoke probeAcpAdapter (CVSS v4.0 7.3; independent assessment CVSS v3.1 AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H). No public exploit code and no CISA KEV listing were identified at time of analysis; an upstream fix commit has been referenced, but no patched release version has been independently confirmed.
Configuration-validation bypass in Nginx UI (versions 2.0.0-rc.6 through 2.4.0) lets an authenticated low-privilege user write arbitrary nginx configuration directives through the MCP tool nginx_config_add, which persists the file and triggers an nginx reload without ever calling config.ValidateConfigFile - the guard the REST endpoint POST /api/configs does invoke. Because blocked directives such as perl, js_import, load_module and user root can therefore be injected, an attacker on a host with the nginx Perl, njs or Lua module loaded can escalate this into post-authentication remote code execution; on hosts without a scripting module the effect is arbitrary config tampering and reload. The issue is fixed in Nginx UI 2.4.1, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Remote code execution in NetEase Cloud Music for Windows 3.1.38 and 3.1.39.205426 allows an attacker with an active adversary-in-the-middle position to forge the /pc/upgrade/get upgrade-check response using a publicly known AES key over an unvalidated TLS connection, inject renderer content, and invoke the os.navigateExternal IPC bridge with a file:// URL to execute arbitrary local binaries under the logged-in user. The vendor CVSS 4.0 score is 9.2, and the independent assessment retains high confidentiality, integrity, and availability impact with no privileges or user interaction required, though AC:H reflects the network-position prerequisite; no public exploit identified at time of analysis and no CISA KEV active exploitation is indicated.
Authenticated privilege escalation in Progress MarkLogic Server lets an attacker who already holds query-execution access invoke an XQuery evaluation function without the additional evaluation privilege that function requires, so the query is evaluated with elevated permissions and can lead to server-side code execution in the server's security context. Affected deployments are 12.x releases before 12.1.0 and 11.x releases before 11.3.7; the vulnerability is rated CVSS 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), with the scope change and full confidentiality, integrity, and availability impact reflecting what is possible once the missing privilege check is bypassed. Exploitation requires a pre-existing account with query-execution access rather than anonymous reachability, and no public exploit code has been identified at time of analysis; there is no confirmed active exploitation (CISA KEV) reported for this issue.
Remote code execution in Project MONAI 0.4.0 through 1.6.0 requires an on-path attacker to tamper with SENet pretrained weights fetched over plaintext HTTP, causing construction of SEResNet50 or another SENet model with pretrained=True to unpickle a crafted .pth file because load_state_dict_from_url is used without weights_only=True. The issue is unauthenticated but requires user interaction and a man-in-the-middle position; no public exploit identified at time of analysis. The CVE record rates it CVSS 7.7, though the assessed precondition set makes real-world urgency conditional rather than broadly exploitable.
Remote code execution in Adminer before 6.1.1 allows authenticated users with SQLite access to bypass ATTACH and VACUUM INTO restrictions by prefixing SQL statements with a UTF-8 byte-order mark. An attacker can then attach a database file at a PHP-served path and create a table named with PHP code, which executes as the web server user. No public exploit identified at time of analysis; exploitation requires valid credentials, SQLite usage, and a web-accessible writable PHP-executing path.
Authenticated code injection in Craft CMS 4.x and 5.x allows a control panel user holding the performUpdates permission (or access to the Updates utility) to execute arbitrary code on the server by submitting a crafted 'updates' request to AppController::actionCacheUpdates. The endpoint forwards the raw request parameter into UpdatesModel without applying Component::cleanseConfig(), so an attacker can inject Yii behavior and event-handler configuration keys such as 'as' or 'on' - for example an AttributeTypecastBehavior gadget - and achieve remote code execution. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (High, 8.7 in the vendor's CVSS 4.0 scoring), and no public exploit code was identified at time of analysis; the practical barrier is the privileged-account requirement, which limits realistic exposure to malicious insiders, over-provisioned admin accounts, or environments where a control panel credential has already been compromised.