chore(deps): bump cryptography from 46.0.3 to 50.0.0 in /02-use-cases/02-workflow-automation-agents/intelligent-event-agent

[dependabot]

Bumps cryptography from 46.0.3 to 50.0.0.

Changelog

Sourced from cryptography's changelog.

50.0.0 - 2026-07-31

* **SECURITY ISSUE**:
  :func:`~cryptography.hazmat.primitives.serialization.pkcs7.pkcs7_decrypt_der`
  and its PEM and S/MIME variants no longer expose distinguishable errors or
  timing when unwrapping a ``RecipientInfo``'s ``encryptedKey``, which could
  act as a Bleichenbacher oracle for callers that decrypt untrusted messages.
  A random key is now substituted on failure, as described in :rfc:`3218`.
  Credit to **@X1AOxiang** for reporting the issue. **CVE-2026-69247**
* Deprecated Diffie-Hellman key exchange over finite fields (FFDH).
  Everything FFDH is deprecated, including the types in
  ``cryptography.hazmat.primitives.asymmetric.dh`` and loading FFDH keys or
  parameters with the key loading APIs. Users should migrate to a more
  modern key exchange algorithm.
* Added ``xof()`` class methods to
  :class:`~cryptography.hazmat.primitives.hashes.SHAKE128` and
  :class:`~cryptography.hazmat.primitives.hashes.SHAKE256` for constructing
  algorithm instances configured for use with
  :class:`~cryptography.hazmat.primitives.hashes.XOFHash`.
* The :mod:`X.509 verification <cryptography.x509.verification>` APIs are now
  considered stable and are subject to our API stability policy.
* Added the :doc:`/cobblestone` recipe, an implementation of the
  Cobblestone-128 and Cobblestone-256 instantiations of the `C2SP
  chunked-encryption specification
  <https://c2sp.org/chunked-encryption>`_ for streaming authenticated
  encryption of large messages.
* Parsing a Signed Certificate Timestamp list now rejects encodings that
  carry trailing bytes after the list or after an individual SCT, instead of
  silently ignoring them.
* Added support for using :class:`~cryptography.x509.Name` as a field type in
  the :doc:`/hazmat/asn1/index` module.
* Loading a public key or an EC private key now rejects DER where the
  ``subjectPublicKey`` (or EC ``publicKey``) ``BIT STRING`` declares a non-zero
  number of unused bits, instead of silently ignoring it.
* Parsing a CRL entry's ``InvalidityDate`` extension now rejects a
  ``GeneralizedTime`` that carries fractional seconds or another non-DER form,
  matching the strict encoding already required for every other X.509 time
  field.
* :func:`~cryptography.x509.ocsp.load_der_ocsp_request` and
  :func:`~cryptography.x509.ocsp.load_der_ocsp_response` now reject a request
  or response whose ``version`` field is not ``v1``, the only version defined
  by RFC 6960, matching the version validation already performed when loading
  certificates, CSRs and CRLs.
* :class:`~cryptography.hazmat.primitives.hashes.XOFHash` is now supported
  when building against AWS-LC.
* HMAC (and therefore PBKDF2-HMAC) with SHA-3 hashes is now supported when
  building against AWS-LC.
* Diffie-Hellman (:doc:`/hazmat/primitives/asymmetric/dh`) is now supported
  when building against AWS-LC.
</tr></table> 

... (truncated)

Commits

• dcb7050 Prepare for 50.0.0 release (#15372)
• 53fccd9 Don't leak how PKCS#7 encryptedKey decryption failed (#15369)
• d472f97 Add from __future__ import annotations to all src/ Python files (#15371)
• 908773d Bump downstream dependencies in CI (#15368)
• 2cc07cc Bump BoringSSL, OpenSSL, AWS-LC in CI (#15367)
• c94ede9 chore(deps): bump ruff from 0.16.0 to 0.16.1 (#15366)
• 67a8308 chore(deps): bump virtualenv from 21.7.0 to 21.7.1 (#15365)
• 95018ff Release the GIL in one-shot AEAD encrypt/decrypt (#15361)
• 6954733 Release the GIL during DH and DSA parameter generation (#15364)
• 6893b94 Import _serialization instead of serialization in x509/extensions (#15363)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[github-actions]

Latest scan for commit: 5de681f | Updated: 2026-08-04 19:06:04 UTC

Security Scan Results

Scan Metadata

• Project: ASH
• Scan executed: 2026-08-04T19:04:53+00:00
• ASH version: 3.0.0

Summary

Scanner Results

The table below shows findings by scanner, with status based on severity thresholds and dependencies:

Column Explanations:

Severity Levels (S/C/H/M/L/I):

• Suppressed (S): Security findings that have been explicitly suppressed/ignored and don't affect the scanner's pass/fail status
• Critical (C): The most severe security vulnerabilities requiring immediate remediation (e.g., SQL injection, remote code execution)
• High (H): Serious security vulnerabilities that should be addressed promptly (e.g., authentication bypasses, privilege escalation)
• Medium (M): Moderate security risks that should be addressed in normal development cycles (e.g., weak encryption, input validation issues)
• Low (L): Minor security concerns with limited impact (e.g., information disclosure, weak recommendations)
• Info (I): Informational findings for awareness with minimal security risk (e.g., code quality suggestions, best practice recommendations)

Other Columns:

• Time: Duration taken by each scanner to complete its analysis
• Action: Total number of actionable findings at or above the configured severity threshold that require attention

Scanner Results:

• PASSED: Scanner found no security issues at or above the configured severity threshold - code is clean for this scanner
• FAILED: Scanner found security vulnerabilities at or above the threshold that require attention and remediation
• MISSING: Scanner could not run because required dependencies/tools are not installed or available
• SKIPPED: Scanner was intentionally disabled or excluded from this scan
• ERROR: Scanner encountered an execution error and could not complete successfully

Severity Thresholds (Thresh Column):

• CRITICAL: Only Critical severity findings cause scanner to fail
• HIGH: High and Critical severity findings cause scanner to fail
• MEDIUM (MED): Medium, High, and Critical severity findings cause scanner to fail
• LOW: Low, Medium, High, and Critical severity findings cause scanner to fail
• ALL: Any finding of any severity level causes scanner to fail

Threshold Source: Values in parentheses indicate where the threshold is configured:

• (g) = global: Set in the global_settings section of ASH configuration
• (c) = config: Set in the individual scanner configuration section
• (s) = scanner: Default threshold built into the scanner itself

Statistics calculation:

• All statistics are calculated from the final aggregated SARIF report
• Suppressed findings are counted separately and do not contribute to actionable findings
• Scanner status is determined by comparing actionable findings to the threshold

Scanner	S	C	H	M	L	I	Time	Action	Result	Thresh
bandit	0	0	0	0	0	0	452ms	0	PASSED	MED (g)
cdk-nag	0	0	0	0	0	0	5.0s	0	PASSED	MED (g)
cfn-nag	0	0	0	0	0	0	8ms	0	PASSED	MED (g)
checkov	0	0	0	0	0	0	4.0s	0	PASSED	MED (g)
detect-secrets	0	0	0	0	0	0	811ms	0	PASSED	MED (g)
grype	0	3	0	3	1	0	59.6s	6	FAILED	MED (g)
npm-audit	0	0	0	0	0	0	171ms	0	PASSED	MED (g)
opengrep	0	0	0	0	0	0	<1ms	0	SKIPPED	MED (g)
semgrep	0	0	0	0	0	0	<1ms	0	MISSING	MED (g)
syft	0	0	0	0	0	0	1.9s	0	PASSED	MED (g)

Detailed Findings

Show 6 actionable findings

Finding 1: GHSA-xgmm-8j9v-c9wx-pyjwt

• Severity: HIGH
• Scanner: grype
• Rule ID: GHSA-xgmm-8j9v-c9wx-pyjwt
• Location: 02-use-cases/02-workflow-automation-agents/intelligent-event-agent/requirements.txt:1

Description:
A high vulnerability in python package: pyjwt, version 2.10.1 was found at: /02-use-cases/02-workflow-automation-agents/intelligent-event-agent/requirements.txt

---

Finding 2: GHSA-j6g5-3hh3-pgw8-bedrock-agentcore

• Severity: HIGH
• Scanner: grype
• Rule ID: GHSA-j6g5-3hh3-pgw8-bedrock-agentcore
• Location: 02-use-cases/02-workflow-automation-agents/intelligent-event-agent/requirements.txt:1

Description:
A high vulnerability in python package: bedrock-agentcore, version 1.0.6 was found at: /02-use-cases/02-workflow-automation-agents/intelligent-event-agent/requirements.txt

---

Finding 3: GHSA-752w-5fwx-jx9f-pyjwt

• Severity: HIGH
• Scanner: grype
• Rule ID: GHSA-752w-5fwx-jx9f-pyjwt
• Location: 02-use-cases/02-workflow-automation-agents/intelligent-event-agent/requirements.txt:1

Description:
A high vulnerability in python package: pyjwt, version 2.10.1 was found at: /02-use-cases/02-workflow-automation-agents/intelligent-event-agent/requirements.txt

---

Finding 4: GHSA-w7vc-732c-9m39-pyjwt

• Severity: MEDIUM
• Scanner: grype
• Rule ID: GHSA-w7vc-732c-9m39-pyjwt
• Location: 02-use-cases/02-workflow-automation-agents/intelligent-event-agent/requirements.txt:1

Description:
A medium vulnerability in python package: pyjwt, version 2.10.1 was found at: /02-use-cases/02-workflow-automation-agents/intelligent-event-agent/requirements.txt

---

Finding 5: GHSA-993g-76c3-p5m4-pyjwt

• Severity: MEDIUM
• Scanner: grype
• Rule ID: GHSA-993g-76c3-p5m4-pyjwt
• Location: 02-use-cases/02-workflow-automation-agents/intelligent-event-agent/requirements.txt:1

Description:
A medium vulnerability in python package: pyjwt, version 2.10.1 was found at: /02-use-cases/02-workflow-automation-agents/intelligent-event-agent/requirements.txt

---

Finding 6: GHSA-jq35-7prp-9v3f-pyjwt

• Severity: MEDIUM
• Scanner: grype
• Rule ID: GHSA-jq35-7prp-9v3f-pyjwt
• Location: 02-use-cases/02-workflow-automation-agents/intelligent-event-agent/requirements.txt:1

Description:
A medium vulnerability in python package: pyjwt, version 2.10.1 was found at: /02-use-cases/02-workflow-automation-agents/intelligent-event-agent/requirements.txt

---

Report generated by Automated Security Helper (ASH) at 2026-08-04T19:04:48+00:00