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 57458 vikunja scoped api token can mint unrestricted
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
High · CVSS 8.1CVE-2026-57458GHSA-V3P6-34MC-HJ7V

Vikunja: Scoped API token can mint unrestricted OAuth session credentialsCVE-2026-57458

Answer in brief

CVE-2026-57458 records a High severity (CVSS 8.1) vulnerability in Vikunja: Scoped API token can mint unrestricted OAuth session credentials. The current sources do not mark it as known exploited. The current feed maps go-vikunja/vikunja (generic), code.vikunja.io/api (go), code.vikunja.io/api (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 9, 2026Updated Oct 9, 2026Source checked Oct 9, 2026First seen by HOL Oct 9, 2026Material review Oct 9, 2026
Upstream Advisory

Key facts

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

Why this deserves its current priority

CVSS is 8.1. 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 go-vikunja/vikunja (generic), code.vikunja.io/api (go), code.vikunja.io/api (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
go-vikunja/vikunjageneric= 2.3.0Not reported
code.vikunja.io/apigo=2.3.02.4.0
code.vikunja.io/apigo>=2.3.0 <2.4.02.4.0

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for go-vikunja/vikunja, code.vikunja.io/api, code.vikunja.io/api.
  2. 2Review the reported fix. Update code.vikunja.io/api to 2.4.0; code.vikunja.io/api to 2.4.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Oct 9, 2026

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

  2. Source modified

    Oct 9, 2026

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

  3. First seen by HOL

    Oct 9, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
Upstream source description

Vikunja is an open-source self-hosted task management platform. In version 2.3.0, a scoped API token limited to the `oauth.authorize` permission can call `POST /api/v1/oauth/authorize`, obtain an OAuth authorization code, and exchange the code at `POST /api/v1/oauth/token` for a normal bearer JSON Web Token (JWT) and refresh token. The resulting credentials are not restricted by the original API token's permissions, allowing access to routes outside its declared scope for the same user. Version 2.4.0 fixes the vulnerability.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Vikunja: OIDC email-fallback account linking ignores email_verified, enabling local-account takeoverSame go-vikunja/vikunja package
  • Vikunja: Plaintext storage of password-reset/email-confirm tokens in database enables account takeover on DB read accessSame go-vikunja/vikunja package
  • MariaDB: `qc_info` plugin can do OOB reads if query contains \0Same generic ecosystem
  • MariaDB: mysql_json plugin OOB readsSame generic ecosystem
  • MariaDB: environment injection via wsrep bootstrap in the mariadb.service fileSame generic ecosystem
  • MariaDB Connector/C: libmariadb allowed cleartext password leakage on TLS hostname verification failureSame generic ecosystem

Record context

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