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 49418 use after free in device pager page list
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 8.8CVE-2026-49418

Use-after-free in device pager page list

Answer in brief

CVE-2026-49418 records a High severity (CVSS 8.8) vulnerability in Use-after-free in device pager page list. 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 8.8
Exploitation
Not marked as known exploited
Affected software
39 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 8.8. 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

When msync(MS_INVALIDATE) is called on a mapping of an unmanaged device object, the physical pages in the mapping range are marked invalid but remain in the pager's page list. A subsequent page fault will cause the fault handler to re-insert the page into the object's list. This corrupts the list, and on object destruction the page is freed twice. An unprivileged local user with access to a device that provides memory-mapped I/O can trigger a use-after-free in the kernel, though this is limited to a pool of objects ("fictitious pages") that are never recycled for a different purpose. It may be possible to exploit this to escalate privileges.

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 - Unauthenticated Stored XSS via Review SubmissionSame generic ecosystem
  • WP Ultimate Review < 2.4.4 - Unauthenticated DoS via Non-Numeric Review RatingSame generic ecosystem
  • WP Ultimate Review < 2.4.4 - Unauthenticated DoS via Unset Display Settings in wp-reviews ShortcodeSame 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

Record context

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