Display Settings:

Format

Send to:

Choose Destination
Free Radic Biol Med. 2006 Feb 1;40(3):420-9. Epub 2005 Nov 10.

Nimesulide-induced hepatic mitochondrial injury in heterozygous Sod2(+/-) mice.

Author information

  • 1Department of Pharmacology, Yong Loo Lin School of Medicine, National University of Singapore, Singapore.

Abstract

Nimesulide, a preferential COX-2 inhibitor, has been associated with rare idiosyncratic hepatotoxicity. The underlying mechanisms of liver injury are unknown, but experimental evidence has identified oxidative stress as a potential hazard and mitochondria as a target. The aim of this study was to explore whether genetic mitochondrial abnormalities, resulting in impaired mitochondrial function and mildly increased oxidative stress, might sensitize mice to the hepatic adverse effects of nimesulide. We used heterozygous superoxide dismutase 2 (Sod2(+/-)) mice as a model, as these mice develop clinically silent mitochondrial stress but otherwise appear normal. Nimesulide was administered for 4 weeks (10 mg/kg, ip, bid), at a dose equivalent to human therapeutic dosage. We found that the drug potentiated hepatic mitochondrial oxidative injury (decreased aconitase activity, increased protein carbonyls) in Sod2(+/-), but not wild-type, mice. Furthermore, the nimesulide-treated mutant mice exhibited increased hepatic cytosolic levels of cytochrome c and caspase-3 activity, as well as increased numbers of apoptotic hepatocytes. Finally, nimesulide in vitro caused a concentration-dependent net increase in superoxide anion in mitochondria from Sod2(+/-), but not Sod2(+/+) mice. In conclusion, repeated administration of nimesulide can superimpose an oxidant stress, potentiate mitochondrial damage, and activate proapoptotic factors in mice with genetically compromised mitochondrial function.

PMID:
16443156
[PubMed - indexed for MEDLINE]
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for Elsevier Science
    Loading ...
    Write to the Help Desk