CVE-2026-116233

waiting for further signalsZero needs more public information before it can validate it.

GHSA-xq2m-vg83-g4j7 ↗EUVD-2026-109657 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Oray Pugongying X5 Pro 7.6.1
CWE-93 Improper Neutralization of CRLF Sequences ('CRLF Injection')
ETK-2026-2635Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 02msince last run
41mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h24m
0
+4h
+6h
+8h
+10h
+12h

description

Oray Pugongying X5 Pro 7.6.1 is affected by CRLF injection in dnsmasq-related handling. A remote attacker with high privileges may inject unintended line breaks through the affected input; the evidence does not establish whether other versions are affected.

mitigation

Restrict device administration to trusted management hosts and limit privileged accounts to authorized administrators. Isolate affected devices from untrusted networks and monitor the vendor for a patched release.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
41m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 08:15Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-26 08:15Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-116233

{
  "etk_id": "ETK-2026-2635",
  "cve_id": "CVE-2026-116233",
  "display_id": "CVE-2026-116233",
  "ghsa_id": "GHSA-xq2m-vg83-g4j7",
  "euvd_id": "EUVD-2026-109657",
  "status": "published",
  "anchor_state": "anchored",
  "title": "CRLF injection in Oray Pugongying X5 Pro dnsmasq",
  "summary": "Oray Pugongying X5 Pro 7.6.1 is affected by CRLF injection in dnsmasq-related handling. A remote attacker with high privileges may inject unintended line breaks through the affected input; the evidence does not establish whether other versions are affected.",
  "mitigation": "Restrict device administration to trusted management hosts and limit privileged accounts to authorized administrators. Isolate affected devices from untrusted networks and monitor the vendor for a patched release.",
  "vendor": "Oray",
  "product": "Pugongying X5 Pro",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "7.6.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Pugongying X5 Pro",
      "purl": null
    }
  ],
  "cwes": [
    93
  ],
  "cvss_score": 9.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 41.09593288333333,
  "t0_at": "2026-10-26T08:15:14.847000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T08:15:14.847000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T08:15:14.847000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-116233"
    }
  }
}

published 2026-10-26 08:42Z
last change 2026-10-26 11:29Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.