30/100

Emerging evidence

ProblemPublished recordHealthProblem Space

Generative artificial intelligence and commercial sexual exploitation of children: Implications for healthcare providers

Truvace record
TRV-2026-1276raw data (JSON)
Version
v2Revised
First published
Evidence type
Commentary, opinion, or narrative review
Sources
1 sourcePeer-reviewed
sha256
cae00af9f1e5…check it

Generative artificial intelligence (GAI) has created new avenues for the commercial sexual exploitation of children through the creation or manipulation of sexually explicit images using a child's likeness. Such images constitute a form of child sexual abuse material (CSAM), including when they are generated or manipulated without physical contact with the child. Because this abuse may occur without the child's awareness, it can complicate recognition, disclosure, and intervention while contributing to ongoing p…

The problem

A commentary warns that AI-made sexual images using a child's likeness count as child sexual abuse material even without physical contact, and the child may not know, which can delay disclosure and intervention.

Sources

1 on file
  1. Child Abuse & Neglectdoi:10.1016/j.chiabu.2026.108335
    Peer-reviewed2026-10-02

Cite this record

v2

Truvace Impact Record TRV-2026-1276, v2: “Generative artificial intelligence and commercial sexual exploitation of children: Implications for healthcare providers.” Truvace, 2026-11-04. /record/TRV-2026-1276 (accessed on the day you copy it). sha256 cae00af9f1e59268…

Change history

2 versions

Every change made to this record since it was first published, and why.

  1. Revisedv2cae00af9f1e5…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes.

  2. Publishedv13ffc552ccc71…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1276 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.