Skip to content

Update rustc crate rkyv to 0.8.18 - #160807

Open
rperier wants to merge 1 commit into
rust-lang:mainfrom
rperier:bump_rkyv_security_issues
Open

Update rustc crate rkyv to 0.8.18#160807
rperier wants to merge 1 commit into
rust-lang:mainfrom
rperier:bump_rkyv_security_issues

Conversation

@rperier

@rperier rperier commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

See
https://rustsec.org/advisories/RUSTSEC-2026-0233
https://rustsec.org/advisories/RUSTSEC-2026-0234
https://rustsec.org/advisories/RUSTSEC-2026-0235

  • I did not use an LLM to create a change in this PR.
  • I used an LLM to create a change in this PR, and I have explained below how it was used.

This fixes RUSTSEC-2026-0233, RUSTSEC-2026-0234 and RUSTSEC-2026-0235.
@rustbot

rustbot commented Aug 9, 2026

Copy link
Copy Markdown
Collaborator

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 9, 2026
@rustbot

rustbot commented Aug 9, 2026

Copy link
Copy Markdown
Collaborator

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

  • Owners of files modified in this PR: @Mark-Simulacrum

@Mark-Simulacrum Mark-Simulacrum changed the title Update rustc crate rkyv to 0.8.18 [SECURITY] Update rustc crate rkyv to 0.8.18 Aug 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants