fix(security): patch sandbox Pillow

[0xjohnnydev]

Problem

The cua-sandbox Python lockfile still resolves vulnerable aiohttp, cryptography, and Pillow releases.

What changed

• Updated aiohttp to 3.14.3.
• Updated cryptography to 50.0.0.
• Kept Pillow at 12.3.0.
• This draft covers current alerts Linux VMs suffer filesystem corruption due to default disk caching mode #1099–lume pull skips multi-part tar layers, fails to assemble disk image #1102 and the earlier sandbox Pillow alerts.
• The root, Cua Bench, and sandbox-apps lock graphs remain separate.

Definition of Done

• The current sandbox aiohttp and cryptography alerts are mapped to this focused draft.
• The lockfile resolves aiohttp 3.14.3, cryptography 50.0.0, and Pillow 12.3.0.
• The lockfile passes uv consistency validation.
• A maintainer reviews and advances this draft; automation will not mark it ready or merge it.
• GitHub closes the alerts after the reviewed fix reaches the default branch.

Validation

• uv lock --upgrade-package aiohttp==3.14.3 --upgrade-package cryptography==50.0.0 --upgrade-package Pillow==12.3.0 in libs/python/cua-sandbox.
• uv lock --check.
• git diff --check.

Impact

This changes only the cua-sandbox dependency lockfile. No VM, installation, or live runtime proof was run on the host.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[0xjohnnydev]

This draft is now included in the consolidated Python security draft #2719. #2719 contains the sandbox lockfile fix together with the matching root, Cua Bench, and sandbox-apps Python updates, checks each lock graph separately, and remains a draft for human review. Closing this copy reduces duplicate review; nothing was merged automatically.