ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-4747

Each RPCSEC_GSS data packet is validated by a routine which checks a signature in the packet.

Published Mar 26, 2026 · catalog updated Jun 17, 2026 · Each RPCSEC_GSS data packet

Check if you run it

No confirmed exploitation is on record for CVE-2026-4747. EPSS is 1.11%. Act only if a listed version of Each RPCSEC_GSS data packet is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Each RPCSEC_GSS data packet).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
1.11%
Remediation
Advisory link
Affected products
cpe freebsd/freebsd

Each RPCSEC_GSS data packet is validated by a routine which checks a signature in the packet. This routine copies a portion of the packet into a stack buffer, but fails to ensure that the buffer is sufficiently large, and a malicious client can trigger a stack overflow. Notably, this does not require the client to authenticate itself first. As kgssapi.ko's RPCSEC_GSS implementation is vulnerable, remote code execution in the kernel is possible by an authenticated user that is able to send packets to the kernel's NFS server while kgssapi.ko is loaded into the kernel. In userspace, applications which have librpcgss_sec loaded and run an RPC server are vulnerable to remote code execution from any client able to send it packets. We are not aware of any such applications in the FreeBSD base system.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe freebsd/freebsd13.5

How to fix CVE-2026-4747

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-4747. EPSS is 1.11%. Act only if a listed version of Each RPCSEC_GSS data packet is installed.

Which versions are affected?

Compare what you have installed with 13.5. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-121: Stack-based Buffer Overflow. EPSS 1.11%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 26, 2026 · NIST NVD

    Detected

    Each RPCSEC_GSS data packet is validated by a routine which checks a signature in the packet. This routine copies a portion of the packet into a stack buffer, but fails to ensure that the buffer is sufficiently large, and a malicious client can trigger a stack overflow. Notably, this does not require the client to authenticate itself first. As kgssapi.ko's RPCSEC_GSS implementation is vulnerable,

  2. Jun 17, 2026 · NIST NVD

    Updated

    Each RPCSEC_GSS data packet is validated by a routine which checks a signature in the packet. This routine copies a portion of the packet into a stack buffer, but fails to ensure that the buffer is sufficiently large, and a malicious client can trigger a stack overflow. Notably, this does not require the client to authenticate itself first. As kgssapi.ko's RPCSEC_GSS implementation is vulnerable,

Sources

  • CVE.orgVulnerability recordCVE-2026-4747

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-4747

    30-day exploitation probability 1.1%

    first.org
  • NIST NVDVulnerability recordCVE-2026-4747

    Each RPCSEC_GSS data packet is validated by a routine which checks a signature in the packet. This routine copies a portion of the packet into a stack buffer, but fails to ensure that the buffer is sufficiently large, and a malicious client can trigger a stack overflow. Notably

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.