Authenticated file disclosure via avatar path traversal
Published Mar 10, 2026 · Updated Mar 10, 2026
Path traversal in Flare before 1.7.3 allows remote authenticated users to read application-container files through the avatar API. The /api/avatars/[filename] route passes a decoded filename to path.join(), and getFileStream() opens the resolved local path without calling the available path validator. A valid session and local-storage deployment are required; default open registration lets remote attackers obtain an account and read files available to the Next.js process.
Summary
What happened
Path traversal in Flare before 1.7.3 allows remote authenticated users to read application-container files through the avatar API. The /api/avatars/[filename] route passes a decoded filename to path.join(), and getFileStream() opens the resolved local path without calling the available path validator. A valid session and local-storage deployment are required; default open registration lets remote attackers obtain an account and read files available to the Next.js process.
The record
- CVE
- CVE-2026-30942
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- FlintSH
- Product
- Flare
- Classifications
- CWE-22, T1005, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 10, 2026CVE publishedPublication date reported by the CVE source.
- Mar 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.7.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory path-traversal proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo