Repository navigation
Bump plug_crypto to 2.2.1 (EEF-CVE-2026-105963) - #231
Merged
Merged
Conversation
plug_crypto 2.2.0 can expose the secret key base in stack-trace arguments; 2.2.1 fixes it. Also locks elixir_make 0.10.1, which every `mix deps.get` (CI included) already resolves. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3 tasks done
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.
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.
Summary
Security update. plug_crypto 2.2.0 is affected by EEF-CVE-2026-105963, published 2026-10-23: when Plug.Crypto functions get wrong-typed arguments, the secret key base can show up in stack-trace arguments. 2.2.1 fixes it.
CI's Hex audit gate allow-lists only the cowlib advisory, so without this bump every PR's Hex audit job fails. Main's last CI run, on 2026-10-21, predates the advisory.
The lock also moves elixir_make 0.10.0 → 0.10.1. 0.10.0 is neither retired nor flagged, but every plain
mix deps.get, including CI's, upgrades it anyway. Locking 0.10.1 matches what CI already builds with and stops the lockfile drifting locally.Test plan
mise run test: 1688 passed, 0 failurescompile --warnings-as-errorsmix hex.audit: only the allow-listed cowlib advisory remains🤖 Generated with Claude Code