Iron(II)-Activatable Conjugates Enable Tumor-Conditional Release of the HDAC Inhibitor Panobinostat

HDAC inhibitorsdrug conjugatespanobinostattumor-conditional activationgenotoxicity mitigationmultiple myeloma
  • Hydroxamic acid-based HDAC inhibitors are limited by poor selectivity among metalloenzymes and by genotoxicity risk linked to isocyanate metabolites.
  • The study applies a previously reported iron(II)-activatable conjugate platform to cage the pan-HDAC inhibitor panobinostat, aiming for tumor-conditional payload release.
  • In multiple myeloma cell line models, the conjugate successfully caged HDAC inhibitory activity, and a bioisosteric control conjugate showed reduced genotoxicity relative to the free hydroxamate.
  • Follow-up investigation identified the carboxylesterase CES1 as responsible for unexpected proteolytic instability of the panobinostat conjugate observed both in vitro and in vivo.
  • The finding is noted as a focus for future work toward mitigating hydroxamate-associated toxicity and mutagenicity through more robust tumor-conditional activation.
💡 Points

Caging panobinostat's hydroxamate behind an Fe(II) trigger is a sensible fix for the isocyanate-genotoxicity liability that's dogged this chemotype, and the bioisosteric control actually showing lower genotoxicity than free drug is the kind of data I'd want before calling any HDACi "safer." But what grabs me is the CES1 finding: an esterase chewing through the conjugate in vitro and in vivo is the failure mode a clean MM cell assay never warns you about. That's not a footnote — it's the design problem for the next iteration, whether you engineer around the CES1 recognition motif or add orthogonal masking. I'd rather see this reported now than discovered in an IND package; it's a useful cautionary data point for anyone building Fe(II)-activatable payloads beyond this one hydroxamate.

Toward Tumor-Conditional Release of Histone Deacetylase Inhibitors from Nongenotoxic Drug Conjugates ↗

← Back to archive