Repository navigation
fix: bump webpki-root-certs to 1.0.10 - #22
Merged
Merged
Conversation
This was referenced Oct 21, 2026
yokuze
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #16
Problem
eMudhra reported eight compromised intermediate CA keys. On Android, the plugin verifies server certificates against the bundled Mozilla roots in
webpki-root-certs. Version 1.0.9 contains "emSign ECC Root CA - G3". This root signs the compromised intermediates (RUSTSEC-2026-0383).Change
webpki-root-certsto 1.0.10. This version removes the emSign root. Host apps cannot build with an older version.rustls-webpki0.103.16. This version rejects the compromised intermediates (RUSTSEC-2026-0382). The plugin does not userustls-webpkidirectly, soCargo.tomldoes not set a minimum version for it.rustls-webpki0.103.16 needsaws-lc-rs1.18. The root lockfile uses 1.18.1, the same version as the example app.cargo metadata --lockedfailed in the example app.silvermine/tauri-plugin-media-parser#27 makes the same change in the media parser plugin.
Tests
--locked.cargo clippy --all-targetsshows no warnings.