CVE-2026-120324

waiting for further signals

GHSA-34ff-jfmp-74pg ↗EUVD-2026-115007 ↗

no check availablenot proven exploitable

cve.orgpublic poc+0mkev

Aklivity Zilla 1.3.0; 1.3.1; 1.3.2; 1.3.3; 1.3.4; 2.4.0; 2.4.1; 2.4.2; 2.4.3; 2.4.4; 2.4.5; 2.4.6; 2.4.7; 2.5.0-rc1; 2.5.0-rc2

ETK-2026-3261, permanent identifier

cvss8.3cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

1h 27msince last run

46mAI analysis

timeline

0 = trigger signal

trigger signal (cve.org) +0hpublic poc+0hwaiting for further signals+2h28m

+4h

+6h

+8h

+10h

+12h

description

Affected Aklivity Zilla releases can mishandle file paths in the http-filesystem binding. A remote unauthenticated attacker may access files outside the intended path when that binding is enabled and reachable.

mitigation

Upgrade Aklivity Zilla to version 2.5.0-rc3. Until upgraded, disable or restrict network access to the http-filesystem binding where it is not required.

check

exploit

automation

–

auth required

EPSS

–

agent run time

46m

cve.org record, t = 0

2026-11-02 02:15Z

Δ to public poc

+0m

Δ to kev

–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

2026-11-02 02:15Z
ghsa: trigger signal, started the run
https://github.com/advisories/GHSA-34ff-jfmp-74pg
2026-11-02 02:15Z
cve.org record for CVE-2026-120324
cve_org · https://www.cve.org/CVERecord?id=CVE-2026-120324
2026-11-02 04:05Z
exploit reference (github.com)
github · https://github.com/0xGenesi/CVE/blob/main/Zilla_Http_Filesystem_Binding_Path_Traversal.md

this entry in the feed

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

{
  "etk_id": "ETK-2026-3261",
  "cve_id": "CVE-2026-120324",
  "display_id": "CVE-2026-120324",
  "ghsa_id": "GHSA-34ff-jfmp-74pg",
  "euvd_id": "EUVD-2026-115007",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in Aklivity Zilla http-filesystem binding",
  "summary": "Affected Aklivity Zilla releases can mishandle file paths in the http-filesystem binding. A remote unauthenticated attacker may access files outside the intended path when that binding is enabled and reachable.",
  "mitigation": "Upgrade Aklivity Zilla to version 2.5.0-rc3. Until upgraded, disable or restrict network access to the http-filesystem binding where it is not required.",
  "vendor": "Aklivity",
  "product": "Zilla",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.3.0",
        "1.3.1",
        "1.3.2",
        "1.3.3",
        "1.3.4",
        "2.4.0",
        "2.4.1",
        "2.4.2",
        "2.4.3",
        "2.4.4",
        "2.4.5",
        "2.4.6",
        "2.4.7",
        "2.5.0-rc1",
        "2.5.0-rc2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Zilla",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 45.56895686666667,
  "t0_at": "2026-11-02T02:15:22.746000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-11-02T02:15:22.746000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-02T02:15:22.746000+00:00",
      "url": "https://github.com/0xGenesi/CVE/blob/main/Zilla_Http_Filesystem_Binding_Path_Traversal.md"
    },
    "trigger_signal": {
      "at": "2026-11-02T02:15:22.746000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-02T02:15:22.746000+00:00",
      "url": "https://github.com/advisories/GHSA-34ff-jfmp-74pg"
    }
  }
}

published 2026-11-02 03:57Z
last change 2026-11-02 05: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.