CVE-2026-124496 · Package
NO FIX YET · SEE WHAT TO DO
The DRPC HTTP endpoint skips the configured impersonation authorizer, so an authenticated client can run DRPC functions restricted to another user. An attacker gets the other user's privileges on the affected service.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Applications that use the DRPC HTTP endpoint with user impersonation configured are exposed to authenticated users acting as others. Applications that do not expose the DRPC HTTP endpoint or do not use impersonation are likely unaffected, though the sources do not say this explicitly.
Not affected if no-http-endpoint, no-impersonation
Who cares drpc, go
3.2.0.The DRPC HTTP endpoint lets an authenticated client act as another user without applying the configured impersonation authorizer. An authenticated user can execute DRPC functions that are restricted to another user. Users are recommended to upgrade to version 3.2.0, which fixes the issue.
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.