Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

Blog · 2-hour update · 2026-10-23

CVE-2026-105963 plug_crypto: top risk today, fix steps

Most urgent: CVE-2026-105963: Externally-Generated Error Message Containing Sensitive Information vulnerability in plug_crypto in elixir-plu
Medium severity (CVSS 5.1). Recommended action: apply the vendor mitigation.

On 23 October 2026, 1 new CVEs were published that we track: 0 critical, 0 already exploited in the wild (CISA KEV) and 0 with a fix or vendor patch available. Each one is ranked by severity, exploitation signals and how easy it is to reach, so you can patch the right ones first.

What happened in this 2-hour window: the most serious item is CVE-2026-105963 (medium, CVSS 5.1, priority 31/100). Recommended action: apply the vendor mitigation. 0 of 1 new CVEs already have a fix or vendor patch; for the other 1, follow the downgrade or mitigation steps until one ships.

Patch these first

CVE-2026-105963: Externally-Generated Error Message Containing Sensitive Information vulnerability in plug_crypto in elixir-plu

Medium severity (CVSS 5.1), priority 31/100 (routine). Recommended action: apply the vendor mitigation.

References: NVD

How to act on this list

  1. Start with anything marked exploited or patch now.
  2. Check what you run: see how to check a version and patch it on Linux, Windows, pip and npm.
  3. Prefer the vendor or distro fix. If none exists, read when to downgrade and when to mitigate.
  4. Verify afterwards. Distros often fix a flaw without changing the upstream version, here is how to confirm.

FAQ

What is the most serious vulnerability published on 23 October 2026?

CVE-2026-105963 (Externally-Generated Error Message Containing Sensitive Information vulnerability in plug_crypto in elixir-plu) ranks highest, with a priority score of 31/100. Recommended action: apply the vendor mitigation.

Are any of the new CVEs exploited in the wild?

None of the new CVEs were on the CISA Known Exploited Vulnerabilities list when this was written. Keep watching the list, it changes daily.

Should I downgrade if there is no fix yet?

Only when an older release is confirmed unaffected and the package is not a core system component. Downgrades can break dependent software, so test first and hold the package until a fix ships.

Sources

← All posts