fix(deps): vuln major: cffi, cryptography, pycparser [tests/authorization]

[gh-worker-campaigns-3e9aa4]

Summary: High-severity security update — 3 packages upgraded (MAJOR changes included)

Manifests changed:

• tests/authorization (pip)

---

✅ Action Required: Please review the changes below. If they look good, approve and merge this PR.

---

Updates

Package	From	To	Type	Dep Type	Vulnerabilities Fixed
cryptography	44.0.1	49.0.0	major	Direct	3 HIGH, 3 LOW
cffi	1.15.1	2.0.0	major	Direct	-
pycparser	2.21	3.0	major	Direct	-

---

Warning

Major Version Upgrade

This update includes major version changes that may contain breaking changes. Please:

• Review the changelog/release notes for breaking changes
• Test thoroughly in a staging environment
• Update any code that depends on changed APIs
• Ensure all tests pass before merging

Security Details

🚨 Critical & High Severity (3 fixed)

Package	CVE	Severity	Summary	Unsafe Version	Fixed In	Case
cryptography	GHSA-r6ph-v2qm-q3c2	HIGH	cryptography Vulnerable to a Subgroup Attack Due to Missing Subgroup Validation for SECT Curves	44.0.1	46.0.5	-
cryptography	CVE-2026-26007	HIGH	cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves	44.0.1	-	-
cryptography	GHSA-537c-gmf6-5ccf	HIGH	Vulnerable OpenSSL included in cryptography wheels	44.0.1	48.0.1	-

ℹ️ Other Vulnerabilities (3)

Package	CVE	Severity	Summary	Unsafe Version	Fixed In	Case
cryptography	PYSEC-2026-35	low	-	44.0.1	46.0.6	-
cryptography	CVE-2026-34073	low	cryptography has incomplete DNS name constraint enforcement on peer names	44.0.1	-	-
cryptography	GHSA-m959-cc7f-wv43	LOW	cryptography has incomplete DNS name constraint enforcement on peer names	44.0.1	46.0.6	-

⚠️ Dependencies that have Reached EOL (2)

Dependency	Unsafe Version	EOL Date	New Version	Path
cryptography	44.0.1	-	49.0.0	tests/authorization/requirements.txt
pycparser	2.21	-	3.0	tests/authorization/requirements.txt

---

Review Checklist

Extra review is recommended for this update:

• Review changes for compatibility with your code
• Check release notes for breaking changes
• Run integration tests to verify service behavior
• Test in staging environment before production
• Monitor key metrics after deployment
• Approve and merge this PR

---

Update Mode: all_vulns

🤖 Generated by DataDog Automated Dependency Management System