CVE-2026-78530

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

GHSA-8h49-8rvq-9vm7 ↗EUVD-2026-96525 ↗

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.
Chimpstudio FoodBakery >= n/a, <= 4.6
ETK-2026-1206Zero's internal tracking ID, independent of the CVE number., permanent identifier
9d 00h 52msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+32h21m
0
+2h
+4h
+6h
+8h
+10h

description

FoodBakery versions through 4.6 are affected by an arbitrary file deletion issue. An attacker with subscriber-level access may be able to delete files; the available evidence does not describe additional preconditions.

mitigation

Restrict or disable subscriber access where it is not required, and maintain tested backups of application and uploaded files. Monitor the advisory source for a patched release, as no fixed version is recorded.

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-1206",
  "cve_id": "CVE-2026-78530",
  "display_id": "CVE-2026-78530",
  "ghsa_id": "GHSA-8h49-8rvq-9vm7",
  "euvd_id": "EUVD-2026-96525",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Arbitrary file deletion in chimpstudio FoodBakery",
  "summary": "FoodBakery versions through 4.6 are affected by an arbitrary file deletion issue. An attacker with subscriber-level access may be able to delete files; the available evidence does not describe additional preconditions.",
  "mitigation": "Restrict or disable subscriber access where it is not required, and maintain tested backups of application and uploaded files. Monitor the advisory source for a patched release, as no fixed version is recorded.",
  "vendor": "Chimpstudio",
  "product": "FoodBakery",
  "affected": [
    {
      "affected_notes": [
        ">= n/a, <= 4.6"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "FoodBakery",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H",
  "epss_score": 0.0041,
  "epss_percentile": 0.3337,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 35.527684533333336,
  "t0_at": "2026-10-10T19:36:15.786000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-10T19:36:15.786000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T19:36:15.786000+00:00",
      "url": "https://github.com/advisories/GHSA-8h49-8rvq-9vm7"
    }
  }
}

published 2026-10-11 02:59Z
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.