Netgate pfSense CE 2.7.0 through 2.9.0 OS Command Injection via interfaces_qinq_edit.php
Affects pfSense CE 2.7.0 through 2.9.0 for users with a WebGUI session holding the page-interfaces-qinq-edit privilege. Netgate's vendor rating is not given here, and no fix is listed.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
Netgate pfSense CE firewall software is affected. An authenticated user with QinQ interface editing privileges can inject operating system commands through the parent interface name, which can run as root and fully take over the firewall.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Netgate pfSense CE 2.7.0 through 2.9.0 contains an OS command injection vulnerability that allows authenticated users with QinQ edit privilege to run commands by storing an unvalidated parent interface name. Attackers can save a crafted 'if' value, then edit the QinQ entry so it is interpolated into ifconfig shell commands, executing commands as root.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Netgate pfSense CE
From 2.7.0 · through 2.9.0
References 7
GitHub · abraxas/pfsense-qinq-parent-if
abraxaslabs.tech
GitHub · pfsense/pfsense
Questions about CVE-2026-111214
What does this mean?
The QinQ edit page stores a parent interface name without checking that the interface exists. That name is later passed unescaped into shell commands in the member add and remove paths, which can give the attacker a root shell.Source: github.com
Am I affected, and how do I check?
The listed range is pfSense CE 2.7.0 through 2.9.0, and the source names the 2.9.0-DEVELOPMENT build (9363ac5) QinQ edit as affected. The bug needs a WebGUI session with the page-interfaces-qinq-edit privilege, which can be checked under System > User Manager, and the running version appears on the dashboard or under System > Update.Source: github.com
What should I do about it?
No fixed release is named in the checked facts, so no upgrade target can be given. Check Netgate's advisory for a fixed version and update to it when one is published.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
Limit who holds the page-interfaces-qinq-edit privilege, removing it from users who do not need to edit QinQ interfaces. Restricting WebGUI access to trusted administrators also reduces exposure to this issue.Source: github.com