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.
  • CIGARPoint your coding agent at the right lines and cut its token bill by about a third.

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.
  • Gauntlet benchmarkGuard tested with real coding agents: safe work runs, risky actions stop.

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 72084 scsi target bound pr out transportid parsing to
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

Get HOL Guard for your computer

HOL Guard is a free desktop app that watches what coding agents such as Claude Code, Codex and Cursor run, read and install, and asks you before anything risky happens.

  • Download for macOS
  • Windows download
  • Linux download

Free. macOS 13+ on Apple silicon, Windows x64, Linux AppImage. Other ways to install

Star HOL Guard on GitHub to download
Runs on
macOS 13 or later on Apple silicon, Windows x64 and Linux x86_64.
Price
Free. Paid plans add Guard Cloud for teams. See pricing
Where your data stays
On your computer. Guard Cloud is optional.
Token savings
33% to 38% lower spend across three coding agents in our CIGAR benchmark.

HOL

HOL builds open infrastructure for AI agents: HOL Guard, a directory of AI plugins and MCP servers, an AI agent registry and the open HCS standards.

  • GitHub (opens in a new tab)
  • X (Twitter) (opens in a new tab)
  • YouTube (opens in a new tab)
  • Telegram (opens in a new tab)

HOL Guard

  • What is HOL Guard
  • Features
  • Cut coding agent token costs (CIGAR)
  • Install Guard
  • Download the desktop app
  • Pricing
  • Guard for teams
  • Compare Guard
  • Release notes

Guard for your AI tool

  • Guard for Claude Code
  • Guard for Codex
  • Guard for Cursor
  • Guard for GitHub Copilot CLI
  • Guard for OpenCode
  • Guard for Pi and Oh My Pi
  • Guard for Hermes
  • Guard for OpenClaw
  • All supported AI tools

Research and security

  • Gauntlet: Guard tested with real agents
  • CIGAR token benchmark
  • Research
  • AI security hub
  • Security advisories
  • Active CVEs in AI tools
  • AI agent security guides
  • Extensions and coverage

Plugins and MCP servers

  • Browse AI plugins
  • New 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

AI agent registry

  • Best AI agents
  • Best ERC-8004 agents
  • Best Virtuals agents
  • Best A2A agents
  • Best x402 payable agents
  • Submit an ERC-8004 contract
  • Feature your agent

Developers

  • Guard docs
  • Documentation index
  • Developer hub
  • Registry API reference
  • OpenAPI spec
  • Registry OpenAPI spec
  • Run in Postman (opens in a new tab)
  • HCS standards

Company

  • About HOL
  • Blog
  • Contribute to HOL
  • Guard contributors
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact

Copyright © 2026 HOL DAO LLC. All rights reserved.

  • Privacy
  • Terms of Service
Back to active CVEs
Critical · CVSS 9.8CVE-2026-72084

scsi: target: Bound PR-OUT TransportID parsing to the received bufferCVE-2026-72084

Answer in brief

CVE-2026-72084 records a Critical severity (CVSS 9.8) vulnerability in scsi: target: Bound PR-OUT TransportID parsing to the received buffer. 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 Aug 15, 2026Updated Oct 19, 2026Source checked Nov 13, 2026First seen by HOL Aug 15, 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>=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <842248047ef28dbf3b3f7f49a0ec315054d4dab8 || >=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <03fbc7de8d5e85fc8420e57e8304c855efd453ab || >=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <6ca5de8782e67573a61a6736b6dc0ffe58dcdf59 || >=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <9298078a8f7d8181a04614a34ab655ccdf038204 || >=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <004ccd2d3b4ac36a300e05e01df152e5c02a5a82 || >=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <555a89846ed888d7401b3f7200934c0fbedcbb46 || >=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <d04a179085c262c9ed577d0a4cbc6482ff1fd9a3842248047ef28dbf3b3f7f49a0ec315054d4dab8, 03fbc7de8d5e85fc8420e57e8304c855efd453ab, 6ca5de8782e67573a61a6736b6dc0ffe58dcdf59, 9298078a8f7d8181a04614a34ab655ccdf038204, 004ccd2d3b4ac36a300e05e01df152e5c02a5a82, 555a89846ed888d7401b3f7200934c0fbedcbb46, d04a179085c262c9ed577d0a4cbc6482ff1fd9a3
Linux/Linuxgeneric2.6.38Not reported
Linux/Linuxgeneric>=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <88c67c3de914e19172e1d878a7625c5b06c20ec5 || >=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <842248047ef28dbf3b3f7f49a0ec315054d4dab8 || >=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <03fbc7de8d5e85fc8420e57e8304c855efd453ab || >=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <6ca5de8782e67573a61a6736b6dc0ffe58dcdf59 || >=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <9298078a8f7d8181a04614a34ab655ccdf038204 || >=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <004ccd2d3b4ac36a300e05e01df152e5c02a5a82 || >=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <555a89846ed888d7401b3f7200934c0fbedcbb46 || >=c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 <d04a179085c262c9ed577d0a4cbc6482ff1fd9a388c67c3de914e19172e1d878a7625c5b06c20ec5, 842248047ef28dbf3b3f7f49a0ec315054d4dab8, 03fbc7de8d5e85fc8420e57e8304c855efd453ab, 6ca5de8782e67573a61a6736b6dc0ffe58dcdf59, 9298078a8f7d8181a04614a34ab655ccdf038204, 004ccd2d3b4ac36a300e05e01df152e5c02a5a82, 555a89846ed888d7401b3f7200934c0fbedcbb46, d04a179085c262c9ed577d0a4cbc6482ff1fd9a3

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 842248047ef28dbf3b3f7f49a0ec315054d4dab8; Linux/Linux to 88c67c3de914e19172e1d878a7625c5b06c20ec5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 15, 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

    Aug 15, 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: scsi: target: Bound PR-OUT TransportID parsing to the received buffer core_scsi3_decode_spec_i_port() and core_scsi3_emulate_register_and_move() hand the raw PERSISTENT RESERVE OUT parameter buffer to target_parse_pr_out_transport_id() without telling it how many bytes are valid. For an iSCSI TransportID (FORMAT CODE 01b), iscsi_parse_pr_out_transport_id() locates the ",i,0x" ISID separator with an unbounded strstr() (and on the error path prints the name with a further unbounded "%s"). An initiator can submit a TransportID whose iSCSI name contains neither a ",i,0x" substring nor a NUL terminator, filling the parameter list to its end, so the scan runs off the end of the buffer. When the parameter list spans more than one page the buffer is a multi-page vmap (transport_kmap_data_sg()), so the over-read walks into the trailing vmalloc guard page and oopses (KASAN: vmalloc-out-of-bounds in strstr). It is reachable by any fabric that delivers a PR OUT to a device exported through an iSCSI TPG, including a guest via vhost-scsi. Pass the number of received bytes down to the parser and validate the iSCSI TransportID's own self-described length (ADDITIONAL LENGTH + 4) once, up front: reject it if it is below the spc4r17 minimum or larger than the received buffer, then bound the separator search, the ISID walk and the name copy by that length. This is the length check the callers already perform after the parse (core_scsi3_decode_spec_i_port() compares tid_len against tpdl, core_scsi3_emulate_register_and_move() validates it against data_length), moved ahead of the scan. Also drop the unbounded "%s" of the unterminated name. Add per-format explicit name-length checks before copying into i_str, rather than silently truncating with min_t: for FORMAT CODE 00b reject if the descriptor body (tid_len - 4 bytes) cannot fit in i_str[TRANSPORT_IQN_LEN]; for FORMAT CODE 01b reject if the name portion (from &buf[4] up to the separator) cannot fit. Both checks make the bounds intent explicit at each format branch. While here, also reject a FORMAT CODE 01b TransportID whose ",i,0x" separator sits at the very end of the descriptor: that leaves an empty ISID and points the returned port nexus pointer at buf + tid_len, one past the descriptor, which the registration code (__core_scsi3_locate_pr_reg(), __core_scsi3_alloc_registration()) then dereferences as the ISID string -- the same over-read of the parameter buffer for a malformed descriptor.

Quoted source text, attributed separately from HOL analysis.

Record context

Vulnerability class
Buffer Overflow
EPSS
Not reported
CWE IDs
CWE-125
Source
CVE List V5
Source checked
Nov 13, 2026
References
8 linked sources
Open source record