CVE-2026-44195: opnsense core · Improper Restriction of Excessive Authentication Attempts
Affects opnsense coreSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 26.1.7 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 26.1.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade core and opnsense/core to 26.1.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| opnsensecore | Affected
| Fixed in
|
GitHubopnsense/corepkg:github/opnsense/coreOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade OPNsense core to version 26.1.7 or later, where this vulnerability is fixed. No other official remediation or temporary workaround is indicated. Patch status is confirmed fixed in 26.1.7.
Description
A logic flaw in OPNsense core versions prior to 26.1.7 allows an unauthenticated attacker to bypass the authentication failure lockout mechanism. By submitting a crafted username containing success keywords between brute-force attempts, the attacker can reset the failure counter for their IP address, preventing lockout. This vulnerability is identified as CWE-307 and has a CVSS score of 5.3 (medium severity). The issue is fixed in version 26.1.7.