CVE-2026-116808

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

GHSA-j23v-hgjh-xpmx ↗EUVD-2026-110516 ↗

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.
Openpanel-dev openpanel < 3.0.0
fixed in 3.0.0
ETK-2026-2712Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 19msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h41m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

OpenPanel versions before 3.0.0 are affected by an SQL injection flaw in profile value handling. An authenticated user may use crafted property input to bypass project isolation and read data from other tenants.

mitigation

Upgrade OpenPanel to version 3.0.0 or later. Until upgrading, restrict access to authenticated users and limit exposure of the affected profile-value functionality where feasible.

fixed in 3.0.0

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
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 23:05Z
Δ 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 23:05Z
    ghsa: trigger signal, started the run
  2. 2026-10-26 23:05Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2712",
  "cve_id": "CVE-2026-116808",
  "display_id": "CVE-2026-116808",
  "ghsa_id": "GHSA-j23v-hgjh-xpmx",
  "euvd_id": "EUVD-2026-110516",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in OpenPanel profile value handling",
  "summary": "OpenPanel versions before 3.0.0 are affected by an SQL injection flaw in profile value handling. An authenticated user may use crafted property input to bypass project isolation and read data from other tenants.",
  "mitigation": "Upgrade OpenPanel to version 3.0.0 or later. Until upgrading, restrict access to authenticated users and limit exposure of the affected profile-value functionality where feasible.",
  "vendor": "Openpanel-dev",
  "product": "openpanel",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 3.0.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.0.0"
      ],
      "package_name": "openpanel",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 35.58723585,
  "t0_at": "2026-10-26T23:05:38.546000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T23:05:38.546000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T23:05:38.546000+00:00",
      "url": "https://github.com/advisories/GHSA-j23v-hgjh-xpmx"
    }
  }
}

published 2026-10-27 01:10Z
last change 2026-10-27 06:05Z

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.