Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 15 May 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opnsense opnsense
|
|
| CPEs | cpe:2.3:a:opnsense:opnsense:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Opnsense opnsense
|
Thu, 14 May 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
ssvc
|
Wed, 13 May 2026 23:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opnsense
Opnsense core |
|
| Vendors & Products |
Opnsense
Opnsense core |
Wed, 13 May 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | OPNsense: Authentication lockout bypass | |
| Weaknesses | CWE-307 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-14T13:46:30.721Z
Reserved: 2026-05-05T15:13:47.570Z
Link: CVE-2026-44195
Updated: 2026-05-14T13:46:18.566Z
Status : Analyzed
Published: 2026-05-13T22:16:43.820
Modified: 2026-05-15T16:06:30.720
Link: CVE-2026-44195
No data.
OpenCVE Enrichment
Updated: 2026-05-13T23:30:06Z