SECURITYCRITICALCVE-2026-116233

CVE-2026-116233 — Oray Pugongying X5 Pro Dnsmasq CRLF Injection

A CVSS 9.1 CRLF injection in the Dnsmasq component of Oray Pugongying X5 Pro 7.6.1 via the rent_time argument. A public exploit exists; no fix is reported.

Dylan H.

Security Team

October 27, 2026
2 min read
CVE-2026-116233 — Oray Pugongying X5 Pro Dnsmasq CRLF Injection

Critical severity

Rated critical. Prioritise patching — see the remediation guidance below.

Affected Products

  • Oray Pugongying X5 Pro 7.6.1

Executive Summary

CVE-2026-116233 is a CRLF injection vulnerability in the Dnsmasq component of Oray Pugongying X5 Pro 7.6.1. Manipulating the rent_time argument lets an attacker inject carriage-return and line-feed sequences into generated configuration. The attack can be launched remotely and a public exploit has been disclosed. The vendor was contacted early and did not respond, and no fixed version is reported.

This is one of several sibling CRLF injection flaws published against the same product and version on October 26, 2026.

Vulnerability Overview

AttributeValue
CVE IDCVE-2026-116233
CVSS 3.19.1 (Critical)
CVSS 4.0 (VulDB)9.4
TypeCRLF Injection (CWE-74, CWE-93)
ComponentDnsmasq, rent_time argument
Attack VectorNetwork
Privileges RequiredHigh
Exploit AvailableYes (public)
Known ExploitedNot reported
Patch AvailableNo vendor response

Both scores assume an attacker with high privileges on the device. Some commentary describes the issue as remote code execution; the official description only says CRLF injection, so treat that claim as unconfirmed.

Affected Products

ProductVersionStatus
Oray Pugongying X5 Pro7.6.1Vulnerable, no fix reported
CVEComponent
CVE-2026-116234IPsec Policy Handler (secproto)
CVE-2026-116235L2TP Authentication (Username)
CVE-2026-116231Ser2net
CVE-2026-116232SNMP Handler
CVE-2026-116237Dnsmasq

Mitigation

  1. Do not expose the device management interface to the internet or untrusted networks.
  2. Restrict administrative access to a dedicated management VLAN and trusted hosts, and use strong, unique admin credentials, since exploitation needs elevated privileges.
  3. Review DHCP and DNS settings for unexpected values, especially lease time fields containing unusual characters.
  4. Monitor the vendor and VulDB entry for a patched release, and consider replacing the device if none is issued.

References