# CVE-2026-115802: InternScience InternAgent LoRA Loading experiment.py train inclusion of functionality from untrusted control sphere


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-cgw3-x9m5-7cc6

## What is CVE-2026-115802?

CVE-2026-115802 is a medium-severity vulnerability in InternScience InternAgent, published on 24 Oct 2026. 

### Official description

A weakness has been identified in InternScience InternAgent 1.5.0. This affects the function train of the file tasks/AutoChem/code/experiment.py of the component LoRA Loading. This manipulation of the argument base_model_name_or_path causes inclusion of functionality from untrusted control sphere. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

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

## Is CVE-2026-115802 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115802 is a medium-severity vulnerability in InternScience InternAgent, published on 24 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115802 exists.

Affected product: InternScience InternAgent. 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.
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-115802/ (Markdown: https://insights.sbomify.com/CVE-2026-115802/index.md)
```

## Sources

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

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