Menu

Star on GitHub · 3.5k

CVE-2026-93207

9.8 · CRITICAL

In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry svcauth_gss_decode_credbody() writes the caller's rpc_gss…

Published Sep 24, 2026EPSS 0.47%

Overview

CVE-2026-93207 is a critical-severity vulnerability. It was published on September 24, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry

svcauth_gss_decode_credbody() writes the caller's

rpc_gss_wire_cred field by field and assigns gc_ctx.len only on

the success tail. The caller storage is svcdata->clcred, which

lives in the per-svc_rqst gss_svc_data and is reused across

requests. Early decode failures leave partially decoded state

mixed with residue from the prior request.

The trailing body_len tightness check is the sharpest case:

xdr_stream_decode_opaque_inline() has already written gc_ctx.data

with a borrowed inline pointer into the current request's XDR

pages, but gc_ctx.len retains its prior value. Once the request

pages are released the pooled clcred carries a dangling pointer

paired with a stale length.

Zero the caller's rpc_gss_wire_cred at function entry so that

every early-return path leaves a deterministic all-zero cred.

On the trailing tightness-check path, gc_ctx.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-93207?

CVE-2026-93207 is a critical-severity vulnerability. It was published on September 24, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

How severe is CVE-2026-93207?

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-93207?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-93207?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-93207 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2026

View all
CyberStrike v2 is here — more intelligence, greater reach