CVE-2026-116235 Oray Pugongying X5 Pro L2TP Authentication crlf injection
Critical 9.4
Published
Updated
Check this codebase for CVE-2026-116235 and fix it if it is affected.
What it is: CVE-2026-116235 is a critical vulnerability in Oray Pugongying X5 Pro, published on 26 Oct 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116235 exists.
Affected product: Oray Pugongying X5 Pro. 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-116235/ (Markdown: https://insights.sbomify.com/CVE-2026-116235/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-116235?
CVE-2026-116235 is a critical vulnerability in Oray Pugongying X5 Pro, published on 26 Oct 2026.
Official description
A flaw has been found in Oray Pugongying X5 Pro 7.6.1. Affected by this vulnerability is an unknown functionality of the component L2TP Authentication. This manipulation of the argument Username causes crlf injection. The attack may be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Which versions are affected by CVE-2026-116235?
How do I fix CVE-2026-116235?
No fix has been published for CVE-2026-116235 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-116235 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116235 exists.
Sources
Also known as GHSA-7qf3-fxvm-8v87.