Skip to main content
LLM Security Database
Skip to research details
Back to research findings
LMVD-ID: eae1e2e8
Paper published April 1, 2025
Entry analyzed April 21, 2025
Paper-reported evidence
Confidence: Source-linked

The LMVD-ID is an internal research identifier, not an official CVE identifier.

LLM Guardrail Evasion

Large Language Model (LLM) guardrail systems, including those relying on AI-driven text classification models (e.g., fine-tuned BERT models), are vulnerable to evasion via character injection and adversarial machine…

BibTeX citation

Paper-evaluated models(3)

  • DeBERTa v3 Base
  • GPT-4o Mini
  • mDeBERTa v3 Base

Description

Large Language Model (LLM) guardrail systems, including those relying on AI-driven text classification models (e.g., fine-tuned BERT models), are vulnerable to evasion via character injection and adversarial machine learning (AML) techniques. Attackers can bypass detection by injecting Unicode characters (e.g., zero-width characters, homoglyphs) or using AML to subtly perturb prompts, maintaining semantic meaning while evading classification. This allows malicious prompts and jailbreaks to reach the underlying LLM.

Examples

  • Character Injection: Injecting "zero-width space" characters into a prompt ("Hel‌lo").
  • AML Evasion: Substituting words with semantically similar synonyms to alter word embeddings and evade detection. Specific examples of successful evasion using various AML methods against multiple guardrails are detailed in the referenced paper. See arXiv:2504.11168 (opens in a new tab).

Impact

Successful evasion of LLM guardrails allows attackers to execute malicious prompts (prompt injection) or bypass safety constraints (jailbreak), leading to unintended LLM behavior, data leakage, or the generation of harmful content.

Affected Systems

Large Language Models protected by various guardrail systems, including (but not limited to) Microsoft Azure Prompt Shield, Meta Prompt Guard, ProtectAI Prompt Injection Detection v1 & v2, NeMo Guard Jailbreak Detect, and Vijil Prompt Injection. The vulnerability is likely present in other LLM guardrails relying on similar AI-based detection mechanisms.

Mitigation Steps

  • Enhance training data used in LLM guardrails to include a wider variety of adversarial attacks, including character injection and AML-generated examples.
  • Develop more robust detection models that are less susceptible to adversarial perturbations and character obfuscation.
  • Implement multiple layers of defense, combining AI-based detection with rule-based filters and other security mechanisms.
  • Regularly update and retrain guardrail models to adapt to evolving attack strategies.
  • Consider incorporating techniques to detect and mitigate the impact of character injection and word manipulation attempts.

Research context and confidence

Evidence and verification
Paper-reported; independent reproduction is not documented.
Primary research source linked.
Severity
Not rated by this catalog.
Source and publication type
arXiv · Research preprint.
Peer-review status is not provided by this source.
Author and publication status
Author metadata is not stored; see the primary paper.
Threat model and attacker access
Both white-box and black-box research contexts are tagged; consult the primary paper for target-specific access.
Related deployment categories
No related deployment category is classified.
Taxonomy labels only; paper-specific deployment prerequisites are not inferred.
Affected systems
Large Language Models protected by various guardrail systems, including (but not limited to) Microsoft Azure Prompt Shield, Meta Prompt Guard, ProtectAI Prompt Injection Detection v1 & v2, NeMo Guard Jailbreak Detect…

Research Paper

Bypassing Prompt Injection and Jailbreak Detection in LLM Guardrails

Primary source: arXiv. Findings are reported by the cited research and have not been independently verified.

View Paper

Evidence

This entry is based on a primary research source. Its findings are paper-reported; independent reproduction and verification are not claimed.

https://arxiv.org/abs/2504.11168