{"answers":{"affected":"2 open source packages ship an affected version, including plug and plug_crypto.","exploited":"There is no known exploitation of CVE-2026-105963 in the wild and no public exploit code.","fix":"Upgrade plug to 1.7.0 or later.","what":"CVE-2026-105963 is a medium-severity vulnerability in elixir-plug plug, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-105963 and fix it if it is affected.\n\nWhat it is: CVE-2026-105963 is a medium-severity vulnerability in elixir-plug plug, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-105963 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- plug (Hex): affected from 1.6.3; fixed in 1.7.0\n- plug_crypto (Hex): affected from 1.0.0; fixed in 2.2.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-105963/ (Markdown: https://insights.sbomify.com/CVE-2026-105963/index.md)","id":"CVE-2026-105963","markdown":"https://insights.sbomify.com/CVE-2026-105963/index.md","name":"CVE-2026-105963","record":{"aliases":["EEF-CVE-2026-105963","GHSA-ffw9-w85g-f2vh"],"analysis":null,"analysis_generated_by":null,"assigner":"EEF","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"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.\n\nTwo 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.\n\nThis issue affects plug: from 1.6.3 before 1.7.0; plug_crypto: from 1.0.0 before 2.2.1.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Secret key base exposed in stack trace arguments on wrong-typed Plug.Crypto arguments","id":"CVE-2026-105963","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":7,"next":{"headline":"Gitea Actions artifact v4 API unbounded request body","id":"CVE-2026-105964"},"packages":[{"ecosystem":"Hex","fixed":["1.7.0"],"introduced":["1.6.3"],"last_affected":[],"package":"plug","purl":"pkg:hex/plug","source":"EEF-CVE-2026-105963"},{"ecosystem":"Hex","fixed":["2.2.1"],"introduced":["1.0.0"],"last_affected":[],"package":"plug_crypto","purl":"pkg:hex/plug_crypto","source":"EEF-CVE-2026-105963"}],"prev":{"headline":"HMS Networks PEAK-System PCAN Windows drivers Improper Handling of Length Parameter Inconsistency","id":"CVE-2026-105960"},"products":["plug","plug_crypto"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-23","vendors":["elixir-plug"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-105963/"}