Aklivity Zilla CVE-2026-120324

Requires a Zilla instance (up to 1.3.4 / 2.4.7 / 2.5.0-rc2) that is configured with and exposes the http-filesystem binding, since the flaw lives in FileSystemServerFactory's handling of the params argument through Path.resolve; a deployment not using this binding is not exposed. Within that configuration the CVSS vector indicates no authentication, no user interaction, and low complexity (AV:N/AC:L/AT:N/PR:N/UI:N), so no special attacker prerequisites apply beyond network reachability of the binding. The principal limiting factor is therefore deployment-specific: the binding must be enabled and network-accessible, and the disclosed data is bounded by what the Zilla process can read on the host filesystem. The exact crafted-input syntax that triggers the traversal is not detailed in the available sources.

This is a moderate-priority issue rather than an emergency. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes remote, low-complexity, unauthenticated reachability with no attack requirement, which is a genuinely low bar - but the vendor-assigned impacts are all Low (VC:L/VI:L/VA:L and subsequent SC:L/SI:L/SA:L), yielding a 6.9 Medium rather than a critical disclosure, and the E:P maturity flag marks the exploit as Proof-of-Concept only. The vuln.today decision label is 'this_month', consistent with a real but non-urgent fix. Key signals are missing or soft: there is no CISA KEV listing (no confirmed active exploitation) and no EPSS score was supplied, so exploitation likelihood cannot be quantified from this data. A PoC reference exists on GitHub (0xGenesi) but the input marks it 'reference only, not verified as working exploit code', so it must not be treated as a confirmed weaponized exploit. The main cross-source tension is impact magnitude: a path-traversal file-read primitive in a file-serving HTTP binding often warrants a higher confidentiality rating than the Low the vendor assigned, so the independent assessment below rates confidentiality higher while leaving integrity/availability untouched - the sources do not establish any write or disruption capability.

An attacker who can reach a Zilla deployment exposing the http-filesystem binding sends a crafted HTTP request whose params value contains directory-traversal sequences. Because FileSystemServerFactory passes the argument into Path.resolve without adequate containment, the resolved path escapes the intended served directory, letting the remote, unauthenticated attacker read files outside it. A public PoC reference exists; it is not verified as working exploit code.