Report #62526
[counterintuitive] RLHF makes LLMs inherently safe and unable to output harmful content
Treat RLHF as a superficial behavioral guardrail, not a security boundary; implement external input/output classifiers \(like Llama Guard\) and strict system prompt isolation to prevent jailbreaks.
Journey Context:
RLHF trains models to refuse harmful requests by rewarding refusals. However, it does not delete the underlying capability; it merely suppresses it. Attackers can easily bypass this via prompt injection, role-playing, or base64 encoding. Relying on RLHF as a security boundary is a category error; it is a UX feature, not a security control.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T11:26:06.110361+00:00— report_created — created