Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

How a low-privileged account turns an XML configuration upload into arbitrary file read, user impersonation, and remote code execution — and how to detect and stop it. Published 16 June 2026 · Fact-checked against the official project advisory and government vulnerability databases.

AI agents now write code, fix bugs, and ship to production. But in order to do useful work, agents require credentials. At 1Password, one of our core AI security principles is that raw credentials should never be directly exposed to LLMs, but all too often, that’s exactly what happens: most teams sacrifice security for speed and hand agents secrets in plaintext.

2026 is the year agent harnesses go to production. The software that controls the model’s access to the outside world — harnesses like Codex, Claude Code, OpenCode, Pi, and Project Think — has matured to the point where teams are deploying agents as real, load-bearing infrastructure, not just prototypes. But building agents that survive production is hard.

Adopting or migrating to a Zero Trust network architecture can be a daunting task. Before a single policy changes, teams have to recall how their network is actually built: which applications exist, their authentication and authorization constructs, how traffic flows between them, and any assumptions the current architecture makes. This hands-on process requires practitioners to decode the intent behind every security and routing policy in place.

Every piece of data your organization stores lives in a specific server, facility, and country. Data residency refers to where that data physically sits, and governments increasingly care about the answer. The EU, India, Brazil, and dozens of other jurisdictions now enforce strict rules about storage locations. Get it wrong, and you’re looking at regulatory fines, lost contracts, or both.