HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

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
  • Gemini 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.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 86326 cisa adp vulnrichment
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 Plugins
  • 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
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 8.6CVE-2026-86326

CISA ADP Vulnrichment

Answer in brief

CVE-2026-86326 records a High severity (CVSS 8.6) vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps Moxa/MGate MB3170 Series (generic), Moxa/MGate MB3270 Series (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 Oct 2, 2026Updated Oct 2, 2026Source checked Oct 2, 2026First seen by HOL Oct 2, 2026Material review Oct 2, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 8.6
Exploitation
Not marked as known exploited
Affected software
2 mapped packages or products
Fix availability
Not reported

Why this deserves its current priority

CVSS is 8.6. 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 Moxa/MGate MB3170 Series (generic), Moxa/MGate MB3270 Series (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Moxa/MGate MB3170 Seriesgeneric1.0Not reported
Moxa/MGate MB3270 Seriesgeneric1.0Not reported

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Moxa/MGate MB3170 Series, Moxa/MGate MB3270 Series.
  2. 2Review the reported fix. Source-reported solution: Users are advised to follow the applicable Security Hardening Guide for the MGate MB3000 or MGate 5000 Series when obtaining and updating firmware. The guides provide recommendations for securely obtaining firmware from official Moxa sources and performing firmware updates. Users should follow the applicable guidance to ensure that the correct and trusted firmware is obtained and that firmware updates are performed securely. For detailed mitigation guidance, please refer to the following Security Hardening Guides: * The Security Hardening Guide for the MGate 5000 Series * The Security Hardening Guide for the MGate MB3000 Series

Evidence timeline and material changes

  1. Published upstream

    Oct 2, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Oct 2, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Oct 2, 2026

Sources and claim methodology

  • Source referencemoxa.com
Upstream source description

An improper verification of cryptographic signature vulnerability exists in protocol gateways because the device does not properly verify the cryptographic authenticity of firmware images before installation. An attacker with high privileges and access to the firmware update interface could provide a specially crafted or modified firmware image, causing it to be installed on the device. Successful exploitation could allow the attacker to execute unauthorized code, compromise the integrity and availability of the device, and persist malicious modifications across subsequent firmware updates.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • WordPress ThemeREX Addons plugin <= 2.46.0 - Server Side Request Forgery (SSRF) vulnerabilitySame generic ecosystem
  • WordPress ThemeREX Addons plugin <= 2.46.0 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • CISA ADP VulnrichmentSame generic ecosystem
  • Tenda AC9 POST Request fast_setting_internet_set stack-based overflowSame generic ecosystem
  • SourceCodester Student Result Management System Announcement new_announcement.php cross site scriptingSame generic ecosystem
  • CodeAstro Simple Pharmacy Management System view.php sql injectionSame generic ecosystem

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
CWE-347
Source
CVE List V5
Source checked
Oct 2, 2026
References
1 linked source
Open source record