Loading story…
Infinite Image Browsing fixed two related path validation flaws that could let remote attackers read files outside intended directories in deployments exposed through Stable Diffusion WebUI. The issues, tracked as CVE-2026-77814 and CVE-2026-77815, affect versions through 1.8.0 and stem from the is_path_trusted() logic in scripts/iib/api.py and path resolution in scripts/iib/tool.py. One bug used a naive startswith(parent_path) check, allowing prefix-collision bypasses such as trusted /data/images matching /data/images_private; the other relied on os.path.normpath(), which failed to resolve symlinks and enabled escapes from scanned directories to disclose readable files such as /etc/passwd.
The project merged a fix in pull request #969 and commit 4057a624c7a23a36f0b4dc6a545b40767d602450, replacing os.path.normpath() with os.path.realpath() and tightening validation to require the trusted parent path plus a trailing separator. The patch also ensures resolved paths are used for file serving, addressing CWE-22 and CWE-59. The original report noted that some standalone configurations had enable_access_control = False by default, while network-exposed WebUI modes such as share, ngrok, listen, or server_name could automatically enable access control and therefore depend on the flawed confinement checks.
See affected versions and whether adversaries are exploiting it.
4 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-77815 was published for a CWE-59 arbitrary file disclosure flaw in Infinite Image Browsing affecting versions up to and including 1.8.0. The CVE describes how os.path.normpath() in to_abs_path failed to resolve symlinks, enabling files outside scanned directories to be disclosed via symlink targets.
CVE-2026-77814 was published for a CWE-22 information disclosure flaw in Infinite Image Browsing affecting versions up to and including 1.8.0. The CVE describes how is_path_trusted() used path.startswith(parent_path) without a trailing separator, allowing unauthorized file access outside the intended directory boundary.
A pull request and merge commit updated Infinite Image Browsing to use os.path.realpath() and require startswith(parent_path + os.sep), addressing both symlink escape and prefix-matching bypasses. The patch modified scripts/iib/api.py and scripts/iib/tool.py and was merged into the main branch.
A GitHub issue documented two file access control bypasses in Infinite Image Browsing: a prefix-collision flaw in is_path_trusted() and a symlink escape caused by using os.path.normpath() without resolving links. The report also noted that the default standalone configuration disables access control, allowing unauthenticated reading of files.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
5 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvefeed.io
Open sourcegithub.com
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Banana Slides through version `0.4.0` is affected by a path traversal flaw in `backend/services/ai_service.py` that allows unauthenticated attackers to read arbitrary image-format files from unintended directories on the server. The bug, tracked as **CVE-2026-49136** and classified as **CWE-22**, stems from using `os.path.startswith()` without a trailing path separator to enforce confinement to the uploads directory. In the default Docker deployment, where `UPLOAD_FOLDER=/app/uploads`, an attacker could submit a crafted markdown image reference in a page description and access sibling paths such as `/app/uploads_secret` because they share the same string prefix. The vulnerable `generate_image()` flow resolves the attacker-controlled `/files/` path and passes it to `PIL Image.open()`, enabling arbitrary file reads before the AI API call runs. Public reporting showed the issue also affected `v0.3.0` at a different line number, and a proof-of-concept used a reference like: ```markdown  ``` The project fixed the issue in commit `e8bc490` after merging pull request `#430`, changing the validation to require the trusted upload path plus `os.sep` so the check enforces real directory containment rather than a simple prefix match; the advisory rates the bug `CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`.
Jun 29, 2026
Two high-severity vulnerabilities were disclosed affecting exposed application and device management surfaces, including a flaw that can give attackers **root access** and another that enables **arbitrary file write** through path traversal. **CVE-2026-3587** describes an unauthenticated remote attack path in a hidden CLI function that lets an attacker escape a restricted prompt and gain root access to the underlying Linux operating system, potentially leading to full device compromise. The issue was mapped to `CWE-912` and assigned a `CVSS v3.1` score vector of `AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`, with CERT VDE publishing advisory `VDE-2026-020`. A separate vulnerability, **CVE-2026-5027**, affects Langflow's `POST /api/v2/files` endpoint, where improper sanitization of the multipart `filename` parameter allows path traversal using `../` sequences. An authenticated attacker can exploit the bug to write files to arbitrary filesystem locations, creating a route to compromise confidentiality, integrity, and availability. The flaw was classified as `CWE-22`, carries the `CVSS v3.1` vector `AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, and is referenced in Tenable advisory `TRA-2026-26`.
Jun 29, 2026
Public proof-of-concept code has been released for three high-severity vulnerabilities in the open-source **File Browser** self-hosted file management application, including **`CVE-2026-73611`**, **`CVE-2026-73612`**, and **`CVE-2026-73613`**. The issues affect File Browser/File Server releases up to **2.63.21** in the broader advisory, while individual fixes were introduced in later versions, including **2.63.22** for the recursive-operations access-control flaw and **2.63.19** as unaffected for the symlink-based deletion issue. `CVE-2026-73612` allows authenticated users to bypass path-based access controls during recursive copy, rename, and delete operations, letting them manipulate restricted descendant files and directories. `CVE-2026-73613` enables arbitrary out-of-scope file deletion through symlink manipulation in the TUS upload cache eviction process, potentially deleting files outside an attacker’s authorized scope with only create permissions. Separately, `CVE-2026-73611` affects JWT-based proxy authentication and can allow expired tokens to be accepted and renewed under certain non-default logout configurations, creating an authentication and security-restrictions bypass risk. Organizations using File Browser have been urged to apply the latest vendor patches immediately.
Aug 14, 2026