Skip to main content
Vulnerability Database/CVE-2026-111227

CVE-2026-111227: pfSense CE CRLF Injection Vulnerability

CVE-2026-111227 is a CRLF injection flaw in pfSense CE that lets authenticated users manipulate DNS Resolver configurations by injecting malicious directives. This post covers its technical details, affected versions, and mitigation.

Published:

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-111227 Overview

CVE-2026-111227 is a Carriage Return Line Feed (CRLF) injection vulnerability in Netgate pfSense Community Edition through version 2.9.0. The flaw resides in services_unbound_acls.php and allows authenticated users holding the DNS Resolver: Access Lists privilege to inject arbitrary Unbound configuration directives. Attackers embed CR/LF characters in the aclname or aclaction fields, which are written unsanitized to access_lists.conf. Injected directives such as local-data, local-zone, or forward-zone let an attacker control DNS answers served to LAN clients. The weakness is tracked as [CWE-93] Improper Neutralization of CRLF Sequences.

Critical Impact

An authenticated administrator with ACL-management rights can poison DNS responses for every client that relies on the pfSense Unbound resolver, enabling traffic redirection and downstream phishing or man-in-the-middle attacks.

Affected Products

  • Netgate pfSense Community Edition versions through 2.9.0
  • Deployments exposing the services_unbound_acls.php web interface
  • Environments using the pfSense Unbound DNS Resolver with access lists configured

Discovery Timeline

  • 2026-10-15 - CVE-2026-111227 published to NVD
  • 2026-10-21 - Last updated in NVD database

Technical Details for CVE-2026-111227

Vulnerability Analysis

The pfSense web UI accepts user-supplied values for Unbound access list entries through services_unbound_acls.php. Those values flow into unbound.inc, which serializes them into the access_lists.conf file consumed by the Unbound resolver. The input handler fails to strip or reject carriage return (\r) and line feed (\n) characters in the aclname and aclaction fields. Because Unbound parses its configuration line by line, an injected newline terminates the current directive and begins a new one controlled by the attacker. The vulnerability requires the DNS Resolver: Access Lists privilege, so exploitation presumes a compromised or malicious administrator account rather than an unauthenticated external attacker.

Root Cause

The root cause is missing neutralization of CRLF sequences before configuration serialization. The code path that writes ACL entries treats the aclname and aclaction strings as opaque text and concatenates them directly into the Unbound configuration body. See the upstream Unbound ACL implementation and the services_unbound_acls.php handler for the vulnerable logic.

Attack Vector

An authenticated attacker submits an ACL create or edit request where aclname or aclaction contains encoded CR/LF bytes followed by Unbound directives such as local-zone: "example.com" redirect and local-data: "example.com A 203.0.113.10". When pfSense regenerates access_lists.conf and reloads Unbound, those directives take effect. From that point, DNS queries for the targeted zones return attacker-chosen answers, redirecting clients to attacker-controlled infrastructure. Additional technical analysis is available in the Abraxas Labs research write-up and the VulnCheck advisory.

Detection Methods for CVE-2026-111227

Indicators of Compromise

  • Unexpected local-data, local-zone, or forward-zone directives in /var/unbound/access_lists.conf that do not correspond to any ACL entry visible in the pfSense UI.
  • Audit log entries showing POST requests to services_unbound_acls.php from administrator accounts outside normal change windows.
  • DNS responses from the pfSense resolver that resolve legitimate domains to attacker-controlled IP addresses on LAN clients.

Detection Strategies

  • Diff the current access_lists.conf against a known-good baseline after every configuration change and alert on directives that were not generated by expected ACL entries.
  • Inspect pfSense web server logs for POST bodies to services_unbound_acls.php containing URL-encoded %0d or %0a byte sequences in the aclname or aclaction parameters.
  • Correlate Unbound reload events with configuration file hashes to identify silent injection of forwarding or redirect rules.

Monitoring Recommendations

  • Forward pfSense system and Unbound logs to a central Security Information and Event Management (SIEM) platform for longitudinal review.
  • Monitor outbound DNS resolution patterns from LAN clients for sudden shifts in resolved IP addresses for high-value domains.
  • Alert on any privilege assignment that grants DNS Resolver: Access Lists to non-administrative users.

How to Mitigate CVE-2026-111227

Immediate Actions Required

  • Audit all accounts that hold the DNS Resolver: Access Lists privilege and revoke it from any user that does not require it.
  • Review access_lists.conf for unexpected local-data, local-zone, or forward-zone directives and remove any that cannot be traced to a legitimate ACL entry.
  • Rotate credentials for any administrator account suspected of compromise and enforce multi-factor authentication on the pfSense web UI.

Patch Information

At the time of publication, no fixed version is listed in the NVD record for pfSense CE beyond 2.9.0. Monitor the VulnCheck advisory and Netgate release notes for an updated build that neutralizes CRLF characters in Unbound ACL inputs.

Workarounds

  • Restrict access to the pfSense administrative interface to a dedicated management network and block it from untrusted segments.
  • Disable Unbound access list management for all non-root accounts until a patched release is deployed.
  • Deploy file integrity monitoring on /var/unbound/access_lists.conf and trigger an alert on any modification not initiated by an approved change process.

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.