HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 89674 nfsd fix xdr length calculation in
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Critical · CVSS 9.8CVE-2026-89674

nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutgetCVE-2026-89674

Answer in brief

CVE-2026-89674 records a Critical severity (CVSS 9.8) vulnerability in nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 11, 2026Updated Oct 19, 2026Source checked Oct 27, 2026First seen by HOL Sep 11, 2026Material review Oct 19, 2026
Upstream Advisory

Key facts

Risk
Critical · CVSS 9.8
Exploitation
Not marked as known exploited
Affected software
3 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=9b9960a0ca4773e21c4b153ed355583946346b25 <e7d9d23ecd9172f05b09bb678ff22db8e361c428 || >=9b9960a0ca4773e21c4b153ed355583946346b25 <0380129b1373c437eb35401a174671c8888f4b80 || >=9b9960a0ca4773e21c4b153ed355583946346b25 <c81cef6a805dec266c10fc4f83c93d6fcf1a2b43 || >=9b9960a0ca4773e21c4b153ed355583946346b25 <f9868174af49d207fbaf0c5e055d088a983684afe7d9d23ecd9172f05b09bb678ff22db8e361c428, 0380129b1373c437eb35401a174671c8888f4b80, c81cef6a805dec266c10fc4f83c93d6fcf1a2b43, f9868174af49d207fbaf0c5e055d088a983684af
Linux/Linuxgeneric4.8Not reported
Linux/Linuxgeneric>=9b9960a0ca4773e21c4b153ed355583946346b25 <3a7fd224df0fbb42167eb1b77be45d72fe0b1098 || >=9b9960a0ca4773e21c4b153ed355583946346b25 <29e4478e2ed5a227e8f0c33cacb91bf227cedd47 || >=9b9960a0ca4773e21c4b153ed355583946346b25 <65a72b721943618eeb3a41c8b36e915591f3f83f || >=9b9960a0ca4773e21c4b153ed355583946346b25 <bee826c00ac900473f91306f1f3e5a5a81fd4a74 || >=9b9960a0ca4773e21c4b153ed355583946346b25 <e7d9d23ecd9172f05b09bb678ff22db8e361c428 || >=9b9960a0ca4773e21c4b153ed355583946346b25 <0380129b1373c437eb35401a174671c8888f4b80 || >=9b9960a0ca4773e21c4b153ed355583946346b25 <c81cef6a805dec266c10fc4f83c93d6fcf1a2b43 || >=9b9960a0ca4773e21c4b153ed355583946346b25 <f9868174af49d207fbaf0c5e055d088a983684af3a7fd224df0fbb42167eb1b77be45d72fe0b1098, 29e4478e2ed5a227e8f0c33cacb91bf227cedd47, 65a72b721943618eeb3a41c8b36e915591f3f83f, bee826c00ac900473f91306f1f3e5a5a81fd4a74, e7d9d23ecd9172f05b09bb678ff22db8e361c428, 0380129b1373c437eb35401a174671c8888f4b80, c81cef6a805dec266c10fc4f83c93d6fcf1a2b43, f9868174af49d207fbaf0c5e055d088a983684af

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux, Linux/Linux.
  2. 2Review the reported fix. Update Linux/Linux to e7d9d23ecd9172f05b09bb678ff22db8e361c428; Linux/Linux to 3a7fd224df0fbb42167eb1b77be45d72fe0b1098 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 11, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Oct 19, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Sep 11, 2026

Sources and claim methodology

  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget The XDR buffer size calculation in nfsd4_ff_encode_layoutget() has multiple errors that can result in either an out-of-bounds write or leaking uninitialized kernel memory to the client: - fh_len doesn't account for XDR padding on the file handle data - uid and gid lengths use "8 + len" but xdr_encode_opaque() actually writes "4 + xdr_align_size(len)" bytes - ds_len omits the flags and stats_collect_hint fields (8 bytes), while len's header constant overestimates by 8 bytes -- these partially cancel but leave a net mismatch The worst case occurs with short strings (e.g. uid=0, gid=0 with an odd-sized file handle), where the function writes up to 5 bytes past the reserved XDR buffer. Conversely, when string lengths happen to be 4-byte aligned, the reservation is too large and stale buffer content is sent to the client. Fix this by breaking out every encoded field explicitly in the ds_len calculation, using xdr_align_size() for all variable-length opaque fields, and correcting the header constants.

Quoted source text, attributed separately from HOL analysis.

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Oct 27, 2026
References
8 linked sources
Open source record