CVE-2026-103255

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

GHSA-34g6-xwv9-46f3 ↗EUVD-2026-90649 ↗

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.
n8n-io n8n < 1.123.80; >= 2.0.0, < 2.39.6; >= 2.40.0, < 2.40.1
fixed in 1.123.80, 2.39.6, 2.40.1
ETK-2026-242, permanent identifier
19d 21h 06msince last run
33mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h54m
0
+2h
+6h
+8h
+10h
+12h

description

Affected n8n releases allow the Supabase node to construct request locations from an insufficiently restricted table identifier. An attacker can access or alter Supabase resources outside the intended table scope when a workflow supplies that identifier from untrusted input; exposed Auth or Storage access can use the configured administrative credential and bypass row-level controls.

mitigation

Upgrade n8n to the applicable fixed release: 1.123.80, 2.39.6, or 2.40.1. Until upgraded, prevent untrusted workflow input from selecting the Supabase table identifier and restrict access to affected workflows.

fixed in 1.123.80, 2.39.6, 2.40.1

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.
0.30%20th percentile
agent run time
33m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 10:42Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-01 10:42Z
    ghsa: trigger signal, started the run
  2. 2026-10-01 10:42Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-242",
  "cve_id": "CVE-2026-103255",
  "display_id": "CVE-2026-103255",
  "ghsa_id": "GHSA-34g6-xwv9-46f3",
  "euvd_id": "EUVD-2026-90649",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in n8n Supabase node",
  "summary": "Affected n8n releases allow the Supabase node to construct request locations from an insufficiently restricted table identifier. An attacker can access or alter Supabase resources outside the intended table scope when a workflow supplies that identifier from untrusted input; exposed Auth or Storage access can use the configured administrative credential and bypass row-level controls.",
  "mitigation": "Upgrade n8n to the applicable fixed release: 1.123.80, 2.39.6, or 2.40.1. Until upgraded, prevent untrusted workflow input from selecting the Supabase table identifier and restrict access to affected workflows.",
  "vendor": "n8n-io",
  "product": "n8n",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.123.80",
        ">= 2.0.0, < 2.39.6",
        ">= 2.40.0, < 2.40.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.123.80",
        "2.39.6",
        "2.40.1"
      ],
      "package_name": "n8n",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": 0.003,
  "epss_percentile": 0.2093,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 33.36353976666667,
  "t0_at": "2026-10-01T10:42:00.052000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T10:42:00.052000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T10:42:00.052000+00:00",
      "url": "https://github.com/advisories/GHSA-34g6-xwv9-46f3"
    }
  }
}

published 2026-10-01 14:03Z
last change 2026-10-21 04:45Z

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.