CVE-2026-108758

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

GHSA-q8ph-7hq3-m5wq ↗EUVD-2026-96923 ↗

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.
alextselegidis easyappointments <= 1.6.0
ETK-2026-1257Zero's internal tracking ID, independent of the CVE number., permanent identifier
9d 10h 18msince last run
29mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+6h10m
0
+2h
+4h
+8h
+10h
+12h

description

Easy!Appointments versions through 1.6.0 are affected by an authorization check failure in booking registration. An unauthenticated remote party may alter appointment records and gain control over their subsequent management when the registration endpoint is reachable.

mitigation

Restrict unauthenticated access to the booking registration endpoint, such as by placing it behind an access-control layer until a vendor update is available. Monitor appointment changes for unauthorized modifications and management-token changes.

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.26%16th percentile
agent run time
29m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-11 12:19Z
Δ 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-11 12:19Z
    ghsa: trigger signal, started the run
  2. 2026-10-11 12:19Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1257",
  "cve_id": "CVE-2026-108758",
  "display_id": "CVE-2026-108758",
  "ghsa_id": "GHSA-q8ph-7hq3-m5wq",
  "euvd_id": "EUVD-2026-96923",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in Easy!Appointments booking registration",
  "summary": "Easy!Appointments versions through 1.6.0 are affected by an authorization check failure in booking registration. An unauthenticated remote party may alter appointment records and gain control over their subsequent management when the registration endpoint is reachable.",
  "mitigation": "Restrict unauthenticated access to the booking registration endpoint, such as by placing it behind an access-control layer until a vendor update is available. Monitor appointment changes for unauthorized modifications and management-token changes.",
  "vendor": "alextselegidis",
  "product": "easyappointments",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.6.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "easyappointments",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N",
  "epss_score": 0.0026,
  "epss_percentile": 0.1692,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 28.67926285,
  "t0_at": "2026-10-11T12:19:55.847000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-11T12:19:55.847000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-11T12:19:55.847000+00:00",
      "url": "https://github.com/advisories/GHSA-q8ph-7hq3-m5wq"
    }
  }
}

published 2026-10-11 18:01Z
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.