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 109194 quay build trigger uuid idor in quay api
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
Medium · CVSS 6.4CVE-2026-109194

Quay: build trigger uuid idor in quay apiCVE-2026-109194

Answer in brief

CVE-2026-109194 records a Medium severity (CVSS 6.4) vulnerability in Quay: build trigger uuid idor in quay api. The current sources do not mark it as known exploited. The current feed maps Red Hat/quay/quay-rhel8 (generic), Red Hat/quay/quay-rhel9 (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 12, 2026Updated Oct 12, 2026Source checked Oct 12, 2026First seen by HOL Oct 12, 2026Material review Oct 12, 2026
Upstream Advisory

Key facts

Risk
Medium · CVSS 6.4
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 6.4. 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 Red Hat/quay/quay-rhel8 (generic), Red Hat/quay/quay-rhel9 (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Red Hat/quay/quay-rhel8generic*Not reported
Red Hat/quay/quay-rhel9generic*Not reported

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Red Hat/quay/quay-rhel8, Red Hat/quay/quay-rhel9.
  2. 2Review the reported fix. Source-reported workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Evidence timeline and material changes

  1. Published upstream

    Oct 12, 2026

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

  2. Source modified

    Oct 12, 2026

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

  3. First seen by HOL

    Oct 12, 2026

Sources and claim methodology

  • Source referenceaccess.redhat.com
  • Source referencebugzilla.redhat.com
Upstream source description

A flaw was found in Red Hat Quay. The build trigger management application programming interface (API) fails to verify whether a requested trigger belongs to the specified repository. An authenticated user with administrative access to any repository can view, modify, or permanently delete build triggers and associated write tokens of another repository if they know the victim trigger's universally unique identifier (UUID).

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • WordPress Salevo plugin <= 1.3.0 - Broken Access Control vulnerabilitySame generic ecosystem
  • hex_core decompresses registry and Erlang term API responses without size limitsSame generic ecosystem
  • WordPress Booktics plugin <= 1.0.28 - Broken Access Control vulnerabilitySame generic ecosystem
  • WordPress Quiz And Survey Master plugin <= 11.2.7 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • WordPress Broadcast Live Video plugin <= 7.3.6 - Broken Access Control vulnerabilitySame generic ecosystem
  • WordPress Paid Videochat Turnkey Site plugin <= 7.5.13 - Broken Access Control vulnerabilitySame generic ecosystem

Record context

Vulnerability class
Secret Exfiltration
EPSS
Not reported
CWE IDs
CWE-639
Source
CVE List V5
Source checked
Oct 12, 2026
References
2 linked sources
Open source record