CVE-2026-105963

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.

• CWE-532

• https://cna.erlef.org/cves/CVE-2026-105963.html
• https://github.com/elixir-plug/plug/commit/56000c33d8a0a2fbac491f8be06b9c5112bc2276
• https://github.com/elixir-plug/plug/commit/aeaa90e76b73ea90c3ecca9aae16fce71bd2a8d4
• https://github.com/elixir-plug/plug/security/advisories/GHSA-ffw9-w85g-f2vh
• https://github.com/elixir-plug/plug_crypto/commit/2d078b7b8264c565f0ff71235c515f4f46882dcf
• https://github.com/elixir-plug/plug_crypto/commit/981887493dada0fce7003c61861c00dfbb0fc8c5
• https://osv.dev/vulnerability/EEF-CVE-2026-105963

Published

Oct 23, 2026

Last Modified

Oct 23, 2026

Status

Deferred

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-10595A path traversal vulnerability exists in parisneo/lollms ver…7.5
• CVE-2026-105950A security vulnerability has been detected in getformwork fo…3.5
• CVE-2026-105957A vulnerability was detected in SourceCodester Performance I…6.3
• CVE-2026-105958A flaw was found in spice-server. Multiple migration data ha…7.5
• CVE-2026-105959A flaw was found in spice-server. The GLZ encoder dictionary…7.5
• CVE-2026-105960PEAK-System PCAN contains a vulnerable operation involving a…5.5
• CVE-2026-105964The Gitea Actions artifact v4 (Twirp) handlers read the whol…6.5
• CVE-2026-105967The Gallery for Social Photo WordPress plugin through 1.0.0.…5.8
• CVE-2026-105969The CodeAtoZ B2B Suite for WooCommerce WordPress plugin befo…5.3
• CVE-2026-10597OMICARD EDM developed by ITPison has a Insecure Direct Objec…6.9
• CVE-2026-105971The Car Dealer (Dealership) and Vehicle sales WordPress plug…5.3
• CVE-2026-105972The Menu Cart for WooCommerce WordPress plugin before 3.2.1 …7.5