Why do AI ETL libraries create such high lateral movement risk?

AI ETL libraries often run inside privileged service contexts that can read documents, reach storage, and call downstream APIs. If that workload is compromised, the attacker inherits the same non-human identity and can move from file handling into secrets access, data exfiltration, or adjacent service abuse. The issue is the runtime privilege set, not just the parser bug.