CVE-2026-113779
Received Received - Intake

Privilege Escalation in pfSense REST API Package

Vulnerability report for CVE-2026-113779, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-21

Last updated on: 2026-10-21

Assigner: GitHub, Inc.

Description

The pfSense REST API package is an unofficial, open-source REST and GraphQL API for pfSense CE and pfSense Plus firewalls. A privilege escalation vulnerability in pfSense-pkg-RESTAPI prior to version 2.9.0 allows authenticated accounts holding the dedicated settings sync permission to modify REST API configuration secrets. This enables a non-administrative user to elevate their privileges to a full administrator. pfSense-pkg-RESTAPI 2.9.0 patches the issue. Access to the HA settings sync endpoint now strictly requires full administrative privileges (`page-all`). The sub-administrative sync privilege has been removed in versions v2.9.0 and later. In addition to correcting the access control boundary, version 2.9.0 includes the following hardening measures: opt-in default and format and validation modernization. As a workaround, one may mitigate exposure by taking either or all of the following steps. Revoke Scoped Permissions: Remove the `api-v2-system-restapi-settings-sync-post` privilege from all non-administrative users. Apply ACLs: Configure REST API Access Control Lists (ACLs) and/or firewall rules to restrict access to API endpoints exclusively to trusted administrator and HA peer IP addresses.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-21
Last Modified
2026-10-21
Generated
2026-11-10
AI Q&A
2026-10-21
EPSS Evaluated
2026-11-09
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
pfrest pfSense-pkg-RESTAPI < 2.9.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a privilege escalation vulnerability in the pfSense REST API package before version 2.9.0. It allows authenticated users with a specific 'settings sync' permission to modify REST API secrets, including the JWT signing secret. This enables them to forge administrative session tokens and gain full administrator privileges.

Detection Guidance

Check the installed version of pfSense-pkg-RESTAPI using the pfSense package manager. If the version is below 2.9.0, the system is vulnerable. Run: pkg info pfSense-pkg-RESTAPI. Also review user permissions for the api-v2-system-restapi-settings-sync-post privilege via the pfSense web interface under System > User Manager.

Inspect API access logs for unauthorized attempts to modify REST API configuration secrets. Look for POST requests to /api/v2/system/restapi/settings/sync from non-administrative users.

Impact Analysis

An attacker with a non-administrative account could exploit this to escalate privileges to full administrator. This could lead to unauthorized system access, configuration changes, or data breaches. The impact includes high confidentiality, integrity, and availability risks.

Compliance Impact

This vulnerability could lead to unauthorized privilege escalation, potentially allowing non-administrative users to gain full administrative access. This may result in unauthorized access to sensitive data, violating confidentiality requirements under GDPR and HIPAA. Non-compliance risks include data breaches, unauthorized modifications, and failure to maintain proper access controls.

Mitigation Strategies

Upgrade pfSense-pkg-RESTAPI to version 2.9.0 or later immediately. Revoke the api-v2-system-restapi-settings-sync-post privilege from all non-administrative users. Configure REST API ACLs to restrict access to trusted administrator and HA peer IP addresses only.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-113779. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...