ETK-2026-3452Zero's internal tracking ID, independent of the CVE number.

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

GHSA-5w6j-qm42-4rc2 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
rust surrealdb < 4.0.0
fixed in 4.0.0
ETK-2026-3452Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:cargo/surrealdb
cvss7.0ethiack provisional
4h 44msince last run
31mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −15h27mwaiting for further signals−4h44m
−15h
−12h
−9h
−6h
−3h
0

description

SurrealDB versions before 4.0.0 may fail to enforce function capability restrictions when built-in functions are invoked through the embedded JavaScript bridge. An attacker able to run embedded JavaScript in an affected deployment could invoke built-in functions that their SurrealQL permissions would otherwise deny.

mitigation

Upgrade SurrealDB to version 4.0.0 or later. Until upgraded, restrict access to embedded JavaScript scripting and limit untrusted users' ability to execute scripts.

fixed in 4.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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-03 15:51Z

this entry in the feed

GET /api/v1/feed/ETK-2026-3452

{
  "etk_id": "ETK-2026-3452",
  "cve_id": null,
  "display_id": "ETK-2026-3452",
  "ghsa_id": "GHSA-5w6j-qm42-4rc2",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Function capability bypass in SurrealDB JavaScript scripting",
  "summary": "SurrealDB versions before 4.0.0 may fail to enforce function capability restrictions when built-in functions are invoked through the embedded JavaScript bridge. An attacker able to run embedded JavaScript in an affected deployment could invoke built-in functions that their SurrealQL permissions would otherwise deny.",
  "mitigation": "Upgrade SurrealDB to version 4.0.0 or later. Until upgraded, restrict access to embedded JavaScript scripting and limit untrusted users' ability to execute scripts.",
  "vendor": "rust",
  "product": "surrealdb",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 4.0.0"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "4.0.0"
      ],
      "package_name": "surrealdb",
      "purl": "pkg:cargo/surrealdb"
    }
  ],
  "cwes": null,
  "cvss_score": 7,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 30.6183209,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T15:51:03+00:00",
      "days": -0.6437319270370371,
      "is_lower_bound": true,
      "measured_at": "2026-11-04T07:18:01.472908+00:00",
      "url": "https://github.com/surrealdb/surrealdb/security/advisories/GHSA-5w6j-qm42-4rc2"
    }
  }
}

published 2026-11-04 04:57Z
last change 2026-11-04 06:57Z

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.