OPNsense 26.1 'Witty Woodpecker'
OPNsense 26.1 'Witty Woodpecker'
The OPNsense 26.1 'Witty Woodpecker' reached end of service life on Jul 15, 2026 — OPNsense no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your OPNsense 26.1 'Witty Woodpecker' incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- opnsense
- release
- 26.1
- product Label
- OPNsense
- release Label
- 26.1 'Witty Woodpecker'
- codename
- Witty Woodpecker
- lts
- latest Version
- 26.1.11
- release Date
- 2026-01-28
- maintained
- source Url
- https://endoflife.date/opnsense
Lifecycle Dates
- End of Service Life
- Jul 15, 2026
- Last OEM Support
- Jul 15, 2026
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for OPNsense 26.1 'Witty Woodpecker' — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for OPNsense 26.1 'Witty Woodpecker'?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for OPNsense 26.1 'Witty Woodpecker' when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
OPNsense 26.1 'Witty Woodpecker' Support: Frequently Asked Questions
Is the OPNsense 26.1 'Witty Woodpecker' still supported?
OPNsense ended support for the OPNsense 26.1 'Witty Woodpecker' on Jul 15, 2026 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the OPNsense 26.1 'Witty Woodpecker' end of service life (EOSL) date?
OPNsense lists the end of service life for the OPNsense 26.1 'Witty Woodpecker' as Jul 15, 2026.
Can I keep using the OPNsense 26.1 'Witty Woodpecker' after its EOSL date?
Yes. EOSL means OPNsense stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the OPNsense 26.1 'Witty Woodpecker' cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting OPNsense 26.1 'Witty Woodpecker'
6 published CVEs affect the OPNsense 26.1 'Witty Woodpecker', including 4 rated critical or high severity. OPNsense no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2026-45158 | CRITICAL | 9.1 | May 13, 2026 | OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.8, unsanitized user input is passed to the DHCP configuration of the configured interface, which is processed by a shell script, allowing remote code execution as root on the underlying operating system. This vulnerability is fixed in 26.1.8. |
| CVE-2026-44194 | CRITICAL | 9.1 | May 13, 2026 | OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.8, an authenticated Remote Code Execution (RCE) vulnerability in the OPNsense core allows a user with user-management privileges to execute arbitrary system commands as root. An attacker can bypass input validation by formatting their malicious payload as a compliant email address, allowing shell commands to reach the underlying operating system. The flaw exists in the local user synchronization flow, within core/src/opnsen |
| CVE-2026-44193 | CRITICAL | 9.1 | May 13, 2026 | OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.7, the XMLRPC method opnsense.restore_config_section fails to sanitize user supplied input leading to Remote Code Execution. This vulnerability is fixed in 26.1.7. |
| CVE-2026-34578 | HIGH | 8.2 | Apr 9, 2026 | OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.6, OPNsense's LDAP authentication connector passes the login username directly into an LDAP search filter without calling ldap_escape(). An unauthenticated attacker can inject LDAP filter metacharacters into the username field of the WebGUI login page to enumerate valid LDAP usernames in the configured directory. When the LDAP server configuration includes an Extended Query to restrict login to members of a specific group, |
| CVE-2026-30868 | MEDIUM | 6.3 | Mar 11, 2026 | OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.4, multiple OPNsense MVC API endpoints perform state‑changing operations but are accessible via HTTP GET requests without CSRF protection. The framework CSRF validation in ApiControllerBase only applies to POST/PUT/DELETE methods, allowing authenticated GET requests to bypass CSRF verification. As a result, a malicious website can trigger privileged backend actions when visited by an authenticated user, causing unintended s |
| CVE-2026-44195 | MEDIUM | 5.3 | May 13, 2026 | OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.7, a logic flaw in the OPNsense lockout_handler allows an unauthenticated attacker to continuously reset the authentication failure counter for their IP address. By interjecting a crafted username containing a success keyword ("Accepted" or "Successful login") between normal brute-force attempts, an attacker can prevent the failure counter from ever reaching the lockout threshold. This vulnerability is fixed in 26.1.7. |