Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-77814 – Path Traversal / Arbitrary File Read – infinite-image-browsing ≤ 1.8.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-77814 is a path traversal vulnerability (CWE-22) in infinite-image-browsing, an image/video management application that also ships as a Stable Diffusion WebUI extension. The flaw lies in the is_path_trusted access-control function and allows an unauthenticated remote attacker to read files outside the directories the application is supposed to restrict access to. The issue carries a CVSS v4.0 base score of 8.7 (HIGH).

Technical details

  • Root cause: is_path_trusted in scripts/iib/api.py validates requested paths using path.startswith(parent_path) without appending a path separator, so a sibling directory whose name merely begins with an allowed path (e.g. /data/images_private) is incorrectly treated as trusted when /data/images is the allowed path.
  • The check also relies on os.path.normpath, which does not resolve symlinks, so a symlink placed inside an otherwise-allowed directory can be used to point outside it.
  • Attack vector: network, no authentication or user interaction required; the attacker sends a crafted request to the application’s file-serving endpoint (used by FileResponse).
  • Trigger conditions: the vulnerable code path is reachable when access control is enabled (IIB_ACCESS_CONTROL set to "enable") or when the application is exposed over the network (e.g. via share, ngrok, listen, or server_name deployment options). Note that in default standalone configuration, access control is disabled entirely, which independently exposes all files without authentication.
  • Impact: disclosure of restricted files on the host filesystem (confidentiality impact only; no impact on integrity or availability per the published vector).

Affected software

  • infinite-image-browsing (zanllp/infinite-image-browsing), including its Stable Diffusion WebUI extension form: versions 0 through 1.8.0 (inclusive).
  • Vulnerable files: scripts/iib/api.py, scripts/iib/tool.py.

Severity

  • CVSS v4.0: 8.7 (HIGH) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: upgrade to a version containing the fix committed in 4057a624c7a23a36f0b4dc6a545b40767d602450 (merged via pull request #969), which resolves the path-validation flaw for versions beyond 1.8.0.
  • If patching is not immediately possible: avoid exposing the application to untrusted networks (do not use share, ngrok, listen, or server_name options without additional protections); ensure access control is explicitly enabled rather than relying on defaults; place the application behind an authenticating reverse proxy and restrict network access to trusted hosts only.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge