# CVE-2026-7669: sgl-project SGLang HuggingFace Transformer hf_transformers_utils.py get_tokenizer code injection

> Attackers can execute arbitrary Python code by exploiting a trust_remote_code override in SGLang's tokenizer loading logic.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-6m5f-673f-5vh7, PYSEC-2026-3062

## What is CVE-2026-7669?

CVE-2026-7669 is a medium-severity code injection vulnerability in sgl-project SGLang, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was detected in sgl-project SGLang up to 0.5.9. Impacted is the function get_tokenizer of the file python/sglang/srt/utils/hf_transformers_utils.py of the component HuggingFace Transformer Handler. The manipulation of the argument trust_remote_code with the input False as part of Boolean results in code injection. The attack can be executed remotely. A high complexity level is associated with this attack. The exploitability is considered difficult. In get_tokenizer(), when the caller passes trust_remote_code=False and HuggingFace transformers v5 returns a TokenizersBackend instance (the generic fallback for tokenizer classes not in the registry), SGLang silently re-invokes AutoTokenizer.from_pretrained with trust_remote_code=True, overriding the caller's explicit security setting. A model repository containing a malicious tokenizer.py referenced via auto_map in tokenizer_config.json will execute arbitrary Python in the SGLang process during this second call. No log line or warning is emitted. The override affects all current SGLang versions because transformers==5.3.0 is pinned in pyproject.toml. Both tokenizer_mode="auto" and tokenizer_mode="slow" are affected. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

3 open source packages ship an affected version, including sglang.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sglang` | PyPI | All versions to 0.5.9 | None |
| `sglang` | PyPI | All versions to 0.5.9 | None |
| `sglang` | PyPI | All versions to 0.5.9 | None |

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

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

## Is CVE-2026-7669 being exploited?

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

Public exploit code:

- PoC for CVE-2026-7669: SGLang silent trust_remote_code override -> RCE (github_poc): https://github.com/gouldnicholas/CVE-2026-7669-PoC

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7669 is a medium-severity code injection vulnerability in sgl-project SGLang, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7669 exists.

Affected packages and fixed versions:
- sglang (PyPI): affected all versions up to 0.5.9; no fix listed
- sglang (PyPI): affected all versions up to 0.5.9; no fix listed
- sglang (PyPI): affected all versions up to 0.5.9; no fix listed

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-7669/ (Markdown: https://insights.sbomify.com/CVE-2026-7669/index.md)
```

## Sources

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

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