Answer in brief
CVE-2026-105963 records a Medium severity (CVSS 5.1) vulnerability in Secret key base exposed in stack trace arguments on wrong-typed Plug.Crypto arguments. The current sources do not mark it as known exploited. The current feed maps elixir-plug/elixir-plug/plug (generic), elixir-plug/elixir-plug/plug_crypto (generic), elixir-plug/plug (generic), elixir-plug/plug_crypto (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps elixir-plug/elixir-plug/plug (generic), elixir-plug/elixir-plug/plug_crypto (generic), elixir-plug/plug (generic), elixir-plug/plug_crypto (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| elixir-plug/elixir-plug/pluggeneric | >=56000c33d8a0a2fbac491f8be06b9c5112bc2276 <* | * |
| elixir-plug/elixir-plug/plug_cryptogeneric | >=2d078b7b8264c565f0ff71235c515f4f46882dcf <981887493dada0fce7003c61861c00dfbb0fc8c5 | 981887493dada0fce7003c61861c00dfbb0fc8c5 |
| elixir-plug/pluggeneric | >=1.6.3 <1.7.0 | 1.7.0 |
| elixir-plug/plug_cryptogeneric | >=1.0.0 <2.2.1 | 2.2.1 |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
Externally-Generated Error Message Containing Sensitive Information vulnerability in plug_crypto in elixir-plug plug_crypto allows an unauthenticated remote attacker to expose the secret key base through application logs via a wrong-typed argument. Every public function in Plug.Crypto validates argument types in a function-head guard. A failed guard makes the Erlang VM raise FunctionClauseError with the actual argument values in the top stack frame, so the secret key base, a derived key, or the value an API key is compared against lands in that frame. The library's rescue blocks and Plug.Crypto.prune_args_from_stacktrace/1 only reach exceptions raised inside a function body, so they never see a guard failure. Plug.Cowboy and Bandit write the frame to the error log and attach it as crash_reason Logger metadata, which error trackers forward. Two entry points take request data. Plug.Crypto.verify/4 exposes the secret key base when the token is neither a binary nor nil, which Phoenix.Token.verify/4 reaches because it forwards the token unguarded. Plug.Crypto.secure_compare/2 exposes the other operand when one side is not a binary, as happens when a missing request header yields nil. Reading the leaked value needs separate access to the logs or the error tracker, so the request alone does not disclose the secret to the attacker. This issue affects plug: from 1.6.3 before 1.7.0; plug_crypto: from 1.0.0 before 2.2.1.
Quoted source text, attributed separately from HOL analysis.