chore(deps): update dependency streamlit to v1.54.0 [security]#206
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
chore(deps): update dependency streamlit to v1.54.0 [security]#206renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.53.1→1.54.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
CVE-2026-33682
Streamlit Open Source Security Advisory
1. Impacted Products
Streamlit Open Source versions prior to 1.54.0 running on Windows hosts.
2. Introduction
Snowflake Streamlit Open Source addressed a security vulnerability affecting Windows deployments related to improper handling and validation of filesystem paths within component request handling. The vulnerability was reported through the responsible disclosure program and has been remediated in Streamlit Open Source version 1.54.0. This issue affects only Streamlit deployments running on Windows operating systems.
3. Server-Side Request Forgery (SSRF) and NTLM Credential Exposure
3.1 Description
Streamlit was informed by a security researcher of 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 usingos.path.realpath()orPath.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:
Captured NTLMv2 challenge-response hashes could be subjected to offline brute-force attacks in an attempt to recover the associated plaintext account password. While NTLMv2 incorporates a server challenge (nonce) that mitigates the use of precomputed rainbow tables, it does not prevent targeted offline password cracking against weak credentials.
Additionally, Microsoft has publicly discouraged the continued use of NTLM in favor of Kerberos and is actively progressing toward disabling NTLM by default in future Windows releases. Organizations that enforce NTLM restrictions, disable outbound NTLM authentication, require SMB signing, or block NTLM authentication to remote servers can reduce or eliminate the risk associated with credential relay or hash exposure scenarios.
As NTLM is considered legacy and increasingly deprecated (though not fully sunset), environments that have already implemented Microsoft-recommended NTLM hardening controls are less likely to be materially impacted. The overall risk therefore depends on the organization's authentication configuration and network security posture.
3.2 Scenarios and Attack Vectors
Streamlit applications running on Windows were vulnerable if component endpoints were exposed to untrusted networks. By appending an attacker-controlled SMB hostname to the URI path and issuing a GET request, the Streamlit server could be coerced into initiating an outbound SMB authentication attempt.
This could result in the leakage of NTLMv2 credential hashes for the Windows account running the Streamlit process.
3.3 Resolution
4. Contact
Please contact security@snowflake.com for any questions regarding this advisory.
If a security vulnerability is discovered in a Streamlit product or website, it should be reported through the responsible disclosure program. For more information, see the Vulnerability Disclosure Policy.
Unauthenticated SSRF Vulnerability in Streamlit on Windows (NTLM Credential Exposure)
CVE-2026-33682 / GHSA-7p48-42j8-8846
More information
Details
Streamlit Open Source Security Advisory
1. Impacted Products
Streamlit Open Source versions prior to 1.54.0 running on Windows hosts.
2. Introduction
Snowflake Streamlit Open Source addressed a security vulnerability affecting Windows deployments related to improper handling and validation of filesystem paths within component request handling. The vulnerability was reported through the responsible disclosure program and has been remediated in Streamlit Open Source version 1.54.0. This issue affects only Streamlit deployments running on Windows operating systems.
3. Server-Side Request Forgery (SSRF) and NTLM Credential Exposure
3.1 Description
Streamlit was informed by a security researcher of 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 usingos.path.realpath()orPath.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:
Captured NTLMv2 challenge-response hashes could be subjected to offline brute-force attacks in an attempt to recover the associated plaintext account password. While NTLMv2 incorporates a server challenge (nonce) that mitigates the use of precomputed rainbow tables, it does not prevent targeted offline password cracking against weak credentials.
Additionally, Microsoft has publicly discouraged the continued use of NTLM in favor of Kerberos and is actively progressing toward disabling NTLM by default in future Windows releases. Organizations that enforce NTLM restrictions, disable outbound NTLM authentication, require SMB signing, or block NTLM authentication to remote servers can reduce or eliminate the risk associated with credential relay or hash exposure scenarios.
As NTLM is considered legacy and increasingly deprecated (though not fully sunset), environments that have already implemented Microsoft-recommended NTLM hardening controls are less likely to be materially impacted. The overall risk therefore depends on the organization's authentication configuration and network security posture.
3.2 Scenarios and Attack Vectors
Streamlit applications running on Windows were vulnerable if component endpoints were exposed to untrusted networks. By appending an attacker-controlled SMB hostname to the URI path and issuing a GET request, the Streamlit server could be coerced into initiating an outbound SMB authentication attempt.
This could result in the leakage of NTLMv2 credential hashes for the Windows account running the Streamlit process.
3.3 Resolution
4. Contact
Please contact security@snowflake.com for any questions regarding this advisory.
If a security vulnerability is discovered in a Streamlit product or website, it should be reported through the responsible disclosure program. For more information, see the Vulnerability Disclosure Policy.
Severity
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
streamlit/streamlit (streamlit)
v1.54.0Compare Source
What's Changed
Breaking Changes 🛠
st.experimental_usercommand by @lukasmasuch in #13626add_rowsdeprecation warning to show in browser by @lukasmasuch in #13628New Features 🎉
keyas main identity forst.dataframewith selections by @lukasmasuch in #13558keyas main identity for vega charts with selections by @lukasmasuch in #13559chartDivergingColorstheming config option by @mayagbarnes in #13581st.date_inputby @lukasmasuch in #13549min_valueandmax_valueinst.datetime_inputwhenkeyis provided by @lukasmasuch in #13620st.radiooptions whenkeyis provided by @lukasmasuch in #13611config.tomlis created by @lukasmasuch in #13625MultiselectColumnandListColumnby @lukasmasuch in #13663st.select_slideroptions whenkeyis provided by @lukasmasuch in #13696st.pydeck_chartparameters whenkeyis provided by @lukasmasuch in #13703Bug Fixes 🐛
st.chat_inputby @sfc-gh-nbellante in #13589KeyErrorwhen sorting melted bar chart data by @lukasmasuch in #13695Other Changes
New Contributors
Full Changelog: streamlit/streamlit@1.53.1...1.54.0
Configuration
📅 Schedule: Branch creation - "" in timezone US/Central, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.