# CVE-2026-33682: Streamlit on Windows has Unauthenticated SSRF Vulnerability (NTLM Credential Exposure)

> Unauthenticated SSRF in Streamlit on Windows allows attackers to trigger SMB connections, potentially exposing NTLM credentials for relay attacks.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-7p48-42j8-8846, PYSEC-2026-2285

## What is CVE-2026-33682?

CVE-2026-33682 is a medium-severity server-side request forgery vulnerability in streamlit, published on 26 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Streamlit is a data oriented application development framework for python. Streamlit Open Source versions prior to 1.54.0 running on Windows hosts have an unauthenticated Server-Side Request Forgery (SSRF) vulnerability. The vulnerability arises from improper validation of attacker-supplied filesystem paths. In certain code paths, including within the `ComponentRequestHandler`, filesystem paths are resolved using `os.path.realpath()` or `Path.resolve()` before sufficient validation occurs. On Windows systems, supplying a malicious UNC path (e.g., `\\attacker-controlled-host\share`) can cause the Streamlit server to initiate outbound SMB connections over port 445. When Windows attempts to authenticate to the remote SMB server, NTLMv2 challenge-response credentials of the Windows user running the Streamlit process may be transmitted. This behavior may allow an attacker to perform NTLM relay attacks against other internal services and/or identify internally reachable SMB hosts via timing analysis. The vulnerability has been fixed in Streamlit Open Source version 1.54.0.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-33682?

3 open source packages ship an affected version, including streamlit and Streamlit. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `streamlit` | PyPI | All versions | 1.54.0 |
| `streamlit` | PyPI | All versions | 1.54.0 |
| `Streamlit` | PyPI | All versions | 1.54.0 |

Products: Snowflake Streamlit.

## How do I fix CVE-2026-33682?

Upgrade streamlit to 1.54.0 or later.

## Is CVE-2026-33682 being exploited?

There is no known exploitation of CVE-2026-33682 in the wild and no public exploit code.

## Other vulnerabilities in streamlit

- [CVE-2022-35918](https://insights.sbomify.com/CVE-2022-35918/): Streamlit directory traversal vulnerability (medium 6.5)
- [CVE-2024-42474](https://insights.sbomify.com/CVE-2024-42474/): Streamlit Path Traversal Security Vulnerability on Windows (medium 5.9)
- [CVE-2023-27494](https://insights.sbomify.com/CVE-2023-27494/): Streamlit Cross-site Scripting vulnerability (medium 5.9)
- [CVE-2026-10804](https://insights.sbomify.com/CVE-2026-10804/): Streamlit Palette hashing.py weak hash (low 2.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33682 and fix it if it is affected.

What it is: CVE-2026-33682 is a medium-severity server-side request forgery vulnerability in streamlit, published on 26 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33682 in the wild and no public exploit code.

Affected packages and fixed versions:
- streamlit (PyPI): affected all versions; fixed in 1.54.0
- streamlit (PyPI): affected all versions; fixed in 1.54.0
- Streamlit (PyPI): affected all versions; fixed in 1.54.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33682/ (Markdown: https://insights.sbomify.com/CVE-2026-33682/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33682
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33682
- OSV: https://osv.dev/vulnerability/CVE-2026-33682

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33682/
Summaries are generated and may contain mistakes; the official description above is the record.