Aklivity Zilla http-filesystem Binding FileSystemServerFactory Path.resolve path traversal
Zilla 2.4.7 and earlier with the http-filesystem binding, where a route parameter is mapped into with.path or with.directory. The checked facts name no fixed release.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 29/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Aklivity Zilla's http-filesystem binding, which serves files over HTTP, is affected by this vulnerability. A remote attacker could manipulate request parameters to access files outside the intended directory on the server.
Read the original description
A weakness has been identified in Aklivity Zilla up to 1.3.4/2.4.7/2.5.0-rc2. The affected element is the function Path.resolve of the file FileSystemServerFactory of the component http-filesystem Binding. This manipulation of the argument params causes path traversal. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks. Upgrading to version 2.5.0-rc3 is sufficient to fix this issue. Patch name: 46a8b15cbea157f7ae8b7cb865809a02fd6b1988. You should upgrade the affected component.
What to do
Check every install: default setups are affected.
Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- 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
Evidence 9
- Advisory
- Advisory
- Advisory
- Advisory
- Patch
Show all 9 sourcesShow fewer sources
- Patch
- Patch
- Exploit
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120324
What does this mean?
A path traversal flaw in the http-filesystem binding's path handling lets a remote, unauthenticated attacker reach files outside the intended directory. The reported impact is reading arbitrary files readable by the Zilla process, and creating, overwriting, or deleting files.Source: github.com
Am I affected, and how do I check?
The checked facts list Zilla versions up to 2.4.7, verified on 2.4.7. The relevant setup is a route parameter substituted into the http-filesystem binding's with.path or with.directory; check the Zilla version and whether the configuration does this.Source: github.com
What should I do about it?
The checked facts do not name a fixed Zilla release, so no upgrade target can be given from them. Check the vendor's advisory for a fixed version.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data