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 59323 micrometer tracing brave bridge w3c baggage
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 5.3CVE-2026-59323

Micrometer Tracing Brave Bridge W3C Baggage propagation DoS vulnerabilityCVE-2026-59323

Answer in brief

CVE-2026-59323 records a Medium severity (CVSS 5.3) vulnerability in Micrometer Tracing Brave Bridge W3C Baggage propagation DoS vulnerability. The current sources do not mark it as known exploited. The current feed maps Spring/Micrometer Tracing (generic), Spring/Micrometer Tracing (generic), VMware/Spring (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 28, 2026Source checked Oct 5, 2026First seen by HOL Aug 21, 2026Material review Aug 28, 2026
Upstream Advisory

Key facts

Risk
Medium · CVSS 5.3
Exploitation
Not marked as known exploited
Affected software
3 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 5.3. 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 Spring/Micrometer Tracing (generic), Spring/Micrometer Tracing (generic), VMware/Spring (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Spring/Micrometer Tracinggeneric1.7.0 || 1.6.0 || 1.5.0 || 0Not reported
Spring/Micrometer Tracinggeneric1.7.0 || >=1.6.0 <=1.6.6 || >=1.5.0 <=1.5.12 || >=0 <=1.4.13Not reported
VMware/Springgeneric>=1.7.0 - 1.7.0 <1.7.0.1 || >=1.7.0 - 1.7.0 <1.7.1 || >=1.6.0 - 1.6.6 <1.6.6.1 || >=1.6.0 - 1.6.6 <1.6.7 || >=1.5.0 - 1.5.12 <1.5.13 || >=1.4.13 and earlier <1.4.141.7.0.1, 1.7.1, 1.6.6.1, 1.6.7, 1.5.13, 1.4.14

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Spring/Micrometer Tracing, Spring/Micrometer Tracing, VMware/Spring.
  2. 2Review the reported fix. Update VMware/Spring to 1.7.0.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 21, 2026

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

  2. Source modified

    Aug 28, 2026

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

  3. First seen by HOL

    Aug 21, 2026

Sources and claim methodology

  • Source referencespring.io
Upstream source description

An application using Micrometer Tracing with W3C baggage propagation in the Brave bridge is vulnerable to denial of service (DoS) due to unbounded object allocation when extracting incoming baggage headers. Micrometer Tracing 1.7.0 Micrometer Tracing 1.6.0 - 1.6.6 Micrometer Tracing 1.5.0 - 1.5.12 Micrometer Tracing 1.4.13 and earlier

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • WordPress Starter Templates plugin <= 4.7.7 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • WordPress Presto Player plugin <= 4.5.2 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • WordPress JS Help Desk plugin <= 4.0.0 - Insecure Direct Object References (IDOR) vulnerabilitySame generic ecosystem
  • WordPress Premium Addons for Elementor plugin <= 4.11.109 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • WordPress Taxi Booking Manager for WooCommerce plugin <= 2.1.1 - Other vulnerability Type vulnerabilitySame generic ecosystem
  • WordPress WP Event Solution plugin <= 4.1.25 - Broken Access Control vulnerabilitySame generic ecosystem

Record context

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