Unsafe reflection in the error mitigation schema validation in Amazon Braket Schemas before 1.32.2 might allow a remote authenticated user with S3 write access to the quantum task output location to execute arbitrary code on any machine that retrieves the quantum task results via a crafted task result document.
We recommend you upgrade to amazon-braket-schemas version 1.32.2 or later.
Description
Nimbus instantiates the class named by a topology's `topology.scheduler.strategy` when scheduling it. The
allowlist intended to constrain that choice, `nimbus.scheduler.strategy.class.whitelist`, was treated as
"allow any class" when unset, and it had no entry in the shipped `defaults.yaml`, so unset was the shipped
state. An authenticated submitter could therefore cause Nimbus to instantiate any class on the Nimbus
classpath that has a no-argument constructor.
Storm's own production artifacts contain classes with side effects suitable for this: instantiating
`org.apache.storm.testing.InProcessZookeeper` starts a ZooKeeper server with its own threads and sockets
and nothing closes it, and `org.apache.storm.LocalCluster` behaves similarly. Repeated submissions
therefore consume threads, sockets and memory in the most privileged daemon in the cluster.
Mitigation
Upgrade to 3.1.0, where an unset allowlist means the strategies shipped with Storm rather than any class.
Note that this is a behaviour change: a cluster running an out-of-tree scheduler strategy without an
explicit allowlist will have those topologies refused until the class is added to
`nimbus.scheduler.strategy.class.whitelist`. The rejection message names the refused class and the
configuration key.
Users who cannot upgrade immediately should set `nimbus.scheduler.strategy.class.whitelist` explicitly to
the strategies they intend to permit.
IBM WebSphere Application Server Liberty 17.0.0.3 through 26.0.0.10 is affected by an information disclosure vulnerability due to unsafe class reflection in the JMX REST connector body parser.
** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP <Fault> carries a <detail><exceptionName> element, Axis loads the named class and, if a String <data> element is also present, instantiates it through its String constructor before checking that it is an AxisFault. Loading alone runs the class's static initializer. With a suitable class on the application's classpath this leads to remote code execution. The fault is parsed while the engine resolves the target service, before any per-service handler chain runs, so authentication handlers configured on a service do not protect against it. This affects all Apache Axis 1.x versions through 1.4.
As Axis 1 has been EOL we recommend you migrate to a different SOAP engine, such as Apache Axis 2/Java. Alternatively you could use a build of Axis with the patch from https://github.com/apache/axis-axis1-java/commit/41f3b4e8d04e310ca81f86b92630ab2c11d608bd applied. The Apache Axis project does not expect to create an Axis 1.x release fixing this problem.
CVE-2026-82894 is a high-severity vulnerability in Apache OFBiz versions before 24.09.08. It allows a remote unauthenticated attacker to invoke arbitrary OFBiz services with attacker-controlled parameters via the public showHelpPublic view. This leads to arbitrary file write, file deletion, and server-side request forgery due to improper authorization and lack of input validation. The issue is fixed in version 24.09.08.
CVE-2026-73098 is a critical vulnerability in Apache Juneau up to version 9.2.0 involving improper control of dynamically-loaded code. The flaw allows input that names a class on the application classpath to cause that class's static initializer to run during parsing, potentially leading to severe security impacts depending on the classes present. The issue is fixed in version 9.2.1, and users are advised to upgrade.
CVE-2026-119084 is a high-severity vulnerability in the Amazon Redshift JDBC Driver before version 2.3.0. It involves unsafe reflection in handling connection parameters and AWS credentials profiles, which could allow an attacker who can influence the JDBC connection URL or credentials profile to execute arbitrary code within the application context if a suitable class is present on the classpath. AWS has fixed this issue in version 2.3.0.
CVE-2026-16306 is a critical remote code execution vulnerability in the IModular.exe URI handler of INFINITT Healthcare System Manager. It allows a remote unauthenticated attacker to execute arbitrary code by crafting a malicious imodular:// URI with attacker-controlled commands and arguments. This affects versions from 3.0.11.3 through 3.0.11.5 inclusive.
CVE-2026-108097 is a high-severity vulnerability in Drupal core involving unsafe reflection, where externally-controlled input is used to select classes or code. This reflection injection flaw affects multiple Drupal core versions from 8.9.0 up to but not including 10.6.19, and several 11.x and early 12.x pre-release versions. The vulnerability allows an attacker to potentially execute arbitrary code, impacting confidentiality, integrity, and availability. Fixed versions are available starting from 10.6.19, 11.3.19, 11.4.10, and 12.0.0-beta2.
CVE-2026-108099 is a high-severity vulnerability in the Drupal Entity List module that allows unsafe reflection injection due to externally-controlled input being used to select classes or code. This affects versions from 0.0.0 up to but not including 3.0.10. The vulnerability can lead to complete compromise of confidentiality, integrity, and availability. A fix is available in version 3.0.10.
MLflow versions from 3.12.0rc0 up to but not including 3.17.0 contain a critical code injection vulnerability in the third-party scorer deserialization mechanism. This flaw allows an attacker to place a malicious Python module under a writable allowed package and invoke it via MLflow artifact endpoints, leading to remote code execution. Deployments without authentication are fully exposed, while basic-auth deployments require credentials with experiment creation and artifact upload permissions. The vulnerability is fixed in version 3.17.0.
CVE-2026-115931 is a critical reflection injection vulnerability in GitroomHQ's postiz-app that allows authenticated users to invoke internal backend functions not intended for web access. Exploitation can lead to arbitrary file reading on the server, exposing sensitive information such as environment secrets and database credentials. Additionally, an attacker can cause the backend process to exit with a single request. The vulnerability affects versions from 2.23.0 up to but not including 2.25.2 and is fixed in version 2.25.2.
MLflow versions from 3.12.0rc0 up to but not including 3.17.0 contain a reflection injection vulnerability in certain endpoints that accept serialized third-party scorer data. This flaw allows attackers to exploit deserialization logic when optional trulens packages are installed, enabling outbound requests to attacker-controlled or internal hosts with crafted headers and body. The vulnerability is fixed in version 3.17.0.
A vulnerability in the Laravel framework versions 12.45.0 through 12.67.9 and 13.0.0 through 13.26.9 allows a user with read-only access to trigger destructive database operations on related tables via crafted relationship inclusion on a read-only endpoint. This can lead to irreversible data loss, denial of service, and loss of data integrity. The issue is fixed in versions 12.68.0 and 13.27.0.
CVE-2026-92206 is a high-severity vulnerability in the CrewAI framework involving unsafe reflection that allows remote code execution. The flaw is in the load_agent_from_repository function, which improperly restricts user-supplied input used to import modules. Exploitation requires user interaction where the target loads a malicious agent configuration from the repository. Successful exploitation enables attackers to execute arbitrary code with the privileges of the service account.
CVE-2026-71253 is a critical vulnerability in Apache Johnzon affecting versions from 1.0.0 before 1.3.1 and from 2.0.0 before 2.2.0. The flaw involves unsafe reflection where ClassConverter loads and static-initializes a class named by untrusted JSON input. This can lead to severe impacts including full confidentiality, integrity, and availability compromise. The issue is fixed in versions 1.3.1 and 2.2.0.
CVE-2026-111440 is a high-severity vulnerability in openGauss-connector-jdbc affecting multiple versions from 3.0.0 through 6.0.6 and release candidates of 7.0.0. The issue arises from unsafe reflection in LogFactory.java, where a logger class name from JDBC connection parameters is loaded and instantiated without proper subclass validation, allowing instantiation of arbitrary classes if present in the client classpath. This flaw was introduced in JDBC 1.1.0 and fixed in version 7.0.0-LTS by enforcing asSubclass(Log.class) checks before instantiation.
TuxGuitar versions prior to 2.1.0 contain a vulnerability where opening a crafted .tg file can lead to arbitrary code execution. This occurs because the application loads an attacker-supplied class from an untrusted archive without proper verification, executing it with the privileges of the TuxGuitar process. The issue is resolved in version 2.1.0.
Sonatype Nexus Repository 3 contains a vulnerability where an unauthenticated remote attacker can supply attacker-controlled input to a Java class loading call via an ExtDirect endpoint. This allows the attacker to determine the presence of specific classes in the application but does not enable code execution by itself. The issue affects versions from 3.0.0 up to but not including 3.97.0. The vulnerability has a medium severity rating with a CVSS 4.0 score of 6.9.
A component loading mechanism in openPDC and openHistorian will construct and run any specified type, which may be an invalid component to load. An attacker with an authenticated user account and the ability to place a file on the host filesystem can use this to run arbitrary constructor code, and this code runs with the privileges of the affected service account.