Side Effects of Erasing Concepts from Diffusion Models

Shaswati Saha, Sourajit Saha, Manas Gaur, Tejas Gokhale
8/20/2025
cs.LGcs.CV

No official code found. Best implementation: shaswati1/see (3 stars, last commit 2026-03-22).

Abstract

Concerns about text-to-image (T2I) generative models infringing on privacy, copyright, and safety have led to the development of concept erasure techniques (CETs). The goal of an effective CET is to prohibit the generation of undesired "target" concepts specified by the user, while preserving the ability to synthesize high-quality images of other concepts. In this work, we demonstrate that concept erasure has side effects and CETs can be easily circumvented. For a comprehensive measurement of the robustness of CETs, we present the Side Effect Evaluation (SEE) benchmark that consists of hierarchical and compositional prompts describing objects and their attributes. The dataset and an automated evaluation pipeline quantify side effects of CETs across three aspects: impact on neighboring concepts, evasion of targets, and attribute leakage. Our experiments reveal that CETs can be circumvented by using superclass-subclass hierarchy, semantically similar prompts, and compositional variants of the target. We show that CETs suffer from attribute leakage and a counterintuitive phenomenon of attention concentration or dispersal. We release our benchmark and evaluation tools to aid future work on robust concept erasure.

View on arXivView PDF

Code Implementations(1)

shaswati1/seeCommunity67%

[EMNLP 2025, Findings] Side Effects of Erasing Concepts from Diffusion Models

30PythonAug 24, 20257 months ago

Similar Papers

Cite this paper

@article{saha2025side,
  title  = {Side Effects of Erasing Concepts from Diffusion Models},
  author = {Shaswati Saha and Sourajit Saha and Manas Gaur and Tejas Gokhale},
  year   = {2025},
  eprint = {2508.15124},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2508.15124v3}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2508.15124.svg)](https://codeofpaper.com/paper/2508.15124)

Discussion