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 89317 jwtverifierimplverify does not enforce the jws
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
Medium · CVSS 6.3CVE-2026-89317

JwtVerifierImpl.Verify does not enforce the JWS `crit` header (RFC 7515 §4.1.11)CVE-2026-89317

Answer in brief

CVE-2026-89317 records a Medium severity (CVSS 6.3) vulnerability in JwtVerifierImpl.Verify does not enforce the JWS `crit` header (RFC 7515 §4.1.11). The current sources do not mark it as known exploited. The current feed maps Eclipse Foundation/Eclipse KeyPont - GOSE (generic), Eclipse Foundation/Eclipse KeyPont - GOSE (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 23, 2026Updated Oct 23, 2026Source checked Oct 23, 2026First seen by HOL Oct 23, 2026Material review Oct 23, 2026
Upstream Advisory

Key facts

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

Why this deserves its current priority

CVSS is 6.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 Eclipse Foundation/Eclipse KeyPont - GOSE (generic), Eclipse Foundation/Eclipse KeyPont - GOSE (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Eclipse Foundation/Eclipse KeyPont - GOSEgeneric>=0.7.3 <=0.13.0-rc1Not reported
Eclipse Foundation/Eclipse KeyPont - GOSEgeneric>=0 <1.0.0-rc41.0.0-rc4

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Eclipse Foundation/Eclipse KeyPont - GOSE, Eclipse Foundation/Eclipse KeyPont - GOSE.
  2. 2Review the reported fix. Update Eclipse Foundation/Eclipse KeyPont - GOSE to 1.0.0-rc4 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Oct 23, 2026

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

  2. Source modified

    Oct 23, 2026

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

  3. First seen by HOL

    Oct 23, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
Upstream source description

gose parsed the JWS `crit` header into `JwsHeader.Crit` and then never read it. RFC 7515 §4.1.11 requires a recipient to reject a JWS whose listed critical extension parameters it does not understand. gose implements no header extensions, so every token carrying a non-empty `crit` should have been rejected — and none were.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • AesGcmCryptor.Open passes attacker-controlled nonce to cipher.AEAD.Open without length check, causing panic on wrong-size IVSame eclipse foundation/eclipse keypont - gose package
  • JwksTrustStore.Get returns the last fetched JWKS key (err=nil) when the requested kid is absent, instead of nilSame eclipse foundation/eclipse keypont - gose package
  • Quadratic-time key_ops duplicate check lets a sub-1 MB JWKS body pin a CPU core for ~15 sSame eclipse foundation/eclipse keypont - gose package
  • JwtClaims.MarshalJSON panics via reflect.StructOf when any untyped claim key is not a valid Go identifier suffixSame eclipse foundation/eclipse keypont - gose package
  • LoadPublicKey panics on kty/alg mismatch (kty=EC with a non-EC alg) via unchecked *ECDSAOptions type assertionSame eclipse foundation/eclipse keypont - gose package
  • JweRsaKeyEncryptionDecryptorImpl.Decrypt panics on attacker-chosen IV length (stdlib GCM.Open reached without nonce-size check)Same eclipse foundation/eclipse keypont - gose package

Record context

Vulnerability class
Secret Exfiltration
EPSS
Not reported
CWE IDs
CWE-20, CWE-347, CWE-1288
Source
CVE List V5
Source checked
Oct 23, 2026
References
1 linked source
Open source record