build(deps): bump rustls-webpki from 0.103.10 to 0.103.13

[dependabot]

Bumps rustls-webpki from 0.103.10 to 0.103.13.

Release notes

Sourced from rustls-webpki's releases.

0.103.13

• Fix reachable panic in parsing a CRL. This was reported to us as GHSA-82j2-j2ch-gfr8. Users who don't use CRLs are not affected.
• For name constraints on URI names, we incorrectly processed excluded subtrees in a way which inverted the desired meaning. See rustls/webpki#471. This was a case missing in the fix for GHSA-965h-392x-2mh5.

What's Changed

• Actually fail closed for URI matching against excluded subtrees by @​djc in rustls/webpki#473
• Prepare 0.103.13 by @​ctz in rustls/webpki#474

Full Changelog: rustls/webpki@v/0.103.12...v/0.103.13

0.103.12

This release fixes two bugs in name constraint enforcement:

• GHSA-965h-392x-2mh5: name constraints for URI names were ignored and therefore accepted. URI name constraints are now rejected unconditionally. Note this library does not provide an API for asserting URI names, and URI name constraints are otherwise not implemented.
• GHSA-xgp8-3hg3-c2mh: permitted subtree name constraints for DNS names were accepted for certificates asserting a wildcard name. This was incorrect because, given a name constraint of accept.example.com, *.example.com could feasibly allow a name of reject.example.com which is outside the constraint. This is very similar to CVE-2025-61727.

Since name constraints are restrictions on otherwise properly-issued certificates, these bugs are reachable only after signature verification and require misissuance to exploit.

What's Changed

• Prepare 0.103.12 by @​djc in rustls/webpki#470

Full Changelog: rustls/webpki@v/0.103.11...v/0.103.12

0.103.11

In response to #464, we've slightly relaxed requirements for anchor_from_trust_cert() to ignore unknown extensions even if they're marked as critical. This only affects parsing a TrustAnchor from DER, for which most extensions are ignored anyway.

What's Changed

• Backport parsing trust anchors with unknown critical extensions to 0.103 by @​djc in rustls/webpki#466

Commits

• 2879b2c Prepare 0.103.13
• 2c49773 Improve tests for padding of BitStringFlags
• 4e3c0b3 Correct validation of BIT STRING constraints
• 39c91d2 Actually fail closed for URI matching against excluded subtrees
• 27131d4 Bump version to 0.103.12
• 6ecb876 Clean up stuttery enum variant names
• 318b3e6 Ignore wildcard labels when matching name constraints
• 1219622 Rewrite constraint matching to avoid permissive catch-all branch
• 57bc62c Bump version to 0.103.11
• d0fa01e Allow parsing trust anchors with unknown criticial extensions
• 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 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.

[jamesadevine]

/rust-review do we have the coverage for this change?

[github-actions]

✅ Rust PR Reviewer completed successfully!

[github-actions]

🔍 Rust PR Review

Summary: Looks good — this is a Cargo.lock-only transitive dependency security bump; existing tests pass and no application-level coverage gap exists.

Findings

✅ What Looks Good

• Diff scope: Only Cargo.lock is changed — rustls-webpki is a transitive dependency (pulled in via rustls → hyper-rustls). Nothing in Cargo.toml or application code is touched.

• Security fixes addressed (0.103.11–0.103.13):

  • GHSA-82j2-j2ch-gfr8 — reachable panic in CRL parsing
  • GHSA-965h-392x-2mh5 — URI name constraints were silently ignored
  • GHSA-xgp8-3hg3-c2mh — wildcard DNS names bypassed permitted subtree name constraints

• Test suite passes on the PR branch: 973 tests across 5 suites (unit, compiler, CLI, init, MCP HTTP) — all green. This gives strong confidence the bump doesn't regress any existing behaviour.

On coverage for this specific change

The security scenarios fixed in this release (CRL parsing, TLS name constraint enforcement) live deep inside the TLS handshake layer. This project consumes rustls as a client (for downloading AWF/MCPG/compiler binaries over HTTPS) but doesn't implement custom certificate validation, CRL checking, or name constraints. Application-level tests cannot meaningfully cover these CVE scenarios — that coverage lives in rustls-webpki's own test suite upstream.

What the existing suite does cover: that the HTTPS-dependent codepaths (binary downloads, MCP HTTP server, etc.) compile and behave correctly with the new version — which they do.

Verdict: No additional test coverage is needed here. Safe to merge.

Warning

⚠️ Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• dev.azure.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "dev.azure.com"

See Network Configuration for more information.

Generated by Rust PR Reviewer for issue #321 · ● 373.6K · ◷