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
  • Gemini 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 49421 unlinkat2 ignores atresolvebeneath flag
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 Plugins
  • 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 7.1CVE-2026-49421

unlinkat(2) ignores AT_RESOLVE_BENEATH flag

Answer in brief

CVE-2026-49421 records a High severity (CVSS 7.1) vulnerability in unlinkat(2) ignores AT_RESOLVE_BENEATH flag. The current sources do not mark it as known exploited. The current feed maps FreeBSD/FreeBSD (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 19, 2026Updated Sep 1, 2026Source checked Oct 3, 2026First seen by HOL Aug 19, 2026Material review Sep 1, 2026
Upstream Advisory

Key facts

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

Why this deserves its current priority

CVSS is 7.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 FreeBSD/FreeBSD (generic). Check affected ranges and fixed versions before updating.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:o:freebsd:freebsd:14.3:-:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p10:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p11:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p12:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p13:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p14:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p15:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p3:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p4:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p5:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p6:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p7:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p8:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.3:p9:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.4:-:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.4:p1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.4:p2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.4:p3:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.4:p4:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.4:p5:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.4:p6:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:14.4:rc1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.0:-:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.0:p1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.0:p10:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.0:p2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.0:p3:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.0:p4:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.0:p5:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.0:p6:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.0:p7:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.0:p8:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.0:p9:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.1:-:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.1:rc2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:freebsd:freebsd:15.1:rc3-p1:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
FreeBSD/FreeBSDgeneric>=15.1-RELEASE <p1 || >=15.0-RELEASE <p11 || >=14.4-RELEASE <p7 || >=14.3-RELEASE <p16p1, p11, p7, p16

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for FreeBSD/FreeBSD.
  2. 2Review the reported fix. Update FreeBSD/FreeBSD to p1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 19, 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 19, 2026

Sources and claim methodology

  • Source referencesecurity.freebsd.org
Upstream source description

The kernel function that implements unlinkat(2) and funlinkat(2) validated the AT_RESOLVE_BENEATH flag but failed to pass it through to the underlying path lookup. The flag was silently dropped, so path resolution was not actually restricted. A process that uses AT_RESOLVE_BENEATH with unlinkat(2) or funlinkat(2) to confine path resolution can in fact resolve paths above the starting directory. A caller relying on this flag for path containment may delete files outside the intended directory tree.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • WP Ultimate Review <= 2.4.3 - Unauthenticated Arbitrary Shortcode Execution via 'xs_reviw_summery' Parameter (Split-Shortcode / Late-Registered Shortcode)Same generic ecosystem
  • WP Ultimate Review < 2.4.4 - Author+ Stored XSS via Review Overview SettingsSame generic ecosystem
  • MPG < 4.2.3 - Editor+ Arbitrary File Read via Project ImportSame generic ecosystem
  • WPMobile.App <= 11.84 - Unauthenticated Stored Cross-Site Scripting via '/android_json/search/<value>/0' Path SegmentSame generic ecosystem
  • WP 2FA < 4.1.0 - Two-Factor Authentication Bypass via TOTP Code ReplaySame generic ecosystem
  • WP Ultimate Review <= 2.4.3 - Authenticated (Subscriber+) Arbitrary Shortcode Execution via 'xs_reviw_summery' ParameterSame generic ecosystem

Record context

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