CWE-470
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Monthly
Arbitrary constructor code execution in Grid Protection Alliance openPDC and openHistorian is reachable by an authenticated user who is also able to place a file on the host filesystem, because the component-loading routine instantiates any type name it is given without validating that the type is a legitimate component (CWE-470, unsafe reflection). Successful abuse executes attacker-supplied constructor code with the privileges of the affected service account, giving high confidentiality, integrity and availability impact on the affected instance. Exploitation is conditional rather than trivial - CVSS 4.0 scores it 7.7 with attack requirements present (AT:P) and low privileges required (PR:L), an independent assessment agrees on AV:N/AC:H/PR:L with high C/I/A impact, and no public exploit was identified at time of analysis (no CISA KEV listing, no PoC reported).
Configuration-controlled code execution in the hydra-optuna-sweeper package (Hydra 1.2.0 up to but not including 1.3.0, plus 1.4.0 development builds before 1.4.0.dev10) allows an attacker who controls Optuna sweep configuration or command-line overrides to name an arbitrary importable Python callable in hydra.sweeper.custom_search_space that Hydra resolves and then invokes inside the controller process at the application's privilege level, including bypassing the trusted execution whitelist introduced on affected 1.4.0 development releases. The assessed CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (7.8 High): delivery is local and unauthenticated, but a victim must actually launch the sweep, after which confidentiality, integrity, and availability impact is total for the affected process. Exploitation is only meaningful where sweep configuration or overrides cross a trust boundary; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.
Code execution with the hosting application's privileges is possible in Hydra 1.3.4 through versions before 1.3.7 (and before 1.4.0.dev10) when an attacker controls multiple sibling target entries in a configuration that the application passes to instantiate(). One sibling resolves hydra._internal.target_policy.UNCONTROLLED_EXECUTION_TARGETS.discard to delete a denied target from Hydra's process-global blocklist, and a later sibling - processed in insertion order against the same mutated policy - invokes the now-permitted callable; the mutation persists for the life of the process. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P, 8.5) indicates no privileges are required and only passive user interaction, and no public exploit identified at time of analysis (not in CISA KEV, no POC referenced); exploitation is limited to deployments that feed untrusted configuration content to instantiate(), and a narrow execution whitelist supplied by trusted Python code is not bypassed by the reported direct mutation path.
Denial of service in Scrapy 1.4.0 through 2.14.1 allows any web server the crawler visits to terminate the crawler process by returning a crafted Referrer-Policy response header, such as 'sys.exit', which the built-in RefererMiddleware treats as a Python import path and invokes. The flaw is reachable over the network without authentication or user interaction (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U, base 7.5 High), and its impact is limited to availability because only importable, zero-argument callables can be triggered, making realistic effect process termination rather than general arbitrary code execution. Any crawler left in its default configuration (RefererMiddleware enabled via REFERER_ENABLED=True) that fetches attacker-controlled pages is exposed; no public exploit identified at time of analysis, and the vendor-released patch is Scrapy 2.14.2.
Unsafe reflection in Kiteworks Email Protection Gateway (all versions before 9.5.0) allows an authenticated administrator holding mail-rule configuration privileges to import a crafted rule configuration that causes the mail-processing pipeline to load and execute code outside the approved set of mail-processing components, resulting in code execution in the context of the mail-gateway service account (CVSS 3.1 base 7.2, High; vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Exploitation is gated behind a high-privilege account (PR:H) with mail-rule import rights and requires no victim interaction, so the practical exposure is insider abuse or lateral movement after an attacker has already compromised such an administrative account; there is no unauthenticated or anonymous path. No public exploit code has been identified and the issue is not listed in CISA KEV; the vendor-supplied fix is version 9.5.0.
Authenticated federation peers can cause denial of service and broker state manipulation in Apache ActiveMQ Artemis before 2.34.0 by sending a crafted FEDERATION_DOWNSTREAM_CONNECT packet that forces the broker to load and instantiate arbitrary classes visible to the Artemis module classloader. The vulnerability arises from unsafe reflection (CWE-470) in FederationStreamConnectMessage.getFederationPolicy(), which passes an unvalidated class name from the CORE protocol wire buffer to Class.forName(). Although the original CVSS 3.1 vector reports PR:N (8.2 High), the described authentication requirement means the practical severity is lower; the authoritative assessment uses PR:L. No public exploit code has been identified at time of analysis.
Denial of service in IBM Financial Transaction Manager (FTM) for Red Hat OpenShift: unsafe reflection handling of externally controlled input lets an unauthenticated remote attacker (CVSS 3.1 AV:N/AC:L/PR:N/UI:N) drive the service into an availability failure, scored A:H with no confidentiality or integrity impact for a base score of 7.5. Deployments affected are the 4.0.6.x through 4.0.10.0 releases listed by IBM prior to the Interim Fix 064 level. Exploitation pressure currently looks low - EPSS is 0.60% (47th percentile), CISA's SSVC decision framework rates exploitation 'none' and automatable 'no', and no public exploit code has been identified at time of analysis - but the practical limiter is exposure rather than exploit difficulty, since this financial middleware is normally run inside controlled OpenShift clusters instead of the open internet.
Unsafe reflection in Apache Calcite Avatica before 1.29.0 allows an attacker who can influence plugin-instantiation parameters to force the loading and static initialization of arbitrary classes on the server classpath. Exploitation requires low privileges (PR:L per the assessed CVSS vector) and a dangerous static-initializer gadget already present on the classpath; the vendor states no well-known class currently satisfies this, so real-world risk is low despite the RCE tag. No public exploit code or active exploitation has been identified at time of analysis.
Data disclosure and permanent record deletion in Mongoid can be triggered by an unauthenticated remote attacker when an application passes an externally supplied field name to certain in-memory query methods for embedded documents, exploiting an unsafe reflection weakness (CWE-470). The vendor CVSS 4.0 base score of 9.2 reflects the network vector and high impact across confidentiality, integrity, and availability, though the attack requires a developer-dependent data flow (AT:P) where untrusted input reaches a field name parameter. No public exploit code or active exploitation has been identified at time of analysis, and affected/fixed versions remain unconfirmed due to an unbounded CPE (mongoid:*).
Unsafe reflection (CWE-470) in Mongoid's document persistence layer allows a crafted key to be reflected into an internal method invocation instead of the intended array-field update, which can delete stored records and render the embedding application unresponsive. The affected component is Mongoid, MongoDB's Ruby object-document mapper; the CPE record (cpe:2.3:a:mongodb_inc.:mongoid:*:*:*:*:*:*:*) carries no version bounds, so the vendor has not published a bounded version range, and exposure applies to any embedding application that forwards unauthenticated, attacker-controlled keys directly into an array-field update. The CVSS 4.0 vector marks this dependency as AT:P (Attack Requirements: Present), meaning Mongoid is not exploitable in isolation, but where that non-default coding pattern exists there is no authentication or user-interaction barrier (PR:N, UI:N/A:H). Impact is integrity and availability only (VI:H/VA:H, VC:N), and no public exploit code has been identified at time of analysis.
Arbitrary constructor code execution in Grid Protection Alliance openPDC and openHistorian is reachable by an authenticated user who is also able to place a file on the host filesystem, because the component-loading routine instantiates any type name it is given without validating that the type is a legitimate component (CWE-470, unsafe reflection). Successful abuse executes attacker-supplied constructor code with the privileges of the affected service account, giving high confidentiality, integrity and availability impact on the affected instance. Exploitation is conditional rather than trivial - CVSS 4.0 scores it 7.7 with attack requirements present (AT:P) and low privileges required (PR:L), an independent assessment agrees on AV:N/AC:H/PR:L with high C/I/A impact, and no public exploit was identified at time of analysis (no CISA KEV listing, no PoC reported).
Configuration-controlled code execution in the hydra-optuna-sweeper package (Hydra 1.2.0 up to but not including 1.3.0, plus 1.4.0 development builds before 1.4.0.dev10) allows an attacker who controls Optuna sweep configuration or command-line overrides to name an arbitrary importable Python callable in hydra.sweeper.custom_search_space that Hydra resolves and then invokes inside the controller process at the application's privilege level, including bypassing the trusted execution whitelist introduced on affected 1.4.0 development releases. The assessed CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (7.8 High): delivery is local and unauthenticated, but a victim must actually launch the sweep, after which confidentiality, integrity, and availability impact is total for the affected process. Exploitation is only meaningful where sweep configuration or overrides cross a trust boundary; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.
Code execution with the hosting application's privileges is possible in Hydra 1.3.4 through versions before 1.3.7 (and before 1.4.0.dev10) when an attacker controls multiple sibling target entries in a configuration that the application passes to instantiate(). One sibling resolves hydra._internal.target_policy.UNCONTROLLED_EXECUTION_TARGETS.discard to delete a denied target from Hydra's process-global blocklist, and a later sibling - processed in insertion order against the same mutated policy - invokes the now-permitted callable; the mutation persists for the life of the process. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P, 8.5) indicates no privileges are required and only passive user interaction, and no public exploit identified at time of analysis (not in CISA KEV, no POC referenced); exploitation is limited to deployments that feed untrusted configuration content to instantiate(), and a narrow execution whitelist supplied by trusted Python code is not bypassed by the reported direct mutation path.
Denial of service in Scrapy 1.4.0 through 2.14.1 allows any web server the crawler visits to terminate the crawler process by returning a crafted Referrer-Policy response header, such as 'sys.exit', which the built-in RefererMiddleware treats as a Python import path and invokes. The flaw is reachable over the network without authentication or user interaction (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U, base 7.5 High), and its impact is limited to availability because only importable, zero-argument callables can be triggered, making realistic effect process termination rather than general arbitrary code execution. Any crawler left in its default configuration (RefererMiddleware enabled via REFERER_ENABLED=True) that fetches attacker-controlled pages is exposed; no public exploit identified at time of analysis, and the vendor-released patch is Scrapy 2.14.2.
Unsafe reflection in Kiteworks Email Protection Gateway (all versions before 9.5.0) allows an authenticated administrator holding mail-rule configuration privileges to import a crafted rule configuration that causes the mail-processing pipeline to load and execute code outside the approved set of mail-processing components, resulting in code execution in the context of the mail-gateway service account (CVSS 3.1 base 7.2, High; vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Exploitation is gated behind a high-privilege account (PR:H) with mail-rule import rights and requires no victim interaction, so the practical exposure is insider abuse or lateral movement after an attacker has already compromised such an administrative account; there is no unauthenticated or anonymous path. No public exploit code has been identified and the issue is not listed in CISA KEV; the vendor-supplied fix is version 9.5.0.
Authenticated federation peers can cause denial of service and broker state manipulation in Apache ActiveMQ Artemis before 2.34.0 by sending a crafted FEDERATION_DOWNSTREAM_CONNECT packet that forces the broker to load and instantiate arbitrary classes visible to the Artemis module classloader. The vulnerability arises from unsafe reflection (CWE-470) in FederationStreamConnectMessage.getFederationPolicy(), which passes an unvalidated class name from the CORE protocol wire buffer to Class.forName(). Although the original CVSS 3.1 vector reports PR:N (8.2 High), the described authentication requirement means the practical severity is lower; the authoritative assessment uses PR:L. No public exploit code has been identified at time of analysis.
Denial of service in IBM Financial Transaction Manager (FTM) for Red Hat OpenShift: unsafe reflection handling of externally controlled input lets an unauthenticated remote attacker (CVSS 3.1 AV:N/AC:L/PR:N/UI:N) drive the service into an availability failure, scored A:H with no confidentiality or integrity impact for a base score of 7.5. Deployments affected are the 4.0.6.x through 4.0.10.0 releases listed by IBM prior to the Interim Fix 064 level. Exploitation pressure currently looks low - EPSS is 0.60% (47th percentile), CISA's SSVC decision framework rates exploitation 'none' and automatable 'no', and no public exploit code has been identified at time of analysis - but the practical limiter is exposure rather than exploit difficulty, since this financial middleware is normally run inside controlled OpenShift clusters instead of the open internet.
Unsafe reflection in Apache Calcite Avatica before 1.29.0 allows an attacker who can influence plugin-instantiation parameters to force the loading and static initialization of arbitrary classes on the server classpath. Exploitation requires low privileges (PR:L per the assessed CVSS vector) and a dangerous static-initializer gadget already present on the classpath; the vendor states no well-known class currently satisfies this, so real-world risk is low despite the RCE tag. No public exploit code or active exploitation has been identified at time of analysis.
Data disclosure and permanent record deletion in Mongoid can be triggered by an unauthenticated remote attacker when an application passes an externally supplied field name to certain in-memory query methods for embedded documents, exploiting an unsafe reflection weakness (CWE-470). The vendor CVSS 4.0 base score of 9.2 reflects the network vector and high impact across confidentiality, integrity, and availability, though the attack requires a developer-dependent data flow (AT:P) where untrusted input reaches a field name parameter. No public exploit code or active exploitation has been identified at time of analysis, and affected/fixed versions remain unconfirmed due to an unbounded CPE (mongoid:*).
Unsafe reflection (CWE-470) in Mongoid's document persistence layer allows a crafted key to be reflected into an internal method invocation instead of the intended array-field update, which can delete stored records and render the embedding application unresponsive. The affected component is Mongoid, MongoDB's Ruby object-document mapper; the CPE record (cpe:2.3:a:mongodb_inc.:mongoid:*:*:*:*:*:*:*) carries no version bounds, so the vendor has not published a bounded version range, and exposure applies to any embedding application that forwards unauthenticated, attacker-controlled keys directly into an array-field update. The CVSS 4.0 vector marks this dependency as AT:P (Attack Requirements: Present), meaning Mongoid is not exploitable in isolation, but where that non-default coding pattern exists there is no authentication or user-interaction barrier (PR:N, UI:N/A:H). Impact is integrity and availability only (VI:H/VA:H, VC:N), and no public exploit code has been identified at time of analysis.