CVE-2026-116231
Oray Pugongying X5 Pro Ser2net crlf injection
- Critical 9.9
- A public exploit reference is listed
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.
Key facts
- Published
- 26 Oct 2026
- Last changed
- 2 Nov 2026
- Assigned by
- VulDB
- EPSS
- 0.436% likely to be exploited in the next 30 days, higher than 38.415% of CVEs (scores for 15 Nov 2026)
- SSVC (CISA)
- Exploitation: poc; Automatable: no; Technical impact: total
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 9.4CVSS 4.0, Criticalfrom the CNA (VulDB)
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 - 9.9CVSS 3.1, Criticalfrom the CNA (VulDB)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R - 9.9CVSS 3.0, Criticalfrom the CNA (VulDB)
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:R - 9.0CVSS 2.0, Highfrom the CNA (VulDB)
AV:N/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Oray | Pugongying X5 Pro |
|
Timeline
- 25 Oct 2026 Advisory disclosed
- 25 Oct 2026 VulDB entry created
- 25 Oct 2026 VulDB entry last update
- 26 Oct 2026 Published