Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-113779 Overview
CVE-2026-113779 is a privilege escalation vulnerability in the pfSense REST API package (pfSense-pkg-RESTAPI) affecting versions prior to 2.9.0. The flaw lets authenticated accounts that hold the dedicated High Availability (HA) settings sync permission modify REST API configuration secrets. An attacker with this sub-administrative privilege can elevate to a full administrator on the pfSense firewall. The issue stems from an access control boundary that treated the sync privilege as sufficient to change sensitive API configuration. Version 2.9.0 restricts the HA sync endpoint to accounts with page-all and removes the sub-administrative sync privilege entirely.
Critical Impact
An authenticated non-administrative user holding the api-v2-system-restapi-settings-sync-post privilege can escalate to full administrative control of a pfSense CE or pfSense Plus firewall.
Affected Products
- pfSense-pkg-RESTAPI versions prior to 2.9.0
- pfSense CE firewalls running the REST API package
- pfSense Plus firewalls running the REST API package
Discovery Timeline
- 2026-10-21 - CVE-2026-113779 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113779
Vulnerability Analysis
The pfSense REST API package exposes a dedicated endpoint for synchronizing REST API configuration between High Availability peers. The endpoint is guarded by the scoped privilege api-v2-system-restapi-settings-sync-post rather than full administrative access. Accounts holding this sync permission can write to REST API configuration secrets, including values that govern authentication to the API itself.
Because these secrets influence how the REST API authenticates and authorizes requests, modifying them lets a sub-administrative user obtain administrator-equivalent access. The vulnerability therefore converts a narrow operational permission (HA sync) into a complete trust boundary violation on the firewall.
The weakness is categorized under [CWE-502] in the published advisory, reflecting unsafe handling of externally supplied configuration state through the sync interface.
Root Cause
The root cause is an over-permissive authorization check on the HA settings sync endpoint. The endpoint accepted requests from any account holding the scoped sync privilege and allowed those requests to overwrite REST API configuration secrets. The authorization boundary did not distinguish between synchronizing state from a trusted peer and mutating privileged configuration that governs administrative access.
Attack Vector
An attacker first obtains credentials for a pfSense account that has been granted the api-v2-system-restapi-settings-sync-post privilege. The attacker then issues an authenticated POST request to the HA settings sync endpoint of the REST API package. By submitting crafted configuration payloads, the attacker rewrites REST API secrets and gains administrative control over the firewall, enabling arbitrary configuration changes, traffic manipulation, and persistence.
No verified public exploit code is available at the time of publication. See the GitHub Security Advisory GHSA-8q8g-9f77-8g8g for the vendor's technical description.
Detection Methods for CVE-2026-113779
Indicators of Compromise
- POST requests to the api/v2/system/restapi/settings/sync endpoint originating from non-administrator accounts or from IP addresses outside the designated HA peer range.
- Unexpected modifications to REST API configuration secrets, authentication keys, or ACL entries recorded in pfSense configuration history.
- Creation of new administrative users, API keys, or privilege grants shortly after an HA sync call from a sub-administrative account.
Detection Strategies
- Audit pfSense user and group assignments for any account holding the api-v2-system-restapi-settings-sync-post privilege that is not a dedicated HA peer service account.
- Correlate REST API access logs with configuration change events to flag sync calls followed by administrative actions from the same session.
- Compare current REST API configuration against a known-good baseline to identify unauthorized secret or ACL changes.
Monitoring Recommendations
- Forward pfSense system, authentication, and REST API logs to a centralized SIEM for correlation and long-term retention.
- Alert on any 2xx response to the HA sync endpoint from a source IP that is not an approved HA peer.
- Monitor for privilege changes, new API tokens, and modifications to the REST API package configuration file.
How to Mitigate CVE-2026-113779
Immediate Actions Required
- Upgrade pfSense-pkg-RESTAPI to version 2.9.0 or later, which enforces page-all on the HA sync endpoint.
- Remove the api-v2-system-restapi-settings-sync-post privilege from all non-administrative users and groups.
- Review recent REST API configuration changes and rotate any API keys or secrets that may have been exposed.
Patch Information
pfSense-pkg-RESTAPI 2.9.0 fixes the vulnerability by requiring full administrative privileges (page-all) for access to the HA settings sync endpoint and by removing the sub-administrative sync privilege. The release also introduces opt-in defaults and modernized format and validation handling as hardening measures. Patch details are available in the GitHub Release v2.9.0 notes.
Workarounds
- Revoke the api-v2-system-restapi-settings-sync-post privilege from every non-administrative user until the upgrade is applied.
- Configure REST API Access Control Lists to restrict API access to trusted administrator IP addresses and HA peer addresses only.
- Apply firewall rules on the pfSense management interface that limit inbound API traffic to the designated HA peer and administrative networks.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

