CVE-2026-116234

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

GHSA-m5vr-m4x4-w4g9 ↗EUVD-2026-109658 ↗

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-2634Zero's internal tracking ID, independent of the CVE number., permanent identifier
19msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h48m
0
+4h
+6h
+8h
+10h
+12h

description

Pugongying X5 Pro firmware 7.6.1 is affected by CRLF injection in IPsec policy handling. A remote, high-privileged authenticated attacker may be able to alter generated IPsec configuration content through the affected setting.

mitigation

Restrict device management and IPsec policy configuration access to trusted administrators on isolated networks, and limit IPsec policy changes where feasible. Monitor Oray for updated firmware; no fixed release is recorded in the supplied package data.

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
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 08:30Z
Δ 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:30Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2634",
  "cve_id": "CVE-2026-116234",
  "display_id": "CVE-2026-116234",
  "ghsa_id": "GHSA-m5vr-m4x4-w4g9",
  "euvd_id": "EUVD-2026-109658",
  "status": "published",
  "anchor_state": "anchored",
  "title": "CRLF injection in Pugongying X5 Pro IPsec policy handling",
  "summary": "Pugongying X5 Pro firmware 7.6.1 is affected by CRLF injection in IPsec policy handling. A remote, high-privileged authenticated attacker may be able to alter generated IPsec configuration content through the affected setting.",
  "mitigation": "Restrict device management and IPsec policy configuration access to trusted administrators on isolated networks, and limit IPsec policy changes where feasible. Monitor Oray for updated firmware; no fixed release is recorded in the supplied package data.",
  "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": 18.446938,
  "t0_at": "2026-10-26T08:30:20.627000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T08:30:20.627000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T08:30:20.627000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-116234"
    }
  }
}

published 2026-10-26 08:42Z
last change 2026-10-26 10:24Z

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.