CVE-2026-77815
HIGHDescription
to_abs_path in scripts/iib/tool.py normalised the requested path with os.path.normpath, which collapses dot segments but does not resolve symbolic links. A symlink placed inside a scanned directory therefore satisfies the containment comparison performed by is_path_trusted in scripts/iib/api.py while pointing outside that directory, and FileResponse follows the link when serving the response, so a link created in an image directory and targeting a file such as /etc/passwd discloses that file. Whether the check applies depends on get_enable_access_control in scripts/iib/tool.py: it returns true when IIB_ACCESS_CONTROL is set to enable, false when set to disable, and otherwise true when the host Stable Diffusion WebUI was started with share, ngrok, listen or server_name, falling back to false. Confinement is therefore active in the network-exposed WebUI deployments that rely on it, while a standalone run with no such option serves every readable file regardless of this flaw. The fix resolves the path with os.path.realpath.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 34% of all known CVEs.
References
Related Vulnerabilities
Other CWE-59 (Link Following) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-30333 | High | 7.5 | 99% | KEV + Ransom | Fix |
| CVE-2021-21300 | High | 8.0 | 89% | - | Fix |
| CVE-2021-32610 | High | 7.1 | 73% | - | Fix |
| CVE-2020-36193 | High | 7.5 | 71% | KEV | Fix |
| CVE-2023-40028 | Medium | 4.9 | 69% | - | Fix |
| CVE-2023-36874 | High | 7.8 | 43% | KEV | Fix |
Common questions
How do I fix CVE-2026-77815?
No published fix for CVE-2026-77815 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-77815 being actively exploited?
Not that we know of. CVE-2026-77815 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.41% is the estimated probability that it will be exploited in the next 30 days. That is higher than 34% of all scored CVEs.
How severe is CVE-2026-77815?
CVE-2026-77815 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-77815
Markdown
[](https://tridentstack.com/cve/CVE-2026-77815)HTML
<a href="https://tridentstack.com/cve/CVE-2026-77815"><img src="https://tridentstack.com/cve/badge/CVE-2026-77815.svg" alt="CVE-2026-77815"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-26.