CVE-2026-123029

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

GHSA-g54c-2vxv-4cp8 ↗EUVD-2026-117386 ↗

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.
Wowza Streaming Engine < 4.12.2
fixed in 4.12.2
CWE-611 Improper Restriction of XML External Entity Reference
ETK-2026-3594Zero's internal tracking ID, independent of the CVE number., permanent identifier
12h 22msince last run
25mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h43m
0
+2h
+6h
+8h
+10h
+12h

description

Wowza Streaming Engine versions before 4.12.2 are affected by an XML external entity injection flaw. An unauthenticated remote attacker may read local files accessible to the Streaming Engine process if they can submit XML that the engine processes.

mitigation

Upgrade Wowza Streaming Engine to version 4.12.2 or later. Until upgrading, restrict untrusted access to interfaces or workflows that accept and process XML.

fixed in 4.12.2

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
25m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-05 06:45Z
Δ 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-11-05 06:45Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3594",
  "cve_id": "CVE-2026-123029",
  "display_id": "CVE-2026-123029",
  "ghsa_id": "GHSA-g54c-2vxv-4cp8",
  "euvd_id": "EUVD-2026-117386",
  "status": "published",
  "anchor_state": "anchored",
  "title": "XML external entity injection in Wowza Streaming Engine",
  "summary": "Wowza Streaming Engine versions before 4.12.2 are affected by an XML external entity injection flaw. An unauthenticated remote attacker may read local files accessible to the Streaming Engine process if they can submit XML that the engine processes.",
  "mitigation": "Upgrade Wowza Streaming Engine to version 4.12.2 or later. Until upgrading, restrict untrusted access to interfaces or workflows that accept and process XML.",
  "vendor": "Wowza",
  "product": "Streaming Engine",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 4.12.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.12.2"
      ],
      "package_name": "Streaming Engine",
      "purl": null
    }
  ],
  "cwes": [
    611
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 24.736342033333333,
  "t0_at": "2026-11-05T06:45:37.554000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T06:45:37.554000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T06:45:37.554000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-123029"
    }
  }
}

published 2026-11-05 06:54Z
last change 2026-11-05 22: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.