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
  • 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.
  • 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 77810 code injection via gremlin query passthrough 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
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Critical · CVSS 9.9CVE-2026-77810

Code Injection via Gremlin Query Passthrough in Amazon Athena Neptune ConnectorCVE-2026-77810

Answer in brief

CVE-2026-77810 records a Critical severity (CVSS 9.9) vulnerability in Code Injection via Gremlin Query Passthrough in Amazon Athena Neptune Connector. The current sources do not mark it as known exploited. The current feed maps AWS/Athena Federated Query Neptune Connector (generic), AWS/Athena Federated Query Neptune Connector (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 21, 2026Updated Aug 27, 2026Source checked Oct 6, 2026First seen by HOL Aug 21, 2026Material review Aug 27, 2026
Upstream Advisory

Key facts

Risk
Critical · CVSS 9.9
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 9.9. 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 AWS/Athena Federated Query Neptune Connector (generic), AWS/Athena Federated Query Neptune Connector (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
AWS/Athena Federated Query Neptune Connectorgeneric2024.15.1Not reported
AWS/Athena Federated Query Neptune Connectorgeneric>=2024.15.1 <=2026.28.1Not reported

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for AWS/Athena Federated Query Neptune Connector, AWS/Athena Federated Query Neptune Connector.
  2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

  1. Published upstream

    Aug 21, 2026

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

  2. Source modified

    Aug 27, 2026

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

  3. First seen by HOL

    Aug 21, 2026

Sources and claim methodology

  • Source referenceaws.amazon.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
Upstream source description

In the Neptune connector, a user with access to Neptune through Athena Federated Query could gain access to properties in the Lambda supplying the compute for the connector. To remediate this issue, users should upgrade to aws-athena-query-federation v2026.30.1 or later.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Newell Brands DYMO ID document parsing failing file type extension authentication checkSame generic ecosystem
  • Newell Brands DYMO ID parent directory open to path traversal through improper spheres of controlSame generic ecosystem
  • Bake filesystem entitlement consent is skipped for certain secret and oci-layout definitionsSame generic ecosystem
  • Improper validation of Ops Manager configuration in MongoDB Kubernetes OperatorSame generic ecosystem
  • GraphQL Tools has prototype pollution in well-established utility function `mergeDeep`Same generic ecosystem
  • O2OA General url ActionUploadExcelWithUrl server-side request forgerySame generic ecosystem

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
CWE-95
Source
CVE List V5
Source checked
Oct 6, 2026
References
3 linked sources
Open source record