# CVE-2026-116231: Oray Pugongying X5 Pro Ser2net crlf injection


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-wf66-wf8x-2jx2

## What is CVE-2026-116231?

CVE-2026-116231 is a critical vulnerability in Oray Pugongying X5 Pro, published on 26 Oct 2026. 

### Official description

A security flaw has been discovered in Oray Pugongying X5 Pro 7.6.1. The impacted element is an unknown function of the component Ser2net. Performing a manipulation of the argument regmsg results in crlf injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-116231?


## How do I fix CVE-2026-116231?

No fix has been published for CVE-2026-116231 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116231 being exploited?

There is no known exploitation of CVE-2026-116231 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116231 and fix it if it is affected.

What it is: CVE-2026-116231 is a critical vulnerability in Oray Pugongying X5 Pro, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116231 in the wild and no public exploit code.

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-116231/ (Markdown: https://insights.sbomify.com/CVE-2026-116231/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116231
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116231
- OSV: https://osv.dev/vulnerability/CVE-2026-116231

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116231/
Summaries are generated and may contain mistakes; the official description above is the record.