[dependabot]

Bumps the cargo group with 1 update in the / directory: rustls-webpki.

Updates rustls-webpki from 0.103.9 to 0.103.10

Release notes

Sourced from rustls-webpki's releases.

0.103.10

Correct selection of candidate CRLs by Distribution Point and Issuing Distribution Point. If a certificate had more than one distributionPoint, then only the first distributionPoint would be considered against each CRL's IssuingDistributionPoint distributionPoint, and then the certificate's subsequent distributionPoints would be ignored.

The impact was that correct provided CRLs would not be consulted to check revocation. With UnknownStatusPolicy::Deny (the default) this would lead to incorrect but safe Error::UnknownRevocationStatus. With UnknownStatusPolicy::Allow this would lead to inappropriate acceptance of revoked certificates.

This vulnerability is thought to be of limited impact. This is because both the certificate and CRL are signed -- an attacker would need to compromise a trusted issuing authority to trigger this bug. An attacker with such capabilities could likely bypass revocation checking through other more impactful means (such as publishing a valid, empty CRL.)

More likely, this bug would be latent in normal use, and an attacker could leverage faulty revocation checking to continue using a revoked credential.

This vulnerability is identified by GHSA-pwjx-qhcg-rvj4. Thank you to @​1seal for the report.

What's Changed

• Freshen up rel-0.103 by @​ctz in rustls/webpki#455
• Prepare 0.103.10 by @​ctz in rustls/webpki#458

Full Changelog: rustls/webpki@v/0.103.9...v/0.103.10

Commits

• 348ce01 Prepare 0.103.10
• dbde592 crl: fix authoritative_for() support for multiple URIs
• 9c4838e avoid std::prelude imports
• 009ef66 fix rust 1.94 ambiguous panic macro warnings
• c41360d build(deps): bump taiki-e/cache-cargo-install-action from 2 to 3
• e401d00 generate.py: reformat for black 2026.1.0
• 06cedec Take semver-compatible deps
• See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[codspeed]

Merging this PR will not alter performance

✅ 21 untouched benchmarks

---

_{Comparing dependabot/cargo/cargo-64b2a50fd2 (01f163b) with main (768a49a)}

[penso]

Summary

Approve. This PR is a lockfile-only Dependabot update that bumps indirect rustls-webpki from 0.103.9 to 0.103.10 in Cargo.lock, with no tracked source or manifest changes.

I sanity-checked the lockfile with cargo metadata --locked --offline --no-deps, which succeeded.

Risks

• The lockfile refresh also re-resolves graphql_client_codegen and snafu-derive from heck 0.5.0 to heck 0.4.1. That is broader than a pure checksum bump, but the practical risk looks low here: Arbor's GraphQL codegen inputs are GraphQL identifiers (ASCII by spec), and there are no direct in-tree Snafu derives.
• I could not do a full offline graph/build check because rustls-webpki v0.103.10 is not cached locally.

Required fixes

None.

Optional improvements

• Rebase onto current main and regenerate Cargo.lock if you want the diff to stay narrowly scoped and avoid unrelated resolver churn.