Possible fix(deps): cryptography 49.0.0 → 50.0.0 (CVE-2026-69247) in uv.lock

This might be a false positive, but `uv.lock` around line 1 looked worth a second pair of eyes.

The project pins cryptography==49.0.0, which is vulnerable to CVE-2026-69247. The flaw allows a Bleichenbacher‑style oracle on RSA PKCS#1 v1.5 decryption of EnvelopedData, enabling attackers to recover the content‑encryption key in services that automatically process untrusted S/MIME messages (e.g., mail gateways). This can lead to full decryption of confidential data. The vulnerability is rated HIGH. Upgrade to cryptography>=50.0.0, where the oracle is removed.

Something like this might fix it:

```
*** Begin Patch
*** Update File: uv.lock
@@
- "cryptography": {
- "version": "49.0.0",
- "hashes": [
- "sha256:..."
- ]
- },
+ "cryptography": {
+ "version": "50.0.0",
+ "hashes": [
+ "sha256:..." # replace with the actual hash for 50.0.0 provided by the lock file generator
+ ]
+ },
*** End Patch
```

For reference: rule `CVE-2026-69247`. Rated high.

I do not maintain this project, so I may well be missing context — if this is intentional or already handled elsewhere, please just close it.

---
*Found with automated scanning ([RedGem](https://code.redgem.net)) and reviewed before opening. If it is not useful, closing it is completely fine.*