CVE-2026-118737 · Infrastructure
NO FIX YET
The Windows Remote Procedure Call runtime does not properly verify a cryptographic signature. An unauthenticated attacker on the network can execute code on an 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 expose RPC over the network are the systems to look at; the sources do not name affected Windows builds or whether default configurations are reachable. unknown
Who cares rpc, windows
Unknown from the sources. In the analyst’s queue.
No fix yet, per the sources.
Improper verification of cryptographic signature in Windows Remote Procedure Call Runtime 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.