{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-63442 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-63442 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-63442 is a high-severity vulnerability in opnsense core, published on 15 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63442 and fix it if it is affected.\n\nWhat it is: CVE-2026-63442 is a high-severity vulnerability in opnsense core, published on 15 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-63442 in the wild and no public exploit code.\n\nAffected product: opnsense core. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-63442/ (Markdown: https://insights.sbomify.com/CVE-2026-63442/index.md)","id":"CVE-2026-63442","markdown":"https://insights.sbomify.com/CVE-2026-63442/index.md","name":"CVE-2026-63442","record":{"aliases":["GHSA-2v2x-m4j7-76pv"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OPNsense firewall","requires_auth":"none","summary":"Unauthenticated attackers can inject CRLF characters into the login username to forge syslog entries, blocking legitimate IPs or bypassing lockout mechanisms.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-117","name":"Improper Output Neutralization for Logs"}],"description":"OPNsense is a FreeBSD based firewall and routing platform. Prior to version 26.1.11, the unauthenticated WebGUI login usernamefld accepts carriage-return and line-feed characters that survive LOG_AUTH processing through syslog-ng-lockout.conf into the syslog-ng program destination feeding lockout_handler. The consumer's readline() processing treats an injected fragment as a separate authentication event and selects the first syntactically valid IP address from the forged line. An attacker with network access to the login page can forge failure events for another IP, causing that IP to be added to the sshlockout PF table and its active states to be killed, or forge accepted events that reset an attacker's own brute-force counter. This can block administrative, DNS, gateway, or monitoring addresses and can bypass password-guessing lockout without authentication. This issue is fixed in version 26.1.11.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"OPNsense: Log Forgery via Login Username CRLF in WebGUI Authentication → Pf Table IP Blocking","id":"CVE-2026-63442","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Coder: Workspace agent API insecure redirect handling allowed cross-agent file read and write","id":"CVE-2026-63443"},"packages":[],"prev":{"headline":"Mail: Email address spoofing via malformed RFC 2047 encoded-words","id":"CVE-2026-63435"},"products":["core"],"published":"2026-10-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["opnsense"]},"summary":"Unauthenticated attackers can inject CRLF characters into the login username to forge syslog entries, blocking legitimate IPs or bypassing lockout mechanisms.","url":"https://insights.sbomify.com/CVE-2026-63442/"}