Skip to main content

OPNsense EUVDEUVD-2026-30185

| CVE-2026-44195 MEDIUM
Improper Restriction of Excessive Authentication Attempts (CWE-307)
2026-05-13 security-advisories@github.com
6.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify exposed OPNsense management interface
  2. Delivery
    Send crafted username containing 'Accepted' keyword
  3. Exploit
    lockout_handler resets failure counter for attacker IP
  4. Execution
    Resume brute-force credential attempts without lockout
  5. Persist
    Guess valid administrative credentials
  6. Impact
    Gain authenticated access to firewall administration

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Brute-force prevention, rate limiting
Exploitation Conditions

No special configuration is required beyond network reachability of the OPNsense authentication endpoint (web management UI or SSH). The CVSS vector PR:N confirms exploitation is unauthenticated. The vulnerability is present in the default OPNsense lockout_handler logic for all core versions prior to 26.1.7 and does not depend on any non-default feature being enabled. Exploitation is limited by two factors: (1) the attacker must be able to reach the authentication interface over the network - organizations that restrict management interface access to internal or trusted IP ranges are not exposed; and (2) successful exploitation of the lockout bypass alone does not grant access - the attacker must additionally succeed at credential guessing, meaning accounts protected by strong, unique passwords are not at direct risk from this flaw in isolation.

Impact

Despite a moderate CVSS base score of 5.3, the real-world risk to internet-facing OPNsense deployments is meaningfully elevated by several converging signals. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms the attack is fully remote, requires no privileges, no user interaction, and low complexity - characteristics that favor opportunistic automated attacks. SSVC classifies the attack as automatable with partial technical impact, and a public proof-of-concept exists (referenced gist at github.com/sopex). Critically, this vulnerability is not a standalone authentication bypass - its impact is as an enabler: by neutralizing the lockout control, it exposes the target to unbounded password guessing, which on weak or reused credentials could lead to full administrative compromise of the firewall. The EPSS score of 0.03% (10th percentile) is notably low given the POC existence and automatable classification, suggesting that mass exploitation has not been observed at the time of scoring - however, OPNsense is commonly deployed as an internet-edge device, and credential attacks against firewall management interfaces are a well-documented threat pattern. There is no conflict in the data signals, but the low EPSS should not be interpreted as low inherent risk for organizations with weak administrative credentials or externally exposed management interfaces.

Exploit ScenarioDerived

An attacker identifies an internet-facing OPNsense firewall with its management web interface or SSH exposed. They initiate an automated credential-stuffing or dictionary attack, but between each failed login attempt, they submit a login request using a crafted username string such as 'Accepted' or 'Successful login', which causes the lockout_handler to reset the failure counter for the attacker's IP. A public proof-of-concept gist demonstrates this technique, enabling the attacker to cycle through password lists indefinitely without triggering the lockout threshold, ultimately achieving authentication if the target account uses a weak or previously breached password.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 08, 2026

Brute-force lockout bypass in OPNsense prior to 26.1.7 allows unauthenticated remote attackers to indefinitely circumvent the authentication failure counter, enabling unlimited credential guessing against any network-accessible login endpoint. The flaw resides in the lockout_handler logic, which interprets attacker-controlled username strings containing the keywords 'Accepted' or 'Successful login' as success signals and resets the IP-based failure counter. A publicly available proof-of-concept exploit exists (SSVC exploitation: poc), the attack is classified as automatable with no prerequisites beyond network reach, and no active exploitation is confirmed in CISA KEV. EPSS is low at 0.03% (10th percentile), suggesting limited observed exploitation at time of analysis.

RemediationAI

Upgrade OPNsense core to version 26.1.7 or later, which contains the vendor-released fix as confirmed by the GitHub Security Advisory GHSA-h3vx-4q27-rc42. If immediate patching is not possible, restrict network access to the OPNsense management interface (web UI, SSH) using firewall rules that limit authentication endpoints to trusted IP ranges only - this directly eliminates the attacker's ability to reach the lockout_handler from untrusted networks, removing exploitability entirely. As an additional compensating control, enforce strong, unique administrative credentials and consider enabling multi-factor authentication if supported, which would render successful brute-force attempts ineffective even if the lockout bypass is exploited. Note that restricting the management interface is a low-risk mitigation with minimal operational trade-off, as OPNsense management interfaces should not be exposed to the public internet under standard hardening guidance.

Affected VersionsENISA

core < 26.1.7

Affected Packages

euvd core fix: 26.1.7

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

OPNsense is a FreeBSD-based open-source firewall and routing platform (CPE: cpe:2.3:a:opnsense:opnsense:*:*:*:*:*:*:*:*). The root cause is CWE-307 - Improper Restriction of Excessive Authentication Attempts - specifically a logic flaw in the lockout_handler component responsible for tracking and enforcing authentication failure thresholds per source IP. The handler appears to parse log-like strings or username fields and triggers a counter reset upon detecting success-indicative keywords ('Accepted', 'Successful login'), a pattern common in log-scraping implementations that mistakenly trust attacker-supplied input as a signal of successful authentication. This design conflates attacker-controlled input with internal authentication state, allowing the attacker to continuously suppress the failure counter by interleaving crafted username strings between legitimate brute-force login attempts. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N reflects network reachability with no authentication or complexity barriers, yielding only partial confidentiality impact because the flaw itself does not grant access - it merely removes the rate-limiting control that would otherwise prevent credential enumeration.

Know when Opnsense gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

2
CVSS changed
Oct 26, 2026 - 14:38 NVD
5.3 (MEDIUM) 6.5 (MEDIUM)
Patch available
May 13, 2026 - 23:17 EUVD

DescriptionNVD

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.

Threat Intelligence Overview

EPSS Score
0.0%
Top 90% exploitable
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2023-39004 CRITICAL POC
9.8 Aug 09

Insecure permissions in the configuration directory (/conf/) of OPNsense Community Edition before 23.7 and Business Edit

CVE-2023-27152 CRITICAL POC
9.8 Oct 23

DECISO OPNsense 23.1 does not impose rate limits for authentication, allowing attackers to perform a brute-force attack

CVE-2023-39008 CRITICAL POC
9.8 Aug 09

A command injection vulnerability in the component /api/cron/settings/setJob/ of OPNsense Community Edition before 23.7

CVE-2023-39001 CRITICAL POC
9.8 Aug 09

A command injection vulnerability in the component diag_backup.php of OPNsense Community Edition before 23.7 and Busines

CVE-2023-39007 CRITICAL POC
9.6 Aug 09

/ui/cron/item/open in the Cron component of OPNsense Community Edition before 23.7 and Business Edition before 23.4.2 al

CVE-2023-39003 HIGH POC
7.5 Aug 09

OPNsense Community Edition before 23.7 and Business Edition before 23.4.2 was discovered to contain insecure permissions

CVE-2023-39005 HIGH POC
7.5 Aug 09

Insecure permissions exist for configd.socket in OPNsense Community Edition before 23.7 and Business Edition before 23.4

CVE-2023-38997 HIGH POC
7.2 Aug 09

A directory traversal vulnerability in the Captive Portal templates of OPNsense Community Edition before 23.7 and Busine

CVE-2023-38999 MEDIUM POC
6.5 Aug 09

A Cross-Site Request Forgery (CSRF) in the System Halt API (/system/halt) of OPNsense Community Edition before 23.7 and

CVE-2019-25373 MEDIUM POC
6.4 Feb 15

OPNsense 19.1 contains a stored cross-site scripting vulnerability that allows authenticated attackers to inject malicio

CVE-2019-25369 MEDIUM POC
6.4 Feb 15

OPNsense 19.1 contains a stored cross-site scripting vulnerability in the system_advanced_sysctl.php endpoint that allow

CVE-2019-25372 MEDIUM POC
6.1 Feb 15

OPNsense 19.1 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject ma

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy