CVE-2026-119423 OPNsense core before 26.7.8 Lockout IP Planting via WebGUI Login Username
Medium 6.9
Published
Updated
Check this codebase for CVE-2026-119423 and fix it if it is affected.
What it is: CVE-2026-119423 is a medium-severity vulnerability in opnsense core, published on 30 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-119423 in the wild and no public exploit code.
Affected product: opnsense core. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-119423/ (Markdown: https://insights.sbomify.com/CVE-2026-119423/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-119423?
CVE-2026-119423 is a medium-severity vulnerability in opnsense core, published on 30 Oct 2026.
Official 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.
Weakness: CWE-117
Which versions are affected by CVE-2026-119423?
How do I fix CVE-2026-119423?
No fix has been published for CVE-2026-119423 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-119423 being exploited?
There is no known exploitation of CVE-2026-119423 in the wild and no public exploit code.
Sources
Also known as GHSA-m68j-m67p-c39j.