CVE-2026-73696

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

GHSA-pqwj-3fcg-h8pr ↗EUVD-2026-115228 ↗

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.
Control Web Panel < 1.12
fixed in 1.12
CWE-698 Execution After Redirect (EAR)
ETK-2026-3287Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 23msince last run
33mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h27m
0
+4h
+6h
+8h
+10h
+12h

description

Control Web Panel versions earlier than 1.12 are affected in the user-panel login flow. A remote attacker may access panel functionality without completing authentication; the available evidence is inconsistent on whether knowledge of a valid hosting username is a prerequisite.

mitigation

Upgrade Control Web Panel to version 1.12 or later. Restrict public access to the user panel until the upgrade is complete.

fixed in 1.12

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
33m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-02 14:52Z
Δ 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-02 14:52Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3287",
  "cve_id": "CVE-2026-73696",
  "display_id": "CVE-2026-73696",
  "ghsa_id": "GHSA-pqwj-3fcg-h8pr",
  "euvd_id": "EUVD-2026-115228",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass from redirect handling in Control Web Panel",
  "summary": "Control Web Panel versions earlier than 1.12 are affected in the user-panel login flow. A remote attacker may access panel functionality without completing authentication; the available evidence is inconsistent on whether knowledge of a valid hosting username is a prerequisite.",
  "mitigation": "Upgrade Control Web Panel to version 1.12 or later. Restrict public access to the user panel until the upgrade is complete.",
  "vendor": "Control Web Panel",
  "product": "Control Web Panel",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.12"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.12"
      ],
      "package_name": "Control Web Panel",
      "purl": null
    }
  ],
  "cwes": [
    698
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 33.23331385,
  "t0_at": "2026-11-02T14:52:29.886000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-02T14:52:29.886000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-02T14:52:29.886000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-73696"
    }
  }
}

published 2026-11-02 15:14Z
last change 2026-11-02 18:25Z

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.