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 56126 pfsense plus 2607 ce 290 stored xss via
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 5.1CVE-2026-56126

pfSense Plus < 26.07 / CE < 2.9.0 Stored XSS via status_monitoring.phpCVE-2026-56126

Answer in brief

CVE-2026-56126 records a Medium severity (CVSS 5.1) vulnerability in pfSense Plus < 26.07 / CE < 2.9.0 Stored XSS via status_monitoring.php. The current sources do not mark it as known exploited. The current feed maps Netgate/pfSense CE (generic), Netgate/pfSense CE (generic), Netgate/pfSense Plus (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 Sep 3, 2026Updated Oct 1, 2026Source checked Oct 18, 2026First seen by HOL Sep 3, 2026Material review Oct 1, 2026
Upstream Advisory

Key facts

Risk
Medium · CVSS 5.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 5.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 Netgate/pfSense CE (generic), Netgate/pfSense CE (generic), Netgate/pfSense Plus (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Netgate/pfSense CEgeneric>=0 <2.9.02.9.0
Netgate/pfSense CEgeneric*Not reported
Netgate/pfSense Plusgeneric>=0 <26.0726.07

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Netgate/pfSense CE, Netgate/pfSense CE, Netgate/pfSense Plus.
  2. 2Review the reported fix. Update Netgate/pfSense CE to 2.9.0; Netgate/pfSense Plus to 26.07 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 3, 2026

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

  2. Source modified

    Oct 1, 2026

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

  3. First seen by HOL

    Sep 3, 2026

Sources and claim methodology

  • Source referencedocs.netgate.com
  • Source referencedocs.netgate.com
  • Source referencedocs.netgate.com
  • Source referencevulncheck.com
Upstream source description

pfSense Plus before 26.07 and CE before 2.9.0 allow authenticated users with the Status: Monitoring privilege to inject arbitrary JavaScript via graph configuration parameters in /status_monitoring.php. Multiple POST parameters including graph-left, graph-right, time-period, resolution, start-date, end-date, start-time, end-time, graph-type, invert, and refresh-interval are concatenated and written to the global pfSense XML configuration without sanitization, then echoed unsanitized into a JavaScript string context on page render. Because the setting is stored in the global configuration, the payload executes in the browser of every user who visits the Status: Monitoring page.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • itsmeravitejak Online-Examination-System Exam exam.php startExam sql injectionSame generic ecosystem
  • blk-mq: set RQF_USE_SCHED when the operation is knownSame generic ecosystem
  • block: reject polled dio with user integrity metadataSame generic ecosystem
  • wifi: mac80211: prevent AP VLAN tx from other interfacesSame generic ecosystem
  • wifi: cfg80211: preserve hidden-group beacon IE ownershipSame generic ecosystem
  • wifi: mac80211: validate TX status rate metadataSame generic ecosystem

Record context

Vulnerability class
XSS
EPSS
Not reported
CWE IDs
CWE-79
Source
CVE List V5
Source checked
Oct 18, 2026
References
4 linked sources
Open source record