OPNsense core before 26.7.8 Lockout IP Planting via WebGUI Login Username (CVE-2026-119423)
Published Last modified Sources: CVE.org
What is affected, what to do
OPNsense core before 26.7.8 contains a log injection vulnerability that allows unauthenticated attackers to plant victim IP addresses in the lockout_handler by submitting crafted WebGUI login usernames. Attackers can submit usernames like 'Invalid user <victim-ip>' repeatedly to add the victim to the sshlockout table, blocking SSH and WebGUI access and killing its pf states.
Update Opnsense Core to version 26.7.8.
- Affected
- Opnsense Core
lt *..26.7.8
- Opnsense Core
- Fixed in
- Opnsense Core
26.7.8
- Opnsense Core
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
6.9
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v4
5.3
CVSS v3
Severity Medium on the scale from 0 to 10.
Source: CVE.org
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Medium
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 64.50 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 6.9 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 5.3
CVSS v4
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 6.9
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-117
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
OPNsense core before 26.7.8 contains a log injection vulnerability that allows unauthenticated attackers to plant victim IP addresses in the lockout_handler by submitting crafted WebGUI login usernames. Attackers can submit usernames like 'Invalid user <victim-ip>' repeatedly to add the victim to the sshlockout table, blocking SSH and WebGUI access and killing its pf states.
Source: cvelistv5, NVD (NIST)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| opnsense | core |
|
|
Vendors and products
Weakness classes (CWE)
CWE-117Improper Output Neutralization for Logs
Base
The product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file.
Entry at MITRE CWE-117
References & sources
- abraxaslabs.techresearch/opnsense-lockout-factory-ipThird-party advisory
- github.comopnsense/coreProduct
- github.comopnsense/core/blob/26.7.7/src/opnsense/mvc/app/library/OPNsense…Technical description
- github.comopnsense/core/blob/26.7.7/src/opnsense/scripts/syslog/lockout_h…Technical description
- github.comopnsense/core/commit/14f8f7dd1d5f06522d60794a7beeac7adb9eca68Patch
- github.comopnsense/core/commit/2076f2c195bf9537ec220f0e5d6aff998f057410Patch
- github.comGitHub Security Advisory (GHSA-2v2x-m4j7-76pv)Vendor advisory
- vulncheck.comVulnCheck Advisory: OPNsense core before 26.7.8 Lockout IP Planting via WebGUI Login UsernameThird-party advisory
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
ReceivedVulnCheck
CVSS V4.0: AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Weakness type: CWE-117
Description added or changed
New references:- https://abraxaslabs.tech/research/opnsense-lockout-factory-ip
- https://github.com/opnsense/core
- https://github.com/opnsense/core/blob/26.7.7/src/opnsense/mvc/app/library/OPNsense/Auth/AuthenticationFactory.php#L232
- https://github.com/opnsense/core/blob/26.7.7/src/opnsense/scripts/syslog/lockout_handler#L70
and 4 more references
Show 13 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —OPNsense core before 26.7.8 contains a log injection vulnerability that allows unauthenticated attackers to plant victim IP addresses in the lockout_handler by submitting crafted WebGUI login usernames. Attackers can submit usernames like 'Invalid user <victim-ip>' repeatedly to add the victim to the sshlockout table, blocking SSH and WebGUI access and killing its pf states.CVSS added —AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS added —AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LWeakness type (CWE) added —CWE-117Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/119xxx/CVE-2026-119423.json">CVE-2026-119423</a>Reference added —https://abraxaslabs.tech/research/opnsense-lockout-factory-ipReference added —https://github.com/opnsense/coreReference added —https://github.com/opnsense/core/blob/26.7.7/src/opnsense/mvc/app/library/OPNsense/Auth/AuthenticationFactory.php#L232Reference added —https://github.com/opnsense/core/blob/26.7.7/src/opnsense/scripts/syslog/lockout_handler#L70Reference added —https://github.com/opnsense/core/commit/14f8f7dd1d5f06522d60794a7beeac7adb9eca68Reference added —https://github.com/opnsense/core/commit/2076f2c195bf9537ec220f0e5d6aff998f057410Reference added —https://github.com/opnsense/core/security/advisories/GHSA-2v2x-m4j7-76pvReference added —https://www.vulncheck.com/advisories/opnsense-core-before-26.7.8-lockout-ip-planting-via-webgui-login-usernameSource identifier: disclosure@vulncheck.com
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-119423"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-119423.svg?lang=en" alt="CVE-2026-119423 – NEOSEC Intel" height="20"></a>