CVE-2026-95956 · Infrastructure
NO FIX YET
A use-after-free bug in the Windows eSCL scanner component lets an unauthorized attacker on the network trigger memory corruption. The sources say this allows the attacker to execute code on the affected Windows machine.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Windows machines that run the eSCL scanner component and are reachable over a network can be exposed. The sources do not say which Windows versions or configurations are affected, so unknown.
Who cares escl-scanner, network-printing, windows
Unknown from the sources. In the analyst’s queue.
No fix yet, per the sources.
Use after free in Windows eSCL Scanner allows an unauthorized attacker to execute code over a network.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.