CVE-2026-7669
Last modified
CVE-2026-7669 is a medium-severity vulnerability rated 6.3/10 on the CVSS scale. 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. EPSS estimates a 0.37% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-7669?
How severe is CVE-2026-7669?
How do I fix CVE-2026-7669?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-7663IBM Langflow OSS 1.0.0 through 1.9.6 could allow unauthentic…9.8
- CVE-2026-7664IBM Langflow OSS 1.0.0 through 1.8.4 could allow unauthentic…9.8
- CVE-2026-7665The Essential Addons for Elementor – Popular Elementor Templ…5.3
- CVE-2026-7666An issue was discovered in Django 6.0 before 6.0.6 and 5.2 b…3.1
- CVE-2026-7667IBM Langflow OSS 1.0.0 through 1.10.0 allows an authenticate…8.8
- CVE-2026-7668A vulnerability was identified in MikroTik RouterOS 6.49.8. …7.3
- CVE-2026-7670A flaw has been found in Jinher OA 1.0. The affected element…7.3
- CVE-2026-7671A vulnerability has been found in CodeWise Tornet Scooter Mo…3.7
- CVE-2026-7672A security vulnerability has been detected in youlaitech you…6.3
- CVE-2026-7673A vulnerability was detected in crmeb_java up to 1.3.4. This…4.7
- CVE-2026-7674A flaw has been found in Shenzhen Libituo Technology LBT-T30…8.8
- CVE-2026-7675A vulnerability has been found in Shenzhen Libituo Technolog…8.8
Are you affected by CVE-2026-7669?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
