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 75554 explicit organization scopes survive token
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
Low · CVSS 2.3CVE-2026-75554

Explicit organization scopes survive token refresh after membership endsCVE-2026-75554

Answer in brief

CVE-2026-75554 records a Low severity (CVSS 2.3) vulnerability in Explicit organization scopes survive token refresh after membership ends. The current sources do not mark it as known exploited. The current feed maps hexpm/hex.pm (generic), hexpm/hexpm (generic), hexpm/hexpm (generic), hexpm/hexpm/hexpm (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 24, 2026Updated Sep 1, 2026Source checked Oct 9, 2026First seen by HOL Aug 24, 2026Material review Sep 1, 2026
Upstream Advisory

Key facts

Risk
Low · CVSS 2.3
Exploitation
Not marked as known exploited
Affected software
4 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 2.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 hexpm/hex.pm (generic), hexpm/hexpm (generic), hexpm/hexpm (generic), hexpm/hexpm/hexpm (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
hexpm/hex.pmgeneric>=2025-10-10 <2026-08-242026-08-24
hexpm/hexpmgeneric>=2025-10-10 <2026-08-242026-08-24
hexpm/hexpmgeneric>=650faa03af511e74c1b3b49ec12d35666b6984c4 <50cffd206490c49c92d7b63c8505949682abedb050cffd206490c49c92d7b63c8505949682abedb0
hexpm/hexpm/hexpmgeneric>=650faa03af511e74c1b3b49ec12d35666b6984c4 <50cffd206490c49c92d7b63c8505949682abedb050cffd206490c49c92d7b63c8505949682abedb0

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for hexpm/hex.pm, hexpm/hexpm, hexpm/hexpm.
  2. 2Review the reported fix. Update hexpm/hex.pm to 2026-08-24; hexpm/hexpm to 2026-08-24; hexpm/hexpm to 50cffd206490c49c92d7b63c8505949682abedb0; hexpm/hexpm/hexpm to 50cffd206490c49c92d7b63c8505949682abedb0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 24, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Sep 1, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Aug 24, 2026

Sources and claim methodology

  • Source referencecna.erlef.org
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • Source referenceosv.dev
Upstream source description

Insufficient Session Expiration vulnerability in the OAuth token refresh grant in hexpm hexpm allows a user removed from an organization to keep reading its private packages. expand_repositories_scope/3 in lib/hexpm/permissions.ex only rewrites the literal repositories scope, so an explicitly granted repository:<org> or docs:<org> scope passes through it untouched. The refresh grant re-derives a new token from the stored granted_scopes, which holds that expanded form, so every refresh reproduces the organization scope without revisiting membership. Because both CDN edges authorize repository access from the token claim without querying the database, an account removed from an organization retains read access for as long as it keeps refreshing, bounded by the 30 day refresh token lifetime rather than the 30 minute access token lifetime. This issue affects hex.pm: from 2025-10-10 before 2026-08-24.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Unauthenticated JSON API Authorization Bypass Vulnerability in TP-Link Tapo C325WBSame generic ecosystem
  • Unauthenticated RTSP Tunnel Denial-of-Service Vulnerability in TP-Link Tapo C325WBSame generic ecosystem
  • Predictable Media Stream Pre-Shared Key Vulnerability in TP-Link Tapo C325WBSame generic ecosystem
  • Eog: eog: arbitrary code execution via heap buffer overflow in png metadata readerSame generic ecosystem
  • fast-jwt treats raw public JWK JSON as an HMAC secret, enabling HS256 token forgerySame generic ecosystem
  • Hazelcast: Authorization bypass in IMap Predicates APISame generic ecosystem

Record context

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