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 73802 gitea runner host isolation bypass through
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.9CVE-2026-73802GHSA-X4Q3-GCJ3-M6CF

Gitea Runner host isolation bypass through container optionsCVE-2026-73802

Answer in brief

CVE-2026-73802 records a Critical severity (CVSS 9.9) vulnerability in Gitea Runner host isolation bypass through container options. The current sources do not mark it as known exploited. The current feed maps Gitea/Gitea Runner (generic), gitea.com/gitea/runner (go), gitea.com/gitea/runner (go). 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 14, 2026Updated Oct 14, 2026Source checked Oct 14, 2026First seen by HOL Oct 2, 2026Material review Oct 14, 2026
Upstream Advisory

Key facts

Risk
Critical · CVSS 9.9
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.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 Gitea/Gitea Runner (generic), gitea.com/gitea/runner (go), gitea.com/gitea/runner (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Gitea/Gitea Runnergeneric>=0 <3.0.03.0.0
gitea.com/gitea/runnergo<1.0.9-0.20260731160927-34bfa19150221.0.9-0.20260731160927-34bfa1915022
gitea.com/gitea/runnergo>=0 <1.0.9-0.20260731160927-34bfa19150221.0.9-0.20260731160927-34bfa1915022

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Gitea/Gitea Runner, gitea.com/gitea/runner, gitea.com/gitea/runner.
  2. 2Review the reported fix. Update Gitea/Gitea Runner to 3.0.0; gitea.com/gitea/runner to 1.0.9-0.20260731160927-34bfa1915022; gitea.com/gitea/runner to 1.0.9-0.20260731160927-34bfa1915022 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Oct 14, 2026

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

  2. Source modified

    Oct 14, 2026

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

  3. First seen by HOL

    Oct 2, 2026

Sources and claim methodology

  • Source referenceblog.gitea.com
  • Source referencegitea.com
  • GitHub security advisorygithub.com
  • Source referencegitea.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
Upstream source description

Gitea Runner passes workflow-controlled container options into Docker job container configuration while privileged mode is disabled. Host namespace settings, expanded capabilities, and security profile overrides can remain effective despite Privileged being forced false. A workflow author able to run jobs on an affected Docker-backed runner can use these options to access host namespaces and execute commands as root on the runner host, bypassing the intended container isolation.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • KEDA: Privilege escalation from namespace admin to cluster admin via KEDA TriggerAuthenticationAlso CWE-269
  • Account pre-hijacking in the Prowler API through email based social account linking without verificationSame generic ecosystem
  • Zulip: Guests can read new messages in non-subscribed public channelsSame generic ecosystem
  • Junos OS and Junos OS Evolved: A specific BGP FlowSpec update causes an rpd crash when BGP FlowSpec import policy is usedSame generic ecosystem
  • Junos OS and Junos OS Evolved: A BGP peer causes an rpd crash if a malformed MCAST-TREE NLRI is received and readvertisedSame generic ecosystem
  • Junos OS: Unauthorized root command execution when J-Web is enabledSame generic ecosystem

Record context

Vulnerability class
Privilege Escalation
EPSS
Not reported
CWE IDs
CWE-269
Source
CVE List V5
Source checked
Oct 14, 2026
References
6 linked sources
Open source record