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.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
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.
Which versions are affected by CVE-2026-7669?
3 open source packages ship an affected version, including sglang.
| Package | 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.
Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.
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: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-6m5f-673f-5vh7, PYSEC-2026-3062.