CVE-2026-103272

validatedZero produced an exploit or a check.

GHSA-ffmj-3ppp-cj4r ↗EUVD-2026-90665 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
TryGhost Ghost >=v2.10.0; <v6.63.0
fixed in v6.63.0
CWE-203 Observable Discrepancy
ETK-2026-233, permanent identifier
pkg:npm/ghost
+1h12mTTV
39mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+72magent stopped
0
+15min
+30min
+45min
+60min

description

Ghost versions 2.10.0 through 6.62.x expose a staff-enumeration issue in the content API. An unauthenticated attacker can infer staff accounts and obtain sensitive user information from differences in API metadata responses.

mitigation

Upgrade Ghost to version 6.63.0 or later.

fixed in v6.63.0

check
available
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.
deterministic
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.37%28th percentile
agent run time
39m
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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-233",
  "cve_id": "CVE-2026-103272",
  "display_id": "CVE-2026-103272",
  "ghsa_id": "GHSA-ffmj-3ppp-cj4r",
  "euvd_id": "EUVD-2026-90665",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated staff enumeration in Ghost content API",
  "summary": "Ghost versions 2.10.0 through 6.62.x expose a staff-enumeration issue in the content API. An unauthenticated attacker can infer staff accounts and obtain sensitive user information from differences in API metadata responses.",
  "mitigation": "Upgrade Ghost to version 6.63.0 or later.",
  "vendor": "TryGhost",
  "product": "Ghost",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">=v2.10.0",
        "<v6.63.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "v6.63.0"
      ],
      "package_name": "ghost",
      "purl": "pkg:npm/ghost"
    }
  ],
  "cwes": [
    203
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0037,
  "epss_percentile": 0.289,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 38.7928201,
  "t0_at": "2026-10-01T10:42:11.111000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-01T11:53:52.747918+00:00",
      "days": 0.04978746432870371,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T10:42:11.111000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-01T10:42:11.111000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T10:42:11.111000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103272"
    }
  }
}

published 2026-10-01 11:15Z
last change 2026-10-21 08:40Z

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.