Does KB5127648 affect PEAP authentication through RADIUS?

November 16, 2026 5 answers
Asked by Nerik-5b

Our VPN uses a machine certificate for device authentication and PEAP with EAP-MSCHAPv2 for user authentication. Windows credentials are passed through automatically.

Will KB5127648 affect either part? User certificates are tricky because shared computers need VPN access before they can retrieve user policy and certificates.

Answers

m.638!clovercrank

The reported issue is with PEAP using EAP-MSCHAPv2 when the logged-on Windows credentials are passed through automatically. Manually entered credentials may still work. Machine certificate authentication is not expected to be affected by that specific change.

The discussion points to Windows 11 24H2 and newer, but check Microsoft's current documentation for the exact update scope and enforcement behavior. The Microsoft-Windows-NTLM/Operational log on an affected client is a useful place to look while testing.

Nerik-5b:

The VPN client does pass through Windows credentials, so that sounds like the part we need to test.

6b!corkspanner_593:

Try the same connection with manually entered credentials as a comparison. That can help narrow down whether credential pass-through is involved.

Reply to this answer
_t81+signalcaddy.6

A possible certificate-based design is a restricted machine tunnel that comes up before user sign-in. It would allow only the infrastructure needed for management and certificate enrollment, such as domain controllers and certificate services. User authentication could then happen after the user certificate is available.

That only helps if the VPN product can keep that limited access available during the transition to user authentication. Check that behavior with the vendor before designing around it.

Nerik-5b:

The current VPN blocks traffic after user sign-in until user authentication succeeds, so that handoff is the difficult part.

Reply to this answer
6r+velvetspanner_482

There is a registry workaround mentioned for the enforcement change, but verify the exact setting and its security implications in Microsoft's guidance before applying it. Treat it as a temporary compatibility measure, not a guarantee that the same option will remain available indefinitely.

Reply to this answer
_y57+socketacorn.2

EAP-TLS is worth investigating, but switching the RADIUS setting alone won't solve the enrollment problem. For shared devices and new users, ask your device management and VPN vendors whether they support a workable way to issue a unique user certificate before the full user tunnel is required.

A separate enrollment network or portal might also provide a path, though it adds another step and needs its own access controls. Test how enrollment and first sign-in would work before committing to it.

Reply to this answer
Velnor+8h

SAML is another route if the VPN supports it, though the extra sign-in prompt could be a real usability drawback here. Ask the vendor what sign-in options are available and test them on shared machines before assuming the prompt can be avoided.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions