-
Notifications
You must be signed in to change notification settings - Fork 8.2k
docs: CVE advisory and patch release 1.5.1 #9584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the WalkthroughDocumentation updates: README warning reworked into a list with added CVE and security links; SECURITY.md expanded with explicit CVE disclosures, version-specific authentication behavior notes, and guidance on AUTO_LOGIN and superuser CLI implications. No code or public API changes. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
Status, Documentation and Community
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
SECURITY.md (1)
61-70: Contradictory statements about API key requirement in 1.5; clarify default vs enforced behavior.Line 65 states 1.5 requires an API key, while lines 66–68 say auth is skipped by default in 1.5 if both env vars are set (and one is default-true). This is confusing and can mislead operators.
-In Langflow version 1.5, a Langflow API key is required to authenticate requests. -Setting `LANGFLOW_SKIP_AUTH_AUTO_LOGIN=true` and `LANGFLOW_AUTO_LOGIN=true` skips authentication for API requests. However, the `LANGFLOW_SKIP_AUTH_AUTO_LOGIN` option will be removed in v1.6. - -`LANGFLOW_SKIP_AUTH_AUTO_LOGIN=true` is the default behavior, so users do not need to change existing workflows in 1.5. To update your workflows to require authentication, set `LANGFLOW_SKIP_AUTH_AUTO_LOGIN=false`. +In Langflow 1.5, API key authentication is supported. +However, when `LANGFLOW_AUTO_LOGIN=true` and `LANGFLOW_SKIP_AUTH_AUTO_LOGIN=true` (the default in 1.5), API requests bypass authentication. +To require authentication in 1.5, set `LANGFLOW_SKIP_AUTH_AUTO_LOGIN=false`. +The `LANGFLOW_SKIP_AUTH_AUTO_LOGIN` option will be removed in v1.6; update workflows accordingly.
🧹 Nitpick comments (3)
README.md (1)
17-20: Align version notation and punctuation for consistency.Use explicit patch versions and end bullets with periods.
-> - Users must update to Langflow >= 1.3 to protect against [CVE-2025-3248](https://nvd.nist.gov/vuln/detail/CVE-2025-3248) +> - Users must update to Langflow >= 1.3.0 to protect against [CVE-2025-3248](https://nvd.nist.gov/vuln/detail/CVE-2025-3248). -> - Users must update to Langflow >= 1.5.1 to protect against [CVE-2025-57760](https://github.com/langflow-ai/langflow/security/advisories/GHSA-4gv9-mp8m-592r) +> - Users must update to Langflow >= 1.5.1 to protect against [CVE-2025-57760](https://github.com/langflow-ai/langflow/security/advisories/GHSA-4gv9-mp8m-592r).SECURITY.md (2)
51-53: Minor formatting: terminate sentences and standardize version string.Adds periods; keeps “>= 1.3.0” consistent with README suggestion.
-**CVE**: [CVE-2025-3248](https://nvd.nist.gov/vuln/detail/CVE-2025-3248) -**Fixed in**: Langflow >= 1.3.0 +**CVE**: [CVE-2025-3248](https://nvd.nist.gov/vuln/detail/CVE-2025-3248). +**Fixed in**: Langflow >= 1.3.0.
54-60: Tighten wording and finish sentences.Clarify impact sentence and add period after “Fixed in”.
-### Privilege Escalation via CLI Superuser Creation (Fixed in 1.5.1) +### Privilege Escalation via CLI Superuser Creation (Fixed in 1.5.1) -A privilege escalation vulnerability exists in Langflow containers where an authenticated user with RCE access can invoke the internal CLI command `langflow superuser` to create a new administrative user. This results in full superuser access, even if the user initially registered through the UI as a regular (non-admin) account. +A privilege escalation vulnerability exists in Langflow containers where an authenticated user with RCE can invoke the internal CLI command `langflow superuser` to create a new administrative user. This results in full superuser access, even if the user initially registered through the UI as a non-admin. -**CVE**: [CVE-2025-57760](https://github.com/langflow-ai/langflow/security/advisories/GHSA-4gv9-mp8m-592r) -**Fixed in**: Langflow >= 1.5.1 +**CVE**: [CVE-2025-57760](https://github.com/langflow-ai/langflow/security/advisories/GHSA-4gv9-mp8m-592r). +**Fixed in**: Langflow >= 1.5.1.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (2)
README.md(1 hunks)SECURITY.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
SECURITY.md
[grammar] ~51-~51: There might be a mistake here.
Context: .../nvd.nist.gov/vuln/detail/CVE-2025-3248) Fixed in: Langflow >= 1.3.0 ### Pri...
(QB_NEW_EN)
[grammar] ~58-~58: There might be a mistake here.
Context: ...security/advisories/GHSA-4gv9-mp8m-592r) Fixed in: Langflow >= 1.5.1 ### No ...
(QB_NEW_EN)
🔇 Additional comments (1)
README.md (1)
16-20: Good addition: clear, actionable security guidance surfaced prominently.Elevating both CVEs into the CAUTION block with direct links is the right call.
…com/langflow-ai/langflow into docs-cve-advisory-and-patch-release
|
* add-info-for-CVE-2025-57760 * cleanup



Summary by CodeRabbit