CVE-2026-30942
Path Traversal in Flare Avatars API Allows Arbitrary File Read
Publication date: 2026-03-10
Last updated on: 2026-03-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| flintsh | flare | to 1.7.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Flare, a Next.js-based file sharing platform. Before version 1.7.3, an authenticated path traversal flaw in the /api/avatars/[filename] endpoint allows any logged-in user to read arbitrary files within the application container.
The issue arises because the filename parameter is passed to path.join() without sanitization, and getFileStream() does not validate the path. This allows attackers to use encoded sequences like %2F to traverse directories (../) and access files outside the intended uploads/avatars/ directory.
Although authentication is required, instances with open registration (the default setting) allow any attacker to self-register and exploit this vulnerability immediately.
This vulnerability was fixed in version 1.7.3 of Flare.
How can this vulnerability impact me? :
This vulnerability can allow an attacker who is able to log in (or self-register if open registration is enabled) to read arbitrary files within the application container.
Such unauthorized file access could lead to exposure of sensitive information stored on the server, including configuration files, user data, or other confidential files accessible to the Next.js process.
This could result in data breaches, loss of confidentiality, and potentially further exploitation depending on the contents of the accessed files.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade Flare to version 1.7.3 or later, where the path traversal issue in /api/avatars/[filename] is fixed.
If upgrading immediately is not possible, consider disabling open registration to prevent attackers from self-registering and exploiting the vulnerability.