CVE-2026-102488

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

GHSA-w6j2-5q9c-xv6x ↗EUVD-2026-94659 ↗

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.
Octopus Deploy Octopus Server >= 2019.5.0, < 2026.2.12438; >= 2026.3.0, < 2026.3.15816
fixed in 2026.2.12438, 2026.3.15816
CWE-863 Incorrect Authorization
ETK-2026-924, permanent identifier
10d 17h 26msince last run
53mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+76h32m
0
+2h
+4h
+6h
+8h
+10h

description

Affected Octopus Server versions can incorrectly combine multiple scoped permission assignments. A highly privileged user with such assignments may gain deployment permissions that were not explicitly granted.

mitigation

Upgrade Octopus Server to 2026.2.12438 or 2026.3.15816, as appropriate for the release line in use.

fixed in 2026.2.12438, 2026.3.15816

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, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.21%10th percentile
agent run time
53m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-08 01:38Z
Δ 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-08 01:38Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-924",
  "cve_id": "CVE-2026-102488",
  "display_id": "CVE-2026-102488",
  "ghsa_id": "GHSA-w6j2-5q9c-xv6x",
  "euvd_id": "EUVD-2026-94659",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in Octopus Server permission evaluation",
  "summary": "Affected Octopus Server versions can incorrectly combine multiple scoped permission assignments. A highly privileged user with such assignments may gain deployment permissions that were not explicitly granted.",
  "mitigation": "Upgrade Octopus Server to 2026.2.12438 or 2026.3.15816, as appropriate for the release line in use.",
  "vendor": "Octopus Deploy",
  "product": "Octopus Server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2019.5.0, < 2026.2.12438",
        ">= 2026.3.0, < 2026.3.15816"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2026.2.12438",
        "2026.3.15816"
      ],
      "package_name": "Octopus Server",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0021,
  "epss_percentile": 0.1026,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 53.06116763333333,
  "t0_at": "2026-10-08T01:38:57.175000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-08T01:38:57.175000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T01:38:57.175000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-102488"
    }
  }
}

published 2026-10-08 02:08Z
last change 2026-10-21 21:36Z

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.