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 87863 hsts response erases persisted entries
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
Unknown severity · Source severity not reportedCVE-2026-87863

HSTS response erases persisted entriesCVE-2026-87863

Answer in brief

CVE-2026-87863 records a Unknown severity vulnerability in HSTS response erases persisted entries. The current sources do not mark it as known exploited. The current feed maps curl/curl (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 20, 2026Updated Oct 20, 2026Source checked Oct 20, 2026First seen by HOL Oct 20, 2026Material review Oct 20, 2026
Upstream Advisory

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
1 mapped package or product
Fix availability
Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. 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 curl/curl (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
curl/curlgeneric>=8.22.0 <=8.22.0 || >=8.21.0 <=8.21.0 || >=8.20.0 <=8.20.0 || >=8.19.0 <=8.19.0 || >=8.18.0 <=8.18.0 || >=8.17.0 <=8.17.0 || >=8.16.0 <=8.16.0 || >=8.15.0 <=8.15.0 || >=8.14.1 <=8.14.1 || >=8.14.0 <=8.14.0 || >=8.13.0 <=8.13.0 || >=8.12.1 <=8.12.1 || >=8.12.0 <=8.12.0 || >=8.11.1 <=8.11.1 || >=8.11.0 <=8.11.0 || >=8.10.1 <=8.10.1 || >=8.10.0 <=8.10.0 || >=8.9.1 <=8.9.1 || >=8.9.0 <=8.9.0 || >=8.8.0 <=8.8.0 || >=8.7.1 <=8.7.1 || >=8.7.0 <=8.7.0 || >=8.6.0 <=8.6.0 || >=8.5.0 <=8.5.0 || >=8.4.0 <=8.4.0 || >=8.3.0 <=8.3.0 || >=8.2.1 <=8.2.1 || >=8.2.0 <=8.2.0Not reported

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for curl/curl.
  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

    Oct 20, 2026

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

  2. Source modified

    Oct 20, 2026

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

  3. First seen by HOL

    Oct 20, 2026

Sources and claim methodology

  • Source referencecurl.se
  • Source referencecurl.se
  • Source referencehackerone.com
Upstream source description

An authenticated HTTPS origin can supply an HSTS `max-age` value that the parser accepts, but time serialization later fails to process. On 64-bit systems, extreme max-age values compute an absolute expiry within standard time integer limits that exceeds calendar time structure bounds. During cache saves, the original HSTS file is truncated before writing a temporary replacement; when serialization fails, the temporary file is deleted, leaving an empty or partial cache. Because the save error is silently ignored during cleanup, curl exits successfully despite the data loss.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • info leak uploading over WebSockets with GnuTLSSame curl/curl package
  • local interface connection reuse mixupSame curl/curl package
  • curl_mime_free stack overflow by recursionSame curl/curl package
  • Authorization: Negotiate sent to foreign originSame curl/curl package
  • password leak in CURLINFO_EFFECTIVE_URLSame curl/curl package
  • @angular/common: XSRF Token Leakage via URL Parsing Discrepancy in Angular HTTP Client (Incomplete fix for CVE-2025-66035)Also CWE-201

Record context

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