TSR Desk · science · 12 September 2026, 01:00 UTC
CS-Guard: Benchmarking LLM Guardrails for Code Generation Security
- What
- CS-Guard: Benchmarking LLM Guardrails for Code Generation Security
- Who
- arxiv.org
- When
- 11 September 2026, 04:00 UTC
- Category
- Science
- Primary source
- https://arxiv.org/abs/2609.09798
- What is not known
- This brief does not claim independent replication. Claims that appear only on X and not in the primary source stay unknown.
We introduce CS-Guard, the first benchmark to systematically evalu- ate guardrails for code generation security. It comes from a paper posted to arXiv on 11 September 2026. Large language models (LLMs) have been ex- ploited to generate malware, but the effective- ness of guardrails for code generation secu- rity remains unclear. It covers 1) text-to-code generation with 1000 high-quality malware-generation prompts, 7 jailbreak attacks, and a novel fictional scenario attack (FSA) that embeds malicious intent in a legitimate fictional software-development sce- nario; and 2) code-to-code generation with 331 code prompts spanning code infilling, code completion, and code translation. We empiri- cally evaluate 9 guardrails across seven LLMs. We find that current guardrails perform poorly against malicious code-generation re- quests: for text-to-code, the average attack success rate (ASR) after jailbreaks reaches about 50% for many guardrails; for code-to- code, average ASR approaches 100% on base LLMs and remains high across many guardrails (14.4% to nearly 100%). Our FSA also achieves ASR close to 100% across many guardrails, raising major reliability concerns for real-world software development. To sup- port future research, CS-Guard uses a modular three-layer guardrail taxonomy that lets devel- opers register guardrails for evaluation. We release the benchmark and data to enable fur- ther community evaluation.
Why it counts
We introduce CS-Guard, the first benchmark to systematically evalu- ate guardrails for code generation security.
Sources
Primary source: primary source
What is not known
This brief does not claim independent replication. Claims that appear only on X and not in the primary source stay unknown.
No clip. The article still stands.