pfSense CE 2.7.0 through 2.9.0 contains a command injection vulnerability in services_captiveportal_hasync.php that allows users with only the Captive Portal HA privilege to execute commands as root. Attackers can set backwardsyncip to a malicious XMLRPC server returning connected_users with shell metacharacters in ip or mac fields, which captiveportal_load_pfctl passes unescaped to a pfctl shell command.
CVE-2026-111229
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-10-15. The CNA's CVSS baseline 7.2; sources differ by 0.0.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
The CVE record's CNA (VulnCheck) lists Netgate pfSense CE versions 2.7.0 up to and including 2.9.0 as affected. No release containing a fix is confirmed on record.
- CVSS v3
- 7.2
- EG Score
- 7.2HIGHhigh confidence
- EG Risk
- 48EG Risk 48/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity72% × 45%The EG Score, 7.2 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix. - EPSS PROB
- 6.4%
- EPSS %ILE
- 93rd
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 15, 2026
Last Modified
October 16, 2026
Advisory Details (5)
Auto-updated Oct 15, 2026Netgate pfSense CE 2.7.0 through 2.9.0 Command Injection via Captive Portal HA Sync | Advisories | VulnCheck
https://www.vulncheck.com/advisories/netgate-pfsense-ce-2.7.0-through-2.9.0-command-injection-via-captive-portal-ha-syncpfsense/src/usr/local/www/services_captiveportal_hasync.php at 9363ac5b8651a1c7a333180425ce7719070f95f9 · pfsense/pfsense · GitHub
https://github.com/pfsense/pfsense/blob/9363ac5b8651a1c7a333180425ce7719070f95f9/src/usr/local/www/services_captiveportal_hasync.php#L106-L140pfsense/src/etc/inc/captiveportal.inc at 9363ac5b8651a1c7a333180425ce7719070f95f9 · pfsense/pfsense · GitHub
https://github.com/pfsense/pfsense/blob/9363ac5b8651a1c7a333180425ce7719070f95f9/src/etc/inc/captiveportal.inc#L2958-L2966pfSense CE leftovers, part 1: the pin that is not RELEASE · Abraxas Labs
https://abraxaslabs.tech/research/pfsense-ce-leftoversGitHub - abraxas/pfsense-cp-ha-pfctl: pfSense CE 2.9.0-DEVELOPMENT - High - Remote - RCE - CP HA host into pfctl · GitHub
https://github.com/abraxas/pfsense-cp-ha-pfctlVendor Advisories for CVE-2026-111229(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-16 18:18 UTCEG score recompute
- 2026-10-16 18:18 UTCGHSA enrichmentGHSA-xf3x-9wqm-925c · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-10-16 17:22 UTCEG score recompute
- 2026-10-16 17:22 UTCGHSA enrichmentGHSA-xf3x-9wqm-925c · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 6.4% · 93rd percentile
- 2026-10-15 21:47 UTCEG score recompute
- 2026-10-15 21:46 UTCGHSA enrichmentGHSA-xf3x-9wqm-925c · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-10-15 19:32 UTCEG score recompute
- 2026-10-15 19:01 UTCEG score recomputeFirst assessed: 7.2 HIGH
- 2026-10-15 18:57 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
- CVE-2026-111226EG 7.2EPSS p94HIGH
- CVE-2026-111225EG 5.0MEDIUM
- CVE-2026-111224EG 7.5EPSS p93HIGH
- CVE-2026-111218EG 7.2EPSS p95HIGH
- CVE-2026-111217EG 7.2EPSS p94HIGH
- CVE-2026-111216EG 7.2EPSS p94HIGH
- CVE-2026-111215EG 7.2EPSS p94HIGH
- CVE-2026-111214EG 7.2EPSS p95HIGH
- CVE-2026-110957EG 10.0CRITICAL
- CVE-2026-111451EG 7.8HIGH
Frequently asked(5)
What is CVE-2026-111229?
When was CVE-2026-111229 made public?
Is CVE-2026-111229 actively exploited?
What is the CVSS score of CVE-2026-111229?
How do I remediate CVE-2026-111229?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-111229
Is Your Infrastructure Affected by CVE-2026-111229?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.