# CVE-2026-126994: Code injection in braindecode

> A malicious model config with a crafted Activation value can make braindecode instantiate attacker-chosen classes or code; users loading untrusted models should care.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`resolve_type_kwargs`)
- **Fix available:** No
- **Published:** 12 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-c3h9-q839-4w8h

## What is CVE-2026-126994?

CVE-2026-126994 is a medium-severity code injection vulnerability in braindecode, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been found in braindecode up to 1.8.1. Affected is the function resolve_type_kwargs of the file braindecode/models/util.py of the component Model Config Deserialization. Such manipulation of the argument Activation leads to use of externally-controlled input to select classes or code. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The name of the patch is 05b764d93b9a50400f523206fbe03d73d0cf5edb. The affected component should be upgraded.

Weakness: CWE-470 (Use of Externally-Controlled Input to Select Classes or Code)

## Which versions are affected by CVE-2026-126994?

An affected version is only exploitable if your software calls resolve_type_kwargs. Many projects that include it are not exposed.


## How do I fix CVE-2026-126994?

No fix has been published for CVE-2026-126994 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126994 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-126994 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126994 and fix it if it is affected.

What it is: CVE-2026-126994 is a medium-severity code injection vulnerability in braindecode, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-126994 exists.
Exposure: An affected version is only exploitable if your software calls resolve_type_kwargs. Many projects that include it are not exposed.

Affected product: braindecode. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
   If an affected version is present, also search the code for calls to resolve_type_kwargs and report whether any exist.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126994/ (Markdown: https://insights.sbomify.com/CVE-2026-126994/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126994
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126994
- OSV: https://osv.dev/vulnerability/CVE-2026-126994

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126994/
Summaries are generated and may contain mistakes; the official description above is the record.
