CVE-2026-119424 OPNsense before 26.7.8 Wireless WPA Configuration Line Injection via Identity
Medium 6.1
Published
Updated
Check this codebase for CVE-2026-119424 and fix it if it is affected.
What it is: CVE-2026-119424 is a medium-severity vulnerability in opnsense core, published on 30 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-119424 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-119424/ (Markdown: https://insights.sbomify.com/CVE-2026-119424/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-119424?
CVE-2026-119424 is a medium-severity vulnerability in opnsense core, published on 30 Oct 2026.
Official description
OPNsense core before 26.7.8 contains a configuration line injection vulnerability that allows authenticated users with wireless-edit privilege to inject directives by embedding CR/LF characters in WPA fields. Attackers can place newlines in wpa.identity, wpa.passphrase, or RADIUS shared secrets to append arbitrary wpa_supplicant or hostapd directives loaded by root-run daemons.
Weakness: CWE-93
Which versions are affected by CVE-2026-119424?
How do I fix CVE-2026-119424?
No fix has been published for CVE-2026-119424 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-119424 being exploited?
There is no known exploitation of CVE-2026-119424 in the wild and no public exploit code.
Sources
Also known as GHSA-r639-jmpp-wf8p.